¡YapZee!

Delete your account

Request deletion in the app or by email. In the app, a pop-up asks you to confirm; the app then schedules the deletion, clears what it keeps on the phone for your account and signs you out. Signing back in during the first seven days cancels the request. After that, the account and its data are permanently deleted, apart from the retained records named below. Deletion and subscription cancellation are separate actions.

Zihan, holding a closed notebook and a pencil, looking back with a calm smile

The seven days

Pick a day to see what is true on it.

Day 1: you ask

The app first asks you to confirm, then asks the server to schedule deletion. After a successful request, it clears the lessons, progress, onboarding answers and other learning records it keeps on the phone for your account, gives the phone a new guest device identity, signs you out and goes back to the start of onboarding, as a fresh install would. Nothing on our servers is deleted yet. A failure can leave the request scheduled even if sign-out did not finish. A few small notes the app keeps in its own storage on the phone (the Privacy page lists them) can stay until you remove the app.

For seven days, signing back in cancels it. There is no button to find and no form: when you sign in, the app asks the server who you are, that call cancels the deletion, and the app tells you it was canceled.

Check the request status before assuming deletion is still pending. An authenticated account request during the cancellation window can cancel it even if you did not intend to change your mind.

Day 7: your account and data are deleted

After the seven-day cancellation window, account routes refuse access and the next successful closure job removes the sign-in identity. That prevents new sessions. Protected learning routes also check that the identity still exists, so an old access token does not preserve access after closure.

In the same run, the job removes the account-owned data listed under What gets cleared and asks PostHog and Sentry to delete what they hold for your account. Failures can delay completion and are retried, and the retained categories below remain.

A few things stay, and each one is named under What stays.

A daily server job checks for identity closure and account-data removal from day seven. Failed steps are retried. These are scheduled thresholds, not a guarantee that every provider copy disappears on that date.

Two ways to ask

In the app

  1. Open Settings.
  2. Scroll to Danger Zone.
  3. Tap DELETE ACCOUNT and confirm. The confirmation shows how long you have to change your mind.

By email

Write to support@yapzee.ai and say you want your account deleted. You don't need the app, or an account you can still sign into.

Write from the email address on the account if you can. If you can't, say which account you mean. We may ask you a question or two first.

Write the email

What gets cleared

From day seven, the scheduled purge attempts to remove these account-owned records. Completion is not guaranteed on that exact day.

  • Your sign-in, closed first, in the same run.
  • Your profile and settings: portraits, email proofs, the onboarding answers saved to your account, course settings, level settings, timezone, social links and our billing records for you.
  • What the app remembers about your learning, in every language, XP included.
  • What you wrote, and what was made for you: lessons, daily tasks and culture cards.
  • The audio made for you, daily and per task.
  • Your analytics profile at PostHog, with its events.
  • Your bug reports at Sentry tagged with your account code, with their screenshots and recordings.

Subscriptions

Deleting your ¡YapZee! account does not cancel a subscription or issue a refund. Billing is separate, so cancel with the company that charges you.

Bought it on this website? Manage your orders. Website purchases are sold through Link, which keeps its own sign-in. This still works after your ¡YapZee! account is gone.

Bought it in an app? Manage an Apple subscription or manage a Google Play subscription.

You can still delete your account now. Subscription cancellation is a separate step, not a condition of erasure.

Confirmation

Do not rely on an automatic completion email: delivery depends on a verified address, provider setup and successful processing. To ask where your request stands, email support@yapzee.ai.

Asked and heard nothing? Send it again and say it's a second message.

What stays

Six retained categories are listed below. Four have direct account or device links. Shared content may also contain identifying material.

