Privacy Policy

1 · The short version

• We collect what it takes to run a food tracker with an account: your email, your food log, the targets and settings you choose, any check-ins you record, and your subscription status.
• We don't sell your data. There are no ads in Likely, no advertising SDKs, and no third-party analytics trackers.
• Your data goes only to service providers needed to run Likely — hosting, sign-in, subscription management, and website delivery — and to an AI assistant only if you connect one yourself.
• You can export the product and account data described in section 6. Account deletion removes your identifying details and product content; section 7 explains the limited pseudonymous, subscription, audit, and billing records that remain.
• Questions, requests, complaints: support@likely.fit. A human reads it.

2 · What we collect

Account

Your email address and sign-in credentials. If you use Sign in with Apple or Google, we receive the identifier (and email) those providers share; your password, if you use one, is handled by our sign-in provider. We also keep a security log of sign-in events (time, method, and technical details such as IP address) to protect your account.

Your food log and health data

What you log is the product, and it stays yours: foods, portions, and the details you refine; custom foods and saved baskets you build; your targets, goals, and settings; answers you give to in-app guidance questions; and progress check-ins you choose to record — such as body weight, other measurements, and notes. We treat all of this as sensitive. It is never used for advertising and never sold.

Purchases

Subscriptions are billed by Apple or Google when you subscribe through their stores. We receive subscription status — plan, trial state, renewal and expiry times, and purchase identifiers — through RevenueCat, our subscription-management provider. Web subscriptions are not currently offered. If that changes, we will name the checkout provider and update this policy before it receives payment details. Likely does not see or store your full card number.

Support and feedback

If you email support or send feedback from the app, we keep the messages and anything you attach so we can help you and fix what's broken.

Product analytics — first-party and bounded

When product analytics collection is enabled for an app release, Likely uses two separate first-party channels. Conversion-funnel events are tied to your Likely account and record bounded categories about onboarding, subscription, and feature flows; they do not contain food or log identifiers, nutrition or body values, or free text, and source rows age out on a rolling 90-day horizon. Product-health events (for example: a search happened or an error occurred) use coarse feature, timing, platform, and app-version categories and are stored under an HMAC-derived key instead of your raw account ID. Internal product-health reporting applies a minimum aggregate group size of 25 accounts. Neither channel is sent to a third-party analytics or advertising service; it is stored with the core infrastructure providers listed below.

What stays on your device

Camera and photo access exist for one purpose: scanning food barcodes when you ask to. Barcode images are decoded on your device and are not uploaded. Reminders you turn on (like a trial-ending reminder) are scheduled on your device. Sign-in tokens are kept in your device's secure storage.

Website

likely.fit is a static site: no analytics scripts, no advertising pixels, and no tracking cookies. Our infrastructure providers process standard server logs (IP address, requested page) to serve the site and prevent abuse.

3 · How we use it

• To run Likely: storing your log, computing your ranges and guidance, syncing your account across devices.
• To handle your subscription: knowing whether your trial or plan is active, and sending account and billing email. We send transactional email, not marketing lists — if we ever add a newsletter, it will be strictly opt-in.
• To keep accounts safe: sign-in security logging, abuse and fraud prevention, rate limiting.
• To understand activation and subscription flows: bounded, account-attributed funnel events that show where people leave a flow without recording food-log content or free text.
• To improve reliability and features: coarse, HMAC-keyed product-health events and aggregate, k-anonymized reporting — never individual browsing of your food log.
• To comply with law when we genuinely must.

We do not use your data to train AI models, and we do not build advertising profiles.

4 · Who touches your data

We use service providers acting on our instructions to run Likely. Our current core providers are:

• Supabase — sign-in identity and our hosted database infrastructure.
• Render — hosting the authenticated Likely API that the apps use.
• RevenueCat — subscription state for store purchases.
• Apple and Google — sign-in when you choose it and billing for purchases made through their stores, under their own terms and privacy policies.
• Cloudflare — website hosting and delivery, plus private storage for feedback attachments when the hosted service is configured to use Cloudflare R2.
• Google Fonts — typeface delivery on likely.fit; your browser sends standard network information such as IP address and user-agent data when requesting those files.

