Security & trust

Your client data is protected. By design, not by promise.

This page is the plain-English version. If your compliance officer wants the technical detail, that's on the compliance page. Here's what a clinician needs to know about how Praxnote keeps client information safe.

Request a BAA For compliance officers

Two security postures, your choice

Hosted by us, or running entirely inside your cloud.

Praxnote ships in two operating modes. Both have the same product, the same audit log, and the same access controls. What differs is where PHI lives — and what that means for your compliance review.

Praxnote Cloud

Hosted by Praxnote.

Multi-tenant SaaS on Praxnote-operated infrastructure. The default for solo and group practices.

  • HIPAA-aligned encryption at rest and in transit
  • BAA included on every paid plan
  • Anthropic-direct AI calls — no third-party proxies or aggregators; Anthropic's API does not train on customer content
  • US-hosted today; Canadian residency on the roadmap
  • SOC 2 audit on the roadmap; documentation available on request
  • Audit log, consent tracking, GDPR-style erasure workflows (PIPEDA-aligned)
Praxnote Dedicated — early access

Inside your cloud account.

Single-tenant Praxnote, deployed and operated by us, running inside your AWS account. Currently in early access — GCP and Azure on the roadmap.

  • PHI never crosses the boundary. All client data lives in your AWS account, in your region
  • Bring your own Anthropic API key — direct contract between you and Anthropic
  • Praxnote operates the tenant via customer-granted IAM. No standing access to PHI
  • Cross-boundary operational telemetry is PHI-stripped: error rates, latency, version, uptime, AI usage counts. Schema below
  • Backups live in your cloud account. Snapshots are yours; we don't retain copies
  • Same audit log, same product, same upgrade cadence (scheduled, customer-approved)
What operational telemetry leaves a Dedicated tenant?

A narrowly-scoped, PHI-stripped channel flows back to Praxnote so we can operate your tenant against its SLA. The channel contains: HTTP error rates, request latency percentiles, application version, uptime, AI usage volume (counts only — not content, not prompts, not responses), and infrastructure health metrics from your cloud provider. The full schema is part of every Dedicated contract and is auditable by you on demand. If we ever need to widen the channel, that's a customer-notification event, not a silent emission.

How your data is locked

  • Every piece of client information is encrypted while it sits in our database. The keys live somewhere else, not in the database itself.
  • When data travels between your browser and Praxnote, it's encrypted in transit. Same protection your bank uses.
  • Database backups are encrypted too. A stolen backup file would be unreadable.
  • If you work in places where wifi is unreliable (home visits, schools, rural clinics), Praxnote can hold a PIN-locked copy on your device. Without the PIN, the cache is unreadable.

Who can see what

  • Each role only sees what their job requires. Therapists see their own clients. Supervisors see the people they supervise. Practice administrators see the practice.
  • Each practice is fully separated from every other practice. No record from another practice is reachable from yours, ever.
  • Your session times out after 30 minutes of inactivity (the practice can adjust this). One open laptop is not one open chart.

Audit trail

  • Every time someone reads or changes client information, the action is logged with who did it and when. You can export the log for your records.
  • HIPAA requires keeping records for six years. Praxnote handles that retention automatically.
  • If a client requests their data be erased (GDPR for the EU, PIPEDA for Canada), Praxnote runs that workflow end to end, without breaking the HIPAA retention rule.
  • Consent is tracked plainly: what the client agreed to, when, and whether they later revoked it.
  • A Business Associate Agreement is included on every paid plan.

How we run the platform

  • The AI we use (Anthropic) is called directly. No middleman vendor sits between Praxnote and the AI.
  • This site uses no third-party fonts, trackers, or analytics. View source if you like, nothing is loading from Google or anyone else.
  • Anthropic's API does not train on customer content. Your charts do not feed any AI model's training data.
  • Anything destructive (deleting, voiding, redacting) requires an explicit confirmation. There's no one-click way to lose work.

What we don't do

  • We do not feed your charts into AI training pipelines, and Anthropic's API does not train on them either.
  • We do not run third-party analytics by default.
  • We do not load fonts, scripts, or images from third-party servers.
  • We do not route AI calls through any other vendor.
  • We do not mark up payment processing.
  • We do not make canceling difficult.

What you can hand your compliance officer

  • Activity log export (CSV)
  • Summary of any erasure request and how it was carried out
  • Per-client consent log
  • Billing audit trail
  • BAA template, on request
  • Data residency setting (US today; Canada on the roadmap)

What we haven't done yet

  • Third-party SOC 2 or HITRUST certification — on the roadmap
  • Independent penetration test — on the roadmap
  • HIPAA-aligned is not the same as third-party-attested. We say so plainly here so your compliance team can plan around it.

When a client asks for their data to be erased

Redacting, not deleting. Compliant with HIPAA and GDPR at the same time.

European law (GDPR) gives clients a right to be forgotten. United States law (HIPAA) requires a six-year retention window. Both can be true. Praxnote redacts the identifiable information from notes, transcripts, documents, messages, assessments, and billing entries, and keeps the empty record shells that HIPAA requires. Every step is logged.

  1. Request. A practice administrator opens a request and chooses what to erase (notes, documents, messages, etc.).
  2. Approval. A Praxnote administrator reviews and approves. Both signatures are recorded.
  3. Execution. Praxnote redacts the requested information. The empty record skeleton stays for HIPAA retention.
  4. Summary. A summary of what was erased is written to the request, and the audit log captures the whole chain.

Have questions?

Talk to us about your specific situation.

The fastest path to a clear answer is a 20-minute call. We can walk through your practice's situation (solo, group, multi-practice, EU clients) and map it to what Praxnote does today.

Request a BAA Email security questions →