When you visit healthclaw.io or interact with this demo application, we may collect:
We do not use third-party behavioral tracking or advertising cookies.
If you deploy HealthClaw Guardrails yourself:
API calls made against the public demo endpoint at /r6/fhir/* are ephemeral and stored
transiently in the demo database. Do not submit real patient data to the public demo.
When you connect a health data source through the hosted HealthClaw connector, we process:
Every read passes through PHI redaction before reaching an AI model; every write requires step-up authorization and explicit human confirmation. In pass-through proxy mode we store nothing — data flows from your own FHIR server through the guardrails and is not retained.
Information collected is used solely to:
We do not sell, rent, or share personal information with third parties for commercial purposes.
HealthClaw Guardrails is designed with PHI minimization as a core architectural principle:
These controls are reference implementations. Organizations deploying this software for production use with real patients must conduct their own risk assessment, engage qualified legal counsel, and satisfy all applicable regulatory requirements (HIPAA, HITECH, state privacy laws, etc.).
HealthClaw is a reference implementation of guardrail patterns for AI-agent access to health data. The guardrails described above — PHI redaction, append-only audit, step-up authorization, and tenant isolation — are active in the software. The public demo runs synthetic or patient-directed data and is not a hardened multi-tenant PHI service. Production deployments are expected to add tenant-authenticated reads, BAA-covered infrastructure, and the organization's own operational and regulatory controls on top of these patterns.
Data submitted to the public demo may be retained for up to 30 days for debugging purposes, then deleted. No backups are made of demo data. Do not submit real PHI to the public demo.
You control all retention. The software does not phone home. No data leaves your infrastructure unless you configure an upstream FHIR server or external service.
A beta tester's tenant holds one fictional sample patient — one condition, three observations, one medication and an intake questionnaire — plus your chat with the agent and anything you approve there, and no other health data about you. Deleting a connection from the CareAgents hub purges that tenant's records immediately, in the same request, and reports the row count back.
Two things outlive that deletion, and neither holds health data. The PHI-free audit trail is retained, including the deletion itself. Your CareAgents account — your email address, your passkey credential and which sources you connected — is a separate record in CareAgents' own database, and deleting your records does not delete it. There is no self-serve button for the account yet: email support@healthclaw.io and we will remove it and confirm when it is done.
The software may connect to the following external services, depending on configuration:
Upstream FHIR server URLs are never exposed to end users (URL rewriting is enforced by the proxy layer).
HealthClaw can deliver health information over consumer messaging platforms such as Telegram, Slack, and Discord. These are consumer communication channels, not BAA-covered transport, and we do not treat them as secure medical channels.
We operate these channels under a patient-directed access posture: the patient is retrieving their own records to a channel they have chosen. Under HIPAA's individual right of access, an individual may request delivery of their own health information over an unsecured channel after being warned of the risk. In this flow HealthClaw acts as the patient's agent retrieving their own data — not as a covered entity making a disclosure to a third party.
To reduce exposure on these channels, HealthClaw applies several mitigations:
To be candid about the trade-off: messaging-app transport combined with HealthClaw's guardrails (redaction, audit, step-up authorization, and data minimization) exceeds the security posture of typical consumer health apps, which routinely move full records over similar channels without these controls. It is still not a substitute for BAA-covered transport where a covered entity is making a disclosure.
The public demo site uses only session cookies required for Flask operation. No advertising cookies, third-party trackers, or behavioral analytics are used. Server-side access logs are the only analytics collected and are not shared with any third party.
If you use the hosted connector (via Claude, ChatGPT, or another MCP client), you can:
We never sell your data, never use it for advertising, and never use it to train AI models.
If you have submitted data through the public demo and wish to request deletion, contact us at privacy@healthclaw.io or support@healthclaw.io. We will respond within 30 days.
For self-hosted deployments, all rights (access, deletion, portability) are exercised directly against your own database. We have no access to your data.
This software and website are intended for healthcare developers and technologists. We do not knowingly collect personal information from children under 13. If you believe a child has submitted personal information through the demo, contact us at privacy@healthclaw.io.
We implement reasonable technical safeguards including HTTPS for all public endpoints, HMAC-signed write tokens, append-only audit logs, and tenant-scoped queries (with optional tenant-bound token authentication on reads, enabled per deployment). No system is perfectly secure. Please report security vulnerabilities via GitHub Security Advisories or security@healthclaw.io.
We may update this policy as the software evolves. Material changes will be noted in the project release notes and this page will reflect the updated effective date. Continued use of the service after changes constitutes acceptance of the revised policy.
Privacy questions: privacy@healthclaw.io
Security disclosures: security@healthclaw.io
General: healthclaw.io
GitHub Issues: aks129/HealthClawGuardrails