How can we help?

Phishing is an attempt to obtain sensitive information or persuade someone to perform an unsafe action by impersonating a trusted organization or person. Attackers may use emails, messages, websites, or other communication channels that appear to be associated with a legitimate service. What are common warning signs? 1. A message asks you to reveal your password. 2. Someone requests an API key or authentication token. 3. A message creates unusual urgency or pressure. 4. A link leads to an unfamiliar website. 5. A sender claims that your account will be deleted unless you act immediately. 6. A message asks you to install unfamiliar software. 7. A person claiming to represent Support requests unnecessary access to your device or accounts. 8. A message contains inconsistent sender details or unexpected attachments. How can I verify a message? Step 1: Avoid clicking suspicious links. Step 2: Open the official Polyosync website directly in your browser. Step 3: Check whether the message relates to an action you actually initiated. Step 4: Review the sender's address carefully. Step 5: Do not rely solely on a displayed sender name or logo. Step 6: Contact Polyosync Support through an established official channel if you are uncertain. Should I share my password with Support? No. You should not provide your password to someone claiming to be a support representative. What about API keys and access tokens? Treat them as sensitive credentials. Do not send them through ordinary support conversations. What if I clicked a suspicious link? Avoid entering additional information. If you entered your password, change it through the legitimate account management process. If you disclosed integration credentials, follow the relevant provider's rotation or revocation procedure. What if I downloaded a suspicious attachment? Do not open or execute it. Follow your organization's endpoint security procedures and seek assistance from the responsible IT or security team. What if the message appears to come from a real employee? Sender identities can be impersonated. Verify unusual requests through a separate trusted communication channel. Recommended practice Use official access points, verify unexpected requests independently, and never disclose sensitive credentials in response to unsolicited messages.