Last updated: June 26, 2026
Overview
Security is central to SRS Cortex. We design the platform to separate public marketing pages from the authenticated workspace, protect credentials and OAuth tokens, and monitor production systems for anomalies.
This page summarizes our approach. For data handling details, see the Privacy Policy and Transparency Report.
We continuously improve controls as threats and product capabilities evolve.
Account security
Passwords are stored using industry-standard hashing. Sessions use secure, HTTP-only cookies with appropriate expiration and rotation.
Role-based access controls limit what team members can view, edit, or publish. Client review links provide scoped access without full workspace credentials.
We recommend strong unique passwords, limiting admin roles, and revoking access promptly when team members leave.
Data protection
Data in transit is encrypted using TLS. Data at rest is encrypted on our cloud infrastructure in the European Union.
OAuth tokens and API credentials for connected channels are stored encrypted and accessible only to authorized backend services — never exposed in client-side code or public pages.
Backups are encrypted and tested regularly. Access to production data is restricted to personnel with a legitimate operational need.
Infrastructure
Cortex runs on hardened cloud infrastructure with network segmentation, firewalls, and automated security patching.
We use monitoring, error tracking, and alerting to detect outages, abuse, and suspicious activity.
Service availability and planned maintenance are published on the Status page.
Integrations
Connecting social and messaging channels requires platform-specific authorization. Cortex requests only the permissions needed for scheduling, publishing, and analytics.
Third-party platforms may change APIs or revoke tokens. We notify users when re-authorization is required.
Payment processing is handled by certified payment providers; card data is not stored on Cortex servers.
Reporting vulnerabilities
If you discover a security vulnerability in SRS Cortex, please report it responsibly through the Report a problem page or email support form with details to reproduce the issue.
Do not publicly disclose vulnerabilities before we have had reasonable time to investigate and remediate.
We acknowledge valid reports promptly and work with researchers in good faith.
Security contact
For security questions or incident follow-up, contact support form.
For data breach notifications, we contact affected users as required by applicable law.