1. Accounts and authentication
Authentication is managed by our backend platform, with passwords stored only as hashes and optional Google sign-in. Session tokens refresh automatically and are revoked on sign-out.
The admin panel depends on a role stored in a dedicated table and verified on the server. No permission is decided by the browser.
2. Isolation of private data
The daily script collection is shared editorial content. Everything derived from your usage — favorites, edits, version history, notes, checklist, YouTube jobs and credits — lives in separate tables with row-level security bound to your identifier.
Write operations verify record ownership on the server before applying a change, so a guessed identifier cannot expose or modify another account's data.
3. Payments
The entire card flow happens on Stripe-hosted pages. We never receive, transmit or store card data, which keeps PCI scope out of our application.
Payment webhooks have verified signatures and idempotent processing per event id, so retries never duplicate access or credit grants.
4. Infrastructure and secrets
All traffic runs over HTTPS. API keys and privileged credentials live in server environment variables, never in browser code, and are read only inside server functions.
Automated database backups, error logs free of sensitive data, and an access-policy review with every schema change.
5. Vulnerability reporting
Found a flaw? Email security@roteiro.app with reproduction steps. We acknowledge within 3 business days and will not pursue legal action for good-faith research that avoids third-party data exfiltration and service degradation.
6. Incidents
If an incident poses relevant risk to data subjects, we notify those affected and the competent authority within statutory deadlines, describing what happened, which data was involved and the containment measures taken.