Skip to content

Commit 3323daf

Browse files
committed
Updating the docs
1 parent 41f8f0b commit 3323daf

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

fern/security-and-privacy/PCI.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,10 +51,12 @@ If either cloud storage or webhook is not configured, the respective data will n
5151
Example configuration for `PCI compliant` assistant is:
5252
```JSON
5353
{
54-
"pciEnabled": true
54+
"compliancePlan": {
55+
"pciEnabled": true
56+
}
5557
}
5658
```
57-
Note: The default value for `pciEnabled` is false. Activating this setting aligns your assistant with PCI DSS standards by ensuring data is securely transmitted without being stored on Vapi’s systems.
59+
Note: The default value for `compliancePlan.pciEnabled` is false. Activating this setting aligns your assistant with PCI DSS standards by ensuring data is securely transmitted without being stored on Vapi’s systems.
5860

5961
## Can PCI be used alongside HIPAA?
6062
Yes, you can enable both HIPAA and PCI compliance for an assistant. In this case, the restrictions from both compliances will apply, meaning that no recordings or transcripts will be stored or transmitted, even if you have specified cloud storage endpoints or webhooks for storing transcripts.
@@ -65,10 +67,10 @@ Yes, you can enable both HIPAA and PCI compliance for an assistant. In this case
6567

6668
A: Enabling PCI compliance does not degrade the quality of the voice assistant services.
6769
However, it restricts you to use only the PCI-compliant endpoints, while limiting access to certain features, such as reviewing call logs, recordings or transcriptions, within the Vapi platform.
68-
If any cloud storage endpoints are provided, you can review the audio recordings in your own storage environment. The recordings follow naming convention:
70+
If any cloud storage endpoints are provided, you can review the audio recordings in your own storage environment. The recordings follow the naming convention:
6971

7072
```
71-
call_ID-recording.wav
73+
<call_UUID>-<timestamp>-<generated_UUID>-<audio_type>.wav
7274
```
7375

7476
**Q: Who should use the PCI compliance feature?**

0 commit comments

Comments
 (0)