Recording
Recording that
respects the room.
Two-party consent is the default. Recording state is announced. Storage is encrypted at rest. Retention windows are enforced per jurisdiction. Access is logged and scope-checked.
At a glance
What recording looks like on Dials.
Consent
Two-party
Spoken disclosure played and acknowledged before the recorder arms.
Storage
Encrypted
AES-256-GCM at rest, customer-managed keys on Enterprise.
Retention
Per-jurisdiction
Default 90 days. Configurable down to a single call.
Access
Scoped
Every read writes an event. Every export is signed.
Two-party consent
Announce. Capture.
Or don't capture.
A Dials seat declares whether it records. If it does, the platform plays the consent disclosure, captures the verbal acknowledgement, and arms the recorder. If the caller declines, the seat continues without storage.
- Spoken disclosure
- Recorded acknowledgement
- Decline-handled gracefully
- Per-seat policy
Disclosure
Played at 00:01
Ack
Caller said "Yes"
Recorder
Armed at 00:04
Storage
Region: US · KMS-DGL
Retention
Time bounded.
Region pinned.
Recordings live in the region the seat was provisioned in. Retention windows respect jurisdictional law. When the window closes, the recording is shredded and the event is recorded.
- US, CA, EU regions
- Default 90-day retention
- Per-call override
- Shred event in ledger
RegionUS-east
Window90 days
EncryptionAES-256-GCM
Key controlCustomer-managed on Enterprise
Shred eventRecorded in ledger
Open recording controls.
Inspect per-seat recording policy in the console and review the shred audit on the ledger.