Security & Privacy at DuoVox

Your conversations deserve strong protection. DuoVox is built with a privacy-first architecture that gives users control over their data.

Private Mode: No Retention by DuoVox

When Private Mode is enabled:

• Audio is processed in real time; DuoVox does not keep it once your session ends
• DuoVox’s own servers do not store your audio, transcripts or conversation content
• DuoVox does not log or retain your session data on your device
• DuoVox does not use your session content for analytics or model training

Note: DuoVox’s own servers do not store your audio, transcripts or conversation content. On paid tiers, audio is streamed to our processing provider in real time for processing only and is not intentionally retained; the provider may keep limited operational logs under its own policy. Private Mode controls what DuoVox itself stores and logs on your device. For Free tier users, all processing is on-device and no audio leaves the device.

Useful whenever you would rather DuoVox kept no local log of your session. DuoVox is an assistive aid and is not certified for medical, legal or other high-stakes use — always verify important information independently.

Standard Mode (Cloud Processing)

When Private Mode is not enabled:

• Audio is streamed to third-party AI services for real-time transcription and is not stored by DuoVox
• Transcriptions and translations exist only in your device’s memory during the session
• DuoVox does not sell your personal data. On Windows, the Free tier shows only our own promotional messages — no third-party ad SDKs. On Android, where advertising is offered, ad providers may collect standard device data for ad serving.
• Third-party processing providers handle data under their own privacy policies and do not use API data for model training under their current data policies

Data Handling Principles

DuoVox follows these core principles:

• Minimal data collection — we collect only what is needed to provide the service
• No unnecessary retention — data is discarded as soon as it is no longer needed
• No sale of user data — your information is never sold to third parties
• No advertising-based profiling by DuoVox — we do not build profiles of our users. Where third-party advertising is offered (Android Free tier), ad providers may collect standard device data under their own policies.
• Clear, transparent communication — we tell you exactly what happens with your data

Compliance Transparency

DuoVox is designed with strong privacy protections, but:

• DuoVox does not claim certification under any regulatory framework (including HIPAA, FERPA, or CCPA)
• DuoVox does not sign Business Associate Agreements (BAAs)
• Organizations are responsible for determining whether DuoVox fits their compliance needs

This ensures clarity and avoids misleading claims. For common questions about using DuoVox in regulated settings, see our Privacy Policy.

Security Practices

• Encrypted data transmission (HTTPS/TLS) for all communications
• Secure infrastructure with industry-standard protections
• No DuoVox servers store user audio, transcriptions, or conversation content; the limited service data we do hold is described in the Privacy Policy
• Regular security reviews and updates

Technical detail

• In transit: every connection that carries your data uses TLS 1.2 or higher — between the app and our service, and between our service and the processing providers.
• At rest: the limited service data we hold is stored on Cloudflare’s platform and encrypted at rest. On your own device, any settings field holding a credential is encrypted with AES-256-GCM under a key derived from a per-installation secret, and protected by an HMAC-SHA256 integrity check; the Microsoft Store build holds no provider credentials at all.
• Credentials: our providers’ API keys never leave our servers. The app is issued short-lived, narrowly scoped tokens instead, minted per session and refreshed automatically, so an intercepted token expires in minutes rather than granting standing access.
• Access control: the administrative dashboard sits behind an identity gateway and a separate administrative key, compared in constant time. Every request that can affect a paid entitlement carries a per-device HMAC-SHA256 signature with a 60-second validity window, so a captured request cannot be replayed.
• Logging and retention: administrative changes to an entitlement are written to an audit trail. Per-device diagnostic events are pruned automatically — typically within 30 days and in any event within 12 months. Retention for every category of data is set out in the Privacy Policy.
• Separation: the key that signs a device’s requests and the key that encrypts its local settings are derived separately, so neither can be used in place of the other.

Reporting a security issue

If you believe you have found a security vulnerability in DuoVox, please email info@duovox.net with enough detail to reproduce it. We will acknowledge your report, keep you informed while we investigate, and will not pursue anyone who reports a genuine issue in good faith and does not access or alter other people’s data while doing so. Please give us a reasonable opportunity to fix the problem before publishing it.

If a personal-data breach occurs and is likely to result in a risk to people’s rights and freedoms, we will report it to the Information Commissioner’s Office within 72 hours of becoming aware of it, and tell affected users without undue delay where the risk to them is high.

Your Control

You can:

• Enable Private Mode at any time so DuoVox keeps no local log of your session
• Clear all session data instantly with the Clear button
• Use DuoVox offline where supported — no audio or conversation content leaves your device
• Uninstall the app to remove all locally stored data

For our full data handling policy, see the Privacy Policy. For data-protection queries, contact info@duovox.net. For questions about regulated environments, see the Privacy Policy.