No. Your audio is never stored. It exists only long enough to create your transcript, then it is deleted immediately. No archive, no recordings database, no hidden retention.

No — and they physically can't. Your audio goes straight to an AI model, gets transcribed, and is permanently deleted. No human at Yapr ever hears your voice. There is no content moderation, no quality review, no "we randomly listen to 1% of recordings for training purposes" program. We built Yapr so that eavesdropping isn't just against policy — it's architecturally impossible. The audio doesn't exist long enough for anyone to access it. Honestly, we're too busy fixing bugs to spy on people.

All data between your browser, our servers, and our infrastructure partners is encrypted with TLS 1.3 — the current gold standard in transport-layer security. This applies to your audio upload, API responses, and all authentication traffic.

Three ways — pick your favorite. OAuth 2.0 through Google or GitHub (fastest), email with a securely hashed password, or passkeys via WebAuthn (biometrics or a hardware key). For OAuth, we receive only a read-only token and your public profile name and email. For email login, passwords are encrypted using industry-standard hashing — never stored in plain text. For passkeys, your biometric data never leaves your device. We literally can't see it.

Yes. Your transcripts are stored in your account only if you explicitly enable history in Settings — it is off by default. Nothing is kept unless you choose it. They are not shared, not used for training AI models, and not visible to Yapr staff in normal operations.

Never. We do not sell, rent, broker, or share your personal data with any third party for commercial purposes. This applies now and under any future ownership. It is written into our Terms of Service.

Yes. Yapr complies with the EU General Data Protection Regulation (GDPR). You have the right to access all data we hold about you, request corrections, and request full erasure of your account and associated data at any time.

We store your account identity (name, email, OAuth provider), usage metadata (timestamps and duration of transcription sessions), and transcript text (only if history storage is enabled in your Settings). We do not store audio content.

We conduct internal security reviews regularly. Our infrastructure leverages enterprise-grade providers (Vercel, Neon, DeepInfra) that maintain their own independent security certifications and audit programs. We implement security-by-design principles throughout the architecture.

In the event of a security incident affecting personal data, we will notify affected users promptly in accordance with GDPR Article 33 (within 72 hours of discovery where required). Because audio is deleted immediately, audio content cannot be part of any data breach.

In normal operations, no. Transcript data is stored in a database accessible only through authenticated API calls. Staff access requires system administrator credentials and is logged. We have no routine business need to read user transcripts.