Privacy Policy
How Intravo Corp handles, encrypts, and isolates data across our Windows operator application and attendee interfaces.
1. Overview & Scope
[LEGAL TEXT] This section outlines the general operational scope of Intravo Corp ("Intravo", "we", "us", or "our") in delivering real-time multilingual interpretation services. Formal legal commitments and statutory definitions are pending final legal review.
Intravo Corp is designed around a fundamental principle: your meeting audio, live transcripts, and personal information belong to you. Our architecture isolates processing to the operator’s local environment and minimizes cloud exposure wherever technically feasible.
This policy applies to our Windows operator application, attendee web player, mobile applications, and white-glove event services.
2. Where Session Data Is Stored
[LEGAL TEXT] Standard placeholder clause governing local desktop processing and customer ownership of local media files generated during sessions.
Unlike cloud conferencing services that centralize recordings on remote servers, the Intravo Windows operator application saves audio recordings only to the operator's local machine. Transcripts and session logs also upload to your own customer portal to build your reports — unless a BAA is in place, in which case nothing from the meeting is uploaded:
- Per-language audio recordings (WAV/MP3) are saved locally on the operator's PC and never uploaded.
- Full transcripts and subtitle files (SRT, VTT) are generated and stored locally, then sent to your own portal for The Honest Report — or nowhere, with a BAA.
- Performance logs and The Honest Report (HTML and CSV) are saved directly on disk.
- API keys configured in the desktop application are encrypted per-user via the Windows Data Protection API (DPAPI).
With a BAA in place, Intravo Corp does not maintain any copies of meeting recordings, transcripts, or logs on central servers after the session stream completes.
3. Attendee Data & Encryption
[LEGAL TEXT] Standard placeholder provisions detailing data handling practices for meeting attendees, listener check-ins, and cryptographic protections.
When attendees connect via mobile web, mobile apps, or radio check-out kiosks, Intravo protects their personal information:
- Attendee personal details are encrypted using AES-256-GCM.
- Attendance counting utilizes a keyed blind index, allowing organizers to see attendance metrics without exposing plain-text identity logs.
- Attendees are never required to create third-party accounts to listen in the room or online.
4. BAA Mode & Healthcare Sessions
[LEGAL TEXT] Contractual provisions specifying zero-retention parameters activated under BAA mode for sensitive and regulated customer environments.
For healthcare meetings, clinical advisory boards, or confidential corporate discussions, operators may engage BAA mode. In BAA mode:
- No attendee personal details or contact information are stored under any circumstances.
- Voice enrolment for Voice Preservation is strictly refused and disabled.
- All ephemeral stream metadata is immediately purged following session termination.
5. Voice Preservation & 7-Day Automatic Deletion
[LEGAL TEXT] Operational terms specifying strict retention schedules, consent records, and automated cryptographic deletion for synthesized voice profiles.
Where Voice Preservation is enabled, speakers provide a short voice sample to deliver interpretation in their own vocal tone. Intravo enforces strict safeguards:
- Voice enrolment requires affirmative e-signed or operator-confirmed speaker consent.
- Audio readings are cryptographically verified against a designated script to prevent unauthorized enrollment from third-party recordings.
- Preserved voice profiles and training data are automatically deleted after 7 days by the server on its own clock (via an hourly purge schedule).
- Deletion is verified and confirmed with our voice providers, while consent documentation is archived for compliance.
6. Data in Transit & Synthesis Credentials
[LEGAL TEXT] Technical definitions regarding cryptographic transit protocols, credential lifespans, and access control governance.
All communication between client devices, the operator PC, and synthesis nodes is protected in transit using industry-standard TLS encryption. Premium synthesis utilizes short-lived, single-use credentials minted per session that expire automatically. Operator access is governed through Google or Microsoft Single Sign-On (SSO) with complete organizational domain isolation.
7. Data Processing Agreements & Contact
[LEGAL TEXT] Standard placeholder guidance for executing customer-specific Data Processing Agreements (DPAs) and submitting formal security questionnaires.
Organizations requiring formal Data Processing Agreements (DPAs) or completed vendor security questionnaires may contact our security team directly:
Contact our Privacy & Security Team
We work directly with enterprise compliance and legal teams to review architecture, provide documentation, and execute bilateral DPAs.