Case data, retention and exports
Your workspace keeps case history for at least 365 days from the last message. Resolving or archiving a case deletes nothing and changes no retention rule.
Export case data
Your manager or an authorized support lead can export cases they can read. Users export their own case. User exports exclude internal notes. Every export page checks permission again. Revoked access stops later pages. Attachments keep the same case access checks.
Workspace export In testing
A saved export can be shared outside Templ. Keep it under your team's own data rules.
Handle user requests
Users can ask your team for a copy, correction, deletion or objection through their case. Verify the request without asking for keys or recovery phrases. A privacy request removes eval copies and improvement copies before the chat. A legal hold can keep required case data. It never keeps the separate de-identified copy. Read Privacy and the DPA for the legal terms.
Check operating limits
| Operating limit | Before funding | After funding |
|---|---|---|
| Messages per UTC month | 2,500 | 250,000 |
| Open cases | 25 | 1,000 |
| Retained cases | 100 | 40,000 |
| Workspace opens and reopens per 24 hours | 25 | 500 |
| User opens and reopens per 24 hours | 10 | 10 |
| Team opens and reopens per 24 hours | 100 | 100 |
| Message size in UTF-8 bytes | 4,000 | 4,000 |
| Seconds between messages | 5 | 5 |
A funded workspace has a verified top-up or reviewed grant. User and team allowances cover the last 24 hours across workspaces. Reopening the same case uses the allowance again. The worker applies pacing and storage checks even when balance is below zero. Team access explains who can act on a case.
Read De-identified copies and Security.
In testing means the feature is built and not yet open to every workspace.