← Back to Yummy Bites

YummyBites

Delete Your Account

Yummy Bites, by Mimi Studio d.o.o.  ·  Last updated: September 22, 2026

You can request deletion of your Yummy Bites account and associated personal data in the app or by contacting us. The in-app workflow has the scope and exceptions below; it is not an instant purge of every provider or backup. To keep your account and request deletion of only certain data, see Delete specific data without deleting your account.

1. Delete it yourself, in the app

This starts the authenticated account-deletion workflow.

On success, the app signs you out and clears the app data covered by its reset flow. If an error is shown, do not assume deletion completed; contact us using the option below. Existing records outside this workflow are described below.

2. Ask us to delete it

If you no longer have the app installed, or you cannot sign in, email [email protected] from the email address on the account with the subject Delete my account.

Tell us that you want your account and associated personal data deleted, including any scan photos or analytics records. Do not send your password, payment-card details or unnecessary child health information. We may need to verify that you are the account holder. We assess the request under applicable law and explain any records that must remain and why; this page does not promise a fixed completion or backup-erasure deadline.

Delete specific data without deleting your account

You can ask us to delete specific personal data while keeping your Yummy Bites account. Email [email protected] from the email address on your account with the subject Delete specific data — keep my account.

State that you want to keep your account and identify the type of data you want deleted, such as particular scan photos, a child profile, food or allergen tracking records, or analytics records. Include only the minimum details needed to identify those records, such as an approximate date. Do not send passwords, payment-card details or unnecessary child health information. We may need to verify account ownership and clarify the scope before handling the request.

This is a support request, not an automatic or immediate deletion action. We will explain any applicable limits, including records needed for legal obligations or other family members' rights. Provider records, shared copies and backups may need separate handling, as described below; this request does not guarantee erasure of every copy or a fixed completion deadline. Requesting data deletion does not cancel a subscription.

What the in-app workflow removes

The current workflow removes the sign-in account and the core records it handles, including:

• your authentication account and sign-in credentials
• private baby profiles — names, birth dates, avatars — and their linked child-data records
• foods tried and liked, and your food notes
• allergen tracker history, reaction notes and introduction plans
• meal plans and the first-28-days plan
• linked onboarding answers and user preferences covered by the profile/account cleanup
• your family-sharing membership; families with no remaining members are removed
• account-linked scan-result and review-event database rows removed through their account relationships; this is separate from the stored photo objects

Shared family data is different: when another family member remains, shared child profiles, tracking histories and plans can be transferred to the earliest-joined remaining member, together with family ownership where applicable. These records are kept for that family rather than erased with your account. Contact us if your request concerns personal data in those shared records.

Removing an account does not prove that every already-issued session token, local device copy, log or backup has disappeared immediately. Do not rely on uninstalling the app alone to request server-side deletion.

What can remain and needs separate handling

• Payment, purchase and entitlement records: the app does not automatically delete records held by Google Play, Apple, RevenueCat or the separate web-payment providers. Our web-purchase ledger is retained for accounting and entitlement handling. Applicable retention requirements vary.
• Scan photos and shared plate content: account deletion does not automatically remove every object in photo storage or every previously shared plate record. A shared record can retain its content and image path after the direct account reference is removed. In-app scan-history deletion separately requests removal of an individual scan and its photo, but is not proof that every provider-side copy was erased.
• Analytics and attribution: the account-deletion function does not send a deletion request to Mixpanel or PostHog. Identified events and profile properties, including child-related fields, can therefore remain. Attribution responses may retain install/analytics identifiers even after their direct account link is removed; these are not necessarily anonymous.
• Infrastructure/provider records and backups: security, support and AI-processing logs or backups can have separate retention. No verified universal 30-day backup-erasure deadline is promised here.

To request deletion or restriction of these remaining personal records, use [email protected]. Some records may need to be retained for legal obligations or the rights of other family members. We will explain the scope of the request and any applicable exceptions rather than treating all remaining data as anonymized.

Your subscription is separate

Questions