Security
Security and your data
What happens to what you log, in plain words. Every line here describes how Vitalure works today.
Last reviewed 2 November 2026.
Where your data lives
Vitalure runs on a server in Google Cloud's us-west1 region, in Oregon, USA. Your log, your account and our backups are stored there.
The server accepts no connections from the internet apart from our own administrator access through Google's identity-checked gateway. Web traffic reaches it through an encrypted tunnel that the server opens out to Cloudflare.
Encryption
In transit. Every connection to Vitalure uses HTTPS. Cloudflare handles the HTTPS connection with your device and carries it to our server through that encrypted tunnel.
At rest. The server's disk and the storage that holds our backups use Google Cloud's default encryption.
Passwords. We store only a strong one-way hash (Argon2), never the password. Sign-in is slowed down after repeated wrong tries.
Your data is walled off
Your log and your messages are walled off per person, and the database enforces it with row-level security: each request runs as you, and the database refuses rows that aren't yours or shared with you. The one exception is support access, below. The app checks this too, so a single mistake in either place doesn't expose anything.
Password hashes, sign-in sessions and password-reset links are closed to the part of the app that answers requests: it can't read them, and a sign-in session can only be seen by its owner. Your plan is only given to you, and to a trainer you let manage it. Your name, email and account type are protected by the app's checks alone.
What this does and doesn't stop, plainly. Requests reach the database through a login that can't switch to the database's full rights, can't read other people's sign-in sessions, password hashes or reset links, and can't change or erase tables. If an attacker found a way to run their own commands in the database through the app, those commands would run as the one person whose sign-in they came through, and could not take over anyone else's. Sharing is checked the same way: the database refuses to turn on sharing of your log unless it is your own sign-in doing it, so those commands could not give their account a view of anyone else's log. They could still do whatever that one person can already do, such as read the names and email addresses every signed-in account can see.
We test it. Our test suite signs in as one person and tries every part of the app, and every tool that Claude or ChatGPT can use, against another person's data. The test fails if any part of the app is added without being checked this way.
Trainers see only what you share
A trainer sees nothing until you share with them. You choose what they may do: see your log, set your targets, message you, manage your plan.
- Change what you share, or stop sharing, in Settings at any time. It takes effect straight away.
- Each time a trainer looks at your data, it's recorded, and you can see that list in Settings.
- Trainers never see your meal photos, your voice notes or your Copilot chats.
Support access, read-only, and you're told
If you report a problem, the person who runs Vitalure can view your account to find it. That access is read-only: the app refuses every change, the database connection itself is read-only, and exporting or downloading your data is blocked. It needs a written reason, ends after 30 minutes, and you get a message from Vitalure support in the app each time, with the date and the reason. Each session is recorded in the list of who has looked at your data (Settings, Sharing), and you can switch support access off in Settings, Privacy, after which it is refused and any open view ends. The administrator can also mark an account as a test account for testing; that allows changes as well as viewing, you get a message from Vitalure support when it happens, and the same switch refuses it. It never reaches your password, and it never creates a connection to Claude or ChatGPT in your name.
AI runs on our own hardware
Reading meal photos, turning speech into text, understanding what you type and answering Copilot questions all run on a GPU computer that we own and run ourselves. No third-party AI service receives your data.
That computer isn't in Google Cloud. It collects one job at a time from our server over HTTPS and sends the answer back. It keeps no copies, and the server deletes the photo or recording from the job as soon as the job ends.
If you connect Vitalure to Claude or ChatGPT yourself (it's optional), that service reads what you ask it to read, under its own terms. You can disconnect it at any time.
No ads, no selling, no sharing
We don't sell, rent or share your data, and Vitalure shows no ads. These pages have no analytics or trackers, and set no cookies of their own.
Two companies run parts of the service for us and handle data only to do that: Google Cloud (the server and backups) and Cloudflare (the network and HTTPS).
If you turn on notifications, they travel through your browser maker's push service (Apple, Google or Mozilla), encrypted so that service can't read them. If you turn on the on-phone voice model, your phone downloads it once from Hugging Face; nothing you say is sent there.
Export and delete, any time
- Export. Settings, Your data, Download everything: one file with your logs, plan, notes and chats. Photos and voice recordings aren't in it yet.
- Delete. In the same place, delete your account. It happens at once and can't be undone. Copies in backups are gone within 30 days.
- On request. Can't sign in? Email [email protected] from your account's address and we'll export or delete it for you.
Backups
The database is backed up every night to Google Cloud Storage in the same region, encrypted at rest, and each backup is deleted after 30 days. The server can add backups but can't read or delete them, so a break-in to the server couldn't reach or wipe them.
Gyms and body composition scans
Scans from gym machines such as InBody are not available in Vitalure yet. When they are, these rules apply:
- A scan is matched to a member only after that member links their own Vitalure account.
- Members are never charged for their own data.
- Scan data stays under the member's control, like the rest of their log: they choose which trainer sees it, and can export or delete it.
What we don't claim
Vitalure holds no security certifications, such as SOC 2 or ISO 27001, and makes no HIPAA claims. It isn't a medical service. If your organisation needs a security questionnaire answered, contact us.
Report a security problem
Email [email protected]. Tell us what you found and how to see it, and please give us a chance to fix it before telling anyone else. We read every report.
The same address is in /.well-known/security.txt.