Privacy Policy
This policy explains what Apex collects, why, and what happens to it. It is written to be read, not to be survived.
If anything here is unclear, email support@apextrainapp.com and ask.
Who we are
Apex is a fitness and nutrition tracking app. The data controller is the operator of Apex, contactable at support@apextrainapp.com.
What we collect
You give us this
| Data | Why | Required |
|---|---|---|
| Name | To address you in the app | Yes |
| Email address | To identify your account and let you sign in | Yes |
| Password | To protect your account (stored only as a salted hash — we never see it) | Yes |
| Age, weight, height, activity level | To calculate your daily calorie and macro targets | Yes |
| Biological sex | Improves the accuracy of the same calculation | Optional |
You create this by using the app
- Food you log — names, brands, serving sizes and macros
- Workouts you log — exercises, weights, reps, and how hard a set felt
- Body-weight check-ins over time
- Photos you take of nutrition labels or barcodes, and any profile or cover images you upload
We do not collect
- Location
- Contacts
- Advertising identifiers
- Anything from other apps on your device
Apex contains no advertising and no third-party trackers. We do not sell your data. We do not share it with data brokers.
Where it is stored
On your device, first. Everything you log — food, training, body weight, weekly check-ins — is written to the app's private storage on your phone the moment you log it. The app works without a connection.
Backed up to your account, encrypted. A copy of that history is also stored under your account in Cloud Firestore (Google LLC), so that if you get a new phone, reinstall the app, or sign in on a second device, your history comes back. Only your account can read its backup: it is encrypted in transit (TLS) and at rest by Google, and the access rules allow exactly one signed-in identity — yours — to read or write it. Nobody at Apex reads it; there is no admin view of it. Firebase's own privacy terms apply: https://firebase.google.com/support/privacy
What is backed up: your training blocks, logged sets and volume history, custom exercises and which muscles you told Apex they work, food logs, saved meals and logged days, your meal-timing settings, body-weight readings and check-ins, weekly wellness check-ins and their settings, the names you give your training blocks, and your record of accepting these agreements.
What is not backed up: your subscription (that belongs to your Apple Account and the purchase; use Restore Purchases on a new device), photos, and anything in the food scanner (barcode and label images are processed on the device and not stored).
Firebase Authentication (Google LLC). Your email address and password hash, so you can sign in on more than one device.
Cloud Firestore (Google LLC). Your profile record (name, email, account type, body stats and goal used for macro targets) and the backup described above.
What we send to other services
USDA FoodData Central
When you search for a food, the words you type are sent to the U.S. Department of Agriculture's public food database to look up nutrition information. No account details are attached to that request. Searches are routed through our own server so that our API credentials are not exposed; that server does not retain your searches.
Open Food Facts
When you scan a barcode that USDA does not recognise, the barcode number is sent to Open Food Facts, a public non-profit food database, to find the product. Nothing identifying you is sent. https://world.openfoodfacts.org/legal
Apple
Subscription purchases are processed by Apple. We never see your payment details. Apple tells us only whether a subscription is active. https://www.apple.com/legal/privacy/
Photo and camera access
- Camera — only when you scan a barcode or a nutrition label. Images are processed on your device to read the text and are not uploaded.
- Photo library — only when you choose an image. Selected images are copied into the app's private storage.
You can revoke either permission at any time in iOS Settings; the rest of the app keeps working.
Health data
Apex does not read from or write to Apple Health. The health-related information Apex holds — your weight, body stats, what you eat and what you lift — is what you typed or scanned into it, and it is used only to run the app for you. It is not used for advertising and not shared with third parties.
How long we keep it
For as long as your account exists. Delete your account and it goes — Profile → Delete account. That removes your identity record, erases the app's data on this device, and deletes your backup from Cloud Firestore. Deletion is immediate on our side; Google's systems complete the removal of deleted data within their published windows. It cannot be undone and we cannot recover it for you.
Apple keeps its own record of purchases; we cannot delete that.
Your rights
Depending on where you live, you may have the right to access, correct, export or erase your personal data, and to object to processing.
- Access and correct — most of it is visible and editable in the app
- Erase — Profile → Delete account
- Anything else — email support@apextrainapp.com and we will respond within 30 days
Children
Apex is not intended for anyone under 13, and we do not knowingly collect data from children. If you believe a child has created an account, email support@apextrainapp.com and we will remove it.
Security
Passwords are stored as salted hashes, never as plain text. Traffic to our services and to the food databases uses HTTPS. Your backup is encrypted in transit and at rest and readable only by your own signed-in account. No system is perfectly secure, and we will not pretend otherwise — but we do not store what we do not need.
Changes
If this policy changes materially we will say so in the app before the change takes effect. The date at the top always reflects the current version.