Skip to main content

Trust center

Security that starts before the first word is recorded

Quillentra handles some of the most private conversations in medicine. Here's exactly how we protect them, and what we ask of your practice in return.

Safeguards

Protection built into every plan

The same safeguards apply to every practice, from a solo clinician on Free to a group on Practice.

A BAA with every vendor that touches PHI

Your practice accepts our Business Associate Agreement when it's created, on every plan including Free. Every subprocessor that can access patient information is bound by a BAA with us, and we report a breach of unsecured PHI to you within 60 days of discovery.

  • Every plan
  • Accepted at setup
  • Subprocessors under BAA

Encrypted in transit and at rest

Everything travels over TLS 1.2 or higher and is stored with AES-256, with keys held in AWS Key Management Service. Patient details, transcripts, documents and assistant conversations are encrypted a second time, field by field, with AES-256-GCM.

  • TLS 1.2+
  • AES-256 at rest
  • Field-level AES-256-GCM

Sign-in without shared passwords

Clinicians sign in with Google, Apple or a single-use 6-digit code sent to their email. A password is optional, and anyone who adds one must also use an authenticator app for every password sign-in.

  • Google · Apple · email code
  • Password + TOTP

Automatic sign-out

Quillentra signs you out after 15 minutes without activity, with a warning a minute before, and every session ends after at most 12 hours. You can see and sign out active sessions at any time.

  • 15-minute idle limit
  • 12-hour maximum

A tamper-evident audit trail

Sign-ins, views, edits, copies and exports are recorded in an append-only, hash-chained log that's verified every day. It never contains clinical content, and owners and admins can check its integrity and export it.

  • Hash-chained
  • Verified daily
  • Kept 6+ years

Short-lived audio by default

Visit audio is deleted as soon as the note is written, unless your practice chooses to keep it for 7 or 30 days. Deleted visits wait 3 days in the trash, then are purged. Notes stay until you delete them, because they're part of your record.

  • Audio deleted after the note
  • 3-day trash

Never used to train AI

We don't use your data to train AI models, and our AI provider doesn't either: it processes content only to return a result to us, under a BAA. Style learning only adjusts your own account, and you can review or turn it off.

  • No model training
  • No selling or advertising

Data flow

Where visit data goes

From your microphone to a signed note, patient information stays inside services covered by a Business Associate Agreement.

  1. Your browser uploads the recording in short segments over TLS. Audio is never saved on your device.

  2. It's stored encrypted with AES-256 in the United States (Amazon Web Services, us-east-1).

  3. Speech-to-text runs on AWS HealthScribe & Amazon Transcribe. Its output files and job records are deleted once we have the transcript.

  4. The note is drafted in your template on Amazon Bedrock. Nothing is used to train models.

  5. You review and sign the note. The audio is deleted, unless your practice keeps it for 7 or 30 days.

Billing is separate. Stripe processes subscription payments outside this flow and never receives patient information.

Access and accountability

The right people in, and a record of everything

Strong sign-in keeps the wrong people out. A tamper-evident trail shows what the right people did.

Passwordless by default

There's no shared password to leak or reuse. Each person has their own account, tied to a verified email address.

  • Sign in with Google, Apple, or a single-use code emailed to you. Codes expire after 10 minutes and allow limited attempts.
  • Add a password if you like: every password sign-in also needs an authenticator app, and that can't be switched off.
  • We email a security notice when a password is added or changed, and you can sign out any device from your settings.
  • Each practice's data is kept separate, and visits are private to the clinician unless the practice turns on a shared workspace.

An audit trail you can verify

Who did what, when, and from where, for every sign-in, view, edit, signature, copy and export in your practice.

  • Each entry is chained to the one before it with a cryptographic hash, and the log is append-only.
  • The whole chain is verified every day, and owners and admins can run the check themselves.
  • Owners and admins can filter the log and export it as CSV for reviews and investigations.
  • Entries hold identifiers and actions only, never clinical content, and they're kept for at least six years.

Retention

Kept only as long as it's needed

Audio is temporary. Your notes are part of the medical record, so they stay until you delete them. Scheduled deletions run every 15 minutes.

Read the full retention policy

DataDefault

Visit audioOwners and admins can choose 7 or 30 days
Deleted after the note
Unfinished recordings
24 hours
Audio of a visit that failed to processSo the visit can be retried
7 days
Deleted visitsOwners and admins choose 1–30 days, or no trash
3 days in the trash
Transcripts and notes
Until you delete them
Encrypted backups
Up to 35 days
Audit trailCan't be edited
At least 6 years

Subprocessors

Who processes data for us

