Security & compliance

Built for HIPAA from the first commit.

How sentr. protects PHI, in plain language. Nothing here that we cannot show you.

BAA at signup

Every practice, every time.

Encrypted everywhere

At rest and in transit.

Every PHI touch audited

Kept six years. Nobody can change it.

Isolated per practice

Enforced by the database itself.

A second step at sign in

Required on every staff account.

Hosted on AWS

United States only. No PHI in logs.

Runs on

Amazon Web ServicesAnthropic Claude on Amazon BedrockClaimRevStripe
How we protect PHI

Eight things we do, and how.

Open any card for the detail. We keep the blueprints to ourselves, but never the facts.

Your agreementA BAA before any record exists.

Your Business Associate Agreement is part of signup. No email chain, no waiting.

More
  • Versioned, timestamped and kept with your account.
  • Our own agreement with AWS covers the hosting underneath.
  • Ask for a countersigned copy any time.
Your dataEncrypted everywhere. Isolated per practice.

Every record is encrypted at rest and in transit, and every practice is walled off inside the database itself.

More
  • Isolation is enforced by the database, not just the app, and tested on every code change.
  • Backups are encrypted, kept daily, and restorable to a point in time.
  • Stored in the United States only.
Your peopleThe right access for every role.

Seven roles, charts scoped to each discipline, and a second step at every sign in.

More
  • Idle sessions sign out automatically, and every sign-in is logged.
  • Admins can view as another user for support. Every view is recorded, and they cannot sign notes or accept terms while doing it.
  • Emergency access expires on its own, needs a written reason, and raises an alert.
Your record of everythingEvery touch of PHI, written down.

Who opened, changed, signed, exported or sent what, and when.

More
  • Nobody, including us, can edit or delete the audit trail.
  • Archived for six years and never changed.
  • Tamper-evident, so you can prove it has not been altered.
The AIPrivate and yours.

sentr. Scribe and sentr. Script run on Anthropic Claude through Amazon Bedrock, inside our own AWS account.

More
  • Nothing you record or upload is used to train any model.
  • Audio is transcribed inside AWS and deleted automatically within days. The signed note is what stays.
  • The referring-provider lookup sends only the provider name and city to the public registry, never a patient.
Payments and claimsCard numbers never touch us.

Stripe holds the card. ClaimRev carries the claim. Both connect over encrypted links.

More
  • Stripe sees a generic line, never a diagnosis or a procedure code.
  • Claims go to ClaimRev as data over an encrypted, authenticated connection.
  • Each practice connects its own Stripe account and its own ClaimRev subscription.
Your logsNo PHI in our logs.

Names, dates of birth and emails are stripped before anything is written to a log line.

More
  • Database logs never contain query values.
  • Alarms page us on failed audit writes and server errors.
Your way outYour data is yours to take.

Export a family’s full record or a batch of signed notes as PDF, any time, without asking us.

More
  • Every export is itself audited.
  • Leaving? We purge your documents and records on request and confirm in writing.
Straight answers

What we do not claim.

Badges are easy. Here is where we actually stand.

  • No telehealth video. We bill telehealth visits correctly. We do not host the call.
  • Compliance is shared. We secure the platform. Your practice still owns its policies, training and workstation rules.
Subprocessors

Three vendors. All under agreement.

Nobody else touches your data. No analytics trackers, nothing that reports crashes to an outside service, no SMS vendors.

Amazon Web Services

Hosting, storage, identity, email, transcription and the AI models. One BAA covers all of it.

ClaimRev

Insurance claims and remittances. Your own subscription, our encrypted connection.

Stripe

Card payments for family statements. Cards live with Stripe, never with us.

The full list, with what each vendor receives, is on the Subprocessors page and is updated before any change takes effect.

Questions

Asked by every practice.

Is sentr. HIPAA compliant?

Yes. sentr. is built to the HIPAA Security Rule: encrypted PHI, audited access, a signed BAA, and administrative controls we keep in writing. HIPAA has no official certification, so any vendor who says they are "certified" is describing an audit, not a government stamp.

Where is my data stored?

In AWS data centers in the United States, with encrypted backups kept in a second US region. It never leaves the country.

Who at sentr. can see my records?

Nobody by default. Support access happens only through audited emergency access that expires on its own and needs a written reason, and you can see every instance in your own audit log.

What happens to sentr. Scribe recordings?

They are transcribed inside our AWS account, used to draft your note, and deleted automatically within days. They are never used to train any model.

Do you store card numbers?

No. Stripe holds every card. We keep only the last four digits and the card brand so your front desk can recognize it.

Can I take my data with me?

Yes. Export a family’s full record or a batch of signed notes as PDF whenever you like. If you leave, we purge your data on request and confirm it in writing.

Found a vulnerability?

Tell us before you tell anyone else and we will work with you, not against you. Email hello@thesentr.com with “Security” in the subject.

Have a security questionnaire? Send it over.

A founder answers it, not a form.