The Commitment
- Zero session retention. Your voice, your words, and the AI's words are never stored on our servers — on any plan. Our voice infrastructure is configured account-wide to retain basic call attributes only: no recordings, no transcripts. What we hold is numeric — scores, progress graphs, cue counts, durations.
- Your device is the only archive. Keeping a session is opt-in, default no. If you opt in, the recording and transcript are created on and saved to your own device. We never receive a copy, and no retrieval mechanism exists anywhere in our system.
- Anonymity by default, anonymization on demand. Accounts are email-only — no name required. Before a session, an optional one-tap Anonymize step rewrites your material with names replaced by roles and identifiers stripped, and you approve the rewrite before it is used.
- Footprint minimization. Session content reaches AI model providers directly — no gateways, no resellers. System logs record lengths and counts, never content. No ad networks, nothing sold, ever.
Subprocessors & What They Hold
| Processor | Role | Session substance retained |
|---|---|---|
| Retell AI | Real-time voice conversation (speech recognition, voice synthesis, audio transport) | None — configured to basic call attributes only; no recordings, no transcripts |
| OpenAI / Google | AI models generating the examiner's questioning and scoring, reached directly | In transit only — API terms exclude training on your content |
| Google Firebase | Authentication, database, functions, hosting | None — numeric results and account data only |
| Stripe | Payments | None — billing data only, no session access |
| Fingerprint | Device identification for fraud prevention — keeps the free Challenge to one daily allowance per device, not per throwaway account | None — browser/device signals only; never audio, words, or material |
Encryption
- In transit: every hop is encrypted — WebRTC voice under DTLS-SRTP (mandatory, cannot be disabled), and all API traffic over TLS.
- At rest: everything we do store (the numbers) is AES-256 encrypted at rest on Google Cloud. API keys live in a managed secret store; your device never holds one.
- A note on "end-to-end encryption": a voice AI must process your audio to converse with you, so no voice-AI product can honestly offer E2EE. We say precisely what is encrypted and where — and we designed the system so the sensitive thing isn't stored at all, which is the stronger control.
Verification
| Item | Status |
|---|---|
| Vendor storage disabled (voice recordings & transcripts) | ACTIVE — VERIFIED JULY 2026 |
| Historical vendor data purged (zero recordings held) | COMPLETED — VERIFIED JULY 2026 |
| Database holds no session text (numeric results only) | ACTIVE — VERIFIED JULY 2026 |
| Independent counsel attestation (privilege & privacy review, co-signed, published here) | IN PROGRESS |
| Independent technical verification of zero-retention claims | PLANNED |
| SOC 2 | ON THE ENTERPRISE ROADMAP |
Disclosure & Contact
If we ever receive a legal demand for session content, our position is structural, not just policy: we do not hold it and no mechanism exists to retrieve it. We can produce only what exists — numeric scores and account metadata.
Security disclosures: security@thirddegreeprep.com · Privacy questions: privacy@thirddegreeprep.com · Full policy: Privacy Policy