# VoiceForge Privacy Policy **Last updated:** June 21, 2026 **Effective date:** June 21, 2026 **Controller:** VoiceForge **Contact:** hello@voiceforge.studio This Privacy Policy explains what VoiceForge collects, why it collects it, how it is used, and how writers can access, export, or delete their work. ## 1. What We Collect ### Account Data - Email address and account identifiers. - Authentication session data managed through Supabase. - Account settings, plan information, and billing identifiers when billing is enabled. ### Creative Work - Manuscripts, chapters, scenes, outlines, story bibles, characters, source material, annotations, research notes, pinned references, and project metadata. - Revision history, autosave state, workflow history, review decisions, and generated patch metadata. - Dictation transcripts and voice-command text created from voice workflows. VoiceForge does not intentionally retain raw microphone audio after transcript processing completes. ### AI and Workflow Telemetry - AI task type, model or provider routing, token counts, cost estimates, request timing, workflow status, and error states. - Review, apply, reject, undo, and recovery events needed to keep manuscript changes traceable. ### Diagnostics - Server logs, client error reports, HTTP status codes, timestamps, latency, and device/browser metadata needed to secure and operate the service. ## 2. How We Use Data VoiceForge uses collected data to: - Provide the writing workspace, manuscript storage, import, export, dictation, AI assistance, and review workflows. - Assemble project context for drafting, rewriting, adaptation, continuity checks, research, worldbuilding, and reconciliation. - Keep writer-approved content, source material, and story bible facts traceable. - Save history, autosave drafts, recover changes, and support undo/review flows. - Enforce account access, abuse prevention, billing limits, and project cost ceilings. - Debug errors, monitor reliability, and improve product safety. We do not sell personal data. We do not use private creative content to train VoiceForge-owned general-purpose models. ## 3. AI Providers and Creative Content VoiceForge sends relevant project context to AI providers only as needed to run writer-requested features such as drafting, editing, transformation, analysis, research assistance, and dictation cleanup. Provider routing can include OpenRouter, Anthropic, or other configured model providers. Voice dictation can use Deepgram or another configured speech-to-text provider. Where a provider offers no-training, zero-retention, or enterprise privacy controls, VoiceForge configures the most protective available setting practical for the service. Do not upload content you are not allowed to process through third-party AI or speech-to-text services. ## 4. Subprocessors VoiceForge uses service providers to operate the product. | Provider | What they process | Purpose | | --- | --- | --- | | Supabase | Account authentication, database records, project metadata, manuscript state, telemetry rows | Authentication and primary data storage | | Vercel | Web application hosting, request routing, logs | Hosting and delivery | | OpenRouter | Prompt context and AI responses for routed model calls | AI model access | | Anthropic | Prompt context and AI responses when selected through routing | AI model access | | Deepgram | Audio stream or transcript input for dictation features | Speech-to-text | | Sentry | Error events, stack traces, browser and server diagnostics | Reliability monitoring | | Stripe | Customer identifiers, subscription and payment metadata, payment method tokenization | Billing | Subprocessor availability depends on which product features are enabled for an account or deployment. ## 5. Retention - Active account content is retained while the account is active unless you delete specific content. - Deleted projects and assets may remain recoverable for up to 30 days. - Closed account data is deleted within 30 days unless retention is required for security, abuse prevention, accounting, tax, chargeback, or legal reasons. - Billing records may be retained for up to seven years where required for tax, accounting, or compliance. - Telemetry and diagnostic records are retained only as long as reasonably needed to operate, secure, debug, and improve the service. - Backups expire on their normal retention cycle. ## 6. Your Choices and Rights Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to processing of personal data. VoiceForge provides project export tools and in-product editing for most creative work. For account-level requests, contact hello@voiceforge.studio from the email address associated with the account. We respond to privacy requests within 30 days unless a longer period is allowed by applicable law. ## 7. Security VoiceForge uses TLS for network traffic, Supabase row-level security for user data separation, environment-managed secrets for service credentials, and provider-side security controls where available. No service is perfectly secure. Report security concerns to hello@voiceforge.studio with enough detail for us to investigate. ## 8. International Transfers VoiceForge and its providers may process data in the United States and other countries where infrastructure or providers operate. Where required, transfers use provider contracts and safeguards designed for cross-border processing. ## 9. Children's Privacy VoiceForge is not directed to children under 13 and is intended for users who are at least 18 or the age of majority where they live. If you believe a child has provided personal data to VoiceForge, contact hello@voiceforge.studio. ## 10. Changes to This Policy We may update this Privacy Policy. Material changes will be posted on this page and, where practical, announced to active accounts. Continued use after an update means the updated policy applies. ## 11. Contact Privacy, support, and security questions: hello@voiceforge.studio