Security is part of the workflow.
How TextToAudio protects accounts, payment information, scripts and generated audio.
Last updated: 1 October 2026
Account protection
Sign-in is handled through Google OAuth. We never receive or store your Google password. Sessions are protected with secure, HTTP-only cookies and signed authentication tokens.
Encryption
Traffic between your browser and TextToAudio is encrypted in transit with TLS. Sensitive service credentials are stored as encrypted runtime secrets and are not included in the client bundle.
Payments
Stripe processes payments. Card numbers, security codes and banking details are entered directly into Stripe-hosted checkout and never reach our application servers.
Data access
Access to production systems is limited to authorized personnel and protected by strong authentication. We log administrative actions and review access regularly.
Infrastructure
The application is served through Cloudflare and uses managed PostgreSQL storage. We apply security updates, monitor error rates and maintain backups for service recovery.
Incident response
If we discover a security incident affecting customer data, we investigate promptly, contain the issue and notify affected customers as required by applicable law.
Report a vulnerability
If you believe you have found a security issue, contact security@texttoaudio.lol with enough detail to reproduce it. Please do not access, modify or disclose other customers’ data while investigating.
Security contact
For coordinated disclosure or security questionnaires, email security@texttoaudio.lol
Our support team replies within one business day, Monday through Friday.