01 · Protect your work

Keep the manuscript before troubleshooting

If the Studio is still responsive, copy any important text into a document you control before clearing browser data, reinstalling the app, or changing device storage. Drafts and history are device-local and may not follow you to another browser, device, or installation.

For rehearsal recordings, confirm the file or in-app recording you need is present before making storage changes. Do not assume local recovery is available after deletion.

02 · Make the issue reproducible

Record the steps without sending the private story

A useful report includes the device or browser, app version if visible, approximate time, the screen or feature involved, what you expected, what happened, and whether it repeats. A screenshot can help when it does not expose private manuscript content.

Do not place names, memories, full draft text, rehearsal audio, email addresses, or other sensitive content into a URL. Attribution and Studio handoff links are intentionally limited to non-sensitive setup values.

  • Device and operating system
  • Browser or app version
  • Feature and exact sequence
  • Expected and actual behavior
  • Whether a fresh draft reproduces it

03 · Writing requests

Separate a service failure from an unsatisfying draft

A failed request, timeout, blank response, or error message is a technical problem. A draft that completes but misses the intended voice is a quality problem. Capture which one occurred because the next diagnostic step is different.

For quality feedback, describe the kind of drift without sending more private material than needed: for example, ‘invented an event,’ ‘changed the relationship,’ or ‘made the tone too formal.’ Always correct factual issues before rehearsal or export.

04 · Commercial boundary

There is no active purchase-support flow yet

The pricing shown on the marketing site is planned launch pricing. A matching production catalog, entitlement ledger, credit consumption, authentication, receipt handling, and support escalation are not complete.

If you encounter a legacy purchase surface in a development or pre-release build, do not treat it as the approved public offer. Commercial launch remains blocked.

05 · Security reports

A dedicated disclosure channel is still required

The current project does not publish an approved security-reporting address. Do not invent one or send sensitive findings into a general manuscript field.

Before launch, Vow & Voice needs a monitored security channel, triage ownership, response expectations, and instructions for handling potentially sensitive evidence.

06 · Unresolved

What must exist before this page becomes final support documentation

A public contact method must be approved, monitored, and added to store metadata, privacy disclosures, terms, and this site. The team also needs severity definitions, response targets, refund and restore procedures, privacy escalation, and a path for accessibility reports.

Until then, this page remains a transparent status record and is excluded from search indexing.