Delete your Baku account

Last updated: 8 October 2026

You do not need to reinstall Baku to request account deletion.

Baku is developed and operated by Dekan Studio — an independent developer. Use the account-deletion option in Baku or contact Baku support using the steps below.

Before you request deletion

Deletion is permanent. Once your request is accepted, account access is disabled and erasure starts. There is no cancellation window or recovery. Registering again creates a new account and does not restore your previous content or purchases.

Cancel store subscriptions separately. Account deletion does not stop subscription billing. Manage subscriptions through Google Play or follow Apple’s subscription cancellation instructions. Your Google or Apple account is not deleted.

Delete your account in the app

With your current guest session or while signed in to your registered account, open Settings → Account information → Permanently delete account. Read both confirmation steps and confirm only when you are ready to permanently delete this account. Guests do not need to register, verify an email or contact support. Once accepted, the request disables access and starts erasure; processing takes time to finish. A failed or uncertain response does not confirm acceptance, even if processing has already started.

Request registered-account deletion by email

Email Baku support. Use the subject “Baku account deletion request”. Include your Baku account email and sign-in method, such as Google or Apple. We respond within 5 calendar days of receiving your email, with instructions for verifying account ownership.
Verify account ownership. Support must confirm that you own the account through a trusted verification process before submitting the deletion request. Knowing an email address is not sufficient. Within 5 calendar days of receiving all the information requested for verification, we notify you of the verification outcome. If ownership is verified, we also confirm acceptance of your deletion request. If we cannot verify ownership, we explain any missing information or next steps; we do not accept the request or start deletion until ownership is verified.
Allow processing to finish. An accepted request disables access and starts deletion; it does not mean all data has already been erased. When a verified registered-account email address is available, Baku queues a confirmation email after erasure in its active systems completes. Email delivery may take additional time or fail; contact support if you need to check progress. This confirmation does not confirm deletion of all backups or provider-held records.

Baku support

[email protected]

Write a deletion request

Opens your email app; it does not submit a request automatically. You can also copy the address above and send an email yourself.

If you use Sign in with Apple and Hide My Email, identify the relay address associated with Baku if you know it. If you cannot access your account email or are unsure which address is linked, explain this to support. An external request can proceed only after account ownership has been verified.

Never send passwords, sign-in codes, access tokens or information about your child. Support does not need your Google or Apple password.

Guest mode

Guests cannot create child profiles or personal stories. Guest mode still stores an account identifier, sessions, account-linked notification preferences and listening progress. Use Settings → Account information → Permanently delete account while your current guest session is available. The same irreversible erasure process and retention exceptions below apply. Guest accounts receive no completion email. Continuing in guest mode creates a new identity and does not restore the deleted account's history.

Language, playback speed and bedtime reminders are device settings. They remain on your device after guest deletion and may be sent again when the app registers the device for a new account. The old account's installation records, push tokens and notification preferences are removed from Baku.

If you uninstall Baku or lose the guest session, reinstalling does not recover that guest account. Baku currently has no established external verification or recovery process for a lost guest session. A guest ID or the email address you contact us from is not proof of ownership. You may contact [email protected] with privacy questions, but an email alone cannot authorize guest-account deletion. Never send session tokens, passwords, sign-in codes or child information.

What is deleted

We erase the following personal data from Baku’s active systems, subject to the limited retention described below: child profiles, private stories and revisions, narration and images, playback history, favorites, personal feedback and notifications, account-linked app installation records (including push tokens, notification preferences and reminder settings), sign-in identities and sessions, AI sharing decisions, usage records and related personal processing data.

Information previously processed by service providers is subject to the retention periods and deletion mechanisms applicable to those services. Completion of Baku’s account-deletion process does not confirm that every provider-held copy has been deleted.

What happens at other services

Baku deletes the personal media it manages on Cloudflare R2. When your account-deletion request is accepted, Baku will automatically send deletion requests to Qonversion, OpenAI, ElevenLabs and Brevo for your associated personal data processed by those services. Sending a request does not mean the provider has completed deletion. The handling of data at each service is described below:

