You share things with Going Visible that you might not share with anyone else — the days when the pain is unbearable, the medications that help you get through, the notes you scribble before a doctor’s appointment. We take that trust seriously. This page explains exactly how we protect it.
No small print. No vague promises. Just what we actually do.
What you writeWoke up stiff again. Hands are bad, maybe a 6.Encrypted before it’s storedWhat our database holds9f3a1c7e0b…d42e8a61f05c77b3e9a0c4…1b6f
Six commitments
How we protect your data.
1
Locked before it’s stored
Your clinical notes and health entries are encrypted before they reach our database. Even our own servers can’t read them in plaintext.
Your clinical notes, health journal entries, medication names, lab results — all of it is encrypted by our application before it ever reaches the database. This means that even if someone broke into our database, they would see scrambled ciphertext. Not your words.
We use AES-256-GCM — the same encryption standard used in banking and healthcare systems worldwide.
2
AI sees patterns, not people
Before AI analyses your health data, your name, email, and dates are automatically removed. AI sees patterns, never people.
3
You decide who sees what
You control exactly what your care circle can see. Every access is logged, so you always know who has seen your data.
4
We don’t sell your data. Full stop.
We don’t sell your data. Our analytics are self-hosted — your health values never appear in any analytics system.
5
You’re always in control
You can export all your data or delete your account at any time. Your identity is permanently removed — nothing left can be traced back to you.
6
Push notifications that protect you
Push notifications never contain health details. The content stays on our encrypted servers — your phone fetches it only when you open the app.
What we actually do, in plain language.
We encrypt your most sensitive data twice.
Everything on our servers is encrypted at rest. Clinical notes, journal entries, medication details, and lab results get an additional layer of encryption applied by the app itself before reaching the database. Two locks.
We enforce your care circle permissions on our servers.
We never let the app decide who can see your data. Every access request is checked server-side, every time. There are no client-side shortcuts.
We log health record access, but never health record content.
Our application logs never contain the words you write in your health journal, your medication names, or your clinical notes. When something goes wrong and we need to debug it, we see event types and IDs — not your health history.
We built the AI pipeline with a mandatory identity-removal step.
Before any health data reaches an AI model, it passes through a scrubbing layer that removes your name, email, provider names, clinic names, and absolute dates. This step is not optional. It cannot be bypassed.
We don’t build on shaky consent.
When you create your account, we record exactly what you agreed to and when. If our Privacy Policy changes meaningfully, we ask again.
Questions
Things people ask us.
No. Your journal entries and clinical notes are encrypted with a key that is not stored alongside the data. Database administrators see ciphertext. Only the running application — with the correct key — can decrypt them.
Privacy isn’t a feature. It’s the foundation.
People with invisible illnesses have often been disbelieved, dismissed, and misunderstood. The last thing you need is to worry about where your health data goes.
Going Visible was built on the belief that your health story is yours. We’re here to help you understand it — not to profit from it.