Yoann C.
03/10/2025, 6:12 PMVapi Support Bot
03/10/2025, 6:14 PMhipaaEnabled property to true within each assistant's configuration:
json
{
"hipaaEnabled": true
}
When this setting is enabled for a specific assistant, no call logs, recordings, or transcriptions will be stored on Vapi's systems for that assistant. Instead, an end-of-call report is generated and stored on your server [source](https://docs.vapi.ai/security-and-privacy/hipaa).
Regarding squad-specific implementation, I couldn't find explicit information about whether HIPAA compliance can be limited to specific squads. The documentation focuses on assistant-level configuration rather than squad-level settings.
If you need more specific information about squad-level HIPAA compliance implementation, you might need additional clarification from Vapi.
Source:
- [HIPAA Security and Privacy](https://docs.vapi.ai/security-and-privacy/hipaa)Vapi Support Bot
03/10/2025, 6:14 PMhipaaEnabled configuration setting for each assistant [source](https://docs.vapi.ai/security-and-privacy/hipaa)
- By default, this setting is false for all assistants
- You need to manually set hipaaEnabled to true for each assistant that requires HIPAA compliance:
json
{
"hipaaEnabled": true
}
This means you can selectively choose which assistants need to follow HIPAA requirements while leaving others with standard settings. For squads (which contain multiple assistants), you would need to configure each assistant within that squad individually.
In newer updates, HIPAA settings are consolidated under Assistant.compliancePlan.hipaaEnabled to streamline compliance configurations [source](https://docs.vapi.ai/changelog/2025/2/17).
When enabled for an assistant, HIPAA compliance ensures no call logs, recordings, or transcriptions are stored during or after calls - instead, only an end-of-call report is generated and stored on your server.
Hope this helps clarify how HIPAA compliance works in VAPI! 😊
Sources:
- [HIPAA Security and Privacy](https://docs.vapi.ai/security-and-privacy/hipaa)
- [Changelog February 17, 2025](https://docs.vapi.ai/changelog/2025/2/17)Yoann C.
03/10/2025, 6:22 PMYoann C.
03/11/2025, 8:59 PMKyle
03/12/2025, 6:33 PMYoann C.
03/12/2025, 11:01 PMparthjshah95
03/13/2025, 4:16 PMKyle
03/16/2025, 7:46 AMartifactPlan.recordingEnabled is set to true
5\. Configure the recordingPath if you want to customize where recordings are stored
3\. **Important Notes**:
- Without proper cloud storage credentials, recordings won't be stored when HIPAA compliance is enabled
- You'll still receive an end-of-call report with call information
- With HIPAA enabled, VAPI won't store the recordings in their own storage
This approach ensures your call recordings are stored in your own HIPAA-compliant environment while still allowing you to benefit from VAPI's call recording functionality.parthjshah95
03/17/2025, 6:11 PM