Account and data deletion
Updated: 27 October 2026
Data is handled by Fit Lab, Zugdidi, Georgia. For privacy questions and data deletion, contact fit123lab@gmail.com.
You can request account deletion by email on Android or without the app. In an iOS version with Delete account, you can submit the request in the app and check its outcome using a server receipt.
- If the feature is available in your iOS version, open Profile → Delete account, confirm your password and deletion. Wait for the server’s Completed confirmation; Pending and sign-out are not completion. If the button is unavailable, use the email option below.
- Use the button below or email fit123lab@gmail.com.
- Subject: Fit Lab account deletion. State that you want to delete your account and associated personal data. Do not send your password or one-time code.
- Send the email. Opening your email app does not submit the request. Fit Lab will acknowledge it and may ask you to verify ownership of the email address.
Account and data deletion
In an iOS version that supports this feature, the deletion path is Profile → Delete account → re-enter password → explicitly confirm. Once accepted, the server immediately closes card access and issues a Pending receipt. Background processing removes Firebase Auth, the card link, name, contacts, personal ID, birth date, photos, private diary, invitations and unnecessary personal copies in history and audit. Normal processing includes at least a 3-minute drain for late requests and retries every 5 minutes; this is not a guaranteed deadline. A failure remains Pending and processing retries. Only the server’s Completed receipt confirms deletion; sign-out and authentication errors do not. Payment, membership, used-visit and used-coupon records retain a technical ID and necessary amounts, dates and terms without client names: this is pseudonymisation, not full anonymity. For necessary financial accounting, the club retains payment, membership-purchase, redeemed-coupon and financial-correction records for 6 years after the end of the relevant calendar reporting year. The basis for accounting documents is Article 4(18) of the Georgian Law on Accounting, Reporting and Audit; this is not a retention period for the entire profile. For example, 2026 records become eligible for cleanup on 1 January 2033. Detailed individual visits, visit corrections and ordinary audit records are retained for 90 days after the deletion request is accepted to investigate errors and disputed deductions; late service audit records are retained for 90 days after creation. Amounts and total used-visit counts remain in financial records for their financial retention period. If an old record has no reliable date, the deletion-request year is used conservatively; a later financial correction uses its own reporting year. Expired records are deleted in daily batches, with retries after failures. A specific record may be retained longer for a documented legal requirement or unresolved dispute, with review of the continuing need. The technical receipt and processing job expire 30 days after completion. A minimal permanent marker containing a random technical ID, without name, contacts or Auth UID, prevents restoration of a deleted card. If ownership of a previously revoked legacy card cannot be established, processing awaits club investigation. Android and users outside the app can also email fit123lab@gmail.com from the registration address with subject “Fit Lab account deletion”. Opening an email app does not submit a request. Never send passwords or one-time codes. The club verifies ownership and confirms the outcome. Uninstalling does not delete an account, and account deletion does not itself refund a membership.
Security and retention
Transfers use HTTPS and the server checks access. Android stores sign-in and language preferences; loaded club and diary information is held in memory and cleared on sign-out, and app backup is disabled. iOS stores club details, visits, photos and diary data in a protected file cache separated by UID and excluded from backup. You can clear it in the app; sign-out and accepted deletion clear it. Passwords and tokens are not passed to that cache; Firebase Auth manages its session and Keychain separately. An iOS version that supports deletion receipts stores its separate random receipt credential in Keychain without device synchronisation. Optional Android reminders periodically fetch membership details in the background without location; preferences and hashes of displayed reminders remain on the phone. iOS schedules local UNUserNotificationCenter reminders from current membership data without that background polling; sign-out or deletion cancels them. Notifications can be disabled in the app or device settings. CRM has a separate disk cache and photo queue: synchronisation replaces a deleted card and discards its queued photos. Server deletion cannot immediately wipe offline computers, other devices, staff exports or the original in your photo library; the club must clear its own copies. Configuration inspected on 15 October 2026 retains recoverable deleted Storage photos for 7 days and Firestore version history for up to 1 hour; PITR is off and no backup schedules were found. Configured Google Cloud log buckets retain _Default logs for 30 days and _Required logs for 400 days; other provider data follows provider policies. Operators must reapply deletions after restoring a copy. No security system provides an absolute guarantee. Android notification registration on the server includes the device registration, chosen language, consent date and update date. Registrations not refreshed for more than 30 days are excluded from sending and cleared during later use of the messaging feature. Turning notifications off in the app immediately stops their display on that phone; server registration is removed when a connection succeeds. Account deletion includes removal of device registrations. Android locally stores the notification preference, technical sync information, up to 20 recent messages and identifiers of previously displayed messages to prevent duplicates. The list shows messages from the last 30 days; it is cleared on opt-out, sign-out or manually and is excluded from app backup. Server campaign history contains the text, staff author and aggregate results without a recipient list; records older than 180 days are cleared during later use of the messaging feature. After opt-out, the server temporarily keeps a technical opt-out record linked to the account and installation, without the push token, to prevent delayed older requests from re-enabling notifications. Records not updated for more than 30 days are cleared during later processing; account deletion removes them too.