Security & privacy
What is in place, and what is not yet.
A clinical tool earns trust by being precise about its safeguards. This page describes the system as it is today.
HIPAA status
HealthDefence will act as a business associate of the clinicians and practices that use it.
Not yet ready for real patient information.The business associate agreements with our hosting and AI providers are not yet in place, so HealthDefence does not accept real patient cases today. Development and demonstrations use invented cases only. We will not describe the service as HIPAA compliant before those agreements, and the program around them, are complete.
| Safeguard | Status |
|---|---|
| Business associate agreement with Google Cloud (hosting) | Before launch |
| Business associate agreement with Anthropic (AI models) | Before launch |
| Business associate agreement offered to every customer | Before launch |
| Written HIPAA risk analysis and security policies | Before launch |
| Identity proofing of every clinician switched on | Before launch |
| Audit logging, kept for six years | In place |
| Patient information kept out of logs, alerts, email and payments | In place |
Who can get in
- Verified clinicians only. The tools open only after a clinician's licence is verified; in the US, the NPI is checked against the CMS NPPES registry, and anything the registry cannot confirm goes to manual review.
- Identity proofing. Before sign-ups open, each clinician will also verify their identity with a government ID and a live selfie through Stripe Identity, so the licence is matched to the person, not just to a name. The ID images stay with Stripe; we receive the result and the verified name.
- Your records are yours. Every stored consultation, document and consent record is scoped to the signed-in clinician. Administrative access is limited to a named allowlist.
- Sessions the page cannot read. The web app keeps its session in HttpOnly, Secure, SameSite=Strict cookies, requires an anti-forgery token on every change, and access tokens expire after 15 minutes.
How data is protected
- Encrypted in transit over HTTPS, with HSTS on the app.
- Encrypted at rest by Google Cloud's default encryption.
- Private database. The database is reachable only on a private network inside our Google Cloud project, with daily backups and point-in-time recovery for production.
- Audit trail. Each consultation is recorded for audit, and cloud audit logs are kept for six years.
- Strict browser policies. A strict content security policy and no third-party scripts in the app; this website has no analytics, cookies or trackers.
Where patient information goes
- The service runs in Google Cloud in the United States.
- The case you enter is sent to Anthropic's Claude models to produce the answer.
- Only drug or concept names, never the case, are sent to the public US reference services used for look-ups (NLM RxNav and terminology services, openFDA, and the AEMPS register for Spanish products).
- Patient information is not written to application logs or operational alerts, and never reaches payments (Stripe) or email (Resend).
Not in place yet: multi-factor sign-in is not offered today, and retention periods for every store of consultation data will be set before real patient information is accepted.
Questions from your security or compliance team
We are glad to walk your team through the architecture and the HIPAA program. Write to sales@healthdefence.ai.