Security
Security Overview
BrandOS is designed to support controlled publishing workflows. Security is treated as an operational requirement, especially where connected social accounts, publishing records, and performance data are involved.
1. Core controls
- Encryption in transit for web traffic and connected service communications where supported.
- Restricted access to operational environments and secrets on a least-privilege basis.
- Logging and audit records for important workflow, connection, and publish actions.
- Credential and token handling controls intended to reduce unnecessary exposure.
2. Access management
Access to administrative systems is limited to authorized operators. Privileged actions are expected to occur within documented workflows rather than anonymous or untracked paths.
3. Monitoring and resilience
We use system logging, configuration checks, backups, and service validation to reduce operational risk. We also review failures that affect content delivery, analytics collection, or account connectivity so problems can be corrected quickly.
4. Responsible disclosure
If you believe you found a vulnerability, misconfiguration, or exposed data path, email security@rebrandos.com. Please include a clear description, steps to reproduce, impact, and any relevant screenshots or request details. We ask for good-faith testing only and request that you do not access, alter, or retain data that is not yours.
5. Disclosure handling
We aim to acknowledge good-faith reports within two business days and to keep reporters informed as triage and remediation proceed. Response timing depends on severity, reproducibility, and the systems involved.
6. Limitations
No online service is completely risk-free. Third-party platforms and infrastructure providers also affect overall system security. We work to reduce exposure and address issues promptly, but cannot guarantee that incidents will never occur.