Privacy Policy – Healthcount

At Healthcount, your privacy is our priority. We know that logging your health is personal, so we've designed Healthcount to keep your information secure, private, and fully under your control.

No ads, no data sales: your health data is never shared with advertisers or sold to third parties.

Private by default: other members and employers cannot see your entries, and we do not share them unless you export them or choose to share your cycle dates with a partner. Some features send what you enter to OpenAI, which provides the AI model that reads it and writes the reply. Our section on features that use AI lists which ones, and what each sends.

Secure storage: all data is stored with modern encryption and security practices to protect your information.

You're in control: you can export your data at any time, or delete your account if you choose to stop using Healthcount.

Features that use AI

Some parts of the app send what you enter to OpenAI, which provides the AI model that reads it and writes the reply. Your name, email address and account ID are not sent with it. This is what each one sends. It was last reviewed on 27 September 2026.

  • Typing into your diary: the words of each thing you log, with your most recent weight. Anything our own rules can read, such as a weight, a dose or a goal, is not sent. A symptom you type is sent on its own.
  • The daily feedback in your diary: your age, gender, weight and goal; your food and exercise totals for the last 7, 30 and 90 days, and your weight change over 90 days; and everything logged that day, as you wrote it. In food journal only mode it sends your age, gender and the last 7 days of entries as you wrote them, with no weights or numbers.
  • Your guide: what you write to it and up to 10 earlier messages from the same day; your age, gender, height, weight, goal and activity level; your goals, a summary of your weight history and your average macros; the last 7 days of food and a list of up to 50 foods you have logged; today's diary in the order you wrote it, the notes you wrote in the last 7 days and the hunger and thoughts you noted after meals, all in your own words; your medication plan, last 20 doses and next dose date; up to 50 symptoms with how bad they were; your last 6 period dates; how you said you felt in check-ins; and the names of your saved meals. In food journal only mode it sends no calorie or macro figures. When your guide looks something up to answer you, what it finds is sent too: up to 14 days of diary entries and notes, weights, doses with the injection site, and symptoms.
  • Meal photos: the photo, and then the name and amount of each food found in it.
  • Fridge meal ideas: the photo of your fridge or the list you type, with protein and fibre targets worked out from your last 7 days of food and your gender. In food journal only mode the targets are left out.
  • Naming a saved meal: its ingredients.
  • Voice input in the diary: on iPhones and iPads, and in browsers that cannot turn speech into text themselves, the recording is sent to OpenAI to be written out. Other browsers do this with their own speech service, which the browser's maker runs, not us.
  • The macro calculator: the foods you type into it.

OpenAI's published policy for its API says data sent through it is not used to train its models unless the customer opts in, and that by default it is kept for up to 30 days to check for misuse, longer only where the law requires it or where that is reasonably necessary to protect its services or anyone else from harm. It is on OpenAI's data controls page.

The Ask AI assistant on our public pages is covered separately below.

Cookies and similar technologies

This section lists what this website stores on your device or reads from it, and what needs your permission first. It was last reviewed on 14 September 2026.

Set without asking

  • Sign-in cookies (names starting sb-): if you log in, they keep you signed in as you move between pages. They come from Supabase, which runs our login and database.
  • region cookie: remembers which version of our content to show (UK, US, Ireland or Australia). It is set on your first visit from the country your connection appears to come from, changes if you pick another region, and lasts a year. If you pick a region yourself, a second cookie, region_pref, and healthcount_region in local storage record that you chose it, so we stop going by your connection. The cookies last a year. The local storage entry stays until you clear it.
  • consent_analytics cookie, and healthcount_consent_analytics in your browser's local storage: remember your answer about analytics cookies, and the local storage entry the date you gave it, so we do not ask on every page. Your answer lasts a year, and then we ask again.
  • Vercel Web Analytics, a page-view counter from our hosting provider, is loaded on every page. It does not set cookies or store anything on your device.

Kept on your device by the app and our tools