Every company that processes customer data on our behalf. Customer data is stored in the United States (Amazon Web Services, us-east-1).

  • Amazon Web Services

    Under BAA
    Purpose
    Hosting, database, encrypted audio storage, key management, logs and transactional email (Amazon SES)
    Data
    All customer data, including PHI
    Location
    United States
    Safeguard
    AWS Business Associate Addendum
  • AWS HealthScribe and Amazon Transcribe (AWS)

    Under BAA
    Purpose
    Speech-to-text: HealthScribe for visit conversations, Amazon Transcribe for dictations and other languages
    Data
    Visit audio
    Location
    United States
    Safeguard
    AWS Business Associate Addendum; output and job records deleted after use
  • Amazon Bedrock (AWS)

    Under BAA
    Purpose
    Claude AI models for note drafting, AI edits, template import and the clinical assistant
    Data
    Transcripts, notes, patient context and assistant messages
    Location
    United States
    Safeguard
    AWS Business Associate Addendum; not used to train models
  • Stripe

    No patient data
    Purpose
    Subscription billing and payments
    Data
    Practice billing contact and payment details; no patient information
    Location
    United States
    Safeguard
    Never sent patient information; card details are entered only on Stripe-hosted pages

We update this list before a new subprocessor begins processing PHI. To be told about changes, email privacy@quillentra.com.

Compliance

Where we stand

Plainly stated, including what's still in progress.

HIPAA

In place

A BAA on every plan, BAAs with every PHI subprocessor, Security Rule safeguards, and a documented incident-response and breach-notification procedure.

Read the BAA

PIPEDA

In place

In Canada we act as a service provider to your clinic, following PIPEDA's ten fair information principles and provincial health-privacy laws.

How we meet PIPEDA

SOC 2

In progress

We're aligning our controls with the AICPA Trust Services Criteria. We haven't completed a SOC 2 examination yet, and we'll update this page when a report is available.

Shared responsibility

Your practice's part

HIPAA is a partnership. These are the safeguards only your practice can put in place.

  • Follow your consent policy

    Tell patients about the AI scribe and confirm their consent before you record a visit.

  • Protect the keys to sign-in

    Turn on two-step verification for the email, Google or Apple account each clinician signs in with.

  • Keep membership current

    Remove people from the practice when they leave, and give admin rights only to those who need them.

  • Handle exports with care

    Downloaded PDF and Word files contain patient information. Store them according to your policies.

FAQ

Questions from compliance teams

Straight answers to what practices ask before they sign up.

Is Quillentra HIPAA compliant?

Quillentra is built for HIPAA. Every practice is covered by our Business Associate Agreement, on every plan, and every vendor that can access PHI is bound by a BAA with us. The safeguards on this page implement the Security Rule's administrative, physical and technical requirements. Compliance is shared, though: your practice remains responsible for its own policies, such as patient consent, who has access and how exported notes are stored.

Do you use our data to train AI models?

No. We never use your data to train AI models, and our AI provider processes content only to return a result to us, under a BAA, without training on it. We don't sell your data or use it for advertising.

Where is our data stored?

Customer data is stored in the United States (Amazon Web Services, us-east-1). Encrypted backups are kept for up to 35 days and are used only to recover from a failure.

Are you SOC 2 certified?

Not yet. We're aligning our controls with the AICPA SOC 2 Trust Services Criteria, but we haven't completed a SOC 2 examination. We'll update this page when a report is available.

Who in our practice can see a visit?

Only the clinician who recorded it, unless your practice's owners or admins turn on the shared workspace. Patient records (name, date of birth and background) belong to the practice, so every member can see the practice's patient list.

What happens to the recording after the note is written?

It's deleted as soon as the note is generated, unless your practice has chosen to keep audio for 7 or 30 days. If processing fails, the audio is kept for 7 days so the visit can be retried, and unfinished recordings are deleted after 24 hours. Audio is never stored in your browser.

Does the billing provider see patient information?

No. Stripe handles subscription payments and receives only the practice's billing details: its name, the billing contact's email, the plan and the number of seats. Card details are typed on Stripe-hosted pages and never reach Quillentra, and no patient information is ever sent to Stripe.

How would we be told about a breach?

Under our Business Associate Agreement, we report a breach of unsecured PHI to your practice within 60 days of discovery, and we follow a documented incident-response procedure.

Can a patient ask for their information to be deleted?

Patients should contact their healthcare provider, who controls the record. Your practice can delete a patient, a visit or a document at any time, and we help providers respond to these requests.

Questions about security?

Bring your compliance team in

We're glad to walk your privacy officer or IT lead through how Quillentra protects patient information.