Website feedback uses a random message identity. Deleting your account does not find those messages by account ID. Contact support about a particular message; avoid including private information in feedback.

  1. 01Traceable to you

    The deletion record and three small safeguards

    The record keeps the dates you asked, the undo window closed, clearance was due, and each step ran. If your email address was confirmed, it also holds that address until our mail provider accepts the completion message.

    The safeguards stop cleared work from coming back: course head records, a content artifact fence and an audio fence, each filed under a fingerprint of your account ID. They hold no lessons or recordings. The record and safeguards are kept for good.

  2. 02Traceable to you

    Crash and bug reports at Sentry

    Our deletion process finds and deletes the bug reports tagged with your account code, with their screenshot and recording. It cannot find crash reports, or reports from under-16 or unknown-age use, because they carry no such code; those expire when Sentry's retention period ends. We have not verified Sentry's backups or its own deletion schedule.

    What Sentry receives

    Crash and error reports go to Sentry automatically in release builds. They carry device details and the error, and no account ID, email, username or screenshot. A bug report you choose to send is different. If your account or your guest age answer shows 16 or older and you have not turned off usage statistics, it can carry a screenshot and, if you dictated it, the recording. When you are signed in it is tagged with a code derived from your account ID, not your account ID, email or username; we can recompute that code from your account ID, so it still links the report to your account. Guarded private screens are left out of screenshots. Optional attachments can fail. If you are under 16, or your age is not on record, a bug report carries the words you typed (with email addresses and phone numbers removed), the screen you were on and your recent screens, your course, level and the lesson date and task, and device details; it carries no account ID, email, username, screenshot or recording. The Sentry SDK disables default personal-information attachment, session replay and app-session tracking. Sentry may still derive a city-level location from the connection, and crash reports built by the phone's native layer can carry a random installation identifier that is not linked to your account. Our Sentry plan keeps reports for about a month. Our account-deletion process searches Sentry for bug reports tagged with your code and deletes them one at a time. It cannot find crash reports or under-16 reports, which carry no such code; they expire with that retention period. We have not confirmed a complete deletion schedule at Sentry.

  3. 03Traceable to you

    Server logs at our host

    Server logs can contain an account ID. Our account purge does not remove matching host log entries. Effective host retention and any request-specific removal need separate verification.

  4. 04Traceable to you

    A separate sign-in record

    Our own database also has a separate sign-in table with fields for an email address, a password hash and a date of birth. It is outside the account purge, and no verified link ties a row in it to the account being deleted. The hosted sign-in identity at our sign-in provider is a different record: the daily job removes it from day seven. We have not verified which accounts have a row in our own table or how long those rows should remain.

  5. 05Shared content

    Grading notes

    Shared grading caches are keyed by text rather than an account. That does not establish that their content is anonymous or impossible to link to someone. They are excluded from the account purge and need a separate retention assessment.

  6. 06Shared content

    Pronunciation and lesson-sentence audio

    One shared copy per word or phrase, for everyone who has tapped the speaker on that card, and one per spoken lesson sentence, for every lesson that says the same words in the same voice. A lesson sentence is kept under a fingerprint of the voice request, with no account, course or date. There is no copy of yours, and removing it would take everyone else's.

  7. Questions about any of these? Write to support@yapzee.ai.

The companies a deletion reaches

The Privacy page describes recipients by feature. Account deletion reaches some storage systems, not every service or backup.

The automated process removes account-owned records in Supabase and files in Cloudflare R2, and requests deletion of the account-linked PostHog person and events and of the Sentry bug reports tagged with your account code. Shared pronunciation audio, shared lesson-sentence audio and grading caches are excluded. PostHog processes deletion asynchronously. A successful request does not prove every copy is already gone. A later daily check reads PostHog and Sentry for leftovers and alerts us if any remain.

  • Supabase
  • Cloudflare R2
  • PostHog
  • Sentry

The automated purge does not send deletion requests to Railway, Fish Audio, Groq, OpenAI, Microsoft Azure AI Speech, OpenRouter, InferenceNet, DeepInfra, Morph, Google, Meta, Twilio, Resend, RevenueCat, Stripe, Apple's push service, Tally or AgentMail. Whether those services retain a copy depends on the service and its settings. We have not yet verified a complete retention schedule for those copies.

  • Railway
  • Fish Audio
  • Groq
  • OpenAI
  • Microsoft Azure AI Speech
  • OpenRouter
  • InferenceNet
  • DeepInfra
  • Morph
  • Google
  • Meta (Facebook)
  • Twilio
  • Resend
  • RevenueCat
  • Stripe
  • Apple's push service
  • Tally
  • AgentMail