1. Current product stage
Today Zahvox provides a free web voice-to-text experience at /tool, plus a set of free utilities under /free-tools. There are no accounts, no billing, and no server-side project storage in the free tool. When those features are introduced, this document will be updated to reflect the new data flows.
2. Voice input handling
Voice input in the current free web experience relies on your browser's speech recognition capability. You start and stop recording. Depending on your browser and platform, recognition may be handled entirely on your device or partly by a service provided by the browser vendor. Zahvox itself does not intentionally record, store, or transmit raw audio to a Zahvox-owned backend in the current free web tool. Zahvox does not claim your voice never leaves your device unless verified for a specific feature and browser.
3. Transcript handling
The transcript produced by the browser appears inside the page so you can read it and edit it. It stays in the page and in your browser tab. It is not synced to a Zahvox-owned backend in the current free web tool. If you close the tab without copying or downloading, the transcript ends when the page ends.
4. Copy, download, and clear actions
The free tool provides simple actions to copy, download, or clear the transcript. Copying moves the text to your system clipboard. Downloading saves it as a file on your device. Clearing removes it from the page. Once text is copied or downloaded, it lives wherever you paste or save it, and Zahvox no longer has control over it.
5. Contact form data
When you use the contact page or reach out by email, Zahvox receives the message content, your reply-to address, and any details you choose to include. That information is used to reply, understand product demand, and improve the product. It is not sold, and it is not shared beyond the service providers needed to receive and respond to messages.
6. Logs and analytics
Basic technical logs may be produced by hosting and error-monitoring services to keep the site running and to diagnose issues. If analytics tools are enabled, they may record aggregate usage — for example, which pages were visited and which features were used. This information is used to prioritize the roadmap, not to build personal profiles.
7. Future account data
When accounts are introduced, additional data may be collected — for example, an email address, a display name, and account preferences. Authentication data such as session tokens will be stored securely and used to keep you signed in. This section will be updated with specifics once account features ship.
8. Future saved history
Saved history is a planned feature that would let you revisit earlier voice sessions or drafts. When it ships, it will require a decision about where content is stored, for how long, and how it can be exported or deleted. Zahvox will document those choices before shipping, so users can decide whether to opt in.
9. Future AI cleanup and writing modes
Planned AI features may send transcript text to a language model provider. If that is how the feature works, Zahvox will publish which providers are used, whether user input may be retained by the provider, and any options users have to opt out. Zahvox does not currently claim that data will never be used for AI training. That claim can only be made truthfully once the actual data flow is confirmed and documented.
10. Future extension, desktop, and plugin workflows
A browser extension, desktop app, and plugin integrations are planned. Each of these introduces new data flows — for example, injecting text into fields, reading focus context in a browser, or writing files on disk. When they ship, this document will describe what each surface can and cannot access.
12. Retention
Contact messages and feedback may be retained for as long as needed to reply, understand demand, and improve the product. Technical logs may be retained for security and debugging purposes. Once account features ship, saved history and account data will have separate retention rules described in this document.
13. User controls
Today the main user controls are: choosing what to record, clearing the transcript inside the tool, choosing whether to copy or download it, and choosing what to send in a contact message. As new features ship, additional controls (for example, deleting a saved history entry) will be documented here.
14. Security limitations
Zahvox aims to use reasonable safeguards for the data it does hold, but no online service can guarantee absolute security. You are responsible for using devices, networks, and accounts you reasonably trust. Zahvox does not claim SOC 2, ISO 27001, HIPAA, or GDPR certification at this stage.
15. Contact
Questions about this Data Handling Policy can be sent through the contact page or by email to hello@zahvox.com.