Bounded runtime AI
Cairie uses Hathr.ai under a Business Associate Agreement. The shipped extension does not introduce a second runtime AI provider.
Security and privacy
HIPAA-aware by design, not reduced to a badge.
Cairie handles PHI inside real Medicare workflows. The controls below describe what the product actually enforces. They are not a claim of HIPAA certification.
The safety model follows the data.
Each control sits at a real boundary: collection, memory, storage, AI dispatch, portal action, or audit.
Encrypted local storage
Sensitive persisted data is protected with AES-GCM in the browser. In-flight call context stays in memory wherever possible.
No screenshots
The product does not send screenshots, vision frames, or image content to an AI model. Portal assistance uses bounded page structure.
Approval before commitment
Submit, enroll, sign, pay, confirm, authorize, and similar actions require explicit agent approval.
PHI-redacted audit trail
Audit records capture what happened while stripping protected identifiers before entries are written.
Narrow portal access
URL allowlists and hard blocks constrain autonomous navigation. Sensitive CMS and ThinkAgent surfaces have additional boundaries.
Data path
Four boundaries, each visible.
- 1
Read
Authorized portal context and optional on-device transcript text.
- 2
Hold
Call state stays in service-worker memory unless encrypted persistence is required.
- 3
Reason
Covered AI processing runs through Hathr.ai under BAA.
- 4
Act
Low-risk preparation can run; commit-shaped actions pause for the agent.
See Cairie work a Medicare call.
Book a focused walkthrough of the live workflow, or join the launch list for the Chrome Web Store install link.
Prefer to try it yourself?