The fastest way to reach us
Email is the official support channel for Social Post AI. Send your message to [email protected] and use a clear subject line such as “Product support,” “Privacy request,” “Security report,” or “Editorial correction.” This helps us route your message and reduces the time needed to understand the request. We do not currently operate telephone, live-chat, or postal support channels.
Please never send passwords, private API keys, complete payment-card numbers, government identification numbers, or other highly sensitive information by email. Social Post AI will not ask for your password or authentication code. If a future support process needs sensitive verification, we will explain a safer method first.
Product support
For a broken page, unexpected generator result, accessibility issue, or device-specific problem, include the page URL, the action you took, what you expected, and what happened instead. Browser name, device type, and an optional screenshot can be useful. Avoid including private client information or unpublished campaign details in screenshots.
Generated content can sometimes be generic, inaccurate, or poorly matched to a brief. When reporting output quality, share a redacted version of the prompt and explain which part missed the mark. This feedback helps us improve instructions and evaluation without requiring you to disclose confidential business information.
Privacy and data requests
Use the subject “Privacy request” for questions about personal information, access, correction, or deletion. Tell us which email address or account identifier is connected with the request, if applicable. We may need reasonable verification before acting so that one person cannot access or delete another person’s information. We will explain what is needed and will not request more information than necessary.
Our Privacy Policy describes the categories of data the service may process, why they are used, and the choices available to users. If local law gives you additional rights, mention your country or region so we can assess the request under the appropriate rules.
Security reports
If you believe you found a vulnerability, use the subject “Security report” and provide reproducible steps, the affected URL, expected impact, and any safe proof of concept. Do not access other users’ information, disrupt the service, run destructive tests, or publish an unresolved vulnerability. We appreciate good-faith reports and will prioritize issues based on realistic risk.
We do not currently offer a paid bug bounty or promise a specific reward. We do commit to acknowledging credible reports, investigating them responsibly, and keeping reporters informed when doing so does not create additional risk. More details appear on our Security page.
Editorial and business inquiries
For a correction, identify the exact statement and provide a reliable source supporting the change. For media, partnership, or commercial inquiries, explain the organization, proposed relationship, expected audience, and any deadline. We do not accept payment for undisclosed editorial coverage, policy changes, or deceptive endorsements.
We aim to acknowledge ordinary messages within five business days and urgent, credible security or privacy concerns sooner. These are service goals rather than guaranteed response times. Repeated messages can slow review, so one complete email is usually the best approach.