Legal

Privacy Policy

Your entries stay on your phone and are never sent to us. Here is exactly what our server does keep, who can reach it, and how to delete it.

Version 3.1 Effective 29 October 2026 English · Български

The short version

We know most people don't read privacy policies. Here's the honest summary before the full document — and everything in it is explained properly, with the reasons, further down.

  • Your entries stay on your phone, and only there. Your moods, diary, food and movement log, goals, onboarding answers and profile settings are stored on your phone and are never sent to us. This changed in version 3.0. From September to October 2026 earlier builds of the app copied them to a server we run; that copy is being removed (see the last point below). Section 3.
  • We cannot see your entries, and we cannot get them back for you. If you uninstall the app, clear its data or lose the phone, they are gone. Android's own automatic backup is switched off for Health Path, so they do not go into your Google account either. The only copy you can make yourself is the PDF from Account → Reflect & share, which goes only where you send it. Section 7.
  • What our server does hold is your account, not your entries: your email address, your name, a hash of your password (never the password), your sign-in sessions, a few timestamps, and — only if you buy a plan — which plan you have and any withdrawal you made. It also sees your IP address while you are connected, and uses it only to stop password guessing, in memory. Section 2.
  • Because your entries never reach us, we do not process them as their controller. They are health data by nature, and we say so (Section 4), but the law's special rules for health data bind whoever receives and handles it. That is no longer us. It does not make us careless with what we do receive.
  • Where the server is: Bulgaria. It is a computer in the EU. It belongs to Petar Kirilov, not to the owner: he runs it as a processor for the owner, with administrator (root) access and a key that opens our encrypted off-site backup, which sits on a second computer in Sofia. Section 3.
  • We don't sell your data, share it, or hand it to advertisers. There is no advertising and no tracking in the app. The only analytics is an optional switch, off until you turn it on, that counts app opens and tabs shown (Section 3). The only emails we send are about your account — a password-reset code, a code to confirm your address, and a warning before an unused account is deleted — plus, if you buy a plan, a confirmation of it, and of a withdrawal if you withdraw. Section 2. Anything you write to support@healthpathapp.com is kept in our Google Workspace mailbox, which Google runs for us as our processor. Sections 2 and 12.
  • If you buy a plan, you pay Google, not us. Google takes the payment and we never see your card. We keep only which plan you have and when it ends. Section 12.
  • You can delete your account, and it really is deleted. Manage Profile → Delete profile removes your account and every row belonging to it from the server immediately, and clears the entries from your phone. Section 9 covers what backups mean for that.
  • If you stop using Health Path, we delete your account for you. An account with no sign-in for 12 months is deleted. Section 15.
  • If you used an earlier build that synced: on the day this version takes effect we delete your entries from our live database. The copy on your phone is not touched. Copies in older backups leave as the backups roll over, which takes up to 14 days for the daily ones, about 30 days for the encrypted off-site ones, and longer for a third kind kept by count rather than age. Section 15.
  • The honest risk of this design is the opposite of version 2's: lose your phone and you lose your entries, and there is no one to ask. This version trades convenience for privacy, and you should know which one you're using. Section 7.

If that's all you needed, you can stop here. If you want the details — what exactly is stored, why, what your rights are, and how to reach us — read on.

1. Who we are

Health Path is made and published by Gabriela Stancheva, a private individual based in Bulgaria. There is currently no registered company behind the app — it is published by one person, in their own name.

We want to be upfront about what that means, because it's a genuine trade-off and you should understand it:

  • What it means for you: there is one accountable person you can contact, whose real name is given below, and who is personally and legally responsible for how this app handles your information.
  • What it means for us: publishing under a personal name rather than a company means the owner carries this responsibility personally, without the liability protection a registered company would give them. We mention this not because it changes your rights, but because we think you should know who you're actually dealing with.

Contact for anything related to privacy or your data:

Who else is involved. The server is administered by Petar Kirilov, who acts as a processor for the controller (Article 28 GDPR), not as a second owner of the app. What that means, and what is and is not yet on paper, is in Sections 3 and 5.

Do we have a Data Protection Officer?

No, and on today's facts the law does not require one. A Data Protection Officer is mandatory for organisations whose core activity involves processing special-category data (which health data is) on a large scale — the wording is Article 37(1)(c) GDPR, and the examples the regulators give are hospitals, insurers, and large advertising networks.

In version 2 this was a closer question, because Health Path held health entries centrally. From version 3.0 it is not: the entries stay on the user's phone, and what the server holds — an email address, a name, a password hash, a plan record — is not special-category data on its own, and it is held for a small number of people on a single machine. The test is therefore not met on either limb.

We still watch the threshold. If Health Path ever receives health data again, or grows to the point where its processing could fairly be called large-scale, the question gets asked again and this section gets rewritten.

2. What the app stores, and why

Health Path keeps two separate kinds of information, in two separate places. Your account — who you are to the server — is stored on Health Path's server, described in Section 3. Your entries — everything you write or tick in the app — are stored only on your own phone, inside a private storage area that Android reserves for this app and that other apps cannot read, and are never sent to us. The table marks each row with where it lives. This is the complete list — there is nothing else the app collects that isn't in this table.

"Kept until you delete your account" below is also subject to the 12-month inactivity rule in Section 15: if you don't sign in for a year, we delete the account ourselves.

