Privacy Policy

Lift Run Fuel · Last updated July 11, 2026

The short version: Lift Run Fuel is a workout tracker that runs on your device. Your training data lives on your own device. If you choose to connect Google Drive, a single backup file is saved to your own Google Drive. We never see your data, never sell it, and there are no ads or analytics.

Who we are

Lift Run Fuel (“the app,” “we,” “us”) is an independent workout-tracking app. If you have any questions about this policy or your data, contact us at liftruntracker@gmail.com.

What data the app handles

The app stores the workout information you enter — exercises, sets, weights, reps, bodyweight, run and cardio logs, and your program settings. This is saved locally in the app’s storage on your device. We do not operate a server that receives or stores your training data.

Google Sign-In and Google Drive (optional)

Connecting Google Drive is entirely optional and only happens if you choose to enable it. When you do:

We request a single permission, drive.file, which lets the app create and manage only the backup file it creates in your Drive. The app cannot see, open, or touch any of your other Google Drive files.
The backup file contains the same workout data described above, so you can sync between devices and restore it.
We do not receive a copy of this file — it stays in your Google account.

Google API Services Limited Use

Lift Run Fuel’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Drive access solely to store and sync your backup file at your request, and for no other purpose. We do not transfer this data to others except as needed to provide that sync, do not use it for advertising, and do not allow humans to read it.

What we don’t do

We don’t sell or share your data. We don’t show ads. We don’t run analytics, tracking pixels, or third-party telemetry. We don’t transmit your training or health data to us or to anyone other than your own Google Drive (and only if you connect it). The only things ever sent to our servers are the specific, momentary requests described in the next two sections — food lookups you type, barcodes you scan, meal photos you choose to analyze, and route-planning requests — and none of them are tied to your identity or stored with your data.

Nutrition lookups, barcode scans & route planning

When you search for a food, scan a barcode, or paste a recipe, the search text or barcode number is sent through our proxy server to nutrition databases (FatSecret and USDA FoodData Central) to fetch nutrition facts. When you plan a running route, the route coordinates are sent through the same proxy to OpenRouteService to compute the path. These requests contain no account identifiers and are not linked to you; results may be cached briefly on our proxy to speed up identical lookups. Your food log itself never leaves your device (except to your own Google Drive backup, if connected).

Photo food estimation (AI)

“Snap a photo” is optional. When you choose it, the photo you take (downscaled) and the optional text hint you type are sent through our proxy server to Google’s Gemini API, which identifies the foods in the image. The AI returns only a plain list of food names and estimated amounts — nutrition numbers still come from the same databases above, and nothing is logged without your review.

Photos are analyzed in memory and never stored — not on your device by us, not on our proxy, and not in any database we control.
Requests carry no account identifiers; the photo is processed under Google’s paid API terms, which do not permit use of the data to train their models.
AI estimates can be wrong — the app always shows the result for you to check and edit before anything is saved.

Third-party services

Google Sign-In and the Google Drive API are used only as described above. FatSecret, USDA FoodData Central, OpenRouteService, and Google’s Gemini API are used only for the momentary, identity-free requests described above. We use no other third-party services.

Apple Health / HealthKit (iOS)

On iOS, the app can — with your explicit permission — read workout and health data from Apple Health (HealthKit), such as runs recorded on your Apple Watch, so you can import them into your training log. If you start a workout from the app on your watch, it may also write that workout session to Apple Health. With sync enabled, the app may also read/write body weight and daily nutrition totals.

Health data is used only inside the app (vitals, readiness, imports, optional write-back).
It stays on your device (and in your own Google Drive backup, if you connect Drive).
We never send Health data to our servers, never use it for advertising or marketing, and never share or sell it to anyone.
You can revoke access at any time in iOS Settings → Privacy & Security → Health.

Health Connect (Android)

On Android, the app can — with your explicit permission — read and (where you enable sync) write health data via Health Connect: steps, active energy, resting heart rate, heart-rate variability (RMSSD), sleep, exercise sessions, continuous heart rate for workout analysis, body weight, and nutrition totals. Wearable apps (Fitbit, Samsung Health, etc.) must share data with Health Connect for those sources to appear.

Health data is used only inside the app (vitals, readiness, imports, optional write-back).
It stays on your device (and in your own Google Drive backup, if you connect Drive).
We never send Health data to our servers, never use it for advertising or marketing, and never share or sell it to anyone.
You can revoke access at any time in the Health Connect app → App permissions → Lift Run Fuel.

Importing from other apps

If you import a CSV file exported from another app (for example Hevy or Strong), that file is read on your device to bring your history into Lift Run Fuel. It is not uploaded to us.

Deleting your data and revoking access

You stay in control of your data:

You can clear the app’s data from within the app or your device settings at any time.
You can disconnect Google Drive in the app.
You can revoke the app’s access entirely at myaccount.google.com/permissions.
Deleting the backup file from your Google Drive removes the synced copy.

Children’s privacy

The app is not directed to children under 13, and we do not knowingly collect data from them.

Changes to this policy

If this policy changes, we will update the date above and post the new version at this URL.

Contact

Questions? Reach us at liftruntracker@gmail.com.