Only the information needed to run the service is collected. It falls into the categories below:

Account details

• Email address and authentication method (Google sign-in or email/password).
• Display name and optional profile photo supplied through authentication providers.
• Account creation date and status.

Scripts and audio

• Text content submitted for rendering is held temporarily to create audio.
• Voice selections, render timestamps, and file metadata.
• Generated audio files stored for download during a short retention window (typically seven days).

Billing information

• Payments are processed by Stripe. No card numbers are stored in AI TTS Microservice.
• Transaction IDs, charge status, and credit usage are retained for accounting.

Technical diagnostics

• IP address, device, browser, and operating system information.
• Event logs, error reports, and usage analytics needed to operate and secure the service.

Voice analytics

• Per-event tracking of voice previews and generations: voice ID, language, model type (premium/ultra), source (preview/generation).
• User ID (when logged in) and session ID for usage patterns and abuse prevention.
• Cache hit status and model details for performance optimization.
• Event data retained for 30 days; aggregated rollups retained for 90 days.

Google Analytics (GA4)

• For EU/EEA/UK users: analytics cookies are only collected after explicit consent via the consent banner.
• For non-EU users: analytics are collected by default to understand usage patterns.
• Data collected includes: pages visited, session duration, device/browser info, and anonymized IP address.
• No personally identifiable information (PII) is sent to Google Analytics.
• You can reject analytics at any time via the consent banner (EU) or browser settings.

Mixpanel Analytics

• Mixpanel is used for product analytics to understand feature usage and improve the service.
• Same consent rules as GA4: EU/EEA/UK users must consent; non-EU users are tracked by default.
• Data collected includes: feature interactions, voice selections, generation events, and error rates.
• Pseudonymous identifiers (hashed user IDs) are used—no email or raw user IDs are sent.
• You can reject analytics at any time via the consent banner (EU) or browser settings.

Bot protection and security

• Google reCAPTCHA v3 is used on forms (contact, registration) to prevent spam and abuse.
• reCAPTCHA collects browser information, IP address, cookies, and user interaction data.
• This data is processed by Google under their privacy policy.
• By using this site, you agree to Google's processing of this data for security purposes.

Information is used to keep the platform running smoothly and securely:

• Deliver text-to-speech rendering, downloads, and API features.
• Authenticate accounts, track usage, and manage credit balances.
• Provide support, answer questions, and maintain service quality.
• Monitor reliability, detect abuse, and improve performance.
• Comply with legal, tax, and regulatory requirements.

Different types of data are kept for different lengths of time:

• Submitted scripts are processed and then deleted immediately after audio is generated.
• Generated audio files remain available via signed URLs for seven days before automatic deletion.
• Account and billing records stay active while an account exists. When you close an account, personal details are removed except where law requires retention.
• Transaction information is stored for seven years to satisfy accounting and tax obligations.
• Security logs and diagnostics are retained for up to 90 days unless extended for investigations.

Third-party providers help run AI TTS Microservice. They process data only to deliver the features listed below and must follow strong security practices.

• Firebase (Google): Authentication, database, hosting, and logging.
• Google Cloud Platform: Text-to-speech rendering, storage, and infrastructure.
• Stripe: Secure payment processing and credit management.
• Google reCAPTCHA: Bot detection and spam prevention on forms. Subject to Google's privacy policy.
• Google Analytics (GA4): Usage analytics to understand how the service is used. Consent required for EU/EEA/UK users.
• Mixpanel: Product analytics for feature usage insights. Consent required for EU/EEA/UK users. No PII sent.

Information may also be disclosed if required by law or to protect the rights, property, or safety of the service and its users. There is no selling, renting, or trading of personal data for marketing.

Data can be processed in the United States, the European Union, and other regions where Google Cloud, Firebase, or Stripe operate. Standard safeguards—such as contractual protections and encryption—are applied for these transfers.

Essential cookies are used to keep you signed in, remember your preferences, and secure your session. Google reCAPTCHA also sets cookies for bot detection.

The following cookies and local storage items are used:

• va_session: Session identifier for voice analytics deduplication.
• analytics-consent: Stores your analytics consent choice (accepted/rejected).
• is-eu-user: Caches your geographic region for consent banner display.
• Firebase Auth cookies: Maintain your authenticated session.

For EU/EEA/UK users, Google Analytics cookies are only set after you accept the consent banner. Non-EU users can manage analytics via browser settings.

You can exercise the following rights at any time:

• Request a copy of the personal data stored about you.
• Ask for corrections to inaccurate or incomplete information.
• Request deletion of your personal data where legally possible.
• Restrict or object to certain types of processing.
• Receive your data in a machine-readable format.
• Withdraw consent for optional processing at any time.
• Lodge a complaint with your local data protection authority.

Use the contact form on the site to make a request. You will receive a response within 30 days, unless laws in your region require a faster reply.

Security is designed into the platform from the start. Measures include:

• All traffic uses HTTPS/TLS encryption in transit.
• Data at rest is encrypted within Google Cloud and Firebase.
• Strict access controls limit who can view operational systems.
• Regular dependency updates and security reviews.
• Automated monitoring to detect suspicious activity or abuse.
• Secure payment handling through Stripe (PCI DSS compliant).

No method of transmission or storage is entirely risk-free, but the safeguards above are reviewed regularly to keep data protected.

The service is intended for users aged 13 and older. Accounts created by anyone younger than 13 will be removed once identified. Contact support through the form if you believe data has been collected from a child.

When this policy changes, the update date will be revised and a highlighted notice will appear on the site. You are encouraged to review the policy periodically to stay informed.

Questions about privacy or data handling? Use the contact form on the site and the request will be answered directly by the person who maintains AI TTS Microservice.