01 · Publication state
This page records a boundary; it does not replace legal review
A privacy policy must identify the responsible legal entity, describe the categories and purposes of processing, name or properly categorize service providers, explain retention, state applicable rights, and provide a working contact path. Those fields are not final in the source template.
This page is therefore marked noindex and does not call itself the governing policy. It should be replaced only when the final text matches the deployed product and approved vendor terms.
02 · Known behavior
Drafts, local history, and recordings are kept in app device storage
The Studio keeps saved drafts and revision history in storage associated with the app on the device. Optional rehearsal recordings are also intended to remain local to the app's device storage.
Device-local does not mean permanently recoverable. Clearing site data, uninstalling the app, losing the device, or changing browsers may remove access. The final policy and support documentation must explain deletion, backup, and migration behavior precisely.
03 · Known behavior
Writing and restyling require a service request
When a person asks Vow & Voice to generate, rewrite, or restyle text, the details needed for that request are sent to the configured writing service through the application API. This can include manuscript context and the story details the person chose to provide.
For that reason, the product must not claim that all writing ‘never leaves the device.’ The final disclosure needs the actual processor identity, purposes, locations, retention terms, safeguards, and any relevant choices.
04 · Site separation
The public site and private Studio have different jobs
vowandvoice.app is the public marketing and guidance site. studio.vowandvoice.app is the drafting application and should remain outside search indexing. The marketing-to-Studio handoff carries only allowlisted setup and attribution values.
Names, memories, draft text, email addresses, and other sensitive content must never be placed in handoff URLs or campaign parameters. The marketing application includes Vercel Web Analytics support for public page-view measurement; it still requires dashboard enablement and must be included accurately in the final vendor and privacy disclosures.
05 · Device permission
Recording is optional and requires microphone access
Rehearsal recording is not required to write or present a piece. When used, the app requests device microphone permission and should explain why at the moment of use.
The final policy needs to match actual platform behavior, including where recordings live, how they are deleted, whether they can be exported, and what happens when permission is refused or revoked.
06 · Launch blockers
Information still required before publication
The project needs an approved legal entity name and address, public privacy contact, complete vendor and subprocessors list, data categories and purposes, retention schedule, lawful-basis or regional disclosures where applicable, rights request process, international-transfer language, children's-privacy position, effective date, and change-notice process.
Those decisions must be made from the deployed architecture and vendor contracts. They cannot be safely inferred from a design brief.