An unbranded microphone and document folder with a sage shield-and-check icon on a slate desk
HIPAAOtter AItherapy documentationlanguage accessBAA

Is Otter AI HIPAA Compliant? Contract Checks Before Recording Therapy

Photo of Dr. Sofia Reyes
Dr. Sofia Reyes Clinical Documentation & Compliance Editor 11 min read
Outline
Decision before uploadFictional completed checkStop rule
Plan and contractNorth Loop: Enterprise and a signed BAA are recorded before PHI enters the workspace.No signed BAA or unclear plan: do not record.
PHI captureMaya Chen: Notetaker, calendar sync, and auto-join are restricted and tested.Unverified capture setting: disable or restrict it.
Sharing and accessJordan Lee: Link sharing is disabled; each clinician has a unique account.Public sharing or unknown access: do not upload.
Language and consentMaya: Language, interpreter need, and recording consent are documented.Unresolved suitability, interpretation, or consent: stop.

Otter’s public HIPAA help article and Enterprise plan guidance, checked November 2026. This filled example uses fictional names and is an operational prompt, not legal, privacy, licensing, or language-access advice.

The printable checklist adds a BAA evidence row, workspace-setting checks, language-suitability questions, consent prompts, and a place to record the person who approved the upload. Use the preview above to stop a risky recording before it starts.

Otter’s current help guidance makes the contract boundary clear, but your practice still has to prove that the workspace behaves as intended. Record the decision, the evidence reviewed, and the person who approved the upload; this is not a certification of Otter or your practice.

What Otter says about HIPAA use

Clinicians who ask whether Otter AI is HIPAA compliant need a conditional answer, so start with the contract boundary rather than the product label. Otter’s HIPAA help article says HIPAA compliance is available only on the Enterprise plan. It directs the customer to an account manager or sales team to begin the Business Associate Agreement process. The article also says Otter is not a HIPAA-covered entity by default and becomes a business associate when a signed BAA is in place. If your intended use creates, receives, maintains, or transmits PHI, the article says the BAA must be executed before that data is handled.

That answer is narrower than “Otter AI is HIPAA compliant.” It describes a plan, a contract step, and a customer responsibility. It does not tell you that every account, feature, calendar connection, auto-join setting, sharing option, or language workflow is suitable for your practice.

If you searched for “otter ai hipaa compliant,” the useful answer is conditional. Treat HIPAA compliance as an evidence question: name the exact plan, contract, and workspace controls rather than treating the vendor name as proof.

The HHS business associate guidance and the requirements in 45 CFR 164.502(e) and 45 CFR 164.504(e) are the federal starting point. They do not turn a vendor statement into a legal conclusion about your use case.

Confirm the plan and BAA before PHI enters Otter

The practical answer is conditional: the Enterprise plan and a signed BAA establish a starting point, not a finished therapy workflow.

Do not start with the microphone. Start with the account and the written agreement.

  1. Record the legal name of your practice and the Otter workspace that will process the session.
  2. Ask the account manager to identify the exact Enterprise plan, product scope, and enabled features in writing.
  3. Obtain the BAA and confirm that it is executed by the right parties before any identifiable client information is captured.
  4. Save the signed agreement, plan confirmation, date checked, and named Otter contact in your vendor evidence file.
  5. Record what the BAA covers and what it does not. Do not fill a silent clause with an assumption from a sales call.
  6. Recheck the agreement if you add a feature, connect a calendar, change a workspace, or move from a test account to production.

A BAA is necessary when Otter is acting as your business associate for PHI. It is not a HIPAA certification badge, a recording-consent form, a language-access plan, or proof that a transcript is clinically fit. Use this business associate agreement checklist to organize the contract evidence. If the vendor says a feature is available only through an account manager, keep the written answer with the contract rather than treating a public page as a feature guarantee.

For this decision, keep the signed agreement beside the tested workspace record. The two documents answer different parts of the same deployment question.

Check the recording setup

Use the pack this week to record the BAA, workspace controls, language check, and consent decision before any PHI upload.

  • Otter pre-upload BAA and language-suitability checklist
  • Rev account, language, and pre-upload activation checklist
  • Consumer-versus-contracted translation data-flow checklist
  • Translation-vendor BAA, Microsoft surface, app acceptance, and therapy-document RFP sheets

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

In the vendor file, identify the review by the tool, plan, BAA, settings, and tested workflow. Treat the label as an index term, not as a conclusion about the vendor.

