Field-level encryption
Medicines, conditions, doctors and call transcripts are encrypted at the field level (AES-128 + HMAC via Fernet). A database breach alone reveals nothing readable.
Your parents’ health story is the most personal data a family has. Here is exactly how we treat it.
Medicines, conditions, doctors and call transcripts are encrypted at the field level (AES-128 + HMAC via Fernet). A database breach alone reveals nothing readable.
On the very first call, your parent hears what CareOS does and gives consent on a recorded line. No consent, no memory — the call data is not retained.
The AI drafts; your family approves. Health facts enter the record only after you confirm them. Bookings and purchases require your explicit tap.
Deletion cascades through recordings, transcripts, embeddings, profile and audit trail, leaving only a tombstone that the deletion happened.
JWT sessions with rotating refresh tokens and reuse detection. Family and care-professional namespaces are physically separated — a family token cannot reach clinical endpoints.
Your parents’ data stays in their own region rather than being shipped abroad. Our care-agency platform already operates under Japan’s APPI, one of the world’s strictest privacy regimes.
Our only revenue is your subscription. No ads, no brokers, no "partners". Your data is not the product.
Emergencies follow a pre-consented plan you define: who to call, which hospital, which ambulance service. Nothing improvised with their safety.
No. CareOS calls any ordinary phone. Your parent never installs anything.
You and the family members you invite. Care professionals see data only if you link them, with the scope you choose (summaries only, emergencies only, or full).
Yes. One action erases calls, transcripts, memory and profile — verifiably, across every layer.
The escalation ladder starts: you are alerted on every channel, then your chosen family contacts, and a one-tap conference bridges everyone with your parent.