Honedly (“the Service”) is operated by Honedly, LLC (“we”, “us”), an Idaho limited liability company. This policy explains what we collect, how we use it, and the choices you have.
1. What we collect
To run Honedly we collect:
- Account info, email, password hash, optional display name, age, sex, gender, height, profile photo, and bio you provide. If you enable two-factor authentication, we store an encrypted TOTP secret (encryption keys held by us, not by you).
- Onboarding answers, what you tell us when you set up your plan: your goal, goal weight and pace, activity level, diet style and preferred units, and the optional questions about what motivates you, what has got in the way before, how much tracking you've done and which apps you've used. We use them to build your targets and tailor the app to you.
- Health & fitness data, meals, macros, workouts, sets, weights, body measurements, mood, sleep, hydration, fasting, daily notes, and progress photos that you log. If you opt into menstrual cycle tracking, the cycle entries you log.
- Voice journal recordings (Pro+ only), when you record a voice note from the dashboard, we send the audio clip to OpenAI Whisper for transcription. The transcript is kept; the audio clip is retained in our private object storage by default so you can replay it, or discarded immediately after transcription if you turn off audio retention.
- Imports, if you upload an Apple Health export, we read body weight, steps, and (optionally) heart rate from that file. We do not retain the raw file after import.
- Device & usage, basic logs (IP address, timestamps, user-agent) to operate and secure the service. Every authentication attempt (sign-in, sign-up, password reset, passkey use) is logged for forensic and abuse-detection purposes. We do not use third-party advertising trackers.
- Product analytics and error reports, first-party records of how the app is used (for example: the app was opened, a screen was viewed, a meal or workout was logged, onboarding was finished, a subscription started) and of errors and crashes the app or our servers hit. See Product analytics and error reports below for exactly what they contain.
- Push subscriptions, if you enable notifications, we store the browser/device subscription token to deliver reminders.
- Payment metadata, if you subscribe to Pro or Pro+, Stripe stores your card and billing details. We retain only the Stripe customer + subscription IDs and the subscription status (active, past_due, canceled, etc.). We never see or store your card number.
- In-app purchase records, if you subscribe in the iOS or Android app, Apple or Google takes the payment and RevenueCat (see Sharing) tells us about it. We keep which store it came from (App Store or Google Play), the product, its status (active, trial, grace period, expired, etc.), whether it is a trial or introductory period, when it expires, whether it will renew, and the store's transaction id. We never see your card, your Apple ID or your Google account details.
- Corrections to AI photo estimates, when you change what the AI estimated from a meal photo before saving it, we keep what it guessed and what you changed it to (food name, grams and calories). We keep your newest 200 of these for up to 180 days, and send your recent ones along with your future meal photos so the estimates get closer to how you log. They are private to your account: other users never see them and they are not used to change shared food data.
2. How we use it
- To provide the tracking, planning, and analytics features you see.
- To compute estimates like TDEE, calorie burn, PRs, and trends.
- To send notifications you have opted into.
- To secure the service and prevent abuse.
- To understand which features help people stick with their goals (for example, how many new members log a first meal), and to find and fix bugs and crashes.
We do not sell your personal data.
3. Sharing
Your data stays private to your account by default. The only exceptions are:
- Public profile, if you turn on the shareable profile, anyone with the link can see the stats you chose to expose. You control which stats and can disable sharing or regenerate the link.
- Household, if you join a household, members can see shared meal plans, recipes, and pantry items.
- Hosting and infrastructure, the application runs on commercial cloud infrastructure (compute, database, and object storage) in the United States, provided by established U.S.-based vendors under standard data-processing agreements. These vendors host the data; they do not access it for their own purposes.
- Service providers that handle specific user data under contracts limiting them to processing on our behalf:
- Mailgun, transactional email (password resets, verification, household invites, lifecycle drip campaigns, broadcasts).
- Stripe, payment processing for Honedly Pro and Pro+. We never see your card details; Stripe stores them. Stripe shares subscription state with us via webhook (no card data).
- Apple (App Store) and Google (Google Play), payment processing for subscriptions bought in the iOS or Android app. Apple or Google holds your payment details and bills you under their own terms and privacy policies; we receive only the purchase records listed above.
- RevenueCat, manages in-app subscriptions for us. It receives your Honedly account id (a random identifier, not your name or email) and the purchase receipts from Apple or Google, and tells our servers the subscription state. It does not receive your health data.
- Google Analytics (only with your cookie-banner consent, and only on our public pages, never inside your account), aggregate page views and feature usage. IPs are anonymized; no Honedly account identifiers are sent. Decline on the cookie banner, change it later with Cookie settings, or turn on Global Privacy Control or Do Not Track in your browser to keep it off.
- AI subprocessors (Pro and Pro+ features), the AI features in Honedly are powered by two upstream vendors. Free-tier accounts never send data to either.
- Anthropic, processes the text inputs for meal parsing, meal-photo estimates (with your recent corrections to earlier estimates), recipe generation, recipe URL import, weekly coach insights, daily briefs (Pro+), plateau narratives (Pro+), prep plans, restaurant lookups, meal swaps, and the nutrition-label scan. The inputs we send are the specific meal text / image / weekly summary you requested AI on — not your full account history. Per Anthropic's data-processing terms, content sent via their API is not used to train their models. Anthropic retains API content for up to 30 days for safety review, then deletes it.
- OpenAI (Pro+ voice journaling only), processes audio clips you record from the dashboard mic. Used solely for speech-to-text transcription via the Whisper API. Per OpenAI's API data-usage terms, audio sent via their API is not used to train their models. OpenAI retains API content for up to 30 days for abuse review, then deletes it. We delete the audio immediately if you turn off audio retention.
- Wearable integrations you connect, if you link Fitbit, Whoop, Oura, Strava, Withings, Google Fit, Garmin (.fit upload), or Apple Health, we exchange data with that vendor only at your direction. You can disconnect at any time from Settings → Integrations, which deletes the stored OAuth tokens on our side; you may also revoke our access from the vendor's own settings.
- Household members, if you join a household, other members see shared pantry, grocery list, and shared meal plans. If you're the beneficiary of a Pro+ “for two” seat, the payer sees that you're covered (your account name + email) in their billing UI. Per-user meals, workouts, weight, sleep, journals, and Coach memory always stay private to your account.
- Legal, we may disclose information if required by law.
4. Storage and security
Your data is stored in the United States. Account data, logged meals/workouts/weights, and other records live in our managed database; binary uploads (avatars, recipe covers, progress photos, feedback screenshots, voice-journal audio) live in separate object storage, with personal uploads gated behind authenticated access only.
We apply industry-standard security practices: passwords are never stored in plaintext, two-factor authentication and passkeys are supported, sensitive secrets (such as wearable integration tokens and 2FA recovery material) are encrypted at rest, and sessions can be invalidated globally by you or by us in the event of a compromise.
We rate-limit authentication endpoints to slow credential-stuffing attempts. Accounts may be temporarily locked in response to a fraudulent chargeback or other abuse signal; affected users are notified by email and can't be signed into until the issue is resolved. We don't publish further detail on our security implementation here for reasons that should be obvious. No online service is 100% secure.
5. Product analytics and error reports
We measure how Honedly is used with our own first-party analytics. The web app and our iOS and Android apps send events to Honedly's servers, and our servers record some events themselves when the action happens. These records are kept in Honedly's own analytics storage on Cloudflare, the provider that already hosts Honedly, separate from your account data. They are not sent to any third-party analytics, advertising or crash-reporting company, and we never sell or share them.
- What an event contains: the kind of action (for example “meal logged” and how: photo, search, manual), the screen as a route name such as
/meals (never an id, date, token or search query), the platform and app version, the time, and a random session id. Events never contain what you ate, your weight, notes, messages, your email or other free text. - Signed in: events are recorded under a random pseudonymous key rather than your user id, email or name, so we can see things like whether onboarding worked or new features are used. Only our account database can map that key back to your account. Our servers attach it; the apps never send any account identifier. You can opt your account out at any time (see “Opting out” below).
- Signed out (on our website): events are kept only if you clicked Accept on the cookie banner. The browser then keeps a random analytics id so visits before and after sign-up can be connected: when you sign in, we record that this analytics id belongs to your pseudonymous key. The id stays in that browser until you sign out, delete your account, decline analytics in Cookie settings (which deletes it) or clear the site's data. Without that consent, no product events are recorded about your visit (error reports still are, as described next).
- Error reports: when something breaks, the error message, technical stack trace, screen, platform and app version are sent so we can fix it. Emails, sign-in tokens, web addresses' query strings and similar identifiers are stripped before storage. Error reports carry no persistent analytics id; if you're signed in they carry your pseudonymous key, unless your account has opted out of analytics or your browser sends Global Privacy Control or Do Not Track.
- Global Privacy Control / Do Not Track: if your browser sends either signal, our website sends no product events at all and our servers record none for the requests your browser makes. When you use your account in a browser that sends either signal, or create your account with one on, we also remember it: your account is opted out of analytics on every device, as described next, until you opt back in.
- Opting out: your account is opted out of product analytics when you click Decline in Cookie settings while signed in (or, if you declined while signed out, the next time you open your account in that browser), when you turn off Share usage analytics in our iOS or Android app (it takes effect the next time the app is signed in and online), or when your browser sends Global Privacy Control or Do Not Track as described above. From then on we record no product events for your account, from any device, including the ones our servers record themselves (such as a meal or workout being logged) and the subscription milestones (trial started, subscription started or canceled) that reach us from our payment providers, and no daily account snapshot. Error reports are still recorded, because they are needed to keep the service working, but without your pseudonymous key. It can take up to 10 minutes to reach all of our servers. Records made before you opted out are not deleted early; they stay linked to your pseudonymous key and age out on the retention schedule below. Clicking Accept in Cookie settings or turning Share usage analytics back on opts your account back in, unless that request itself carries Global Privacy Control or Do Not Track. While your browser keeps declining (or keeps sending either signal), opening your account there opts it out again.
- Daily account snapshot: once a day we store, under your pseudonymous key, the date you signed up and on which app (web, iOS or Android), your plan and how it's paid for (our website, the App Store, Google Play, a trial or a household), and whether it is one of our test accounts, so we can measure conversion and revenue. It contains no name, email or health data. No snapshot is stored for an account that has opted out of analytics.
- Mobile apps: our apps keep their own random analytics id on your device, which connects events from before you sign in to your pseudonymous key the same way; turning off Share usage analytics in the app's settings deletes it, stops product events from that app and opts your account out (see “Opting out”). Our apps do not use your device's advertising identifier, and we don't combine this data with data from other companies or use it to track you across apps or websites.
- Retention: product events and account snapshots are kept for up to about 13 months (400 days) and error reports for up to 90 days. Older records are deleted by a periodic clean-up, so a record can outlast its limit by a few weeks at most. When you delete your account we immediately delete, from our live account database, the key that links these records to you (database backups keep it for the period described in section 6). From then on the records can no longer be connected to your account through that key, and they age out on the same schedule. The analytics id kept by your browser or by our app is replaced with a new one when you sign out or delete your account (an app does this when it next finds it has been signed out), so if the same browser or app install is later used with another account, your earlier records are not connected to it. Declining analytics in Cookie settings, or turning off Share usage analytics in the app, deletes the id at any time. These records are included when you export your data (except signed-out events from a device that has also been used with another account).
6. Retention
We retain your data for as long as your account exists. When you delete your account, your personal records are removed from our active systems within 30 days. Backups containing your data may persist for up to 90 days before they roll off, after which they are irrecoverable. Product analytics and error reports are kept on the schedule in section 5, and deleting your account unlinks them from you straight away. Corrections to AI photo estimates are deleted after 180 days. In-app purchase records are kept while your account exists so your subscription keeps working; Apple, Google and RevenueCat keep their own records under their policies.
7. Your rights
At any time you can:
- Access & export your data from the Account tab.
- Correct information from the profile and settings pages.
- Delete your account and all associated data from the Account tab.
- Withdraw consent for notifications, public sharing, integrations, or analytics at any time: Cookie settings on the website, Share usage analytics in our apps, or Global Privacy Control or Do Not Track in your browser (see section 5, “Opting out”).
If you reside in the EU/UK/California or another region with data-protection laws, you may have additional rights (e.g., the right to lodge a complaint with a supervisory authority).
8. Cookies and sessions
We use a single first-party session cookie set by our authentication system to keep you signed in, and first-party browser storage for our own product analytics (a per-tab session id, plus a random analytics id only with your cookie-banner consent). We do not use third-party advertising or tracking cookies. See our Cookies Policy for the full inventory.
9. Children
Honedly is not directed to children under 13. If you believe a child under 13 has created an account, contact us and we will remove it.
10. Changes to this policy
We may update this policy. We will note the effective date above and, for material changes, notify you in-app or by email.