Built for health data

Most consumer apps treat health data like marketing data

Read the privacy policy of the average caregiver app and you’ll find phrases like "we may use de-identified data to improve our services" or "third-party advertising partners." For an app that holds your parent’s medication list, hospitalization history, and advance directive, that’s not OK. Most users never read the policy, so the gap between expectation and reality is invisible until something goes wrong.

Encryption, audit, no data brokers

Every database row is encrypted at rest (AES-256). Every connection is TLS 1.3. Every change to the workspace is logged with actor, timestamp, and consent basis. Your data is never used to train AI models. Your data is never sold to brokers or advertisers. AI features (visit summaries, smart upload) pass content to Claude via Anthropic’s API on a no-retention basis; the prompt and response are not stored on Anthropic’s side and Anthropic doesn’t train on it. Read the full posture on /security.

What "private by default" actually means

You add Mom’s medication list. The list is encrypted in the database. It’s visible only to her workspace members. It does not show up in any internal Kintaria dashboard, search, or report. If you export the workspace and delete it, the data is gone from Kintaria’s primary database within 24 hours and from backups within 30 days. We can’t read your data even if we wanted to (and we don’t).