What we collect, and what we do not

Encrypted before it leaves your device

What you record in your trackers and your journal is encrypted on your device with AES-256-GCM, and only your devices hold the key. That covers:

• The values you log, and any notes attached to them
• The meals you log, including the foods in them
• Your journal entries
• The names you give your trackers and routines
• How much of a medication you have, and when you last refilled it
• Any emotions you add to your mood tracker yourself
• The symptoms you tag on an entry, and any you add to the list yourself
• Your reminders and workout templates

Your 12-word recovery phrase is what unlocks all of it on a new device. Healthsome never receives that phrase and genuinely cannot recover it for you.

The details on your account (your name, birthday, height and the rest) are a separate matter, and they are not encrypted this way. The next section says exactly what stays readable.

What the server can still see

Some structure has to stay readable, or the app could not sort, filter or remind you of anything. The server can see:

• Your account identifier, and the identifiers of your trackers, entries, and routines
• Timestamps, reminder times and the days they repeat on, and whether a reminder is switched on
• When your routines and habits are scheduled: their time of day, and which days or how many days a week
• Tracker types, Apple Health metric names, goal flags, and whether a tracker offers symptom tags, so a weight tracker is known to be a weight tracker
• The details on your account itself: your name, email, birthday, gender, height, weight and units. These are not encrypted the way your entries are
• Which trackers and tags you have hidden. Hiding a journal tag stores its name in the clear, even though the same tag is encrypted inside the entry

So the server can tell that you logged a sleep entry this morning. It cannot tell what the entry said.

Our servers also keep ordinary web server logs, as any website does: when each request came in, what it asked for, whether it worked and how long it took, your account identifier, and your IP address with the rough location it gives away. We send these logs to Datadog so we can spot errors and outages. Nothing you record is in them.

No ads, and no analytics

There is no advertising SDK and no analytics or telemetry SDK anywhere in Healthsome, on the phone or on the web. Nothing profiles you, nothing follows you between apps, and the iPhone app does not ask for tracking permission because it has no use for it. Your health data is never sold, and never shared for marketing.

We do watch how our servers are doing, from the logs described above: how many requests fail and how long they take. That tells us when something is broken. We never use it to follow what any one person does.

Cookies

This website sets only the cookies needed to sign you in and keep you signed in. There are no advertising cookies and no analytics cookies, so there is nothing here to consent to and no banner to dismiss.

The iPhone app does not use cookies at all. It keeps your sign-in token in the device's keychain instead.

The services we rely on

Running the app means a few companies are involved. None of them can read what you record. The one that sees anything about your health is Edamam, and only the food searches you type, as described below.

• Auth0

  Handles signing in. It sees your email address and the usual login records, such as times and IP addresses.

• RevenueCat and the App Store

  Handle Healthsome subscriptions. They see your account identifier and your purchase history, along with device details Apple provides for billing. No health data goes to either.

• Vercel and MongoDB

  Host the service and store your data. What they hold for the things you log is encrypted, and neither can read it.

• Datadog

  Monitors our servers. It receives the web server logs described above, so it sees request times, IP addresses and the rough location they give, and your account identifier. Nothing you record goes to it.

• Microsoft 365

  Hosts our email. It sees anything you write to us, including a request to see or delete what we hold.

• Apple Health

  Steps, weight, heart rate, sleep and nutrition are read on your device, with your permission, and encrypted like everything else before they are uploaded.

• Edamam

  The food database behind meal logging. When you search for a food or scan a barcode, it receives what you typed or scanned from our server, with nothing that identifies you. It never sees the meals you log.

Two lookups that leave your device in the clear

We would rather tell you about these than let you find them yourself. Each is a request to an outside service that carries no account identifier:

• Weather. If the weather module is on, your device asks Open-Meteo for the forecast at your coordinates. You can switch the whole module off in your account settings, and nothing is requested after that. This one does reveal your IP address to Open-Meteo.
• Food search. When you search for a food or scan a barcode while logging a meal, what you typed or scanned goes through our server to Edamam, the food database we use. Our server passes it on without storing or logging it, and Edamam sees our server rather than your device. The meal you then log is encrypted like everything else.

Questions

If anything here is unclear, or you want to see, correct or delete what we hold, write to hello@healthsome.io. You do not have to wait for us, though. The iPhone app can export a full, readable copy of everything it holds for you, from App Settings, and either app can delete your account outright whenever you like.

The formal privacy policy

Everything above is the plain-language version, and it is the one we would rather you read. The full legal policy lives here too, and nothing in it contradicts this page.