FUEL//TRACK · FuelTrackLLC (a Texas limited liability company) · Effective September 29, 2026 · Supersedes the version effective September 28, 2026
This Privacy Policy explains how FuelTrackLLC ("FuelTrack," "we," "us") handles information in connection with the FUEL//TRACK mobile application (the "App") and our website at fueltrack.llc (the "Site"). FuelTrack is the controller of the limited personal data the App transmits to our servers. The App is designed to be local-first: the large majority of your information is stored only on your device and is never received by us. This policy describes the narrow set of data that does leave your device, your rights, and how to exercise them. It supplements our Terms of Service and EULA.
The following are stored in the web view's local storage on your device and are not uploaded to us: your food and water logs; profile (such as age, sex, height, weight, and goals); body measurements and weight history; workouts; inventory and saved meals; settings; and any health-related inputs you choose to enter into optional modules (for example, diabetes mode and blood-sugar entries, pregnancy status, and menstrual-cycle information). Any values the App reads from Apple Health, and the calories, protein, carbs, and fat it writes back to Apple Health, also stay on your device — see section 11. We cannot see this data. You can export it from the Profile screen at any time. There is no in-app wipe or reset. To delete it, uninstall the App. If you are in a Squad, tap Leave Squad first so your member record is deleted from the server, or email us to ask. Because this data lives on your device, its security depends primarily on your device's own protections (passcode, encryption, biometrics).
| Flow | What is sent | Recipient / purpose |
|---|---|---|
| Food & barcode lookups | The search term or barcode number you enter | Open Food Facts (via our lookup proxy) to return nutrition data. Not tied to your identity. |
| Feedback / bug reports | Only the text you type in the feedback box | A third-party form service (Web3Forms) so it can be emailed to us. |
| Squad (optional) | The handle you choose, the squad name, your logging streak, and your calorie % of target. If you choose, also your protein % and water %. A device identifier stored with those stats. | Our Cloudflare Squad Worker, and shown to other members of your squad. Pick any handle. No real name, email, or account needed. The handle does not need to be a real name, and no account is created. The handle is stored with your streak and calorie % of target (and protein % and water % when you choose them). Your squad always sees your streak and your calorie % of target. Leave Squad, or an email, removes the member record. Not your food log. |
| Squad reports (optional) | The reported handle, member hashes, and any reason you type | Our Squad server, kept for moderation review. The reason is not shown to other squad members. |
| Squad abuse limiting | Your IP address | Stored by the Squad server in rate-limit records to limit abuse. Cleanup runs occasionally and is not guaranteed on a schedule. |
| Subscriptions | Your purchase/subscription status, an anonymous app-user identifier, and a RevenueCat subscriber attribute named saw_paid_beat (a timestamp recorded when you view the plans screen) | Apple processes payment. RevenueCat validates your purchase receipt, tells the App whether your subscription is active, and stores saw_paid_beat. We do not receive your payment-card details. |
| Anonymous usage statistics (optional — in the EEA and UK this is off until you turn it on; elsewhere it is on by default and switchable off at any time) | An event name (for example: the App was opened, a food was logged, a barcode was scanned, or the subscription screen was shown), a random identifier created on your device and hashed before it is sent, a per-launch session identifier, and for some events a small code such as which screen was viewed or how many days have passed since you installed | TelemetryDeck GmbH (our analytics processor) so we can see how many people use the App, whether they keep using it, and which features are worth improving. No food names, weights, calorie figures, targets, handles, or free text are ever included. The identifier is used only for these statistics, is not your Squad device identifier, and is not derived from it, so usage statistics cannot be connected to your Squad membership. You can switch this off at any time in Profile → Anonymous Usage Stats. |
We do not use third-party advertising SDKs, and we do not track you across other apps or websites for advertising. We assign no advertising identifier.
We do not sell your personal information, and we do not "share" it for cross-context behavioral advertising, as those terms are defined under California law. We do not knowingly process the sensitive information you store locally for any purpose other than providing the features you use, and that data is not transmitted to us at all unless this policy says so.
We process the limited data above to operate and secure the App's features you use (food lookups, feedback handling, and the Squad feature), to provide subscriptions through Apple, and to comply with law. For users in the EEA/UK, our legal bases under the GDPR are: performance of a contract (operating features you request, such as Squad and subscriptions); consent (where you opt into a feature that transmits data — enabling Squad, and the anonymous usage statistics described in section 2, which in the EEA and UK are off until you switch them on in Profile → Anonymous Usage Stats), which you may withdraw at any time; and our legitimate interests in maintaining, securing, and improving the App in a privacy-protective way. Outside the EEA and UK the anonymous usage statistics in section 2 rest on that legitimate interest, are never used to identify you, and can be switched off at any time in Profile → Anonymous Usage Stats.
These providers process data only to perform services for us. International transfers (for example, processing on Cloudflare's global network) are conducted under appropriate safeguards where required, such as Standard Contractual Clauses.
On-device data stays in the web view's local storage until you uninstall the App. You can export it from the Profile screen at any time. There is no in-app wipe or reset.
Leave Squad deletes your member record from our server. If that squad then has no members, the squad record, including the squad name, is deleted too. If you uninstall without leaving, your member record stays on the server until you email us and ask us to remove it.
When you report a Squad member, we keep the reported handle, the member hashes, and any reason you typed, for moderation review. We do not apply an automatic deletion period to those records.
Anonymous usage statistics are retained in aggregate by our analytics processor; because they carry no name, account, or contact detail and cannot be linked back to your device by us, they cannot be traced to an individual user.
The Squad server stores IP addresses inside rate-limit records to limit abuse. Cleanup of those records runs occasionally. It is not guaranteed on any schedule, and this policy does not promise a retention window for them.
Lookup requests are processed to answer the search and are not used to build a profile of you. Feedback is kept as needed to address your report. Subscription status and the saw_paid_beat timestamp are held by Apple and RevenueCat; we do not set a retention period for them.
We maintain reasonable administrative, technical, and physical safeguards appropriate to the limited data we handle, consistent with the New York SHIELD Act and similar laws, including transport encryption (HTTPS), access controls, and data minimization. We never receive your food log, weight, or health entries. If you join a Squad, we receive only the daily percentages described above. Your handle, squad name, streak, reports, and IP address in the table above are separate from your food log, weight, and health entries. No method of transmission or storage is perfectly secure.
If you are a California resident, you have the right to: know the categories and specific pieces of personal information we have; delete personal information we hold; correct inaccurate personal information; opt out of any sale or sharing (we do none); and limit the use of sensitive personal information (we do not use sensitive personal information beyond providing your requested features). We will not discriminate against you for exercising these rights. The personal information we hold is Squad records (member rows, squad name, reports, and rate-limit IP addresses) and feedback. RevenueCat holds subscription status and the plans-screen timestamp. To exercise a right, contact justin@fueltrack.llc; we will verify your request and respond within the time the law requires. You may use an authorized agent where permitted.
Subject to applicable law, you may request access to, correction, deletion, restriction of, or portability of your personal data, and you may object to certain processing or withdraw consent (without affecting prior processing). You may lodge a complaint with your local data protection authority. To exercise these rights, contact justin@fueltrack.llc.
The App is not directed to children under 13, and we do not knowingly collect personal information from them (COPPA). For the EEA/UK, the App is not intended for users under 16 without appropriate consent. If you believe a child has provided us information, contact us and we will delete it.
Health-adjacent inputs (such as diabetes, blood-sugar, pregnancy, and cycle data) are stored only on your device and are not transmitted to us. They are not "Protected Health Information" under HIPAA because FuelTrack is not a covered entity or business associate, and you are entering data about yourself. Pick any handle. No real name, email, or account needed. Your squad always sees your streak and your calorie % of target. You choose whether to also share protein and water. The handle and those figures are stored on our Cloudflare Worker. The Squad feature does not send your health entries or food logs.
Apple Health (HealthKit). If — and only if — you turn on the Apple Health integration and grant permission in iOS, the App exchanges a small amount of data with Apple Health on your device. It reads your active energy burned today (counted toward calories burned; we use the higher of that figure and workouts you log, not both) and your most recent body-weight sample (which you can import into a body entry). It writes the calories, protein, carbs, and fat you log back to Apple Health. That exchange happens entirely between the App and Apple Health on your device. We never receive your Apple Health data, it is not sent to our servers or to any third party, and it is not used for advertising or marketing. You can revoke access at any time in the iOS Settings app under Privacy & Security → Health, or switch the integration off in the App under More → Profile.
Our website at fueltrack.llc sets no cookies, shows no advertising, and asks you for no information. It does use Cloudflare Web Analytics to count page views, which loads a small script from static.cloudflareinsights.com when you visit a page. That measurement is cookieless: it stores nothing on your device, does not use cookies or local storage, does not fingerprint you, does not build a profile, and does not follow you to other websites. It reports only aggregate figures such as page views, referring site, browser, and general country — never anything that identifies you. We do not sell or share it. As with any website, your IP address is necessarily visible to our host in the course of delivering the page; it is used to serve and secure the Site, not to identify you. None of this is present in the App.
We may update this policy. Material changes will be reflected by the "Effective" date above and, where appropriate, noticed in the App. Continued use after an update takes effect constitutes acceptance.
FuelTrackLLC · 5900 Balcones Drive Ste 100, Austin, TX 78731, United States · justin@fueltrack.llc
Nutrition data © Open Food Facts contributors, licensed under the Open Database License (ODbL), and USDA FoodData Central (public domain).