What it isWhy it existsWhere it livesHow long it's keptHow to delete it
Account email addressYour username, and the address the account emails below are sent toServer; also on your phone, because the app shows it; passed to Resend each time an email is sent to youUntil you delete your accountManage Profile → Delete profile
Name given at sign-upShown back to you in the app, and used in the inactivity warning email. If you later change your display name in the app, that change stays on your phone and the server keeps the name from sign-upServer + phoneSame as aboveSame as above
PasswordTo confirm it's you when you sign in. Stored only as an argon2id hash on the server, never as text, and not stored on your phone at all — see Section 10Server only (as a hash)Same as aboveSame as above
Sign-in sessionKeeps you signed in for up to 90 days without retyping your password. The phone holds the token; the server holds only a one-way hash of it, with the random device identifier below and when the session was created, last used and expiresPhone + server (hashed)The session stops working after 90 days or when you sign out; its record stays on the server until you delete your accountSign out ends it; delete your account removes the record
A device identifierA random value generated on your phone at install. It names the phone, not you. It is sent when you sign up or sign in and is stored with the session record. It is no longer used for anything else, because entries are no longer synchronisedPhone + serverUntil you delete your account (uninstalling the app only removes the copy on the phone)Delete your account
Password-reset codeThe six-digit code for the "forgot password" flow, stored as a hash, with a 15-minute expiry and a five-attempt limitServer only (as a hash)The code works for 15 minutes; a used or expired record stays on the server until you delete your accountDelete your account
Email-confirmation codeThe six-digit code (and matching link) in the "Confirm your email" message, stored as a hash, with a 48-hour expiry and a five-attempt limit. The record also holds the address that was being confirmed, as readable textServer onlyThe code works for 48 hours; a used or expired record stays on the server until you delete your accountDelete your account
Whether your email address is confirmed, and whenSo the app stops asking you to confirm itServerUntil you delete your accountDelete your account
Account timestamps: when the account was made and last changed, and when you last signed inThe last sign-in is the clock for the 12-month inactivity rule (Section 15). Whether your founding year (Section 12) is running is worked out from the date the account was made; nothing more is stored for itServerUntil you delete your accountDelete your account
When an inactivity warning was sentSo nobody is sent the same warning twice, and so no account is ever deleted under the 12-month rule without one (Section 15)ServerUntil you next sign in, or you delete your accountSigning in clears it and the 12-month clock starts again; or delete your account
Google account id — only if you use "Sign in with Google"So that next time you sign in with the same Google account, we know it is you. It is Google's number for your Google account, not your email address. Google also gives us your email address and name, which become the rows above (Section 12)ServerUntil you delete your accountDelete your account
Your plan — only if you buy oneThe purchase token Google Play gives for your subscription, which plan it is (monthly or yearly), its state, when the current period ends and whether it renews — so the app knows whether adding entries is open to you. Also the date our server first saw the purchase, which is the day your 14-day right to withdraw is counted from, and when the confirmation email for it was sent. No price, no order number, nothing about how you paidServer; checked with Google (Section 12)Until you delete your accountDelete your account. This does not cancel the subscription — cancel it in Google Play
Account reference — only if you buy a planA one-way code made from your account's internal id, given to Google with each purchase so our server can confirm the purchase is yours. Not your email address or nameCalculated when needed; kept by Google with the purchaseAs long as Google keeps the purchase, under its own policyNot something we can delete — it is in Google's records
A withdrawal — only if you withdraw from a planThat you withdrew: which purchase, when, and whether Google refunded it. Kept so we can show that your withdrawal was received and handled, and so the same plan is not refunded twice. No order number and no amount are stored. The name and address you give in the withdrawal statement are not stored either; they go into the acknowledgment email and a note to our support mailbox (below)ServerUntil you delete your accountDelete your account
The emails themselves, as sentResend keeps a record of each account email it delivers: the address, the subject, the message (which contains the code, or for a warning your display name and a date, or for a plan email the plan, its dates and the Google Play order number) and whether it arrivedResend30 daysNot individually deletable — it expires by itself
Your IP address, and the email address or account being triedSeen by the server the way it is by any website you visit. Held briefly, in memory only, to stop someone guessing passwords or hammering the sign-up route; and written into Cloudflare's own edge logs (Section 12)Server, in memory + CloudflareFor the length of the rate limit it counts towards, at most an hour; gone when the server restarts. Cloudflare's own retention for the edge logsNot individually deletable — it isn't stored against your account
Mood entries (Journal check-ins and the Calendar's daily mood, and the reasons you tag them with)The core of the app — a private, personal mood log for your own reflectionYour phone only. Never sent to usUntil you delete the entry, the profile, the app's data or the appDelete the entry directly; or Manage Profile → Delete profile, which clears all of them from the phone; or uninstall / clear data
Diary notes (free text you write, and their titles)A private space for you to write, for yourselfYour phone onlySame as aboveDelete the note directly; or as above
Food-group log (which of the five groups you ate from each day, and optional grams/calories if you've turned that on)To let you look back at your own eating pattern, without judgementYour phone onlySame as aboveDelete the entry; or as above
Movement entries (which of the five activity groups you ticked on a day)Same purpose — your own record, no scoringYour phone onlySame as aboveDelete the entry; or as above
Custom foods, custom activities and custom activity groups you've addedSo something you typed in can be placed into a group and logged like any otherYour phone onlySame as aboveDelete the entry; or as above
Goals you've selected ("My Goals") and your onboarding answers (including what you said you'd like support with)To show your chosen intentions back to you, and to personalise which parts of the app are shown to you, e.g. seeding your goals listYour phone onlySame as aboveManage Profile → Delete profile; or uninstall / clear data
Profile settings: display name as shown in the app, avatar choice, numbers preference, reminder settings, the onboarding-complete flag and similar small internal switches, and the record of which privacy notices you have seen and acknowledgedSo the app looks and behaves the way you set it. The avatar is one of seven bundled images, never a photo you upload. The numbers preference (whether grams/calories are shown at all) is an opt-in switch, off by default. Reminders are scheduled by your phone, not sent by us — we never push a notification to youYour phone onlySame as aboveChange them in settings; or as above
The "Reflect & share" PDF — only when you make oneA PDF summary of entries you choose, to read or to hand to someone you chooseYour phone only, in the app's private cache, until you close the preview; then wherever you send itDeleted from the cache when you close the preview. What you send is held by whoever you send it to, under their rulesClose the preview; delete it where you sent it

Recipients: Cloudflare, Inc., Resend (Plus Five Five, Inc.) and Google, and nobody else outside the owner's own arrangements (below). Cloudflare carries the encrypted connection between your phone and our server. Resend delivers the four kinds of account email described below, so it receives your email address and the message itself — never your password or anything you wrote in the app. Google receives, only if you buy a plan, the account reference above, and our server asks it about your purchase. (If you use "Sign in with Google", it is Google that tells us about you, not the other way round.) Section 12 explains exactly what each of them can and cannot see, and why Google, unlike the other two, is not our processor for Google Play and sign-in. Mail sent to support@healthpathapp.com — by you, or by our server on a withdrawal — is held by Google in our Google Workspace mailbox, where Google acts as our processor (as described below). Beyond that, nothing in this table is disclosed, sold, or transmitted to any other company, service, or person. There is no analytics company (the optional usage counts in Section 3 go to our own server, not to another company), no advertiser, no crash-reporting vendor, and no other app or partner receiving any of it. Your entries are not on this list at all, because they never leave your phone.

Who can reach it on our side: two people. The app's owner, named in Section 1, and Petar Kirilov, who administers the server: he runs it, installs updates, and holds administrator (root) access to the machine and a key that opens the encrypted off-site backup (Section 3). There are no employees, no other contractors, and no support team with a login. There is no admin screen in the app or on the website that displays anybody's data; reading it would mean opening the database by hand on the machine itself. What that database holds is the account data in the table above, not your entries. We say that not because it is impressive but because it is the truthful answer to "who could look?".

What happens if you don't provide something: an account email, name, and password are required to create and sign in to an account at all — without them, you can't use the app. Everything else in the table above is optional: if you simply never use a feature, the only consequence is that the corresponding part of the app (Journal, Diary, Food or Movement) has nothing to show you — nothing else about the app is affected.

You need an account to use Health Path, and creating one includes acknowledging where your entries live. Your account itself — email, name, password — is stored on our server as soon as you sign up. Your moods, notes, food, movement, goals and onboarding answers are not: they stay on your phone, and the separate tick box at sign-up, "I agree to saving my health data", is now an acknowledgement of that, not a consent to server storage — see Section 4.

What we do not collect, anywhere, ever: your location, your contacts, photos from your camera roll, your device's advertising ID, browsing history, or any information about how you use other apps. The app has no permission to access any of these, and no code that would even try.

On "why does the app need my email?" — it is your username, it is how you get back into your account if you forget your password, and it is the address we send account emails to. We never use it to market to you, we do not add you to any list, and we do not give it to anyone other than Resend, which delivers those emails for us.

The only emails Health Path sends, all from no-reply@healthpathapp.com:

  1. A password-reset code, when you ask for one on the "forgot password" screen. It works for 15 minutes.
  2. A code to confirm your email address, when you sign up or ask for a new one. It works for 48 hours. Confirming is optional — nothing in the app is locked if you don't — but an address you have confirmed is the one we can trust to help you back in.
  3. A warning before an unused account is deleted, about 11 months after your last sign-in and again about two weeks later (Section 15).
  4. A confirmation of your plan, and of a withdrawal. If you buy a plan, we email you a confirmation of it: the plan, the start date, the price as Google Play showed it in the app (or, if Google cannot tell us, the standard price in euro, with a pointer to Google's receipt), the Google Play order number, our name and address, a note about the 7-day trial, the full information about your 14-day right to withdraw with the last day to use it, and the model withdrawal form. If you withdraw from a plan with the button in the app, we email you an acknowledgment at once, to the address you gave in your withdrawal statement, whether or not your account's address is confirmed — you typed or confirmed it a moment earlier: your name, the plan and its start date, the order number if Google gives us one, that address, the date and time you sent the statement, and either "refunded in full" or "we will refund within 14 days". Consumer law requires both emails, and they are meant to be records you can keep, which is why they carry those details; both are in English and in Bulgarian. We put the order number, your name and the address into them when we send them, and do not store them. The plan confirmation goes to your account's address; the app only offers a plan to buy once that address is confirmed.

Separately from those four, when you withdraw from a plan our server also sends a note to ourselves, at support@healthpathapp.com, through Resend like the emails above. It is not a message to you. It contains your account's email address, your withdrawal statement (your name, the plan and its start date, the address you gave for the acknowledgment, and the date and time), the Google Play order number, whether Google refunded the payment automatically or it has to be refunded by hand, and whether our acknowledgment to you went out. It is our copy of your statement. Our server does not keep a copy of it.

Where mail to support@healthpathapp.com goes. Every email sent to that address — a message you write to us, and this note from our server — goes to the owner's Google Workspace mailbox, run by Google (Google Cloud EMEA Limited). For Workspace, Google is our processor: it holds that mail for us under Google's Cloud Data Processing Addendum, which we have accepted, and may not use it for its own purposes (Section 12). From 20 October 2026, mail to that address no longer passes through Cloudflare or a personal Gmail account; between 14 August 2026 and that day it was forwarded by Cloudflare Email Routing to the owner's personal Gmail account, where Google acted as its own controller. Please still do not put health details in an email to support unless you need to. If you want to withdraw from a plan, the button in the app (Account → Your plan) does not need you to write to us, though our server still sends us the note described above.

That is the complete list. No newsletters, no tips, no "we miss you", no marketing of any kind. The messages contain no tracking pixel, and the logo is attached to the email itself rather than loaded from a server, so opening one tells nobody that you did.

3. The server: what it is, where it is, and what reaches it

Version 2 of this policy described a server that held a copy of your entries. Version 3.0 describes a server that does not. We are going to be exact about what it still does.

The app has permission to use the internet, and it uses it to talk to one place: a Health Path server. Apart from Google, when you use "Sign in with Google" or buy a plan through Google Play, it talks to nothing else. It does not use that connection for your entries.

What stays on your phone

  • Every entry you make is written to your phone and read back from your phone, and goes nowhere else. Nothing waits for the network, and nothing is queued to be sent later.
  • The only things that need a connection are the account itself — creating an account, signing in, resetting a password, confirming an email address, deleting the account — and, if you use them, buying or withdrawing from a plan.

What is sent to the server, and when

Only what the account needs, and only when you do something that needs it:

  • Signing up or in: your email address, your name (at sign-up), your password (which the server turns into a hash and does not keep), the random device identifier, and, with "Sign in with Google", the token Google gives the app.
  • Changing or resetting a password; confirming your email address: the password, the code or link, and your email address.
  • Plans: the purchase token and plan Google gives the app; the price as the app showed it (used once, in the confirmation email, and not stored); and, if you withdraw, the name and email address you type into the withdrawal statement (not stored; Section 2).
  • Asking whether adding entries is open to you: only your sign-in token.
  • Deleting your account: the request, with your sign-in token.

Nothing in your Journal, Diary, Food, Movement, Goals or Profile is in any of these. The server has no place to put it and no route that accepts it.

Older builds. Builds of the app before 1.0.0+7 still try to synchronise. The server now answers every such request with "gone" (HTTP 410). It does not read, store or return the entries those builds send; they are discarded on arrival. They do pass through Cloudflare on the way (Section 12). Updating the app stops this.

Where the server is, and who runs it

It is a computer in Bulgaria — inside the EU — that belongs to Petar Kirilov, who runs and physically controls it for the app's owner. Health Path does not rent space from Amazon, Google, Microsoft or any other cloud provider. The database is an ordinary PostgreSQL database on that machine, and it holds the account data listed in Section 2.

Petar Kirilov administers the machine. He runs it, deploys updates to it, and has administrator (root) access, which means he could open the database and read what is in it. He also holds a key that decrypts the off-site backup copy described below. He does this as a processor for the controller (Article 28 GDPR): on the owner's instructions, for the purposes in this policy, and not for himself. See Section 5, which also says what is not yet on paper.

The machine has no port open to the internet. Instead it dials outwards to Cloudflare, and Cloudflare passes requests back down that connection. In practice this means there is no door on the server for someone on the internet to try the handle of. Section 10 covers what that does and does not protect you from, and Section 12 covers what Cloudflare can see.

The server does not keep a request log. Its access log, which used to write the IP address of every request to the machine's system journal, is switched off. IP addresses are used in memory for rate limiting and then forgotten (Section 2). Log lines written before that change remain in the journal until it rolls over (Section 15).

Backups of the account data

The account database is backed up so that a disk failure does not destroy every account. There are three kinds of copy, and Section 15 says how long each lasts:

  • A daily copy on the server itself, readable only by administrators.
  • An encrypted copy of each daily copy on a second computer, a shared machine in an office in Sofia, Bulgaria. It is encrypted on the server with a public key before it leaves (using age), so that machine holds only files it cannot read. The key that opens them is held by Petar Kirilov, and copies of it are also kept on the server itself and in his own backups, so the encryption protects the files on the second computer, not against someone with administrator access to the server.
  • A copy taken before a server update that changes the layout of the database, kept on the server, readable only by administrators.

They contain the account data. Backups made before this version took effect also contain the entries of anyone who used a build that synchronised; Section 15 says how long those last.

Usage statistics (optional, off until you turn it on)

Health Path can count how the app is used, so that we can see whether it is used at all and which parts. This is off by default. Nothing is counted or sent unless you open Account → Usage statistics and turn the switch on.

If you turn it on, the app sends:

  • how many times the app was opened that day, and how many times each of four tabs (Home, Food, Journal, Account) was shown — nothing else is counted;
  • a random code the app makes on your phone. It is not your account, your email, your device's identifier or your advertising ID;
  • the app's version number, and the date the server received it.

It never sends anything you write or log, any health information, your account or email, your device model, or your location. The counts are not linked to your account: the request carries no sign-in, and the server cannot tell which account, if any, a code belongs to. Your IP address reaches the server as it does with every request, and is used only by the rate limiter (Section 2); it is not stored with the counts. We still treat the counts as personal data, because a random code on one phone is a pseudonym, not nothing.

When it is sent: when the app goes to the background. If the connection fails, that batch is dropped and not retried.

Turning it off: use the same switch. The app then asks the server to delete everything sent under that code, and throws the code away, so turning the switch on again starts from nothing and cannot be joined to the earlier counts. If your phone cannot reach the server at that moment, the request is not repeated, and what was sent stays until it reaches 400 days (Section 15). Uninstalling the app does the same as that: the counts are kept until 400 days and cannot be tied back to you.

Our basis is your consent (Article 6(1)(a) GDPR), which you can withdraw at any time with the switch. Not turning it on costs you nothing: the app works the same.

What is never sent, from the app or the server

  • No analytics unless you switch it on. The app contains no crash-reporting tool, no advertising software and no tracking code. The one exception is the optional usage statistics described in the previous subsection, which are off until you turn them on. With that switch off, we do not measure which screens you open or how long you spend in them.
  • No location, contacts, photos, camera roll, advertising ID, or browsing history. The app has no permission to reach any of them and no code that would try.
  • None of your entries is sent to us, or to any third company. The list of who receives anything is in Section 2 and has three names on it: Cloudflare, which carries the connection; Resend, which receives only your email address and the account emails we send you; and Google, which receives a one-way account reference if you buy a plan. (Mail to support@healthpathapp.com is held by Google as our processor, as Section 2 explains; it contains only what you choose to write to us, and our server's note on a withdrawal.)

Sharing your history. Account → Reflect & share can make a PDF summary of the entries you choose and open Android's share sheet. The PDF is made on your phone and goes only where you send it; we never receive it. A temporary copy sits in the app's private cache and is deleted when you close the preview. Once you send it, the person or app that gets it holds it under their own rules. It is also the only copy of your entries you can make.

The honest consequences of this design

  • A lost or replaced phone loses your entries. There is no copy on our server, no copy in your Google account (Section 7), and no way for us to restore one. We would rather say that plainly than let you assume a safety net.
  • We cannot read your entries, and neither can anyone who breaks into or seizes our server. They are not there. What such a person could reach is the account data in Section 2.
  • The account data is still on one machine. It is one computer in a home, not a data centre, with no standby machine and no failover. An encrypted copy of each daily backup is kept on a second computer (above), but it cannot take over. If the server goes down — a power cut, a failed disk — your entries on your phone are untouched, but signing in, creating an account, confirming an address, buying or withdrawing from a plan and receiving account emails wait until it is back.
  • Two people can technically read the account data: the owner and the administrator. We don't, there is no feature anywhere that does, and no automated process looks at it beyond what the account needs — but we would rather say it than say "nobody could".

Why there's no cookie-banner-style pop-up in this app

Some apps and most websites show you a pop-up asking you to accept cookies, or something like them, before you can use them. Health Path doesn't show anything like that, and we'd rather explain why than leave you wondering if we simply skipped a step.

That kind of pop-up exists for a specific reason: to ask your permission before something outside your control — usually another company — reads or writes information on your device for a purpose that isn't strictly needed to give you the feature you asked for, often for tracking or advertising. Health Path doesn't do that. Everything the app stores on your device (Section 2 above) is written and read only by the app itself, and only for the feature you're actively using — your mood entries so the Journal can show them back to you, your diary text so it's still there next time you open the app, and so on.

The rule exempts storing things on your device when it is strictly necessary to provide the service you asked for. Everything the app writes to your phone is in that category: the entries themselves, the sign-in token that keeps you signed in, and the device identifier. None of it is advertising, none of it is tracking, none of it is read by another company, and none of it follows you anywhere. What this paragraph is about is only the narrow cookie-style rule, and that one genuinely has nothing here to ask you about.

4. Is this "health data" under the law? Yes — and why that no longer makes us its controller

Under EU data protection law, certain categories of personal information get extra legal protection because of how sensitive they are — this includes information about your physical or mental health. It doesn't need to come from a doctor to count: a pattern of entries that reveals something about your mental or physical state counts too.

We have thought about this carefully rather than taking the easy route of calling it ordinary "lifestyle" information, and our honest conclusion about what the entries are has not changed:

  • Your mood entries (Journal and Calendar) are health data. A recurring, dated record of how you're feeling is exactly the kind of thing this protection exists for.
  • Your diary text is health data, and arguably the most sensitive thing in the app, because it's free text — you could write about anything, and for many people using an app built for food guilt and body image, that will include exactly the things this protection is meant to cover.
  • Your food-group log is health data too, even without calories switched on. Given what this app is for — supporting people who struggle with restrictive eating — a record of what you did and didn't eat over time is capable of revealing something about your relationship with food.
  • Your onboarding answers about what you'd like support with, and the goals you select are health data too: choosing one discloses something about your relationship with food or your body.
  • Your movement log is treated the same way. On its own it is thin, but next to a food log in an app about restrictive eating, a record of exercise can reveal the same thing the food log does.

What changed: we no longer receive any of it

In versions 2.0 to 2.5 these entries were copied to our server, so we processed them, and we asked for your explicit consent to do it. From version 3.0 they are stored only on your phone and are never sent to us. The special rules for health data — the need for explicit consent, a data protection impact assessment, the strictest security duties — bind whoever receives and handles the data. We do not receive it: we cannot see it, copy it, analyse it, back it up or recover it. An app that only keeps its user's own entries on the user's own phone, with its maker having no access to them, makes its maker the supplier of software, not the controller of those entries. That is our reading of the law, and it is why we no longer ask for your consent to something we do not do.

We want to be careful about how far that claim goes:

  • It is our reading, not a promise that no law touches the app. The law about apps and software, about consumers, and about Google Play still applies to us.
  • It does not mean we are careless with what does reach us. An email address belonging to someone who uses a mood and food app can say something personal about them. We treat the account data in Section 2 with that in mind: we never use it to market to you, we put no health detail in any email, and we ask you not to put any in an email to support.
  • It does not mean the entries are safe from everyone. They are on your phone, readable by anyone who can unlock it, and by anything you send them to (Section 10).

What the tick box at sign-up now means

Since 13 September 2026 the sign-up screen has two tick boxes, both starting empty. The first accepts the Terms and this Privacy Policy. The second, "I agree to saving my health data," used to be your consent to server storage. From version 3.0 it is an acknowledgement, and it says three things: your entries stay on this phone only; nobody else, including us, can see them; and they are lost if the app is uninstalled or the phone is lost. It is not a consent to anything, because there is nothing for you to consent to on our side.

  • The underlined words open a short explanation of exactly that. Reading it does not tick the box.
  • Without that box, no account is created. We want everyone to have read the one fact that matters most in this version: nothing here can be recovered.
  • The acknowledgement is recorded on your phone, with the date and time you ticked it and the version of this policy in force. We do not receive it and cannot show it back to you. The records of the consents you gave under versions 2.0 to 2.5 were stored on our server with your profile and are deleted with it (Section 15).

Your account email and name are not health data — they're ordinary account information, handled under a different (lighter) legal basis explained in Section 6.

5. Which law applies, and who is responsible

EU data protection law (the GDPR) applies to Health Path's account data, and the app's owner — named in Section 1 — is the "controller". That means one identified person in Bulgaria is legally answerable for what the server holds and does: your email address, name, password hash, sessions, plan and withdrawal records, and the emails we send.

The administrator. The server is run for the controller by Petar Kirilov, with administrator (root) access to the machine and a key to the encrypted off-site backup. He processes account data only on the controller's instructions: he is a processor under Article 28 GDPR, not a second controller.

Entries on your phone. Version 1.0 said the law covers storing information on a device, and that the person who decides what an app collects is its controller whether or not they ever see the result. For entries that are never sent to us, we now take the narrower position set out in Section 4: we are the supplier of the software, and you are the person keeping your own diary on your own phone. Section 4 says how far we think that goes.

Three obligations belong to the data we do hold, and we would rather name them than let them sit unstated:

  • A duty to keep it secure, in a way that can be judged — Section 10.
  • A duty to tell you, and the Bulgarian supervisory authority, if it is ever breached — within 72 hours of us becoming aware. Section 10.
  • A duty not to keep it forever — Section 15.

Bulgarian law applies alongside the GDPR, and the Bulgarian supervisory authority (the КЗЛД, contact details in Section 9) is the one that oversees us. If you live elsewhere in the EU or EEA, you can go to your own country's authority instead.

6. Why we're allowed to process each type of data (legal basis)

WhatWhy we're allowed to process it
Account email, name, password hash, sign-in session and device identifier, confirmation state, account timestampsPerformance of our contract with you (Art. 6(1)(b)) — you asked for an account, and these are what an account is made of
Google account id, if you use "Sign in with Google"Performance of our contract (Art. 6(1)(b)) — you chose to sign in that way, and the id is how we recognise you
Your plan, and the account reference given to Google with a purchasePerformance of our contract (Art. 6(1)(b)) — you bought a plan, and these are how we give you what you paid for and make sure a purchase is credited to the right account
The plan confirmation and withdrawal acknowledgment emails, the withdrawal record, and the note to our support mailbox about a withdrawalLegal obligation (Art. 6(1)(c)) — consumer law requires us to confirm a distance contract on a durable medium, to take and acknowledge a withdrawal, and to be able to show we did — and performance of our contract (Art. 6(1)(b))
Your IP address and the email or account being tried, held briefly by the rate limiterOur legitimate interest (Art. 6(1)(f)) in stopping password-guessing and bulk fake sign-ups. This is the narrow security case the law expressly contemplates (Recital 49), and the data is not linked to your account or kept
The account emails (reset code, confirmation code, inactivity warning) and the record that a warning was sentPerformance of our contract (Art. 6(1)(b)) — they are part of running an account, and the 12-month rule is a term of the account (Terms, Section 11)
Messages you send to support@healthpathapp.com, and our repliesPerformance of our contract, or steps you ask for (Art. 6(1)(b)) when it is about your account or a plan; otherwise our legitimate interest (Art. 6(1)(f)) in answering you
Withdrawal emails kept for 5 years (Section 15)Legal obligation (Art. 6(1)(c)) to be able to show a withdrawal and a refund, and our legitimate interest (Art. 6(1)(f)) in defending a claim
Optional usage counts under a random code (app opens, tabs shown), only if you switch them on (Section 3)Your consent (Art. 6(1)(a)) — the switch is off until you turn it on, and turning it off withdraws the consent and deletes what was sent
Counts of website page views (Cloudflare Web Analytics, Section 11)Our legitimate interest (Art. 6(1)(f)) in knowing which pages are read; it sets no cookie and does not identify you
The “Get launch news” list (Section 11)Your consent (Art. 6(1)(a) GDPR; Art. 6 of the Bulgarian Electronic Commerce Act), given by ticking the box
Your email and password when you delete your account on the website (Section 11)Performance of our contract (Art. 6(1)(b)) — they are how we confirm the request is yours
Mood entries, diary text, food and movement log, goals, onboarding answers and profile settingsNone needed — we do not process them. They are stored on your phone and never sent to us (Section 4)

On backups, which are a processing operation in their own right: the account database is backed up so that a disk failure does not destroy every account. The basis is the same as for the data being backed up, and the retention is in Section 15. Backups made before version 3.0 took effect also hold the entries of people who used a build that synchronised; they are kept only until they roll off, and nothing is done with them in the meantime.

"Legitimate interest" appears in four rows of that table, and nowhere else. It is a basis that lets an organisation weigh its own interests against yours and decide in its own favour, so we use it only where the interest is narrow and the data small: the rate limiter (keeping other people out of your account; the data is held for minutes to an hour), answering your messages and being able to defend a claim about a withdrawal, and counting page views without identifying anyone. If you object to any of these uses, write to us and we will tell you honestly what would change (for the rate limiter, the answer is that the protection would weaken, not that we would refuse).

We do not use any of your data for advertising, and we do not build a profile of you to predict or influence your behaviour. Nothing in the app makes an automated decision about you.

7. Android backups, lost phones — please read this section

Android phones normally back up the data of the apps on them into the owner's Google account. Health Path switches that off for itself.

This is not a setting you have to find. The app tells Android, in its own configuration, not to include Health Path's data in either kind of transfer Android offers:

  • Backups to your Google account (the "Back up to Google Drive" feature). Your diary text, mood history and food log are never copied there.
  • Phone-to-phone transfer, the copy Android offers to make when you set up a new device. Health Path's data is excluded from that too.

In version 2 we kept this off because our own server was the backup, and we preferred one backup we could describe and be held to over a second one in an account we cannot see. In version 3.0 there is no server copy, so there is no backup at all. Android's backup stays off for a different reason now: leaving it on would put your diary into a Google account without your ever having chosen it, which is the opposite of what this version promises.

What this means for you in practice

If you uninstall the app, clear its data, factory-reset the phone or lose it, your entries are gone, and neither we nor anyone else can bring them back. That is the price of keeping them only where you are.

  • Uninstalling the app does not delete your account. It removes the entries and the copy of your sign-in on that phone. The account stays on the server until you delete it — use Manage Profile → Delete profile before uninstalling if you want it gone, or write to us afterwards. Deleting the profile from the app clears the entries from the phone as well.
  • A new phone starts empty. You can sign in with the same account, but there are no entries to come back.
  • The only copy you can make is the PDF from Account → Reflect & share. It is a summary of the entries and dates you choose, for reading or for handing to someone you trust. It is not a backup the app can restore from. Make one before you change phones if you want to keep what you've written.

If you have already used an older version

Health Path has had Android's backup switched off since its first public release, so there should be no old backup of it in your Google account. If you are ever unsure, your Google account's own backup settings will show you what it holds for each app, and you can delete it there. We have no access to that and cannot do it for you.

If you used a build between September and October 2026 that synchronised, a copy of your entries was on our server. We delete it from the live database on the day this version takes effect, and your phone is not touched. Section 14 and Section 15 say what that leaves behind in older backups.

8. Children and age

Health Path is intended for people 16 years old and up. This is our own choice — it's stricter than the minimum Bulgarian law itself would require for this kind of service, which is 14 — but we think 16 is the right floor for an app that deals directly with body image and food guilt.

What we do about age: the app does not ask for your age and does not check a document. By creating an account you tell us, as the Terms (Section 4) say, that you are at least 16, and we have no way to verify it. If we learn that someone under 16 is using Health Path, we close the account and delete the data attached to it within 5 working days. We say this openly rather than implying an age check exists when it doesn't.

The risk is smaller than it was in version 2, and we are not going to claim it is gone. A child who uses the app now has their diary on their own phone, not on our server. What reaches us is the account data in Section 2 — an email address, a name, a password hash — and the emails we send. It is still personal data of a person we did not verify.

Where consent comes in. We ask consent for two things: the website's launch-news form (Section 11), whose box says “I am 16 or older”, and the optional usage statistics in the app (Section 3), which are off until you switch them on. Bulgarian law (Art. 25в of the Personal Data Protection Act) lets a child give valid consent to an online service from the age of 14, so our 16 is stricter; we do not knowingly take anyone's consent, or email address, from under 16.

If you are a parent or guardian and believe someone under 16 is using Health Path, you (or they) can delete the account directly in the app (Manage Profile → Delete profile) — that erases it from our server and clears the entries from the phone. You can also write to support@healthpathapp.com and we will delete the account and confirm when it's done. We will not ask for proof of anything before deleting a child's account.

9. Your rights, and how they actually work here

Under data protection law you have a set of rights over your personal data. They apply to the data we hold — your account data — and, for your entries, the honest answer in most rows is that we do not hold them. Each row below says what we actually do.

RightWhat it meansHow it works for Health Path
Access — see what's held about youAsk what data is processed about youYour account email, name and plan are visible in the app (Profile, Account → Your plan). For the rest, and for a written confirmation of what our server holds about you, write to support@healthpathapp.com and we will answer within one month with the whole of it, not a summary. Your entries are not on our server, so there is nothing of them to give you; they are in the app, on your phone.
Rectification — correct wrong dataFix inaccurate informationEdit any entry directly in the app, any time; it exists only on your phone, so there is no second copy to correct. The server holds the name from sign-up and your email address, and the app has no screen to change either on the server: write to support@healthpathapp.com and we will correct them.
Erasure — delete your dataHave your data deletedUse Manage Profile → Delete profile. It clears your entries from the phone and deletes your account from our server — every row belonging to you is removed from the database at that moment, not flagged as hidden and not queued for later. Three caveats we would rather state: the backups in Section 15 keep a copy of the account data until they roll off — up to about 14 days on the server, about 30 days for the encrypted off-site copy, and longer for the copies taken before a database change, which are counted by number rather than age; Resend keeps its copy of the emails we sent you for 30 days (Section 12); and mail you sent to support is in our Google Workspace mailbox for the periods in Section 15. If any of these matters to you, say so and we will tell you exactly where you stand. For an individual entry, delete it in the app.
Restriction — limit processing while a dispute is resolvedPause processing without deletingWrite to us. We can lock an account so it cannot be signed into while a question is being resolved, without deleting anything.
Portability — take your data elsewhere in a usable formatGet a copy in a structured, machine-readable formatFor account data, write to support@healthpathapp.com and we will send you a JSON file — structured, machine-readable, and complete. A GAP, STATED PLAINLY: your entries are not ours to export, and the app has no machine-readable export of them. The Reflect & share PDF is the only thing that can be taken out of the app, and it is made for reading, not for loading into another program.
Objection — object to processingObject where processing relies on our own interest rather than your consentThe things on that basis are the rate limiter's brief use of your IP address, our replies to your messages, the five-year keeping of withdrawal emails and the website's page-view counts (Section 6). You can object to any of them and we will explain what changes.
Withdraw consent — for anything based on consentStop consent-based processing at any timeNothing about your account or entries rests on consent any more (Section 6). The one place consent is used is the website's "Get launch news" form (Section 11): write to support@healthpathapp.com and we remove you.
Automated decisionsObject to being subject to a decision made by an algorithm aloneNot applicable — nothing in the app or on the server scores, ranks, profiles, or makes any automated decision about you.

How we check it's you. For anything that reveals or deletes data, we need to be reasonably sure we are talking to the account's owner. We will normally ask you to write from the email address the account uses. We will never ask you for your password, and we will never ask you to send us a photo of an identity document unless there is a genuine doubt we can't resolve any other way.

Response time: we reply within one month. If a request is complex, we may need up to two further months, and we'll tell you that it's happening and why — we won't just go quiet. There is no charge for any of this.

The right to complain

You have the right to complain to a data protection supervisory authority at any time, whether or not you've contacted us first. In Bulgaria, that's:

If you live elsewhere in the EU/EEA, you can complain to your own country's equivalent authority instead — you don't have to use the Bulgarian one just because we're based here.

You also have the right to take the matter to court, in addition to or instead of complaining to a supervisory authority.

10. Security — what actually protects your data, and what doesn't

We'd rather tell you plainly what is and isn't in place than let a vague phrase like "industry-standard security" stand in for specifics. There are three places data sits — your phone, the connection, and the server — so this section covers all three.

On the connection between your phone and us

  • Everything is encrypted in transit, with HTTPS. Nobody on the café WiFi, on your mobile network, or anywhere between you and us can read what your app sends.
  • The connection is carried by Cloudflare. Section 12 explains what that means for what Cloudflare can technically see, because we would rather you heard it from us.

On our server

  • Your password is hashed with argon2id. That is the algorithm currently recommended for exactly this job — deliberately slow and memory-hungry, so that guessing passwords in bulk is expensive even for someone holding the whole database. The password is never stored on your phone in any form.
  • Sign-in tokens are stored only as a one-way hash. If someone stole the database they would not get a usable key to anyone's account. Tokens expire after 90 days and are revoked the moment you sign out.
  • Password-reset codes are stored hashed, expire in 15 minutes, allow five attempts, and can be used once. Email-confirmation codes work the same way, with 48 hours.
  • Emails leave our server over an encrypted connection to Resend. Once delivered, an email is as private as your inbox and no more — like almost all email, it is not end-to-end encrypted. That is why the codes in them expire quickly and work only once.
  • Sign-in gives the same answer for "no such account" and "wrong password", so the server cannot be used to find out whether a given person has a Health Path account.
  • Rate limiting on the routes that take a password, a code or a Google token, or that send an email, counted per internet address and, on sign-in, password reset, email confirmation and password change, per account too, so a bot cannot grind through guesses from many machines.
  • The server has no port open to the internet. It makes an outbound connection to Cloudflare and receives requests down it. There is no door to try the handle of.
  • The server keeps no request log, so there is no file of who connected and when.
  • The database is backed up, and the off-site copy is encrypted with a key that never sits on the machine that stores it — though copies of that key are on our own server (Section 3).
  • The server holds no health entries. Whatever happens to it, it cannot lose or leak what it does not have.

On your phone

  • The Android app sandbox. Every Android app's private storage is walled off from every other app on the phone. Another app cannot read Health Path's data without breaking Android's own security model — root access, or an exploit. This is a real protection.
  • Android's own backup is switched off for this app (Section 7), so your entries are not copied into your Google account.
  • This is now the only place your entries are. That makes the phone's own protection — its screen lock, its updates — the thing that protects your diary.

What does not protect your data — stated plainly, because you should know

  • Your entries are stored on your phone as ordinary readable text inside the app's private storage. The sandbox protects it; a second layer of encryption does not. We are not going to imply an "end-to-end encrypted" or "encrypted at rest" property the app does not have.
  • A rooted phone, or one shared with people you don't trust, is a real risk. If someone has physical access to your unlocked phone, they can read your diary by opening the app.
  • The account data on our server is not encrypted with a key only you hold. It is ordinary data in a database: email, name, plan and so on. Anyone with administrative access to that machine can read it. Today that is two people: the owner and the administrator, Petar Kirilov.
  • The server is one computer in a home in Bulgaria, not a data centre. It has physical protection no better than a house, no security staff, no standby machine, and no independent security audit or penetration test has been carried out on it. That is the honest description, and if it changes we will change this paragraph.
  • A "data breach" is possible for the account data. Version 1.0 of this policy could say there was no server to hack. There is one, and it holds account data, though not your entries.

If there is ever a breach

If we become aware that your data has been exposed — a break-in, a lost backup, a mistake of ours, anything — then:

  • we notify the Bulgarian supervisory authority (the КЗЛД) within 72 hours of becoming aware of it, as the law requires;
  • if the breach is likely to put you at real risk, we tell you directly, without undue delay, in plain language: what happened, what data was involved, and what you should do;
  • we will not wait to be asked, and we will not describe it as a "security incident" to make it sound smaller than it is.

Although your entries are not on our server, an email address of someone who uses an app like this can itself say something personal, so we treat "likely to put you at real risk" as a low bar. If in doubt, we will tell you.

11. The website — separate from the app, handled separately

This section covers https://healthpathapp.com, the marketing website — not the app itself, which is covered by everything above. If you've only ever used the app and never visited the website, this section doesn't add anything for you.

  • Server logs. Like essentially any website, ordinary web server logs — which record things like IP address and request time, generated automatically by the server software — may be created when you visit. We don't run analytics on top of these logs; the page counting described below is a separate thing.
  • Cookies. This website does not set any cookies.
  • Analytics. This website uses Cloudflare Web Analytics to count page views. It is cookieless: it stores nothing on your device, does not identify you, and cannot follow you to other websites. We see totals only — how many pages were viewed, which pages, roughly which country, and what kind of device. Cloudflare, Inc. acts as our processor for this, as it already does for hosting the site; Section 13 explains what that means. Your browser fetches the counting script from Cloudflare's own address (static.cloudflareinsights.com), so Cloudflare sees that request the way any website host sees a visit. The basis is in Section 6. The app itself runs no analytics unless you switch on its optional usage statistics, which are separate and described in Section 3.
  • Fonts. The website's fonts are served from our own hosting, not from Google's servers, so visiting the site does not send your information to Google by this route. Until 15 August 2026 it did load them from Google on every page, which sent your IP address to Google before you had agreed to anything; we removed it ourselves rather than wait to be asked.
  • The link to TikTok. The footer links to a TikTok profile. That link takes you to a third party's website, which has its own privacy practices and its own tracking, entirely outside our control. Check TikTok's own privacy policy if that concerns you.
  • Two forms. The “Get launch news” form on the home page, and the account-deletion page. There is no contact form, no newsletter and no account on the website.
    • “Get launch news” asks for a first name (optional) and an email address, and has a box you must tick: “Yes, email me once, on the day Health Path is out on Google Play. I am 16 or older.” It is entirely optional and nothing else on the site depends on it.
    • What we store: your email address, your name if you gave it, the date and time you ticked the box, and your country, which Cloudflare works out from your connection when you submit; for the confirmation step, a one-way hash of the token in the confirmation link (we never keep the token itself), the time the confirmation email was sent and the time you confirmed. We do not store your IP address.
    • Confirmation (double opt-in): Before an address counts, we email you one link to confirm it, from no-reply@healthpathapp.com, through Resend, our email processor (Section 12). The address is on the launch list only after you click the link, which works for 7 days. If it is not clicked, a daily job deletes the address after 7 days. Signing up again sends a new link, at most once every 10 minutes.
    • What we do with it: send that one launch email, which will also mention the founding offer, and nothing else. We do not sell or share the list, and we send nothing in the meantime except the confirmation email.
    • How long: an address you do not confirm is deleted automatically after 7 days by a daily job. A confirmed address is kept until the launch email has been sent; we then delete the list within 30 days. If you leave the list sooner, we delete you then.
    • Earlier sign-ups: Addresses given before 20 October 2026, when the form asked for your email so we could tell you when Health Path launches, receive that one launch email without a separate confirmation (your request was to be told), with an unsubscribe link, and are then deleted within 30 days.
    • Who holds it: our own endpoint on Cloudflare, the company that also hosts this website, writes it to a Cloudflare database. The confirmation email is sent by Resend (Section 12). We asked for that database to be placed in Western Europe; Cloudflare treats the location as a request, not a guarantee. Until 17 August 2026 this form was handled by Formspree (Formspree Inc.) in the United States; we moved it so that an address given here would stay in the EU. Cloudflare, Inc. is a US-headquartered company acting as our processor, which is not quite the same as “nothing leaves the EU” — Section 13 says plainly what it does and doesn't mean. What the app sends, and where, is Section 3.
    • Getting off the list: at any time, at api.healthpathapp.com/unsubscribe (the launch email links there too), or write to support@healthpathapp.com and we delete you from it.
    • Why we're allowed to: your consent (Art. 6(1)(a) GDPR), and, for the launch email, Art. 6 of the Bulgarian Electronic Commerce Act (ЗЕТ чл. 6), given by ticking the box, submitting the form and confirming through the link. You can withdraw it at any time, through the unsubscribe link, and withdrawing is as easy as giving it was.
    • The delete-account page (healthpathapp.com/delete-account) asks for your email and password. Your browser sends them to our server to sign you in and delete the account, and that sign-in is ended straight afterwards. The page keeps nothing in your browser: no cookie, no local storage. The basis is in Section 6.

12. Third parties: Cloudflare, Resend, and Google

Cloudflare — the one company in the middle

There is exactly one company between your phone and our server, and it is Cloudflare, Inc. We would rather explain it properly than list it in a table of "partners".

What it does for us: it gives api2.healthpathapp.com its address and its HTTPS certificate, it absorbs attacks aimed at the server, and it carries each request down the outbound-only connection our machine makes to it. It is the reason the server can be reached from a phone without a single port being opened at our end. Cloudflare also hosts the website (Section 11) and the launch sign-up list.

What it can technically see: because Cloudflare terminates the HTTPS connection, it handles requests in the clear at its edge before passing them on. In principle that means the content of the requests the app makes — your email address, name and password when you sign up or in, a purchase token, a withdrawal statement — passes through their systems. Your entries do not, because the app no longer sends them; the one exception is an older build that still tries to synchronise, whose request reaches Cloudflare before our server refuses it (Section 3). Cloudflare's role is a processor: it acts on our instructions, under its own data-processing terms, it has no right to use your data for its own purposes, and it does not receive a copy of the database. But "nobody can see it but us" would be an overstatement, so we are not making it. Cloudflare also keeps its own connection logs, which include your IP address, under its own retention policy.

Where it is: Cloudflare, Inc. is headquartered in the United States and operates a global network. Section 13 deals with what that means for your data leaving the EU.

Resend — the account emails and the waitlist confirmation

What it does for us: it delivers the four kinds of email listed in Section 2 — a password-reset code, a code to confirm your address, an inactivity warning, and a confirmation of a plan or of a withdrawal. It also delivers the note to ourselves that our server sends to support@healthpathapp.com when someone withdraws. Our server hands each message to Resend over an encrypted connection, and Resend sends it to your inbox from no-reply@healthpathapp.com. It is not involved in anything else: it is not on the path between your phone and our server, and it never sees what the app sends to our server.

The waitlist confirmation email. Resend also delivers the one confirmation email sent to an address given on the website's launch-news form (Section 11), from no-reply@healthpathapp.com. For that it receives the address and the message, which holds the confirmation link, in English and Bulgarian. Resend is our processor for this exactly as for account email: the same data processing addendum, the same 30-day record kept in the United States, the same switched-off open- and click-tracking, and Section 13 applies in the same way.

What it receives: your email address, the subject line, and the message. The message contains the code or confirmation link, in an inactivity warning your display name and the date the account would be deleted, and in a plan email the plan, its dates, the Google Play order number and, where the app passed it on, the price. In the note to ourselves it is your account's email address, the plan, the time and the order number. It never receives your entries, your diary, your moods, your password, or anything else from Section 2's table.

What it keeps: a record of each message — including its content — for 30 days, so that a message that failed to arrive can be looked into. After that it is deleted. Deleting your Health Path account does not reach into that 30-day record; it runs out by itself.

Its role: processor. The company is Plus Five Five, Inc., trading as Resend. It acts only on our instructions, under a data processing addendum that applies to every Resend customer as part of its terms, and it may not use your address or the messages for its own purposes. Open-tracking and click-tracking are switched off on our sending domain, not merely left unused — so Resend is not told whether you opened a message or followed the link in it. Resend uses sub-processors of its own to deliver mail, in the United States, and its addendum requires it to give us at least 14 days' notice before it adds or replaces one; if one of them ever mattered to what this policy says, Section 14 is how you would hear about it.

Where it is: San Francisco, United States. Our sending domain is set to Resend's eu-west-1 region, so the messages themselves are dispatched from Ireland — but that setting moves only the sending, and we would rather say so than let it read as more than it is: the 30-day copy, the delivery logs and the account records sit in the United States whichever region sends. So this is a real transfer outside the EU, unlike Cloudflare, and Section 13 says what protects it.

Google — the store, paying for a plan, "Sign in with Google", and our support mailbox

Google appears in this policy in four ways. In three of them Google is not our processor: for Google Play, for the payments taken through it, and for "Sign in with Google", Google decides for itself what it collects and why, and acts as its own controller under its own privacy policy (policies.google.com/privacy). In the fourth, our support mailbox in Google Workspace, Google is our processor (below). For those three, we do not instruct it and we cannot change what it does. What we can tell you is exactly what passes between Google and us, in each direction.

Google Play, the store. Health Path is distributed through Google Play. To run the store, Google collects its own information — your Google account, your device, and what you install — under its own policy. We don't receive it. Play Console shows us only overall figures, such as the number of installs and how often the app crashes on a given phone model, which say nothing about who you are.

Paying for a plan. If you buy a plan (Terms of Service, Section 12), the payment is between you and Google. Google takes the payment, holds your card or other payment method, sends you the receipt, and handles renewals, cancelling and refunds. We never receive your card details, your billing address, or the name on your payment method.

  • What we send to Google: with each purchase, the app gives Google an account reference — a code made from your Health Path account's internal id by a one-way function (SHA-256). Google stores it with the purchase and gives it back to us, so our server can check that a purchase belongs to the account claiming it. It does not contain your email address or your name, and it cannot be turned back into your account id. Like any fixed code, it does let Google tell that two purchases of a Health Path plan were made by the same account.
  • What we receive and keep: the purchase token Google gives the app for your subscription, which plan it is, its state (for example active, cancelled or expired), when the current period ends, and whether it will renew. Our server asks Google's Play Developer API about that token when you buy, and again when a period ends, signing in to Google with a key that belongs to Health Path. Google's answer also contains an order number. We put it into your confirmation or withdrawal email at the moment we send it and do not keep it. We do not store the price, the order number, or anything about how you paid.
  • If you withdraw: our server asks Google Play, through the same Developer API, to refund the payment and end the subscription immediately. Google carries out the refund under its own policy; our server records only that you withdrew, which purchase it was, when, and whether Google refunded it.

"Sign in with Google". If you choose it instead of a password, Google tells our server your Google account's id, your email address, whether Google has confirmed that address, and your name. We keep the id, so we recognise you next time, and use the email address and name as your account's email and display name (Section 2). Google learns that you signed in to Health Path. We receive nothing else from your Google account — no contacts, photos, files or history.

Google Workspace, our support mailbox. support@healthpathapp.com is a mailbox in the owner's Google Workspace account. Google therefore receives and stores every message sent to that address: what you write to us, your email address and name as your mail program sends them, and the note our server sends on each withdrawal (your account's email address, your withdrawal statement, the Google Play order number, and whether the payment was refunded). For Workspace, Google is our processor, bound by Google's Cloud Data Processing Addendum, which we have accepted: it processes that mail only to provide the mailbox to us, under our instructions, and not for advertising or its own purposes. Our server never sends your entries to this mailbox, and only the owner reads it. Please do not put health details in an email to support unless you need to; withdrawing from a plan does not require you to write to us, because the app has a button for it (Section 2). Until 20 October 2026 this address forwarded to the owner's personal Gmail account, where Google acted as its own controller (Section 2).

Where: Google LLC is in the United States; Google Ireland Limited is the Google company responsible for users in the EEA. Section 13 says what that means for transfers.

Petar Kirilov — not a third-party company, but not the owner either

The administrator of our server is a person, not a company, and he is not a recipient in the sense of the three above: he runs the machine on which the account data is stored, as the controller's processor. Section 3 says what he can reach, and Section 5 says what is still to be put in writing. A second computer in a shared office in Sofia holds the encrypted off-site backup; it holds only files it cannot read (Section 3).

That is the complete list: Cloudflare, Resend and Google, and the administrator of our own server. There is no analytics company (the optional usage counts in Section 3 are kept on our own server), no advertising network, no crash-reporting vendor, no email-marketing service, and no cloud storage provider — the account data is on a machine we run, and your entries are on your phone and nowhere else. If that list ever grows, this section is where it will say so, and Section 14 says how we will tell you.

13. International data transfers

Your entries are not transferred anywhere, because they never leave your phone. Where the account data is stored: in the EU. The server is in Bulgaria (Section 3), the encrypted backup copy is on a second computer in Sofia, and the website's sign-up list is in a Cloudflare database we asked to place in Western Europe (Section 11; Cloudflare treats the location as a request, not a guarantee). What is kept outside the EU/EEA: Resend holds a copy of each account email we send you, in the United States, for 30 days; and if you buy a plan or use "Sign in with Google", Google keeps its own records, partly in the United States; and Google, which holds mail sent to our support address in Google Workspace, may process it outside the EU as well (all below).

Where it is honest to say "it's complicated": Cloudflare. Cloudflare, Inc. is a US-headquartered company, and it carries every request between your phone and our server. Two things follow, and we would rather write both than only the comfortable one:

  • We do not choose to send your data to the United States, and it is not stored there. Cloudflare's network routes traffic through nearby locations, which for a user in Europe means European ones.
  • But a US-headquartered processor handling EU data is legally a transfer question, not a non-question. The safeguard relied on is Cloudflare's own standard data-processing terms, which incorporate the European Commission's Standard Contractual Clauses, together with its published supplementary measures. Cloudflare is also certified under the EU-US Data Privacy Framework.

Resend is a plain transfer, and we say so. When our server sends you an account email, your email address and the message go to Resend, which dispatches it from Ireland but keeps its copy — and its delivery log — in the United States for 30 days. It is limited to what Section 12 lists — never your entries. The safeguards relied on are:

  • Resend is certified under the EU-US Data Privacy Framework, which the European Commission has recognised as giving adequate protection to data sent to certified US companies; and
  • its data processing addendum also includes the European Commission's Standard Contractual Clauses, which apply if that framework ever stops being available.

Google is a different case again, because for Google Play and sign-in it is not our processor (Section 12). What we disclose to it — only if you buy a plan — is the one-way account reference, and questions about a purchase token that Google issued in the first place; with "Sign in with Google", it is Google that tells us about you. Google then handles that information as its own controller, under its own privacy policy, including in the United States. Google LLC is certified under the EU-US Data Privacy Framework. We do not send Google your entries, your diary, your moods, your email address or your name.

Google Workspace is a different case from the rest of Google, because there Google is our processor. Mail sent to support@healthpathapp.com is held in Google Workspace, and Google may process it outside the EU, including in the United States. The transfer is covered by the Standard Contractual Clauses built into Google's Cloud Data Processing Addendum, and Google LLC is also certified under the EU-US Data Privacy Framework. What reaches the mailbox is only what you choose to write to us, plus our server's note on a withdrawal (Section 12) — never your entries.

If this matters a lot to you, the honest advice is this: the strongest protection we can offer is that your entries never travel at all. What does travel — your email address and the account emails, and, if you use them, a purchase or a Google sign-in — involves US-headquartered companies as described above, and a diary app run by one person cannot offer you an EU-only network path today.

14. Changes to this policy

If we make a meaningful change to this policy — for example, adding a new feature that changes what data is collected — we will update this document, update the "last updated" date at the top, and note the change in the change-history table. For any change that meaningfully affects what we do with your data, we'll also tell you by email to your account's address, not just by quietly editing a web page. The app has no notice of its own for this, so the email and this page are the two places a change is announced.

Version 3.0 is that kind of change, in the opposite direction from version 2.0. Version 2.0 started copying your entries to a server; version 3.0 stops, and removes the copy. We are not going to treat that as a quiet edit. The text in the app that describes where your entries live, including the tick box at sign-up (Section 4), changes with the same release.

What users of earlier builds should know.

  • If you used a build that synchronised (any build before 1.0.0+7), a copy of your entries was on our server. On the day this version takes effect we delete it from the live database. You do not need to do anything.
  • The copy on your phone is not touched. It is now the only copy of your entries. If you want to keep a record that survives losing the phone, make a PDF with Account → Reflect & share (Section 7).
  • Copies of that data inside older backups are not deleted one by one; they leave as the backups roll over, over the periods in Section 15, including one that is counted in backups rather than days.
  • Update the app. An older build keeps trying to synchronise; the server now refuses (Section 3) and nothing it sends is kept.
  • The consents you gave under versions 2.0 to 2.5 are no longer needed, because we no longer process the data they covered. The records of them go with the profile data.

15. How long we keep your data

Version 1.0 of this policy did not need this section: data lived on your phone, and it lasted exactly as long as you let it. Version 3.0 is back to that for your entries; for the account data we hold, the law calls the duty storage limitation, and it means we are not allowed to keep things forever just because storage is cheap.

WhatHow long
Your entries, profile settings and goalsNot held by us. They stay on your phone until you delete them, delete your profile, clear the app's data or uninstall the app
Your account (email, name, password hash, confirmation state, timestamps, Google id)For as long as your account exists. Deleting your account deletes all of it at once
An account you stop usingDeleted automatically after 12 months with no sign-in, together with the account data we hold. Entries on your phone are not touched. See below
Sign-in sessionsThe session works for 90 days or until you sign out. The record of it (including the random device identifier) stays on the server until your account is deleted, because we have not yet built the clean-up that would remove expired ones
Password-reset codesThe code works for 15 minutes. A used or expired record stays on the server until your account is deleted, for the same reason
Email-confirmation codesThe code works for 48 hours. A used or expired record, including the address it confirmed, stays on the server until your account is deleted, for the same reason
Copies of account emails and of the waitlist confirmation email, kept by Resend30 days
Your plan (purchase token, plan, state, end date, start of the 14 days, when the confirmation was sent)As long as your account exists; deleted with it
A withdrawal record (which purchase, when, whether Google refunded it)As long as your account exists; deleted with it
Emails to support@healthpathapp.com, including the note sent on a withdrawalNot on our server. They sit in our Google Workspace mailbox (Section 12) until 1 year after the matter is closed, then we delete them. Emails about a withdrawal (the note sent on a withdrawal, and a withdrawal you sent us by email) are kept for 5 years, as proof that the withdrawal was received and the refund made, then deleted. Google keeps that mail only as our processor, for as long as we keep it
Google's own records of your paymentsGoogle's retention, under its policy and the tax law that applies to it, not ours. Deleting your Health Path account does not delete them, and does not cancel a subscription
Rate-limiting records (your IP address, and the email or account being tried)In the server's memory only, never written to disk: each is counted for the length of the limit it belongs to, at most one hour, and all are lost when the server restarts
The server's request logNone is kept now. Until the server was updated for version 3.0 its access log wrote the IP address, time and address requested of every request to the system journal. Those older lines stay until the journal rolls over; it is limited by size, not by time
Daily backups of the account database, on the serverThe newest 14 are kept, so up to about 14 days. A deleted account disappears from them as they roll over
Encrypted copies of the daily backups, on a second computer in a shared office in SofiaThe newest 30 are kept, so up to about 30 days. They hold only files that machine cannot read
Backups taken before a server update that changes the database layoutThe newest 10 are kept, counted by number and not by age. There is no age limit: how long one lasts depends on how often the database layout changes, and one can be older than a month. They are stored on the server and readable only by administrators
Launch-news address you have not confirmed (email, name, time of consent, country, hash and time of the confirmation token)Deleted automatically after 7 days by a daily job, or when you leave the list, if sooner (Section 11)
Launch-news list, confirmed addresses (the same, plus the time you confirmed)Until the launch email has been sent, then deleted within 30 days; deleted when you leave the list, if sooner (Section 11)
Optional usage counts under a random code (Section 3)400 days from the day of the count, deleted by the server whenever it receives new counts; or at once when you switch the statistics off, if your phone can reach the server then
Cloudflare's own connection logs and web-analytics dataCloudflare's retention, under their policy, not ours

Backups made before this version took effect

Backups taken before the day this version took effect still contain the entries of people who used a build that synchronised. We do not edit backups. Each kind leaves as it rolls over: the daily copies on the server within about 14 days of the purge, the encrypted off-site copies within about 30 days, and the copies taken before a database change when ten newer ones have been made. Until then the daily and pre-deploy copies are readable by the administrator, and the off-site ones by whoever holds the backup key. Nothing is done with them in the meantime other than keeping them for recovery from a disk failure.

The 12-month rule, in plain terms

If you don't sign in to Health Path for 12 months, we delete your account and the account data we hold. Not archive, not deactivate — delete, the same as if you had pressed the button yourself. It cannot be undone, by you or by us. Entries stored on your phone are not affected by this: we cannot reach them.

We chose this deliberately, and it is a genuine trade-off:

  • Why we do it: an abandoned account is an email address and a name with no purpose. Keeping it indefinitely means holding someone's details for no reason, and every year it sits there is another year it could be exposed by something going wrong.
  • What it costs you: if you take a year away from the app — which people recovering from difficult relationships with food quite reasonably do — and come back, your account will be gone and you would sign up again. Signing in once, at any point in the year, resets the clock.
  • What we do first: warn you. About 11 months after your last sign-in we email your account's address, and if you still haven't signed in, we email again about two weeks later. Signing in after either email cancels the deletion, restarts the clock and clears the record of the warning, so a later year of silence gets warnings of its own.
  • No warning, no deletion, and no deletion within a fortnight of one. An account is deleted under this rule only if a warning was actually sent to it, and only once that warning is at least 14 days old. If an email fails to send, the account is kept, and we try the warning again rather than deleting without it. These two sentences are our commitment on the point, and they are enforced in the code that does the deleting, not only here.

If Health Path ever changes shape again

Paid plans were added in version 2.5, and Section 12 says who takes your payment and what Google, rather than we, holds. Version 3.0 moved the entries off the server. If any new company is added to Section 12, if the server moves, or if anything about your entries ever reaches us again, we will say so under Section 14 before it happens rather than after.