Firebase Analytics and Crashlytics: Baku currently has no automatic process that deletes records already sent to these services when you delete your Baku account. Deleting Baku’s account-linked installation records does not delete Firebase’s separate records. See the Analytics and Crashlytics explanations, or contact support about a privacy request.
Qonversion: Baku removes its own account-linked purchase records and will automatically request deletion of your associated Qonversion customer data. Store subscriptions must still be cancelled separately.
OpenAI: Baku removes its own prompts and generated content and will automatically request deletion of saved responses associated with your account. New text-generation requests ask OpenAI not to save responses for later retrieval. Provider security and abuse-monitoring records remain subject to OpenAI’s applicable retention rules.
Microsoft Azure: Baku removes its own narration files. Microsoft states that real-time text-to-speech does not retain input text or generated audio; other Azure processing modes and records have separate retention controls.
ElevenLabs: Baku removes its own narration files and will automatically request deletion of narration history associated with your account that is retained by ElevenLabs.
Brevo: Baku will automatically request deletion of your associated recipient information, email logs and stored previews. A deletion-confirmation email may create new delivery records after account erasure; these remain subject to the applicable retention and deletion rules.

Read the provider-specific explanation in the Privacy Policy for available deletion mechanisms and official references. Contact Baku support about privacy requests involving these services; you do not need to send us passwords, tokens or your child’s story content.

What may remain

Shared stories and genuinely aggregate statistics remain. Minimal purchase fingerprints, without an account link or the original transaction value, are retained to prevent reuse of old purchases. Deletion records, protected backups and limited security records follow their applicable retention rules. Copies already downloaded to an offline device cannot be erased remotely.

Processing and retention

We complete erasure of personal account data from Baku’s active systems within 30 days after your deletion request is accepted. Account access is disabled and erasure starts on acceptance; there is no waiting period before work begins. For email requests, account ownership must be verified before acceptance. Contact support for progress or questions about retained information. Completion in Baku’s active systems does not mean all backups or provider-held records have disappeared at the same time; the exceptions below still apply.

Protected backups: Each backup copy is retained for no more than 90 days from its creation. Backups are isolated from ordinary use, and deletion is reapplied before any restored data is used.
Deletion records: We keep a record that your account was deleted for up to 120 days after deletion is complete. This helps us prevent your data from being accidentally restored. Your account cannot be recovered. If deletion is still in progress, we keep the request until it is complete.
Firebase Analytics: Our policy limits user-level and event-level retention to 2 months without resetting it on new activity. Google deletes expired data monthly; standard aggregated reports may remain longer. Baku account deletion does not automatically delete Analytics records. See analytics retention.
Firebase Crashlytics: Firebase keeps crash reports and associated identifiers for 90 days before starting removal from live and backup systems; not every copy is necessarily gone on day 90. Baku account deletion does not automatically delete these reports. See crash-report retention.
Support correspondence: Support correspondence is kept while a request is open and for no more than 90 days after closure. On an accepted, verified deletion request, active-mailbox copies are removed within 30 days, except the minimum still needed for an open request or legal obligation. Those exceptions end when the request is resolved or the obligation ends; backups follow their applicable lifecycle. Support handles mailbox removal separately from account erasure. See support correspondence retention.
Email delivery at Brevo: Our policy requires transactional logs to expire after 1 month, with up to another 24 hours for deletion. Email preview storage must be disabled for new emails; older previews require separate handling. This includes new delivery records from your deletion-confirmation email. Contact records have a separate deletion process. See email delivery retention.
Deletion-confirmation recipient in Baku: An available verified email address is kept during account erasure and while the confirmation email is queued or retrying. The recipient is removed from the delivery job when sending succeeds, permanently fails or is cancelled. Copies in backups, the recipient’s mailbox and Brevo have separate lifecycles. See confirmation recipient handling.
Other diagnostics and security records: Only records needed for an unresolved technical incident, an active abuse or security investigation, or a specific legal obligation are retained. They are reviewed at closure or when the obligation ends and deleted when no retention reason remains. Separate server logs, backups and provider-held records have their own lifecycles. See security record retention.
Purchase fingerprints and store records: Minimal purchase fingerprints remain for as long as needed to prevent reuse of purchases belonging to a deleted account, including lifetime purchases. They are pseudonymous, not fully anonymous. Store payment and accounting records are controlled by Google Play or Apple under their own policies.

Downloaded copies may remain on your devices after account deletion. Reconnecting the app does not guarantee their removal. See the Privacy Policy for other privacy rights and the Terms of Use for purchase and account terms.