Security & Privacy

What Katexs stores, how long it keeps it, who can reach it, and what you are responsible for. Written to be readable by the person who has to sign off on it.

Data we handle

Encryption

• In transit — TLS 1.2 or higher on every external connection. Media over SIP uses SRTP where the carrier supports it.
• At rest — AES-256 on recordings, transcripts, and database storage.
• Secrets — API keys and integration credentials are encrypted with per-workspace keys and are never returned by the API after creation.
• Key handling — Managed keys rotated on a fixed schedule. Enterprise workspaces can supply their own key material.

Access control

• Roles — Owner, admin, builder, and viewer. Publishing to production and managing keys are admin-and-above actions.
• SSO — SAML single sign-on with enforced-only login available on Enterprise.
• Audit log — Every configuration change, key creation, promotion, and export is recorded with actor and timestamp.
• Internal access — Katexs staff access to workspace data requires an approved support ticket, is time-boxed, and is logged. We do not browse customer conversations.

Model and training

Your conversations are not used to train any model, ours or a provider's. Model traffic runs under zero-retention agreements with our inference providers where such terms are available, and the current provider list is published in the subprocessor register.

Call recording consent

Consent law varies by jurisdiction and it is your obligation, not ours. The practical rule most legal teams land on is to announce recording on every call regardless of where the caller is — it is cheap, it is defensible everywhere, and it removes the need to detect location before speaking.

recording:
  enabled: true
  announce: true
  announcement: "This call is recorded for quality and training purposes."
  allow_caller_opt_out: true      # caller says no, call continues unrecorded
  redact_sensitive_fields: true   # masks fields marked sensitive in transcripts
  retention_days: 30

Sensitive data

• Mark fields sensitive — Marked variables are masked in transcripts, exports, webhook payloads, and the dashboard.
• Never collect card numbers by voice — Transfer to a payment IVR or send a secure link. Katexs is not a cardholder data environment.
• Health and financial data — Available under a signed BAA or equivalent on Enterprise. Do not process regulated data before that is in place.
• Redaction on export — CSV and API exports honour the same masking rules as the dashboard.

Deletion and data subject requests

Deleting a contact removes their transcripts, recordings, and variables across the workspace within 30 days, including from backups on their normal expiry cycle. Requests can be made from the dashboard or through the API, and each deletion is recorded in the audit log so you can evidence completion.

curl -X DELETE https://api.katexs.com/v1/contacts/+15555550142/data \
  -H "Authorization: Bearer $KATEXS_API_KEY"

Your responsibilities

• Lawful basis — You decide why you are calling or texting someone and hold the consent for it.
• Disclosure — Tell people they are speaking with an automated assistant.
• Key hygiene — Scope keys per environment, rotate on staff changes, and never ship a secret key to a browser.
• Retention policy — Set retention to the shortest period your business actually needs.