Web subscriptions are not currently offered. Before adding them, we will identify the payment processor here and at checkout. We otherwise disclose data only if the law compels it, to protect against fraud or abuse, or — if Likely LLC is ever acquired or merged — to a successor bound by this policy, with notice to you. We do not sell personal data, and we do not share it for cross-context behavioral advertising. If our provider lineup changes, we will update this policy.

5 · Connected AI assistants

Likely lets you bring your own AI assistant. That connection is yours, not ours:

• If you copy a Likely prompt (or your own data) into an AI assistant, that assistant's provider processes it under their terms — the same as anything else you paste into it.
• If you connect an assistant to your Likely account, it can read and write your data only within the scopes you approve, and we record the grant and its use in your security log. You can revoke a connection from Connected agents in the app. If that screen is unavailable, email support@likely.fit from your account address and we'll revoke it for you.

Likely itself sends nothing to any AI provider. Data moves to an assistant only when you move it, or when a tool you connected requests it under your grant.

6 · Export, correction, deletion

• Export. You can request a portable, machine-readable file containing the account and product data covered by our export: profile details, security history, your log, custom foods, targets, settings, check-ins, feedback, and account-linked analytics events. It does not include sign-in credentials, secret internal token records, subscription state stored by Likely, or records held separately by Apple, Google, RevenueCat, or other providers.
• Correction. Your log is editable in the app; anything you can't fix yourself, we'll fix for you.
• Deletion. Deleting your account removes your identifying profile fields and deletes your food log, custom foods, targets, check-ins, settings, feedback, and account-linked analytics source events from our live systems. We also ask Supabase to delete the hosted sign-in identity. We retain a pseudonymous Likely user and provider-identity tombstone, subscription state, and a deletion audit event; those records no longer contain your email, display name, or food-log content. Deleting Likely does not cancel a store subscription.

Use the app's account settings, or follow the steps on our account deletion page. You can also email support@likely.fit from your account address and we'll do it with you. We don't charge for any of this, and we don't treat you differently for exercising your rights.

7 · Retention & security

We keep your data while your account exists. When you delete your account, the identifying fields and product content listed in section 6 are removed immediately from our live systems. The limited pseudonymous account, identity, subscription, and deletion-audit records described there remain while needed for security, subscription reconciliation, and legal or accounting obligations; Apple, Google, and RevenueCat keep their own billing records under their policies. Short-lived backups age out within a bounded window. Aggregated, k-anonymized statistics that do not identify you may persist.

In transit, your data is encrypted with TLS. Access to production systems is restricted and logged. Product-health privacy-unit keys are HMAC-derived; conversion-funnel events remain account-attributed as described above. Sign-in tokens live in your device's secure storage. No system is breach-proof, and we won't pretend ours is — if a breach ever affects your data, we'll notify you as the law requires, and plainly.

8 · Your regional rights

Depending on where you live, the law gives you specific rights over your data — access, correction, deletion, portability, objection, and restriction among them. Likely's answer everywhere is the same: the controls in section 6 are available to everyone, no residency test applied.

European Economic Area & UK. Our legal bases are: performing our contract with you (running Likely), legitimate interests (security, abuse prevention, aggregate product analytics), consent (optional features like notifications and AI connections), and legal obligation (billing records). You may complain to your local supervisory authority, though we'd appreciate the chance to fix it first.

California. We collect the categories described in section 2 (identifiers, commercial information, app activity, and health information you volunteer), for the purposes in section 3, shared only as described in section 4. We do not sell personal information and have not in the preceding 12 months, and we do not share it for cross-context behavioral advertising. You have rights to access, delete, correct, and port your data, and to not be discriminated against for using them — see section 6.

Likely is operated from the United States, and your data is processed in the United States and other countries where our providers operate — data-protection laws there may differ from your own country's.

9 · Children

Likely is for adults. You must be 18 or older to use it, and we do not knowingly collect data from anyone under 18. If we learn we have, we delete it. If you believe a minor has an account, tell us at support@likely.fit.

10 · Changes & contact

If we change this policy, we'll update it here and change the effective date at the top. If a change meaningfully reduces your privacy, we'll tell you in the app or by email before it takes effect — no quiet edits.

Likely LLC · Wyoming, USA
support@likely.fit