Revision dated October 23, 2026.
This revision takes effect upon publication as the current revision on October 27, 2026 (UTC).
1. App and developer
This page lets you request deletion of your Shopping List STAT account and associated data. Developer: Individual Entrepreneur Lopatka Aleksandr Fedorovich, Uzbekistan.
2. Request without the app
Email head.stat@gmail.com with the subject “Shopping List STAT account deletion” and identify the account email and sign-in method: email, Google or Apple. Preferably write from the account email. If this is not possible, including with Apple Hide My Email, tell us so that we can offer proportionate, secure verification. You do not need to install the app to send a request.
Email an account deletion request
Do not send passwords, sign-in codes, tokens or identity documents on your own initiative. Merely providing someone else’s email does not authorize deletion of that account.
3. Request in the app
Open Menu → Account → Delete account. Read the consequences, choose whether to also delete this account’s personal local data and related files, and confirm. The app verifies the current session, submits the request and waits for server acknowledgment; until then the request has not been accepted, for example while offline. The app then attempts immediate account and cloud-data deletion. Sign-in is requested again only where needed to verify identity. The app shows either “Account deletion completed” after completion has been verified or “Deletion request accepted” for further processing. Closing the screen after acceptance does not cancel the request. If additional ownership verification is needed, an unfinished check is not treated as verification: we provide a proportionate way to complete it and explain what is needed. An operator can continue a verified request independently of the app. Starting an in-app request does not require emailing support.
4. What is deleted
Account deletion covers your authentication and profile data, owned personal cloud data, memberships and invitations, technical tokens and processor identifiers within our control. Shared lists you own are deleted with their server content and other members lose access. For other owners’ lists, your identifying information and records clearly attributable to you are removed; other people’s independent content is not destroyed. For jointly edited records, your account links and personal fields are removed without assigning your authorship to someone else. Ambiguous provenance requires separate investigation, not an inaccurate claim of complete deletion. Legacy shared files are considered only if actually found. Lawful exceptions are documented with the basis and retention period or criterion.
Deletion review includes our server storage and processor records, including RevenueCat and invitation email delivery. Deleting only a profile or local copy does not count as completing deletion of all associated data. Payment records independently controlled by stores and their mandatory retention periods are governed by the respective store.
The deleted account’s local shared data and related managed files are cleared. Personal local data is retained by default; a separate option removes this account’s personal lists, items, notes, custom categories and associated files and reminders on the current device. It does not clear another account’s data. Recipes, ingredients, the catalog, settings and files used by retained records remain on the device. Version 1.2.0, which has no shared lists, follows the personal-data part of this process. Remove unwanted content on other devices separately. We cannot remotely erase independent copies, exported files or system backups. Uninstalling the app does not itself delete the cloud account. If local cleanup on the current device is not yet complete, the app shows a separate status and retries cleanup. Completing an external request for server-side deletion does not depend on your device being switched on.
5. Timeframe and confirmation
The app attempts to perform deletion immediately. An operator manually processes unfinished requests and requests received by email. After ownership verification, the necessary actions and checks are performed within applicable statutory deadlines. An accepted request is distinct from verified completion; a technical failure does not justify indefinite retention. We confirm completion to the verified account or request email, including after verifying deletion performed by the app. If additional verification is needed, we explain what is required; applicable legal response deadlines still apply. For status, email the same address and include the request number if provided. Applicable statutory deadlines are observed in all cases.
Support contact details and correspondence are retained until confirmed closure of the case, then for no more than 90 calendar days. For an account-deletion request, closure means completion of the necessary actions and checks, not receipt of the request. Cleanup covers working emails, attachments and controlled copies. A justified dispute or mandatory legal retention may require a specific exception with a recorded basis and review date; the data must be deleted when that basis ends. A prepared email or technical receipt alone does not prove completed erasure. A minimal technical receipt without UID or email is retained for no more than 30 days after completion; scheduled cleanup is allowed from day 29 so that daily maintenance stays within this limit. A justified hold has a separately recorded basis and review date. External provider and backup periods are described in Privacy and checked separately.
Server-side installation safeguard records are retained until confirmed completion of account deletion and verification that old tokens, sessions and deferred operations cannot be reused. After safety is confirmed, they become eligible for cleanup after 30 days. Cleanup must not allow deleted data to be restored; a verifiable safeguard and specific review are required until that risk is resolved. Hashed identifiers and operation versions are not automatically anonymous. Deletion of the Firebase Installation ID is checked separately from deletion of the FCM token; Firebase services may create a new identifier on subsequent use. A separate temporary UID write block is retained while the deletion request exists and until its technical expiry, one day after the block is set; a justified hold prevents cleanup. The 30-day period after safety confirmation applies to installation safeguard records.
If you separately stopped invitation emails, that recipient preference also applies without an account. After account deletion, only a minimal protected suppression key remains, without a UID, profile or list content, to prevent unwanted invitations from resuming. It is not considered anonymous and is used only to honor that preference. You can revoke the preference and remove its record by a separate request to head.stat@gmail.com after proportionate address-ownership verification without registration; invitations will then be permitted again. The record is also removed if the invitation-email feature ends.
After completed deletion, the deleted account and content cannot be restored through the app. Deleting the app or account does not automatically cancel a Google Play or App Store subscription. Before confirming deletion, you may open subscription management and cancel renewal, but cancellation is not a condition for deletion: you may submit the request immediately. A one-time purchase does not automatically renew. Refunds and later purchase restoration follow store rules, purchase terms and mandatory law; deleting an account does not waive those rights.