PCI Compliance

Overview

This page goes deeper into the mechanics behind PCI mode than the summary on the HIPAA & PCI page — specifically the compliancePlan.pciEnabled field, the artifactPlan options for granular per-assistant opt-out, and the selective-recording-with-squads pattern used to collect payment data mid-call without ever capturing card data in a recording or transcript. See the HIPAA & PCI page for the broader compliance overview including HIPAA mode, and HIPAA Subprocessors & Data Residency for the HIPAA-specific subprocessor and data-residency detail.

compliancePlan.pciEnabled is the top-level switch that enables PCI DSS compliance mode for an assistant. It defaults to false.

{
  "compliancePlan": {
    "pciEnabled": true
  }
}

When set to true, the assistant is aligned with PCI DSS standards by ensuring sensitive data isn't retained on the core system's own infrastructure:

• Recordings can be routed to a PCI DSS Level 1 compliant cloud storage destination — AWS S3, Azure Blob Storage, Google Cloud Storage, or Cloudflare R2.
• Transcripts can be delivered via your own webhook instead of being stored on the platform.
• If neither a compliant storage destination nor a webhook is configured, recordings and transcripts are permanently deleted rather than retained anywhere.

While compliancePlan.pciEnabled operates at the assistant level, artifactPlan gives you finer-grained control over exactly which artifacts are captured for a given assistant — which matters most when a single call moves through more than one assistant in a squad, and only part of that call touches payment data.

"artifactPlan": {
    "recordingEnabled": false,
    "loggingEnabled": false,
    "transcriptPlan": {
        "enabled": false
    }
}

Setting all three to false on a payment-collection assistant means none of its portion of the call is ever captured in any form — not just the recording.

The recommended way to combine these two mechanisms is a three-assistant squad, so you retain a normal record of the beginning and end of the call for quality assurance, while guaranteeing that card data collected in the middle is never captured in any form:

1. Greeting assistant — recording and logging enabled as normal. Handles the opening of the call and confirms the caller wants to make a payment.
2. Payment-collection assistant — artifactPlan fully disabled (recordingEnabled: false, loggingEnabled: false, transcriptPlan.enabled: false). Collects the card details with nothing captured.
3. Confirmation assistant — recording re-enabled. Confirms the payment was processed and wraps up the call.

When handing off from the payment-collection assistant to the confirmation assistant, also set contextEngineeringPlan on that handoff destination to previousAssistantMessages or none, so that any tool call results from the payment step (which could include sensitive data even if not recorded) aren't forwarded into the confirmation assistant's context. See Squad Routing: Handoff Destinations & Context Engineering for the full set of contextEngineeringPlan options.

PCI and HIPAA compliance modes can be enabled on the same assistant at the same time. When both are active, the stricter combined restriction of the two applies — there is no scenario where enabling both loosens what either mode would enforce on its own. In practice this typically means no recordings or transcripts are stored or transmitted unless you've explicitly configured compliant custom storage or a webhook destination that satisfies both modes' requirements.

In summary: compliancePlan.pciEnabled is the assistant-level PCI switch, defaulting to permanent deletion of recordings and transcripts unless you configure PCI DSS Level 1 storage or a webhook; artifactPlan gives you per-assistant granularity to fully suppress recording, logging, and transcription during a sensitive phase of a squad call; and PCI plus HIPAA together always apply the stricter of the two rule sets.