SHA-256 Trust Timeline
Each Legacy Vault™ entry is given a SHA-256 fingerprint on the server when it is created. When the entry is read, the fingerprint is recomputed and compared, so a changed entry shows up as a mismatch.
Security & Privacy
Your health data,handled plainly.
Health information is among the most sensitive data a person has. This page says what we do to protect it, what we do not do with it, and — just as important — what is not built yet.
In place today
What protects your data now.
Server-side AI only
Protocol Coach™ calls the Anthropic API from our servers, never from your browser. Only the context relevant to a request is sent, and your health data is not used to train AI models.
No data brokering
We do not sell, rent, or share your health data for advertising, and the product carries no ads. The service providers we rely on are named in the Privacy Policy.
Credentials kept out of page scripts
Sign-in tokens are held in HttpOnly cookies and attached to requests by our server, so scripts running in the page cannot read them.
Browser hardening
The web app sends a Content Security Policy, X-Frame-Options: DENY, HSTS in production, and a strict Referrer-Policy. No third-party frames or ad trackers are loaded.
Cookieless site analytics
Marketing pages record anonymous, cookieless page views only, and honor Do Not Track and Global Privacy Control.
Tamper-evident, explained
How the Trust Timeline works.
When you create a Legacy Vault™ entry, the server computes a SHA-256 fingerprint from the entry and stores it with the entry. Sealed entries are not edited in place; a correction is a new entry.
When an entry is opened, the fingerprint is computed again and compared with the stored one. If they differ, the entry is reported as failing its integrity check. The Trust Timeline lists these proof events — fingerprints, timestamps, and status, never the content itself.
You can ask a trusted person to witness an entry. That request, and the witnessing, are recorded as events on the timeline.
Tamper-evident means a change can be detected. It does not make a change impossible.
- Entry
- Example entry
- Fingerprint recorded
- sha256: e3b0…a41c
- Fingerprint recomputed
- sha256: e3b0…a41c
- Result
- Match — integrity verified
Where things run
The architecture, as far as it matters to you.
Website and web app
Served through Cloudflare. This is what your browser talks to.
Application server
The API runs on a server hosted with Hetzner and operated by VaultSpark Studios. AI requests are made from here.
Database
Account and protocol data are stored in a Postgres database provided by Supabase, with row-level access rules.
Hetzner and Supabase act as service providers under data processing agreements, as listed in the Privacy Policy.
Honest limits
What is not built yet, and what we do not claim.
Not yet / not claimed
- Member-held, zero-knowledge Vault Keys are planned and are not available today. Vault contents are protected by access controls on our systems, not by a key only you hold.
- The Living Protocol™ is not a HIPAA covered entity, and we do not claim HIPAA compliance or any third-party security certification.
- Sign-in is by email and password. Studio single sign-on is planned and not yet available.
What we collect
- Health and training information you choose to enter
- Protocol actions such as workouts logged, meals tracked, and vault entries created
- Account and session data needed to sign you in
What we never do
- Sell or rent your data
- Use your health data to train AI models
- Share your data with advertisers
- Keep your account data after you delete your account, except records the law requires us to retain
AI Provider Key
An optional setting for members to add their own Anthropic API key for eligible Protocol Coach™ requests is built but not yet activated: secure key storage is still being set up. It is separate from vault encryption; member-held Vault Keys are also planned and are not available today.
Legal
The binding detail is in the policies.
The Living Protocol™ is operated by VaultSpark Studios LLC. How your data is handled is governed by the Privacy Policy and Terms of Service.
The Living Protocol™ is wellness software. It is not a medical device and does not provide diagnosis, treatment, or emergency care.