DracariHealth
Privacy Policy
What is stored, why it is stored, who else sees it, and how to take it away or destroy it. Written against the code rather than from a template.
Last updated 2 September 2026
The short version
DracariHealth stores the food, weight and training you log, because that is the product. It is kept on servers run by Supabase, and nobody else is given access to it.
There is no analytics, no advertising, no tracking and no third-party software development kit in the app. Nothing is sold, and nothing is shared for marketing. There is no profiling and no automated decision-making about you.
Two things leave the system, both only to look up food: the words you type into food search, and a barcode you scan. See Food lookups below.
You can export everything, and you can delete the account outright, from Settings → Account & Privacy inside the app.
Who is responsible
DracariHealth is operated by its developer, who is the data controller for the purposes of the UK GDPR, the EU GDPR and equivalent laws. Contact: [email protected]
What is stored
Everything below is stored because you entered it or because the app cannot work without it.
| Category | What exactly | Why |
|---|---|---|
| Account | Email address and a hashed password. Handled by Supabase Auth; the password is never stored in a readable form and is never visible to the developer. | To let you sign in and to keep your data yours. |
| Profile | Display name, and optionally sex, height, date of birth and your timezone. | Nutrient targets differ by sex and age, energy needs by height and weight, and every day boundary is resolved in your own timezone rather than the server's. |
| Health and body | Weigh-ins, body-fat estimates and their source, body measurements, goals and pace. | The projection, the calorie target and the progress charts are computed from these. |
| Food log | What you logged, how much, in which meal window, on which date, and the nutrition figures for it at the time. | The diary, the daily totals, the nutrient panel and the streak. |
| Foods you make | Custom foods, recipes and their ingredients, saved meals, and your favourites. | So you only enter something once. These are private to your account and are not added to the shared food catalogue. |
| Training | Workouts and their sets: exercise, muscle, reps, weight, effort. | The muscle recency map and training volume. |
| Reminders | Your reminder settings, a record of reminders already sent, and a push token for each device you enabled notifications on. | To send a reminder when a meal window is closing, and to avoid sending the same one twice. A push token addresses a device, not a person. |
| Search behaviour | Which food you picked for a given search phrase, and how often. | So your own searches get better at finding what you actually eat. It is used only to rank your results. |
What is not collected. No location, no contacts, no photos beyond one you deliberately attach, no advertising identifier, no device fingerprint, no browsing history, and no data from Apple Health, Google Fit or any other app. Camera access is requested only when you open the barcode scanner, and the image is processed on the device — a scan sends a barcode number, never a picture.
Food lookups
When the local catalogue has no match, the search is widened to two public food databases. This happens on our server, not on your device, so those services never see your IP address, your account or anything identifying.
- USDA FoodData Central receives the words you typed, or the identifier of a food you opened. Its data is public domain.
- Open Food Facts receives the words you typed or a scanned barcode. Its data is used under the ODbL.
Nothing about you accompanies those requests. Results are cached in the shared food catalogue so the same lookup is not repeated — the cached food is not linked to you.
Who else processes it
| Service | Role | What it sees |
|---|---|---|
| Supabase | Database, authentication and server hosting | All of it, as the processor that stores it. Bound by its own data-processing terms. |
| Google Firebase Cloud Messaging | Delivers push notifications to Android devices | The device token and the text of the reminder. Reminders name a meal window and a time; they do not contain what you ate. |
| Railway | Hosts this website and the browser version of the app | Ordinary web-server request logs. |
These are processors acting on instructions, not partners. No one is given your data for their own purposes, and it is never sold, rented or traded. Data is stored in the United States; if you are in the UK or EEA, transfers rely on the providers' standard contractual clauses.
How long it is kept
For as long as the account exists. A food diary is only useful because it goes back, so nothing is aged out on a timer.
When you delete the account it is removed immediately: the account itself, the profile, every logged day, every weigh-in and workout, your reminder settings and device tokens, and the private foods and recipes you made. There is no grace period and no archive copy. Encrypted infrastructure backups may retain a copy for up to 30 days before they expire on their own schedule; they are never used to restore a deleted account.
Deletion cannot be undone. Export first if you want to keep anything. The export is one JSON file containing every record above.
Your rights
Under the UK and EU GDPR you have the right of access, rectification, erasure, restriction, objection and portability. Under the CCPA and CPRA you have the right to know, delete, correct and opt out of sale or sharing — there is nothing to opt out of, because neither happens. Two of these do not need a request at all:
- Access and portability — Settings → Account & Privacy → Export My Data.
- Erasure — Settings → Account & Privacy → Delete My Account. If you cannot reach the app, see deleting your account.
Rectification is editing your own entries, which the app allows throughout. For anything else, or to complain, write to [email protected]. You may also complain to your data-protection authority — in the UK, the Information Commissioner's Office.
The legal basis is contract for the data needed to provide the tracker, consent for push notifications and camera access, both withdrawable at any time in the operating system or in Settings, and legitimate interest for keeping the service secure and working.
Security
Every request is authenticated and encrypted in transit. Row-level security is enabled on every table in the database, so a row can only be read by the account that owns it — that is enforced by the database itself, not by the app asking politely. Passwords are hashed by Supabase Auth and are never visible to anyone.
No system is perfect. If a breach affects your data you will be told, and the relevant authority notified within 72 hours, as the law requires.
Children
DracariHealth is not intended for anyone under 16, and accounts are not knowingly created for them. If you believe a child has an account, write to the address above and it will be deleted.
Changes
If what is collected or where it goes changes, this page changes with it and the date at the top moves. A change that materially affects you will be announced in the app before it takes effect, not buried here.