Privacy Policy
Fuel Guard helps you notice fuelling and hydration rhythm. This notice explains what the private beta web app and Garmin apps process, how that information is used, and how to ask for access, correction or deletion.
Fuel Guard is currently a private beta. This policy will be updated if the app's data practices materially change.
Fuel Guard is operated by the Fuel Guard developer for the private beta. It is not a medical service and it is not designed to diagnose, treat or monitor a health condition.
For privacy or deletion requests, use the developer contact email displayed on the Fuel Guard Connect IQ Store listing. Do not include passwords, access tokens or health information in your initial message.
This notice covers the Fuel Guard web app, the Supabase-backed account and sync features, the private beta Garmin Activity Logger and Quick Log apps, and the server endpoint used by those Garmin apps.
The web app can process the information you enter or generate while using Fuel Guard, including:
Fuel Guard does not add calories, food weights, macros, body weight or food-quality judgements to the log model unless you type that information into an optional note yourself.
The private beta Garmin apps may transmit these fuel-log fields to the Fuel Guard endpoint:
If you explicitly enable Garmin health-pattern sharing in Quick Log settings, Fuel Guard may also receive bounded recent Connect IQ-local watch samples, where the device supports them: heart-rate history, stress history, Body Battery history, Garmin resting-heart-rate values, average resting-heart-rate values and high-level recent activity summaries such as activity type, start time, duration and distance. Availability varies by Garmin device.
Pairing/device-token credentials authenticate the request. They are not stored as fuel-log database fields.
Based on the private beta source code, the Garmin apps do not intentionally transmit GPS routes, precise location, raw beat-to-beat intervals, sleep stages, sleep score, HRV Status, Training Readiness, Recovery Time, gender, birth year, height, body weight, passwords, email addresses from the watch, calorie totals, macros, food weights or detailed descriptions of food.
Fuel Guard uses the information to:
Web account sign-up, login, password reset and session handling are managed through Supabase Auth. Fuel Guard's browser code uses the public Supabase anon or publishable key, not a Supabase service-role key.
The Garmin beta uses short-lived pairing plus revocable device tokens. Server-side credentials such as the Supabase secret key are used only by the backend endpoint and must not be placed in browser code, Garmin code or public files.
Fuel Guard processes information so it can provide the beta service you use, keep records synced, maintain account and endpoint security, prevent duplicate submissions, handle requests, and understand whether the private beta is working as intended.
Supabase provides authentication and database storage for account-backed Fuel Guard data. Row Level Security policies are used so authenticated users can access only their own app tables.
Vercel hosts the web app and serverless endpoint used by the Garmin private beta. The endpoint stores Garmin events in Supabase after validating the request.
Garmin and Connect IQ provide the watch platform and app distribution path for the private beta Garmin apps. Garmin Connect or Connect IQ settings may be used to configure the endpoint and beta token on the watch.
The web app can keep local cache data in your browser to support offline use, refresh recovery and syncing when you sign back in.
Fuel Guard relies on cloud providers that may process information in countries where they operate infrastructure or support services. Data transfer details can vary by provider account configuration and service region.
Fuel Guard keeps account-backed logs, targets, planning data and optional Garmin health-pattern samples while your account is active or until you delete entries, clear supported local data, disable/clear supported watch sharing, or ask for account and associated-data deletion. Local browser cache may remain on a device until you clear app data, browser storage or the app's local data controls.
Fuel Guard uses practical security controls for the private beta, including Supabase Auth, Row Level Security on user-owned tables, server-side handling of elevated Supabase credentials, and Garmin event idempotency checks. No internet-connected service can guarantee absolute security.
Depending on where you live, you may have rights to ask for access to your information, correction of inaccurate information, deletion of information, or objection to certain processing. Fuel Guard will review privacy requests in light of applicable law and the private beta's technical capabilities.
Use the contact method above for account-level privacy requests. To help verify the account, contact Fuel Guard from the email address used for your Fuel Guard account where possible. Do not send passwords, access tokens or detailed health information in your request.
Where the app shows delete or undo controls for a log, you can remove individual entries from the app. If you are signed in and online, cloud deletion is sent to Supabase. If you are offline, deletion can be queued locally and synced later.
Use the contact method above to request deletion of your Fuel Guard account and associated cloud data. The request may require account verification before account-backed data is removed.
Fuel Guard is not intended for children. The private beta should be used only by people who are old enough to manage their own app account and understand this notice.
Fuel Guard may update this policy as the beta changes. The effective date and last updated date at the top of this page show when this version applies.