Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion fern/security-and-privacy/hipaa.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ When enabling HIPAA compliance, only HIPAA compliant providers may be chosen.

<AccordionGroup>
<Accordion title="Will enabling HIPAA compliance affect the quality of Vapi's service?">
Enabling HIPAA compliance does not degrade the quality of the voice assistant services. However, it limits access to certain features, such as reviewing call logs or transcriptions, that some users may find valuable for quality improvement purposes.
Enabling HIPAA compliance does not degrade the quality of the voice assistant services. However, it limits access to certain features, such as reviewing call logs or transcriptions, that some users may find valuable for quality improvement purposes. With HIPAA compliance enabled, storage of transcripts, recordings, and logs on Vapi's servers is disabled. However, Vapi is still able to generate these call artifacts and store them at an external cloud storage location of your choosing such as AWS S3 if the corresponding credentials are provided in the Vapi dashboard.
</Accordion>
<Accordion title="Who should use the HIPAA compliance feature?">
This feature is particularly useful for businesses and organizations in the healthcare sector or any entity that handles sensitive health information and must comply with HIPAA regulations.
Expand Down