How can we help?

Support tickets should contain enough information to investigate a problem without exposing unnecessary confidential data. Business information belongs to the organization that provides it, and support requests should respect the organization's privacy and security requirements. What information is generally useful? 1. The affected feature. 2. A description of the problem. 3. Relevant timestamps. 4. Non-sensitive error messages. 5. Configuration details that do not reveal secrets. 6. Execution or request identifiers. 7. Reproduction steps. 8. Screenshots with sensitive information removed. 9. The operational impact. What information should I avoid sharing? Do not include: 1. Passwords. 2. API keys. 3. Access tokens. 4. Private cryptographic keys. 5. Authentication cookies. 6. Unnecessary personal information. 7. Complete customer databases. 8. Confidential documents unrelated to the issue. 9. Information belonging to another organization. What if a screenshot contains customer information? Remove or obscure information that is not necessary for investigation. Where possible, use a representative example or test record instead. What if a technical error contains an API credential? Do not copy the credential into the ticket. If the credential may have been exposed, follow the appropriate rotation or revocation procedure. Can I provide a log file? If the support interface supports attachments, provide only relevant diagnostic material after reviewing it for secrets and sensitive records. Do not assume that every raw application log is safe to share. What if Support needs additional technical information? Ask which specific information is required and why. Use the appropriate authorized process for sharing sensitive diagnostic material. Does Polyosync own the business information included in a support request? No. The principle remains that business data belongs to the business. Polyosync does not sell customer business data or use it to train its own AI models. Support-related processing remains subject to applicable privacy and contractual obligations. Recommended practice Share the minimum information necessary to explain the problem and remove secrets or unrelated confidential records before submission.