Our approach
Security is an ongoing product and engineering responsibility, not a one-time feature. We design the service to reduce unnecessary access, protect credentials, and preserve your control over what gets published.
We continue to improve our controls as DispatchOS grows. This page describes our current approach and does not represent a certification or guarantee of absolute security.
Data protection
Least privilege
Access to systems and customer information is limited to what is needed for a person or service to perform its role.
Separation of environments
Development and production concerns are managed separately where appropriate to reduce unnecessary access and operational risk.
Secure integrations
Connected channel permissions are used to perform the actions you authorize, and you can disconnect channels you no longer use.
Operational awareness
We monitor service behavior and investigate reports, errors, and signals that may indicate abuse or a security issue.
Your website content, onboarding information, generated posts, publishing settings, and social authorization data are handled to provide the service described in our Privacy Policy.
Access controls
- Account access is protected by authentication controls provided by the application.
- Access to internal systems and customer data is limited according to role and operational need.
- We review access as responsibilities change and remove access that is no longer needed.
- We expect team members and service providers with access to protect confidential information.
Connected channels
When you connect a social channel, DispatchOS uses the permissions and authorization data needed to stage or publish the content you approve. The available permissions depend on the platform.
Review connected channels regularly and disconnect accounts you no longer use. If a token or account may be compromised, disconnect it and contact us at support@dispatchos.dev.
Third-party platforms have their own security practices, permissions, terms, and privacy policies. DispatchOS cannot control how a platform operates after content or an authorization request reaches it.
Infrastructure and operations
- We use managed infrastructure and service providers selected to support reliable operation of the product.
- We apply reasonable protections to production systems, application secrets, and operational data.
- We use logging and diagnostics to operate the service, troubleshoot failures, and investigate suspicious behavior.
- Backups and retention depend on the systems involved and are handled according to operational and legal requirements.
Specific infrastructure providers, control details, and retention periods may change as the service evolves.
Monitoring and response
We investigate credible reports of unauthorized access, account compromise, data exposure, abuse, and service vulnerabilities. When appropriate, we take steps to contain an issue, restore service, preserve evidence, and notify affected users in accordance with applicable law.
Security events can also involve third-party platforms or providers. We will work to understand the scope and communicate material information where required.
Your part
You help protect the service when you:
- Use a strong, unique password and protect your account credentials.
- Connect only websites and social accounts you control or are authorized to use.
- Review generated content before publishing.
- Do not paste passwords, private keys, access tokens, or unnecessary sensitive information into DispatchOS.
- Keep your device and browser reasonably up to date.
- Report suspicious activity promptly.
Report a concern
To report a suspected vulnerability or account compromise, email:
support@dispatchos.devPlease do not include passwords, API keys, access tokens, or other secrets in your report. Include enough detail for us to reproduce or investigate the issue safely.