Yapr is here to turn voice into text, not to turn your voice into a data product. We do not sell personal data, we do not use your audio or transcripts to train our own models, and we do not listen to recordings as part of normal operations.

The practical version: audio and transcript text can pass through Yapr, our hosting stack, and AI providers so transcription and Restyle can work. We also keep the useful little records the app needs, like account, security, quota, support, and product-usage records, as described below.

We collect the data needed to run the service, protect it from abuse, and support users:

• —Account data - name, email, sign-in method, password hash if you use email/password, passkey records if you add passkeys, account settings, role, ban or support status, and onboarding/terms consent timestamps.
• —Usage and quota records - recording duration, file size, language, provider, model, request IDs, latency, cost, word/character counts, quota use, and related operational metadata. We do not store audio content in these records.
• —Transcripts - only if transcript history is enabled, or temporarily where needed to deliver a transcript or apply Restyle. You can delete saved transcripts from History.
• —Voice/audio input - processed to generate transcripts. Direct requests are held in memory during processing. Retry/chunk uploads may be encrypted temporarily in a short-term holding area and deleted after processing or cleanup.
• —Security data - IP address, user agent, login attempt results, rate-limit keys, nonce records, and similar abuse-prevention metadata.
• —Referral, email, and support data - referral attribution, transactional email delivery metadata, marketing preference, feedback messages, and admin notes needed to operate support and safety workflows.
• —Cookie and analytics choices - session state, theme/preference storage, consent settings, and product analytics events that do not include audio or transcript text.

When you record, your browser sends audio to Yapr over an encrypted connection so we can transcribe it for you. That job may run through DeepInfra and, when fallback or rescue transcription is configured, OpenAI. If you use Restyle, transcript text goes to OpenAI so it can rewrite exactly the text you asked us to rewrite.

Yapr does not keep audio as account history, does not create an audio archive, and does not run human quality-review listening. Some temporary handling still happens because computers need a place to work: direct audio sits in server memory during the request, and retry/chunk audio can sit encrypted in a short-term holding area until transcription finishes or cleanup removes it.

We use personal data only to keep Yapr useful, fair, safe, supported, and legally buttoned-up:

• —Signing you in and keeping your session cozy and active.
• —Tracking your transcription quota so the free tier works fairly.
• —Delivering your transcripts and (if you want) saving them for later.
• —Running Restyle when you ask Yapr to rewrite a transcript.
• —Crediting referral bonuses when friends you invite sign up.
• —Detecting abuse, debugging failures, protecting accounts, enforcing our Terms, and meeting legal obligations.
• —Understanding aggregated product usage so we can improve the app without sending audio or transcript text to analytics tools.

These are the carefully chosen helpers that let Yapr work. Their processing is limited to the jobs they perform for us, subject to their own service terms and privacy commitments:

• —DeepInfra - primary speech-to-text provider. They receive audio for inference and return transcript text. Their public data-privacy docs say inference inputs and outputs are generally not stored to disk and are not used for training, with limited exceptions for logs, debugging, security, and certain model/provider paths.
• —OpenAI - fallback or rescue speech-to-text provider when configured, and the provider used for Restyle text rewriting. OpenAI API data is not used to train OpenAI models by default, but API abuse-monitoring logs may be retained under OpenAI's platform policies unless a stricter retention setting applies.
• —Google / GitHub — handle OAuth sign-in. We only get your name and email. If you sign in with email/password or a passkey, these two aren't involved at all.
• —Vercel - hosts the Yapr app and API. Live request traffic, including audio during transcription, passes through request handling.
• —Neon / PostgreSQL — stores your account, quota, and (if opted in) your saved transcripts.
• —Resend - sends transactional email and records delivery events. It receives email addresses and email delivery metadata.
• —Upstash Redis - powers rate limiting and abuse prevention, including hashed or scoped identifiers derived from requests.
• —Sentry - receives technical error context. We do not intentionally send audio or transcript text to Sentry.
• —Umami, Google Analytics, and Microsoft Clarity - product analytics and interface diagnostics. We do not intentionally send audio or transcript text to these tools. Google Analytics and Clarity run under consent controls where required or configured.

Audio: not kept as account history. Direct audio is held only while processing. Encrypted retry/chunk holding is deleted after processing, and old chunks are automatically swept away.

Transcripts: saved only if history is enabled, or temporarily when needed to deliver a result. Deleted transcript records may remain in backup or cleanup windows for a limited time before removal.

Account data: kept while your account exists and for as long as needed for security, legal, dispute, fraud-prevention, and business-record purposes. Account deletion has a short grace period so an accidental goodbye can be cancelled.

Usage, security, email, analytics, referral, and support records: kept as needed for service health, abuse prevention, accounting, debugging, legal compliance, and support. Some operational records are cleaned on rolling retention schedules.

You have real rights over your data, and we are happy when people use them. Depending on where you live, that includes:

• —Access — ask us what data we have on you.
• —Correction — if something's wrong, let us know and we'll fix it.
• —Deletion — ask us to delete account data, subject to legal, security, fraud-prevention, backup, and dispute-resolution exceptions.
• —Portability — request an export in a readable format where required or supported.
• —Objection/withdrawal — withdraw optional consent, including experience-improvement analytics where available.
• —California rights — know, delete, correct, limit where applicable, and opt out of sale or sharing. We do not sell personal data.
• —EU/UK rights — request access, rectification, erasure, restriction, portability, objection, and complaint to a supervisory authority where applicable.

We use required session and preference storage so Yapr remembers the basics, like whether you are signed in and which choices you made. Optional analytics and interface diagnostics sit behind the cookie/consent experience. Full details are in our Cookie Policy.

We use HTTPS/TLS, access controls, rate limits, short-lived nonces, encrypted temporary chunk holding, hashed secrets where appropriate, and provider infrastructure with its own security programs. No internet service can promise perfect security, but our design goal is simple: keep less sensitive content, guard what we keep, and limit who can reach it.

Found a vulnerability? Email security@yapr.lol. We read those reports carefully.

Yapr is for people aged 13 and older. By using Yapr, you represent that you meet the minimum age for your location and have any required parental or guardian consent. We do not knowingly collect information from children under 13. If you believe a child created an account, contact privacy@yapr.lol.

We may update this policy as Yapr changes. If a change materially expands how we collect, use, or disclose personal data, we will provide notice through email, in-app notice, or another reasonable method before the change applies where required. We will not use old data for materially new purposes without the consent or legal basis required by law.

Privacy questions, data requests, or a careful note from a privacy-minded human:

Email: privacy@yapr.lol

Yapr Inc. 131 Hazelton Avenue, Yorkville Toronto, ON M5R 2E4, Canada

This English policy is the controlling version. Translations or summaries are provided for convenience only.