These are stored without asking too, because the features they belong to need them. They stay in your browser, apart from diary lines waiting to be saved, which go to your account when you are back online.

  • Your offline diary (a database in your browser called healthcount-offline): anything you log in your diary with no connection is kept here until it is saved to your account. It also keeps a copy of the last two weeks of your diary, updated each time the diary loads, so the diary opens with no signal. A copy more than 14 days old is not shown. This is health data. It is deleted when you sign out with a sign-out button in the app, or delete your account. If something has not been saved yet, signing out says how many entries and asks before deleting them. It is not deleted when your sign-in simply runs out, so those entries can still be saved when you next sign in.
  • A copy of the app for use offline (a service worker, with caches called healthcount-shell-v1 and healthcount-static-v1): once you have opened a page you need to be signed in for, your browser keeps a copy of the diary page, the offline page, our icons and the files the site runs on, so the diary opens with no connection. None of your entries goes into these caches. They are deleted when you sign out or delete your account. The service worker itself stays until you clear this site's data in your browser.
  • Small settings in local storage. Signing out does not remove these. Clearing this site's data in your browser removes all of them.
    • hc-hero-segment: which audience you picked on the home page.
    • hc_macro_calc_v1: the foods you add to the macro calculator, with their calories and macros, so the list is still there when you come back.
    • hc_onboarding_step: how far you got through setting up your account. It is removed when you finish.
    • signup_firstName and signup_lastName: until August 2026 our sign-up page kept your first and last name here until your profile was saved. It no longer does, and removes them if they are still there.
    • hc_beacon_schedule: puts a dot on the Schedule tab after you set up your account. It is removed when you tap Schedule in the menu at the bottom of the screen.
    • hc_coach_seen: that you have opened your guide, so its button stops pulsing.
    • dose_banner_dismissed_date: the day you last closed the dose reminder banner in your diary.
    • drift_prompt_dismissed_date, drift_prompt_paused_until and drift_prompt_dismiss_count: when you last closed or paused the prompt that suggests a check-in, and how many times in a row you closed it.
    • hc_diary_checkin_prompt_handled: followed by a date: that you have dealt with that week's check-in prompt in your diary. Only the latest one is kept.
    • hc_eating_support_signpost_shown_on: the day your diary last showed you where to get support with eating, so it appears at most once a week.
    • hc_guides_email_given: that you have already given your email for one of our free PDF guides, so the next one downloads without asking again.
    • hc_founding_members_joined and hc_founding_members_dismissed_until: that you joined the founding members, or until when you asked not to see the box, so it does not keep appearing.
    • diaryEntriesUpdated, medicationEntriesUpdated, weightEntriesUpdated and activityEntriesUpdated: the time of your last change of that kind, and nothing else, so other Healthcount tabs you have open know to refresh.

Only if you accept analytics cookies

Nothing in this group runs until you press Accept in our banner. If you reject, or never answer, none of it loads.

  • Google Analytics (Google): counts visits and shows us where visitors come from and which pages they read. It sets cookies named _ga and _ga_ followed by a code. We use Google's consent mode in its basic form: until you accept, the Google Analytics script is not loaded at all, so nothing is sent to Google. Accepting turns on analytics storage only. The advertising settings in Google's consent mode stay off.
  • PostHog (hosted in the EU): records which parts of the site and app are used, including clicks. It records no words from the page or from what you click, and it makes no recordings of your screen. It keeps an identifier in a cookie or local storage entry whose name starts with ph_.

Grow by Mediavine, on our public pages

Grow is a reading tool from Mediavine that lets you save articles and see related ones. It runs on our public pages, apart from these, where it is never loaded:

Grow decides for itself what it may store. If its location check places you in the UK or the European Economic Area, it stores nothing on your device and records no visit unless you have given consent through an industry-standard consent tool (the IAB Transparency and Consent Framework). This website does not use one, so for visitors there Grow stores nothing.

Elsewhere, including the US, Canada and Australia, Grow keeps an identifier in your browser's local storage and a small cookie called growme_version, and sends Mediavine information about your visit. Once Grow has loaded, it stays loaded until the page is reloaded. So if you follow a link from a page where it has loaded into the app, or to one of the pages listed above, Grow stays loaded in the background with its buttons hidden. Opening or reloading one of those pages directly means Grow does not load at all. Mediavine explains what it does with this information in its legal and privacy centre.

Changing your choice

You can accept or reject analytics cookies here at any time. Rejecting takes effect straight away: Google Analytics and PostHog stop on the page you are on, the Google Analytics cookies on this website are deleted, and PostHog is told to stop recording.

 

You can also clear cookies and site data in your browser's settings. If you do, we will ask again on your next visit.

When you fill in a form

This covers the forms on our public pages: requesting a pilot, the employer policy starter pack, the printable dose chart, the employer cost calculator, price-drop alerts, the free PDF guides on our blog and the founding members box on our dose calculator pages. It was last reviewed on 27 September 2026.

