Data We Collect
Voice Over AI Studio collects data only to provide app functionality, support purchases, protect the service, improve reliability, and respond to support requests. The app does not sell personal data and does not use data for third-party advertising or cross-app tracking.
Account and identifiers
- Email address for sign-in, account recovery, and support.
- User ID, including Supabase Auth user IDs and account/profile identifiers.
User content
- Audio Data, including recordings, imported source audio, cleanup/polish audio, narration audio, and voice samples the user chooses to submit.
- Photos or videos selected by the user for import, Look-and-Voice workflows, export, or media handoff.
- Other User Content, including transcripts, captions, project titles, edit metadata, prompt text, export settings, job metadata, and consent text for voice features.
Purchases
- Purchase History for StoreKit subscriptions, consumables, entitlement sync, billing support, and restore-purchase behavior.
Analytics and diagnostics
- Product analytics and Other Diagnostic Data from closed-vocabulary app events, such as recording, transcript, export, paywall, and onboarding funnel states. When you are signed in these events are associated with your account identifier; when signed out they use an anonymous per-install identifier.
- Crash Data used to diagnose production stability defects.
How Data Is Used
Account, media, transcript, job, purchase, and entitlement data is used for app functionality: authentication, cloud transcription, audio cleanup, voice generation, captions, exports, project storage, quota enforcement, purchase restoration, and support.
Product analytics is first-party only. The app disables PostHog autocapture and screen-view capture, and uses a per-install identifier that is associated with your account identifier when you sign in (and is anonymous when you are signed out). It sends only explicit app-functionality events. PostHog is not used for advertising, cross-app tracking, IDFA collection, or data-broker sharing.
Processing and Storage
Supabase stores account records, entitlement records, media metadata, job metadata, generated outputs, transcript/edit metadata, and consent logs where applicable. Uploaded source media and generated results are stored in private Supabase Storage buckets and accessed through short-lived signed URLs.
AI providers may process uploaded media, transcripts, prompts, voice samples, edit instructions, and selected settings only to create requested transcription, cleanup, polish, narration, caption, music, sound-effect, scene-understanding, or export outputs. Launch provider processing includes Supabase for authentication, database, storage, and Edge Function orchestration; ElevenLabs for transcription, cleanup/polish, voice catalog, text-to-speech, speech-to-speech, music generation, sound-effect generation, and voice cloning only when those routes are enabled; Cloudflare R2 for provider-staging media storage when video handoff is required; Apple for Sign in with Apple and StoreKit purchase processing; and Google for default text-to-speech narration (Gemini), voice-prompt generation (Gemini), music generation (Lyria), and short-clip scene understanding (Gemini), where short clips sent for scene understanding may be retained by the provider for up to 30 days for abuse review and are not used to train models.
Before Voice Over AI Studio sends user-selected content to third-party AI providers, the app shows an AI Privacy Permission sheet that identifies what data will be sent and who receives it. Users can choose Allow & Send to continue or Do Not Send to stop the upload or AI request.
Third-party processors that receive user content are required to provide the same or equal protection for that data and may use it only to perform the requested service, not for advertising, cross-app tracking, data-broker sharing, or training their models.
Voice Cloning, Voice Biometrics, and Consent
Voice cloning or voice-reuse features, when enabled, require explicit consent that the user owns or is authorized to use the sampled voice. Consent records may include the consent text/version, sample IDs, accepted timestamp, and provider policy version. The app can require liveness checks before clone training.
Cloned voices and related voice biometric models are used only to provide user-requested voice features. Users can revoke voice-clone consent and request deletion of associated cloned voices, samples, and generated assets.
Retention
- Account/profile records are retained until account deletion.
- Uploaded source media is retained while the related job or project is active, then eligible for deletion.
- Generated outputs are retained while the user keeps the project or result.
- Entitlement and purchase records are retained as needed for account history, abuse prevention, tax/accounting, and support.
- Consent logs are retained while the related voice feature or generated asset exists and as needed for compliance and support.
Your Choices
Users can delete projects, delete or revoke cloned voices, restore purchases, and contact support. Users can also delete their account from the app's Settings screen.
Account Deletion
Voice Over AI Studio supports account deletion from Settings. Account deletion removes the Supabase Auth user, app database rows, private uploaded media, private generated outputs, and cloned voices owned by that account. If storage cleanup fails, the backend must retry or fail deletion before orphaning private files.
To request help with account deletion, contact support@voice-over.app from the email address associated with the account.
Tracking
Voice Over AI Studio does not track users across other companies' apps or websites. The app does not use IDFA, advertising SDKs, or data brokers.
Children's Privacy
Voice Over AI Studio is not directed to children under 13 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal data from them. If you believe a child has provided us personal data, contact support@voice-over.app and we will delete it.
Changes
We may update this policy as the app changes. Material changes will be reflected on this page.