Data Management
Erasure on request and automatic data retention.
During the beta, erasure for GDPR Article 17 (Right to Erasure) is handled by the Risicare team on request. There is no route that erases data for a request that carries an API key, and the dashboard has no control for it.
Erasure on Request
To have a data subject's data erased, write to support@risicare.ai. Name the project, and give the identifiers of the data:
| Identifier | What it selects |
|---|---|
| Session ID | The data of one session |
| Agent ID | The data of one agent |
| Trace IDs | Specific traces |
The same applies to a single trace or a single session: no route deletes a trace or a session, so ask the Risicare team.
Deleting Your Account or Organization
Handled by the Risicare team on request
There is no self-service way to delete your account or your organization. To delete an account, contact support@risicare.ai. Deleting an account removes the person and every organization they are the sole owner of, together with those organizations' projects, keys and data. An erasure request (above) concerns a data subject's traces; it does not delete accounts.
Automatic Data Retention
In addition to erasure on request, Risicare automatically purges aged data with fixed ClickHouse TTLs, applied uniformly to every project regardless of plan. Retention is not a single window — it varies by data type:
| Data | Retention |
|---|---|
| Traces, spans, sessions, agent spans, agent messages | 90 days |
| Prompt/completion content | 90 days — it is stored on the span itself |
| Evaluations | 365 days |
| Scorer results | 365 days |
Content is kept as long as the span — not 30 days
A dedicated 30-day content table exists in the schema and is the source of a widely-repeated "content is deleted after 30 days" claim, including in earlier versions of this page. Nothing writes to that table. Captured prompt and completion text is stored in the span's own attributes, so it lives for the span's full 90 days. Plan for 90, not 30.
If you need prompts and completions kept for a shorter period than the
surrounding trace, there is no setting for that today — keep content capture
off instead. It is off by default in the SDK (trace_content=False). When the
project's trace_content_enabled setting is false, the gateway replaces
content with a placeholder before anything is stored, even when an SDK sends
it. You cannot change that setting yourself during the beta.
One more thing that is easy to miss: evaluations and scorer results are kept for a full year, four times longer than the traces they were computed over; if the scored content is sensitive, that is the window that governs.
Coming Soon
The 90-day TTL is fixed and is not adjustable from Project Settings. Retention is enforced by a table-level ClickHouse TTL that applies to every project alike, so per-project and per-plan windows are not configurable today and are not on a committed date.