FIT LAB

Privacy Policy

Updated: 27 October 2026

Data is handled by Fit Lab, Zugdidi, Georgia. For privacy questions and data deletion, contact fit123lab@gmail.com.

Scope and purpose

This policy describes Fit Lab for Android and iOS and the shared club backend. The apps show memberships, trainers, visits and personal progress, allow profile editing and QR check-in. Data supports these functions, service accounting, support and security. Platform differences are stated below. If your iOS version does not yet have a Delete account button, use the email request described below.

Account and club information

When you register, your email and password are sent to Google Firebase Authentication to create your account and sign you in. A unique account identifier is created. Club staff cannot see your password. New clients can complete their details in the app; staff can also create a card in the CRM. A first or last name is sufficient. Personal ID, birth date, gender, phone number and photo are optional and can be added later. The submitted details are sent to the server, stored in your club card and available to authorised Fit Lab staff. An existing card is connected using an administrator’s one-time code without repeating the form. You can edit your personal details and choose a photo using the system image picker. The app does not request access to your entire photo library, contacts or SMS. Only the selected image is uploaded. Photos are resized and metadata, including GPS, is removed from the stored image. After a successful replacement, the old image is removed from active storage; backups and storage recovery remain subject to the retention information below. Photos are used in your profile and for staff to recognise you at reception; there is no automated facial recognition. Your assigned trainer, membership and visit history are also loaded into the app. Completing your details does not create a paid membership.

Location only for QR check-in

Only when you start QR check-in and grant permission does the app obtain your current precise location. Coordinates, accuracy, measurement age and location verification information are sent over HTTPS to verify proximity to the club. The inspected server processes these values in request memory and does not write them to Firestore, visits, the diary or application logs. It stores the visit time, client identifier and check-in method; the visit itself indicates attendance at the club. There is no background tracking or route recording. Infrastructure processes technical connection information such as IP addresses, which is not a GPS trail. You can revoke permission in Android or iOS settings. Other features remain available without location, and club staff can record a visit manually.

QR scanner and camera photos

On Android, Google Code Scanner through Google Play services processes QR images on the device; Fit Lab receives the decoded code. Provider diagnostics are described below. Android profile photos use the system camera or single-image picker and local uCrop editing. Temporary private-cache files are removed after processing or cancellation; files from interrupted sessions older than one day are removed when you next choose a photo. On iOS, AVFoundation reads QR codes, while the system PhotosPicker or camera provides profile photos. Cropping runs locally in the app without Google Scanner or uCrop. QR video is neither stored nor uploaded. Both platforms upload only the photo you confirm; the server resizes it and strips metadata including GPS. The apps do not obtain the entire photo library, contacts or SMS and do not record in the background.

Private fitness diary

You may choose to enter height, gender, a goal, target weight and dated measurements of weight, waist, hips and chest. These data are sent to the server and saved in a private diary linked to your account for charts and access across devices. They are not required to sign in or record visits. You can edit and delete measurements in the app and clear optional profile fields. CRM staff, trainers and other clients cannot access the diary through the app or CRM. Authorised technical administrators may need limited access for system maintenance or data erasure; the diary is not end-to-end encrypted. The app is not a medical device and does not diagnose conditions or prescribe treatment.

Technical data and service providers

The shared backend uses Google Firebase Authentication, Cloud Functions, Firestore and Cloud Storage for sign-in, data and photos. iOS uses Firebase Core, Auth and Functions. Android additionally uses Google Play services for location and Google Code Scanner/ML Kit; diagnostics may include device model, OS, app and SDK versions, identifiers, errors, performance and scanner events, and, for auto-zoom, a random session ID, zoom level and code bounding box. Those Android components are not in iOS. Firebase and Google infrastructure process technical connection and security information, including IP address, request time and outcome, and authentication identifiers. New application deletion logs contain only a random request number and fixed failure stage, without email, name, photo, GPS or receipt secret. Data may be processed outside Georgia, including in the United States and Europe. Inspected sources contain no advertising SDK, Firebase Analytics or Crashlytics. Fit Lab does not sell data or use it for targeted advertising. Disclosure may be required by law. Android versions that support this feature let you separately enable Fit Lab news and promotional notifications. They are off by default. Delivery uses Firebase Cloud Messaging: Google and the club server process technical app-installation identifiers and a push token; the server links the device registration to your account, language and notification choice. This information is used to deliver club messages, not to select advertising based on location or fitness-diary information. Declining does not restrict your membership, QR check-in or other features. You can turn off promotional notifications in the app or disable notifications in Android settings. This messaging feature has not been added to the current iOS version.

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.

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.

Account and data deletion

Your choices and support

You can request information about your data, a copy, correction, erasure or restriction of processing, subject to applicable circumstances. You can edit your personal details and photo in the app’s Profile section, through club staff or by emailing us. Location and personal measurements are optional. If you contact support, we process your message and contact details to respond. We do not request data for purposes unrelated to the app's operation.

Minors and policy changes

The app is intended for users aged 13 and over and is not directed to children under 13. Minor clients and their parents or legal representatives should contact the club about accounts and personal data. Let us know about data collected without any required consent and we will review the request. We will update this policy and its date when features or data practices change, and request additional consent where necessary.