What happens to a recording once you send it.
For security, risk and procurement teams. Where ORAVYS runs, how data is encrypted, how long it is kept, who processes it, and what we do not have yet. Every statement here repeats our Privacy Policy and Terms of Service, which prevail.
- Hosted in the EU
- No training on your audio
- Limits stated
europe-west1
Google Cloud, Belgium, EU
TLS 1.2+
In transit
AES-256
At rest, stored files
Not yet
Independent audit report
Hosting and region
Analysis runs in the EU.
ORAVYS is hosted on Google Cloud Platform (europe-west1 region, EU), with access restricted to authorised personnel. For the analysis flow accessible from oravys.com, audio is processed in memory inside our EU compute region (Google Cloud, europe-west1, Belgium) and the buffer is freed at the end of the call. Analysis results delivered as reports remain in the EU region for the retention durations described below.
Transfers outside the EU
Oravys, Inc. is based in the United States, as are the payment, e-mail delivery, network security, sign-in and statistics, and AI text drafting providers. These transfers rely on the EU Standard Contractual Clauses in each provider's data processing terms, with encryption in transit and at rest.
EEA-only processing, by contract
Enterprise customers may ask, in their Data Processing Addendum, that audio and reports be processed and stored only within the European Economic Area. On-premise pilots are scoped by contract.
Encryption
Encrypted in transit and at rest.
In transit
Data transmitted between your browser and our servers is protected by TLS (version 1.2 or higher).
At rest
Files that are written to storage (free check by e-mail, API jobs, enterprise contracts) are encrypted at rest by Google Cloud with AES-256 and provider-managed keys.
Retention
Audio is not kept after the analysis.
Audio is deleted after analysis. Reports are kept at least 30 days, then deleted automatically (35 days after creation; 30 days for full and expert reports); you can ask us to delete them sooner.
Where a file is written
- Analyses started on oravys.com: processed in memory and freed at the end of the analysis.
- API jobs: stored in the same EU bucket while the job runs and discarded as soon as the result is written.
- Free voice check by e-mail: deleted within 48 hours of upload.
Deletion and custom retention
When a retention period ends or you ask for deletion, the data is deleted from our live systems within thirty (30) days. Enterprise customers may request a written confirmation of deletion, and may set stricter settings for metadata and reports in their Data Processing Addendum. The full schedule is in Privacy Policy, Section 3.2.
Training
Your audio does not train our models.
No training without opt-in
ORAVYS does not use your audio, your reports, or features derived from your audio to train, fine-tune, evaluate, or improve its AI models, on any plan, unless you tick the Research Contribution box. That box is unticked by default, and the program is currently paused. Enterprise data is never used for training, whatever the settings.
No external AI on audio
All voice analysis is performed by ORAVYS's own software. No audio data is transmitted to any external AI provider. The single exception concerns text, not audio: for Enterprise forensic reports, a narrative summary may be drafted by an external language model from anonymized labels.
Sub-processors
A short list of processors.
Categories: cloud hosting (EU, Belgium), payment, e-mail delivery, network security and anti-bot protection, sign-in and optional statistics, and AI text drafting for Enterprise reports. Each provider processes data under data processing terms that include the obligations of GDPR Article 28. The named list is sent on request and provided to customers under contract, who are informed at least 30 days before any new sub-processor that processes personal data. See the sub-processor categories.
Access controls
Access is authenticated and limited.
Your side
- Account areas and report downloads require an authenticated session.
- API keys are tied to a plan and can be rotated.
- Public free checks run without an account, behind rate limits and a bot challenge.
Our side
- Infrastructure access is restricted to authorised personnel.
- E-mail addresses are hashed before being written to application logs.
- Uploaded files are checked for type, size and duration before analysis.
Assurance
What we have, and what we do not have yet.
The code base is scanned with automated static analysis and dependency auditing. ORAVYS does not currently hold a SOC 2 or ISO 27001 attestation.
| Independent audit report | Not yet |
|---|---|
| External penetration test report | Not yet |
| Data Processing Addendum (GDPR Article 28) | Available on request |
| Non-disclosure agreement | Sign online |
| Pre-filled security questionnaire | Available on request |
| Sample report, anonymized | Available on request |
Incidents and vulnerabilities
Tell us, and we tell you.
Report a vulnerability
Our contact for security reports is published in our security.txt file (RFC 9116). Please include the affected URL or component, steps to reproduce and the impact you observed. We do not run a bounty program.
Breach notification
In the event of a personal data breach, ORAVYS will notify the competent supervisory authority within 72 hours of becoming aware of it where required by GDPR Article 33, and will inform affected users without undue delay where the breach is likely to result in a high risk. Enterprise customers with active DPAs are notified within the period set in their DPA.
Your review
You stay in charge of every decision.
Results are investigative indicators, not definitive conclusions, and must be supplemented by human review. Send us your questionnaire, or ask for ours already filled in.
This page summarises our Privacy Policy and Terms of Service. If they differ, those documents prevail.