# Is Voice In HIPAA compliant?

Voice In is built with privacy in mind. 

Modern browsers provide speech-to-text APIs. These APIs take in raw audio and returns raw transcribed text. 

Voice In uses the browser's speech-to-text API to transcribe text. On Chrome it uses Chrome's speech-to-text API, on Edge it uses Edge's API. By design, all of your audio is transcribed by your browser. **No audio data or the resulting transcripts are sent to Dictanote's server.** 

Here’s all the data we need in order to make Voice In work:

* Your email address to identify your account (optional)
* If you are a paying customer, a payment\_token from Stripe/Paypal linking to your subscription payment details and voice commands (stored so you can access them from other machines).

Many 1000s of medical professional use Voice In every day to voice type in sites like Teladoc, Athena Health, many EHRs and EMRs, clinical note taking apps, etc.

We have never offered HIPAA business associates agreement before as we do not control the core speech-to-text function which the browser (Chrome/Edge) provides.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.dictanote.co/help/general/is-voice-in-hipaa-compliant.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.