Control how therapy PHI is captured

Otter’s help guidance puts the customer in charge of controlling when and how PHI enters the workspace. That matters because Notetaker can automatically join and record scheduled meetings. A calendar connection or auto-join default can capture a meeting that was never approved for recording.

Before a session, have the workspace owner and the treating clinician walk through the same settings:

  • Whether Notetaker is enabled for members
  • Whether scheduled events can trigger auto-join
  • Which calendar is connected and which events are synced
  • Whether a clinician can change meeting settings without an admin review
  • Whether the workspace permits capture from a personal calendar or device
  • What the client is told before recording begins
  • How the practice stops a recording when consent is withdrawn

Otter’s public help article says workspace admins can manage Notetaker access, review calendar connections and synced events, and manage auto-join and sharing settings. Those controls are useful only if the practice assigns an owner, tests them, and keeps evidence of the result.

A completed record is not proof that a session may be recorded. It is proof that your practice asked the right questions before an upload.

Disable sharing and map access

Otter says public and link-based transcript sharing are not appropriate when PHI is involved and that customers must explicitly disable those features. Make that a workspace control, not a personal reminder.

Test the path with fictional content:

  1. Create a non-identifying test conversation.
  2. Attempt to share it by public link and by external invitation.
  3. Confirm that the workspace blocks the paths you do not permit.
  4. Confirm which administrators can view, export, delete, or change retention.
  5. Record whether support staff or subprocessors can access audio, transcripts, or logs.
  6. Remove the test conversation and document the deletion result and any backup window.

Use unique accounts. Do not use a shared practice password. Keep front-desk, billing, supervisor, and clinician access separate when their duties do not require full session content. The minimum-necessary principle is a practice design question, not a feature label.

Ask the vendor in writing:

  • Who can open audio, transcripts, notes, and usage reports?
  • Which subprocessors touch the content or provide support?
  • Can a support person play audio, and under what approval?
  • What is retained after a conversation is deleted?
  • Can the practice export the transcript and delete the vendor copy?
  • What notice and response process applies to a suspected disclosure?

If the answer is “contact your account executive,” keep the question and the answer in the vendor file. A blank public page is not evidence that a control does not exist, and it is not evidence that it does.

Tie the review label to the exact account, plan, and evidence checked, rather than to the vendor name alone. That evidence matters more than a generic compliance label.

Separate language suitability from contract eligibility

A signed BAA answers a contract question. It does not answer whether Otter’s transcription workflow is suitable for the language, dialect, script, code-switching pattern, or clinical setting in front of you.

That distinction matters in practice. Contract eligibility and language suitability must be recorded as separate checks. For broader safeguards around AI transcription, see the HIPAA-compliant AI transcription guide.

Before a non-English session, record these as separate decisions:

QuestionWhat you need to confirmWhat it does not prove
Transcription languageThe exact language and variant supported by the account and current product workflowThat the output will be clinically accurate or complete
Note outputWhether your chosen note workflow can use the transcript in the language you needThat the client-facing material or interface is translated
Mixed-language sessionWhether code-switching is supported for the specific configurationThat a bilingual clinician can safely accept every sentence
Client communicationWhat the client will hear, see, and consent to before recordingThat machine output is qualified interpretation
Human language supportWho will interpret or translate when the clinician does not speak the client’s languageThat software replaces a qualified interpreter or translator

Do not claim a language is supported because a vendor page names a broad language family. Confirm the current official list, the region or script when relevant, and the behavior of the actual workflow you will use. If you cannot verify a language or configuration, write “we could not find this stated” and stop before PHI upload. The contract review should not end with a generic HIPAA answer.

The assessment is incomplete until the language and configuration are recorded separately from the BAA. A defensible “otter ai hipaa compliant” review names both decisions instead of treating the search phrase as a certification.

If the clinician does not speak the client’s language, do not use transcription as a substitute for a qualified interpreter. Confirm the applicable federal, state, payer, professional, and organizational requirements. The working with interpreters in therapy guide can help you plan the conversation, but it does not decide your legal or professional duty. Your answer to “otter ai hipaa compliant” should keep that language-access decision separate from the contract review.

HIPAA and recording consent overlap in practice but are not the same question. A BAA does not authorize a recording. A client’s consent to record does not create the safeguards required for a business associate.

Before the session, decide:

  • What the client is told about the recording and its purpose
  • Whether the client can decline without losing care
  • How the practice handles a pause, withdrawal, or correction
  • Which state recording rules and professional rules apply
  • Where the consent and refusal are documented
  • What happens if an interpreter, caregiver, or other participant joins

