YanliFit

Account deletion

Delete your YanliFit account and account-owned data.

Production account deletion is temporarily unavailable while its required backend migration and deletion function await separate deployment approval. This page documents the planned in-app route and data handling; it does not claim that deletion is operational.

For YanliFit mobile accountsLast updated July 20, 2026

Planned in-app deletion path

The app contains this flow under Settings → Account → Delete Account, but the production backend cannot complete it yet. After the required backend work is separately approved, deployed, and verified, the intended steps are:

  1. Open YanliFit and go to Settings.

    You must be signed in to the account you want to delete.

  2. Choose Account, then Delete account.

    You can also open Data controls, then Delete account.

  3. Review the deletion explanation.

    Deletion is permanent. Read what will be removed before continuing.

  4. Type DELETE exactly.

    This deliberate confirmation is case-sensitive.

  5. Verify recent account ownership.

    Enter a fresh six-digit code sent to your verified email. Where supported, a Google-authenticated user may instead be asked to sign in again with the same Google account.

  6. Confirm deletion.

    After the backend confirms that cloud deletion completed, YanliFit clears local account data, signs you out, and resets navigation to the signed-out route.

This cannot be undone. Export or record anything you need before confirming.

What is deleted

A successful deletion removes account-owned information under YanliFit’s control, including:

  • your YanliFit authentication identity (not an external Google account);
  • profile information, body details, preferences, and goals;
  • food and nutrition history, water logs, weight logs, and YanliFit-owned step records;
  • strength workout plans and sessions, exercises, sets, and cardio history;
  • account-owned AI usage records, entitlement records, and account-linked rate-limit keys;
  • pending or rejected community-food submissions and user-linked submission metadata;
  • local account caches and account-specific reminder state; and
  • YanliFit progress photos and thumbnails stored by the application on the device.

What may remain

Deletion is designed to remove your account and private history. The following limited shared, pseudonymous, reliability, or provider-controlled information may remain:

  • Promoted community food. If a contribution already became part of YanliFit’s shared food catalog, shared details—including name, brand, nutrition information, and locale or country fields—may remain after the account identifier and submission metadata are removed.
  • Shared reference data. Canonical foods, aliases, clusters, and barcode cache entries may remain because they are shared reference information rather than private account history.
  • Service protection and aggregates. Pseudonymous installation aggregates and network-hash abuse-prevention records may remain. A fixed purge schedule for current network-hash records has not been established.
  • Deletion reliability records. A non-identifying completed receipt supports retries for seven days. Expired receipts are purged during later deletion processing, so removal is not guaranteed at the exact seven-day mark. An incomplete-deletion recovery record may retain the account identifier until cleanup finishes.
  • Provider records. Supabase, Google, or other providers may retain provider-controlled operational or security logs under their own retention practices.
  • Health Connect source records. Deleting YanliFit revokes YanliFit’s permission where supported but does not delete records held by Health Connect or the application that created them.
  • Future transaction records. If paid subscriptions are introduced, records required for billing, tax, fraud prevention, or legal compliance may follow separate retention duties.

If you cannot access the app

YanliFit email support is temporarily unavailable while we complete the public launch. A dedicated support address will be published here before the app is released publicly.

Production account deletion is temporarily unavailable while its required backend migration and deletion function await separate deployment approval.

External account-deletion assistance is also unavailable until the dedicated support address is published. Both limitations are public-release blockers.

Do not send a password, one-time code, JWT or other access token, payment-card number, recovery code, or identity document.

Processing and retry behavior

Once the required backend work is deployed, in-app deletion is designed to complete directly after verification. Network interruption or a partial provider response may require recovery processing. YanliFit does not promise an unsupported fixed support deadline.

The application does not present deletion as complete or remove its local account state until the backend returns confirmation.

Subscription clarification

YanliFit does not currently offer a production paid subscription. If paid subscriptions are offered later, deleting your YanliFit account will not automatically cancel a Google Play subscription. You must manage any active subscription through the Google Play account used for the purchase.

Need help?

Visit YanliFit support for the current launch status.

YanliFit email support is temporarily unavailable while we complete the public launch. A dedicated support address will be published here before the app is released publicly.

Production account deletion is temporarily unavailable while its required backend migration and deletion function await separate deployment approval.

Never send credentials or verification codes.