Trust & Privacy
Your dictated content stays in the local workflow.
VeloxWaves is designed so core dictation, local memory, translation, and local AI work happen on your computer. This guide explains the product's data flows in plain language. It is a product overview, not a contract or a compliance certification.
Data map
Where information is handled
The core content path is local. Separate service workflows handle your account, billing, app delivery, and any support materials you choose to send.
On your device
These are part of the desktop app's local content workflow. VeloxWaves does not send them to a hosted transcription service.
- Dictation audio and transcript text
- Transcription history, local memory, embeddings, and knowledge-graph data
- Imported document content, translation records, and local AI prompts and outputs
Service metadata
These limited service records help operate accounts, subscriptions, product delivery, and usage limits. They are separate from transcript content.
- Account and authentication information
- Plan, trial, subscription, and billing state
- Usage-limit events such as word count, duration, timestamp, and device fingerprint where collected
- Release, updater, and explicit model-download requests
Only if you submit it
Support materials are sent only when you choose to submit an issue. Review and redact them before sending.
- Support issue descriptions
- Logs and system information
- Screenshots and attachments
Controls
You control local content and optional sharing.
Delete local transcription history, projects, documents, and local memory from the desktop app when they are no longer needed. Some exports, such as translated document exports, are saved to a location you choose.
Local AI features that need an additional model ask for an explicit download. Downloading a model does not upload the dictation, document, or prompt used by that local model.
Support reports are optional. Do not include patient information, client content, passwords, access tokens, or other sensitive data in a report, screenshot, or log attachment.
For sensitive work
What local processing does not replace
Local processing can reduce the number of third parties that handle dictated content. It does not replace a secure, access-controlled workstation, full-disk encryption, an organization's retention policy, or employee training.
Healthcare, legal, financial, and other regulated organizations must evaluate their own privacy, security, and legal obligations before using any software with sensitive information. VeloxWaves does not present this local-first design as HIPAA or GDPR compliance, certification, or a substitute for that assessment.
For individual clinicians, start with the practical workflow and its boundaries in our healthcare dictation guide.
For the future-facing organizational use case, read our shared clinical memory vision. Multi-user sharing and clinical integrations described there are not current VeloxWaves features.
Questions about privacy?
Contact Neural Wave Labs at contact@veloxwaves.com. For account-data requests, use the same contact path.