Most health tools do one of these. VitaCrypt does all four, and the value is in how they compound.
A unified data fabric built to ingest any health signal; every recommendation cited to live science; personalization down to your genotype and local environment; and privacy built in by design, so centralizing this data never means exposing it. Here is how each one works.
VitaCrypt pulls each source and normalizes it into one schema, so scattered data becomes a single queryable profile, built to fold in any health signal and grow over time. The privacy pillar is built so that profile is encrypted under your key and the server works with one ciphertext, not a separate plaintext feed per source.
Wearables connect via Apple Health export today, with direct device APIs on the build path; DNA, microbiome and lab files are uploaded; environment is pulled from your location.
Different formats (VCF, FHIR, CSV, JSON) are mapped into one queryable health schema.
In the target custody model, the unified profile is encrypted with a key held in your iOS Keychain / Android Keystore. The design goal: plaintext never leaves the device.
| Source | What it adds | Availability |
|---|---|---|
| Genetics | Variants that reshape every other signal: folate cycle, lipids, caffeine, methylation | At MVP launch23andMe / Ancestry upload |
| Wearables | HRV, sleep stages, recovery, resting heart, activity load | At MVP launchApple Health export today; direct device APIs on the build path · Apple Watch, Oura, Whoop |
| Environment | PM2.5, ozone, pollen, UV, by your location in real time | At MVP launchPurpleAir / IQAir / OpenWeather |
| Lifestyle | Sleep, energy, stress, diet and workload, captured as lifestyle check-ins | At MVP launchin-app check-ins |
| Microbiome | Gut composition → inflammation, nutrient absorption, diet response | Upload at MVPpartner API on roadmap |
| Labs & blood | CRP, ApoB, HbA1c, lipid panels: the objective check on the wearable signal | Upload at MVPHL7/FHIR connectors 2027 |
See the sources on the home page → Integration spec in the litepaper →
Most apps bake in whatever the guidelines said the year they shipped. VitaCrypt re-queries the literature continuously, so a recommendation can change the week a relevant paper, GWAS hit, or guideline update appears. Every recommendation carries a real source (PubMed PMID) retrieved live, and the model cannot invent citations.
An agent continuously scans public literature and guidelines. It never touches your data, it works entirely on published papers.
Whether a finding applies to you is matched against your profile server-side, over a backend encrypted at rest. Running that match under FHE, so the model never sees your genotype or labs in the clear, is an R&D roadmap goal.
Each surfaced recommendation carries the source it rests on, graded by evidence strength.
Live today, we search PubMed (~40M indexed records), Europe PMC, OpenAlex, ClinVar/dbSNP and the GWAS Catalog. On the roadmap: USPSTF, NICE, WHO and Cochrane. "Cross-referenced" means we search these indexes for evidence relevant to your profile, not that millions of studies stand behind any one recommendation.
Every insight is classified before it is shown. Evidence-backed insights carry real PMIDs, a confirmed-N-of-M corroboration check across the retrieved papers, and a High / Moderate / Emerging confidence indicator. Exploratory insights, the cross-domain connections the literature has not settled, are labelled preliminary rather than asserted. And anything clinical is withheld server-side and replaced with a warm handoff to the right clinician. For established pharmacogenomic markers (starting with CYP2C9) the published CPIC consortium guidance is shown as a descriptive reference, the one place the grade comes from a clinical consortium rather than a model.
See the full corpus list → Matching protocol in the litepaper →
Generic advice optimizes for a median person who doesn't exist. VitaCrypt reads each signal against your genotype and local exposures, so the same air, the same HRV dip, the same lab value yields a different instruction for a different person.
Genotype + current exposures (air, season, location) + physiology (HRV, sleep, labs).
Gene × environment interactions are evaluated against the cited literature; keeping that evaluation under FHE is on the privacy roadmap.
A small set of concrete, time-bound steps, each with its evidence attached.
The folate-cycle variant blunts homocysteine clearance; ambient PM2.5 adds inflammatory load. Together they're linked to higher ischemic-heart and vascular risk.
ε4 carriers show a greater neuroinflammatory response to fine-particulate exposure, observed even in young adults, relevant to long-horizon cognitive risk.
David is a composite case from the litepaper. Values are illustrative; the gene–environment methodology and citations are real.
Privacy here is concrete and present-day: your data is encrypted at rest under per-user keys, retention is minimal, the most sensitive data is minimized and pseudonymized before egress, and VitaCrypt is independent, not a feature of any single AI giant and built so the underlying model can be swapped rather than welded in. Stronger cryptographic guarantees, including fully homomorphic encryption, are a far-horizon roadmap item, not a current capability.
Today: encrypted at rest under per-user keys, minimal retention, and independence from any single AI giant. The near-term build is minimization and pseudonymization before egress and a BAA-grade zero-retention inference endpoint. Self-hosted open-weight inference and, far out, fully homomorphic encryption are roadmap, the strongest theoretical guarantee but today a poor fit for live multi-source cross-referencing. The master key is still server-side today and the platform is not yet end-to-end blind. We state this plainly.
Architecture designed for HIPAA / GDPR alignment. Working product, pre-launch; no production health data yet.
Watch the live walkthrough → Threat model in the litepaper →
VitaCrypt opens to its first design partners in Q4 2026. Investors and prospective partners, reach out directly.