What Fitly stores, and why.

Who provides Fitly

Fitly is provided by Fitly. This page describes what the service actually does with your information. It is written plainly on purpose; if something here is unclear, ask.

What we store

• Account: your email address and a hash of your password (Argon2id). The password itself is never stored.
• Nutrition records you choose to save: foods, recipes, diary entries (with the nutrition they had when logged), planned future days and recurring meal schedules. Grocery lists are calculated from those records when you ask for one; they are not stored as separate editable checklists.
• Preferences: your targets, units, timezone and week start.
• Basic usage metadata: timestamps and activity counters on your account, such as when it was created and last used.
• Browser sessions: a digest of your sign-in credential, the browser’s user-agent string, and created, last-seen and expiry timestamps, so you can see and end sessions. The credential itself lives in one HttpOnly cookie set by the Fitly API on its own host (api.getfitly.app), sent only to that host; this website cannot read it. The website keeps a single non-secret flag in your browser’s local storage that records whether you recently signed in, so the menu can show “Your account” without contacting the API; it grants nothing and is cleared when you sign out.
• Assistant connections: which assistant clients you granted access to, the permission level, when the grant was made and when it expires. Tokens are stored only as digests.
• Change receipts: a record of what an assistant changed on your behalf, so you can check it.
• Support correspondence: what you send to [email protected], and our replies. That address is forwarded by Cloudflare Email Routing to a Google-hosted mailbox used by the operator, so Google processes support email under its own terms. Support email is kept separately from the nutrition database and is never joined to your records.
• Operational logs and error reports: may contain your IP address, the route requested, timing, account identifiers and error details. Routine API request logs are configured to record metadata only, without request or response bodies or query strings, and error reports sent to Sentry are configured to strip headers, cookies, bodies and query strings. Exception messages and the logs of our infrastructure providers can still carry additional diagnostic context. Passwords and session credentials are never written to logs by Fitly’s code.

The services that run Fitly

Fitly runs on a small number of infrastructure providers, each of which processes data only to run the service:

• Cloudflare serves this website, handles its DNS and TLS, and routes email sent to the support address. Requests to the website pass through Cloudflare’s network, which sees your IP address and the pages you request.
• Google hosts the mailbox that receives forwarded support email, and nothing else.
• Oracle Cloud Infrastructure hosts the Fitly API and delivers transactional email, such as password reset messages. Fitly does not send marketing email.
• PlanetScale hosts the PostgreSQL database that stores your records and keeps its own restricted backups of it under its separate operational retention.
• Sentry receives error reports from the API for monitoring. Those reports may include account identifiers, the route and timing of the failed request and the error itself; the request context sent with them is configured to exclude bodies, query strings, headers and cookies.
• Your assistant’s provider (OpenAI for ChatGPT, Anthropic for Claude, xAI for Grok) is chosen by you. When you connect an assistant, it reads and writes your Fitly data under the permission you granted, and your conversation with it is held by that provider under its own terms. Fitly does not receive your conversations; it receives only the requests the assistant makes to it.
• No payment provider is used. Fitly is free during the beta and collects no payment information. If paid plans are introduced, payments would be handled by a hosted payment provider and Fitly would store only a customer reference and subscription status; this page would be updated first.

What we do not do

• Fitly has no advertising and does not sell your data or share it with third parties for their own purposes.
• Fitly does not run its own AI model over your data. The assistant you connect does the talking and the looking up; Fitly keeps the records you or it save.
• Fitly does not calculate or recommend nutrition targets and does not give health or medical advice. The numbers you enter are yours.

Retention and deletion

Your records stay in your account until you change or delete them. Detailed change receipts are compacted after 14 days to a short summary digest, which is kept until you delete your account. Browser sessions that have expired or been ended are removed by routine maintenance.

Deleting your account (Security → Delete account) removes your active application records from the live database immediately: foods, recipes, diary, schedules, settings, sessions, assistant connections and any billing references. Copies may persist for a limited time in database backups, restricted operational logs and provider records. Those are kept under separate operational and legal retention, are restricted to recovery and operational use, and are not accessible through the service.

Fitly’s own API backups keep the three most recent copies and replace the oldest whenever a new one is made, so their retention is a count of backups rather than a fixed number of days. Backups kept by PlanetScale are managed by that provider under its own operational retention.

Deleting your Fitly account does not delete the copies of your conversations that your assistant’s provider holds. Manage those with the provider.

Your controls

• Revoke an assistant’s access at any time; it stops working immediately.
• End browser sessions, change your password, or delete your account. Changing or resetting your password also signs out every connected assistant.
• Change your targets and preferences, or ask your assistant to.
• For other privacy requests about your account, contact [email protected].

Security

Connections to the website and the API use HTTPS. Passwords are hashed with Argon2id; sign-in credentials and assistant tokens are stored only as digests; sign-in, registration and recovery are rate limited. No system is perfectly secure, and this page will be updated if the way Fitly protects your data changes.

Changes

This page describes current processing and will change as the service does. Changes are posted here with a new effective date.

Contact

[email protected]