Privacy policy
Last updated 4 October 2026
Squeeze.fit is a body composition, training and nutrition app. Its body scan, physique analysis and every calculation run on your phone. This policy describes what the app and this website do with information. The short version: your photographs never leave your phone, we run no servers that receive your data, and the only network connection the app makes is an optional backup to your own Google Drive.
What the app stores on your phone
- Your profile: height, year of birth, the equation variant, your goal, sports, training days and time, and favourite foods.
- Your measurements: weights, circumferences, skinfolds, body fat estimates and any reference results you enter.
- Your training: logged sets, sessions and the physique scores from each scan.
- Your scan photographs: encrypted, and described in full below.
- Your settings: theme, sound and screenshot preferences.
All of it is written to an encrypted database in the app's private storage, which other apps cannot read. Deleting the app deletes the data on the phone with it.
Photographs
Scan photographs are analysed on your phone by models built into the app. They are saved so you can look back at them, encrypted with a key held in your phone's secure hardware, and they do not appear in your gallery. Photographs are never uploaded, including to your Google Drive backup. Deleting a measurement deletes its photograph.
The camera permission is used only while you take a scan photo or photograph a gym machine. You can pick an existing photo instead.
Google sign in and Drive backup (optional)
You can sign in with your Google account to back up your data. If you do:
- The app receives your Google account's name and email address, to show which account is signed in.
- It asks Google for the
drive.appdatapermission only. This lets the app read and write a hidden folder in your own Google Drive that only Squeeze.fit can see. It gives no access to any other file in your Drive. - The backup contains your profile, measurements, training logs, plans and settings. It does not contain photographs.
- The backup is sent directly from your phone to Google over an encrypted connection. It is stored in your Google account, subject to Google's privacy policy. We do not receive a copy and cannot access it.
If you do not sign in, the app makes no network connections. To stop backing up, choose Sign out in the app. To delete the backup, open Google Drive, go to Settings, then Manage apps, find Squeeze.fit and choose Delete hidden app data. You can also remove the app's access at myaccount.google.com/permissions.
Purchases
Purchases are handled by Google Play. We receive confirmation that a purchase was made, never your payment details.
What we do not do
- No analytics, telemetry, crash reporting or usage tracking.
- No advertising and no advertising identifiers.
- No servers of our own that receive your data, and no accounts with us.
- No selling or sharing of data with anyone.
Sharing, when you choose it
The celebration screen has a Share button. It hands a short text summary (body fat percentage, entry count and days tracked) to Android's share sheet, and you pick where it goes. No photograph or measurement history is attached.
This website
This site serves static pages. It sets no cookies, runs no analytics and embeds no third party scripts. Our hosting provider processes standard request logs, such as IP address and user agent, to serve pages and prevent abuse.
Children
The app is not intended for children under 13, and the body composition equations it uses are not validated for them.
Your rights and deleting your data
Your data lives on your phone and, if you choose, in your own Google Drive. You can delete everything on the phone by deleting the app or clearing its storage in Android settings, and delete the backup as described above. We hold no copy to disclose, correct or delete.
Changes
If this policy changes, the revised version will be published here with a new date, and material changes will be noted in the app's release notes.
Contact
Questions about this policy can be raised as an issue on the project's GitHub repository.