Privacy Policy

1. What this policy covers

This Privacy Policy explains how Speechivo handles information when you use our website and text-to-speech service. Speechivo is a tool for turning user-provided text into generated speech.

2. Information we handle

Depending on how you use Speechivo, we handle:

• Account information such as your email address and, when supplied by your sign-in provider, your name and profile information.
• Authentication data managed by Supabase Auth, including the information needed to keep you signed in. We do not receive or store your Google password.
• Text submitted for speech generation; selected voice and language; request timestamps and character counts; and generation-history entries.
• Subscription, usage, and Paddle identifiers/status needed to apply your plan and display subscription information.

3. Google Sign-In

If you choose Continue with Google, Google authenticates you and Supabase Auth creates or signs you into your Speechivo account. Speechivo receives the account information Google and Supabase make available for authentication, such as your email address and profile name when provided. Speechivo does not receive your Google password. Google's own privacy policy applies to Google's handling of your information.

4. How we use information

We use this information to authenticate accounts, generate speech, apply usage limits, show and manage generation history, administer subscriptions, maintain the service, and respond to support or security issues. Submitted text is sent to the third-party text-to-speech service used by the generator. The repository does not establish that provider's retention or model-training practices, so do not submit sensitive text unless you have reviewed the provider's terms and privacy information.

5. Text, usage, and generated audio

Speechivo stores submitted text, voice, language, character count, and timestamp in your account's generation history. You can delete individual history entries in the History page. The application does not store generated audio in that history; audio is returned to your browser for playback or download. The TTS provider receives the text and voice selection to perform generation, and its retention practices have not been verified by Speechivo.

6. Service providers and security

Speechivo uses Supabase Auth and its database for authentication, account/profile settings, subscriptions, usage, and generation history. Speech generation is sent to the external service at ahm7xmakki.com. Paddle processes applicable subscription orders as Merchant of Record and receives payment and subscription information. Google processes sign-in if you choose Google. Hosting and runtime providers may process technical logs. The application can send error events to Lovable when its runtime error-reporting hook is enabled. Provider retention periods, locations, and other processing terms depend on each provider and must be reviewed separately. We use measures intended to protect information, but no online service can guarantee absolute security.

7. Your choices

You can update available account settings, delete individual generation-history entries from the History page, or sign out. Account deletion is not available as a self-service feature; contact speechivo@gmail.com to request account-data access or deletion. Requests may require identity verification and may be subject to information we must retain for legal, payment, security, or operational reasons. Retention and deletion of data held by Paddle, Supabase, Google, the TTS provider, and hosting/error-reporting providers are also subject to their own processes.

8. Cookies, logs, and contact

Supabase authentication uses persistent browser session storage to keep you signed in. No separate advertising analytics integration is present in the application code reviewed. Hosting, authentication, payment, and error-reporting providers may use cookies, logs, or similar technologies as described in their own policies. For privacy questions or to request account deletion, email speechivo@gmail.com. We may update this policy as the service changes; the revised version will be posted here with a new date.