Security

We apply layered safeguards to protect your data. This page summarizes our practices without disclosing implementation details that could weaken those protections.

• OAuth tokens are stored encrypted at rest.
• Uploaded digital certificates (.p12) are stored encrypted.
• Application secrets are kept outside the source repository.
• Role-based access control (RBAC) governs what each user can do.
• Scheduled background jobs (cron) are protected by a dedicated secret.
• Tokens and secrets are never exposed to the frontend.
• Logs are sanitized to avoid leaking sensitive data.
• The PostgreSQL database is access-restricted.
• Users can revoke OAuth access at any time.

Reporting a vulnerability

If you believe you have found a security issue, contact info@rosettastudio.io. Please do not publicly disclose the issue before we have had a chance to respond.