What we keep

  • Requesting a pilot: your name, email address, organisation and message.
  • The policy starter pack, the dose chart and the cost calculator: your email address and which of these forms you used. The figures you type into the calculator stay on your screen and are not sent to us.
  • Price-drop alerts: your email address, the medicine and dose you picked, and your price limit if you set one.
  • The free PDF guides: only if you choose to leave it, your email address and which guide you were reading. The download never needs one.
  • Founding members: your email address, the page you were reading, where you said you are with treatment if you picked one, and whether you said you would be happy to talk to us.

With each one we keep the date and time you sent it. It is saved in our database, which Supabase runs for us.

Who sees it, and what we use it for

Each time you send a form, a copy is emailed to our team through our email provider, so we can read it and reply to you personally. Sending a form does not email you anything automatically. We use what you send only to get in touch with you personally and, for price-drop alerts, to send the alerts you asked for once they start. They are not running yet. If you leave your email on a free guide or join the founding members, the form says we may email you now and then about Healthcount: that is what we do with those addresses, and we stop as soon as you reply to ask, or email anna@healthcount.app. If you said you would be happy to talk, we may email you to arrange it. We never sell your details.

How long we keep it

We keep it in our database until you ask us to delete it, which you can do by emailing anna@healthcount.app. If you delete your Healthcount account, anything sent through these forms with the same email address is deleted from our database too.

The copy emailed to our team is separate, and deleting your account does not remove it. It stays in our team mailbox until we delete it there. If that email could not be sent at the time, the details are sent to our team later in a daily summary email, which stays in the mailbox in the same way. To have your emailed copies deleted as well, email anna@healthcount.app.

Healthcount Weekly, our email newsletter

If you sign up for Healthcount Weekly, this is what happens. It was added on 5 October 2026.

What we keep

  • Your email address, which edition you signed up for (for example the US one), the page the sign-up box was on, the exact words you agreed to, and the date and time of each step: when you signed up, when you confirmed and, if you do, when you unsubscribed. We also note which issue we last sent you and when, so nobody gets the same issue twice.
  • Nothing about your health. The sign-up doesn't ask which medicine you take. The page the box was on (for example a Wegovy dose chart) only tells us which pages people sign up from.

How it works

  • After you sign up we send one email asking you to confirm. Until you tap the link in it, we send you nothing else, and if you never tap it we do not email you again.
  • Once you confirm, you get a welcome email and then one email a week. Every email has a link that unsubscribes you in one click.
  • We send these emails through MailerSend, our email provider, and keep the list in our database, which Supabase runs for us. We never sell your address or share the list with anyone else.

How long we keep it

While you are subscribed. If you never confirm, we keep the address marked as unconfirmed and send nothing more. If you unsubscribe, we keep your address marked as unsubscribed so that we never email you by mistake. To have it deleted completely, email anna@healthcount.app. If you delete your Healthcount account, a newsletter sign-up with the same email address is deleted too.

Emails we send to members

If you have a Healthcount account, we send you one kind of email through our email provider. Nothing in it is advertising. It was last reviewed on 19 September 2026.

  • The weekly summary: once a week, a short recap of your week in the app: your weight, how many diary entries you made, the symptom you noted most, whether a dose was logged and your weekly check-in. You can turn it off in Settings.
  • It has a link to stop it, and you can also turn it off in Settings.

The Ask AI assistant

The Ask AI button on our public pages opens a chat assistant. This is what happens to what you type into it. It was last reviewed on 14 September 2026.

What we keep

  • Each question you ask, the answer you were given, the page you asked it on, and the date and time.
  • Email addresses and phone numbers are removed from questions and answers before they are saved. Anything else you type, such as a name, is saved as you wrote it, so please leave personal details out.

What we do not keep

We do not save your IP address or any account details with your questions, even if you are logged in. Our server does use your IP address, in its memory only and never saved, to stop any one connection sending too many questions.

Who sees it

To write each answer, your question and the earlier messages in the same chat are sent to OpenAI, which provides the AI model. This happens before anything is removed, so OpenAI receives exactly what you typed.

Our team reads the saved questions, including in a daily summary emailed to us through our email provider, to see what people want to know and to improve the answers.

How long we keep it

We keep saved questions in our database for up to 12 months.

The daily summary emailed to our team includes each question and its answer, and those emails are not covered by the 12 months: they stay in our team mailbox until we delete them there. We do not save your IP address or account with a question, so we cannot tell which ones are yours. If you want one deleted from both, email anna@healthcount.app with what you asked and roughly when.

Healthcount is built as the simplest way to track your health, and we believe simplicity applies to privacy too. No hidden terms, no complicated opt-outs, just clear and transparent practices.