Confirm the applicable rule with qualified counsel, your board, payer, or organization before recording. Apply the requirements for each state and setting rather than relying on a general vendor statement.

Trial with simulated content before real sessions

Do not upload real client audio to discover whether a setting works. Use fictional names and simulated content first. Then verify the controls again on the approved Enterprise workspace.

If your Otter HIPAA assessment depends on a setting you have not tested, you do not have a deployment decision yet.

A cautious rollout looks like this:

  1. Execute the BAA for the exact plan and workspace.
  2. Write the capture, sharing, access, retention, and deletion policy.
  3. Confirm the language and consent workflow for the intended session.
  4. Run a simulated meeting and test Notetaker, auto-join, export, sharing, and deletion.
  5. Review the transcript for speaker attribution, omissions, unsupported detail, and language behavior.
  6. Run a short, consented trial only after the non-negotiables pass.
  7. Require the clinician to review and sign any note before it becomes part of the record.

A fluent transcript can still produce an unsafe note. Check risk language, clinically important omissions, speaker attribution, and whether the draft matches the note format and treatment plan. Transcription quality is not interpretation quality, and note quality is not contract compliance. That distinction remains part of any “otter ai hipaa compliant” deployment decision.

This workflow still requires clinician review of the recording, transcript, and final note before the result enters the record.

Where session notes fit under a signed BAA

Once the contract, settings, language workflow, and consent process are separate and documented, session documentation becomes its own operational question. Every Emosapien plan includes a signed BAA, and the clinician reviews and signs each AI-drafted therapy note. The clinician sets the session language, and Emosapien supports transcription and note output across 63 session languages: Afrikaans, Arabic, Armenian, Assamese, Belarusian, Bengali, Bosnian, Bulgarian, Cantonese, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English, Estonian, Farsi (Persian), Finnish, French, Galician, Georgian, German, Greek, Gujarati, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Kannada, Kazakh, Korean, Latvian, Lithuanian, Macedonian, Malay, Marathi, Mongolian, Nepali, Norwegian, Pashto, Polish, Portuguese, Punjabi, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Tagalog, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, Vietnamese, Xhosa, and Zulu. Mixed-language sessions (code-switching) are supported for English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian, and Dutch only; Arabic, Farsi, Hebrew, Urdu, and Pashto work as single session languages only, chosen directly, not mixed. A transcript can be viewed in another language, and a note can be generated and signed in another language. The interface and client app are in English, so compare the documentation workflow with the client-facing experience before choosing a tool. Book a qualified interpreter for the conversation; Emosapien handles the note. See how notes are drafted and reviewed and read the AI clinical notes overview before you compare a documentation workflow with a meeting agent.

Do therapy in the language your client speaks

Set Spanish, Tagalog, or Urdu for sessions. Emosapien drafts the note for you to review and sign.

Start free in their language
  • Free plan
  • No credit card
Session language: Tagalog
Draft note follows the session

Session detail

The clinician marked the draft for review before signing the note.

Draft for review

Keep contract evidence and the signed note in their separate workflows.

Ask about reviewed session notes… →

References

  • U.S. Department of Health and Human Services. Business associates, checked November 2026.
  • 45 CFR 160.103, definition of business associate, checked November 2026.
  • 45 CFR 164.502, uses and disclosures, checked November 2026.
  • 45 CFR 164.504, business associate contracts, checked November 2026.
  • Otter.ai, “HIPAA | Otter.ai,” public help article, checked November 2026. Vendor facts in this article are limited to the current Enterprise, BAA, admin-control, sharing, and retention statements on that page.
  • Otter.ai, “We’re Now HIPAA Compliant!”, company announcement, checked November 2026. Vendor statements can change after publication; confirm the current plan and contract before use.

Free PDF: Translation and Transcription Tool BAA Checklist

A practical eight-page evidence pack for deciding whether a translation or transcription workflow is ready for client information, with product-boundary, BAA, data-flow, language-review, and acceptance sheets.

  • Otter pre-upload BAA and language-suitability checklist
  • Rev account, language, and pre-upload activation checklist
  • Consumer-versus-contracted translation data-flow checklist
  • Translation-vendor BAA, Microsoft surface, app acceptance, and therapy-document RFP sheets

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

Ready to transform your practice?

Join 10,000+ therapists using Emosapien.