Privacy Policy
Last updated: 2026-09-02
This Privacy Policy explains what personal data FoodTrack ("we", "us", "our") collects when you use the Service, why, and what rights you have over it. It should be read alongside our Terms of Service.
Simon Walker, a private individual based in Scotland, UK, is the data controller. Contact: foodtrack-support -AT- stwalkerster.co.uk.
Where your data is stored and processed
FoodTrack's infrastructure (application servers and the AWS S3 storage described in section 3) is hosted in London, UK. Data does not leave the UK except where a recipient named in section 3 is itself based elsewhere.
1. What we collect, and why
Account and tracking data
- Login details — username, password (stored hashed, never in plain text), and an optional email address. If you provide one, we use it for password recovery and to contact you about important account or service matters — for example, changes to these policies (section 8) or a moderation decision affecting your account. If you don't provide an email address, we have no way to reach you outside the app, and you won't be able to reset a forgotten password.
- Date of birth and sex — used to enforce the minimum age requirement (section 7) and as direct inputs to your basal metabolic rate (BMR) and energy/nutrient target calculations (the app uses the Mifflin-St Jeor equation, which requires age and sex alongside weight and height).
- Height and weight — also direct inputs to the same BMR/energy-target calculations, and to your logged body-measurement history.
- Logged meals, hydration, workouts, and goals — the core tracking data you enter.
- Optional AI-agent context — if you choose to enable MCP (AI agent) access, you may separately write free-text personal context (e.g. dietary preferences, usual routine) to help an AI agent tailor its advice. This is entirely opt-in and separate from the data above.
Security, sessions, and account access
- Session data — when you log in, we record your IP address, browser/device information (user agent), and when you were last active, so we can show and let you revoke your own active sessions.
- Two-factor authentication and passkeys — if you enable 2FA, we store the security credential needed to verify your login codes, and any backup/recovery codes you generate. If you register a passkey, we store the public key and device information your authenticator provides (not a secret — passkeys are designed so the private key never leaves your device). We use these only to verify it's you logging in.
- Trusted connections — if you set up another account to be able to log food on your behalf (or vice versa), we record that connection, since it reflects a real-world relationship you've chosen to create between two accounts.
Connected third-party services
If you connect a third-party fitness service (for example Strava or Hevy) to sync workouts, we store the access token or API key that connection gives us, so we can keep pulling your workout data from that service without asking you to reconnect every time. If you enable AI-agent (MCP) access, a similar short-lived, scoped access token is issued and stored so the agent can read only the specific categories of data (weight, nutrition, workouts) you've authorised, for as long as you keep that access enabled — you can revoke it at any time from your account settings.
Reports and feedback
- Content reports — if you report content, we record who made the report, what was reported, and why (see our Retention Policy for how long).
- Feedback you submit — if you use the in-app feedback feature, we store your message, the page you submitted it from, and your browser/device information. Any internal notes we make while handling your feedback are not shown back to you.
System and audit logs
Changes to your data are logged for security and accountability — who made the change (or, if your account is later deleted, that the change was made by an account that no longer exists), what changed, and the IP address the change was made from. See our Retention Policy for how long these logs are kept.
Data you export
When you use the in-app data export feature, we temporarily store the resulting archive so you can download it, then automatically delete it (see our Retention Policy).
Uploaded files
The Service also accepts several categories of uploaded file. Each is handled differently:
| Category | Visibility | Lawful basis |
|---|---|---|
| Progress photos (measurements) | Private to you only | Consent — uploading a progress photo is entirely optional, not required to use the Service |
| Nutrition-label photos | Visible to every user of this deployment (there's no per-item privacy setting — any logged-in user can browse the shared food item database, whether or not they've logged that item themselves) | See note below — the image itself generally isn't personal data |
| Workout GPS/route data | Private to you only, never shared | Consent — uploading a route file is entirely optional, not required to use the Service |
A nutrition-label photo is a picture of a product's packaging, not of you — on its own it doesn't identify you, so it generally isn't "personal data" under UK GDPR and Article 6 doesn't require us to have a lawful basis for the image content itself. What is personal data is the separate record of who uploaded it (see below); we rely on legitimate interests for that — specifically, preventing abuse of the shared database and keeping it accurate — since that record is minimal, never shown to anyone else, and something you'd reasonably expect us to keep for exactly that purpose.
For every uploaded file, we also record who uploaded it. For progress photos and measurement photos this uploader record is never shown to any other user — we keep it only so we can act on abuse (e.g. identifying a pattern of misuse), and it's cleared if you delete your account (see "What happens to uploaded files when you delete your account" below).
Sensitivity of this data, and special category data
Progress photos, nutrition data, body-fat percentage, and GPS/route data are treated by us as sensitive data, even though none of it is processed as special category data under Article 9 UK GDPR. We considered this classification carefully:
- Progress photos can reveal physical characteristics.
- GPS/route data can reveal movement and location patterns.
- Nutrition, weight, and body-fat data can, indirectly, suggest health-adjacent information.
However, we do not process any of this data for a health or diagnostic purpose — it is processed for personal tracking purposes that you control. On that basis it does not fall within Article 9. We nonetheless apply the minimisation and security practices described in this policy to all of it, regardless of its formal classification.
2. Automated scanning and moderation
Every file you upload is automatically scanned and moderated before it becomes visible anywhere in the Service. This happens for all upload types, not only nutrition-label photos, and includes automated malware scanning and content moderation. We think this is important enough to state plainly here, not just as a term buried in our Terms of Service.
3. Who we share data with
We use the following processors and, in specific circumstances described below, recipients:
- Amazon Web Services (AWS) — object storage (S3) for all uploaded files; Amazon GuardDuty for automated malware scanning of uploads; Amazon Rekognition for automated content moderation.
- Relevant authorities — in cases of confirmed or suspected abuse (for example, illegal content identified through moderation), relevant data may be shared with the appropriate authorities, as described in our incident response process. We do not routinely share upload content with any authority outside of these circumstances.
We do not sell your data, and we do not share progress photos or GPS/route data with any third party beyond the processors above who need it to operate the scanning pipeline.
4. EXIF and other metadata
We strip EXIF and other embedded metadata from uploaded images as a data-minimisation measure. Among other things, this removes GPS coordinates that cameras and phones sometimes embed directly in photo files, which is a location-privacy protection independent of how workout route data is otherwise handled.
5. How long we keep your data
Our retention periods for uploaded files and related records are set out in full in our Retention Policy; we don't duplicate that detail here. In summary: files serving a one-off purpose (moderation, OCR extraction) aren't kept any longer than that purpose, or any legal retention obligation, requires. Nutrition-label photos are the exception — we keep them indefinitely by design, not just for the moment of OCR, because they double as ongoing reference content for the shared product database (so future users logging the same product can see the label, not just its extracted text).
6. Your rights
You have the right to access, export, and delete your personal data. In-app, you can:
- Export your data — download an archive of your structured data, together with your progress photos.
- Delete your account — permanently remove your account and data.
What happens to uploaded files when you delete your account
- Private files (progress photos, measurement photos) are deleted, along with the rest of your account data.
- Nutrition-label photos are kept but anonymised. These are cross-user reference content, visible to every user of this deployment (see section 1) as part of the shared food item database — so rather than deleting the image, we detach it from your account. The image is no longer attributed to you or any deleted account; it is not retained "for" you in any way.
You can also exercise your other UK GDPR rights (rectification, restriction, and objection) by contacting us at foodtrack-support -AT- stwalkerster.co.uk. You also have the right to complain to the UK's data protection regulator, the Information Commissioner's Office (ICO), at ico.org.uk.
7. Minimum age
The Service is only available to users aged 18 or over, or the age of majority in your jurisdiction if higher. We collect your date of birth at registration and technically enforce this requirement by rejecting registration if it implies you are under 18 at the time of signup — see our Terms of Service for detail. We do not knowingly collect personal data from anyone below this threshold.
8. Changes to this policy
We may update this Privacy Policy from time to time. A change takes effect from the date shown at the top of this page. Where a change meaningfully affects how we handle your data, we will also email the address on your account before, or as soon as reasonably possible after, it takes effect — see our Terms of Service for the same mechanism applied there.
9. Contact
foodtrack-support -AT- stwalkerster.co.uk