What Ancha keeps
What is removed or replaced before storage
This happens before anything is stored, also for spans waiting to be assembled into a trace. The trace page lists how many of each were removed or replaced.
Names, addresses and other personal details written in free text are not detected. If your agent handles them, remove them before export, for example in an OpenTelemetry span processor.
Retention and deletion
- Traces are kept for 30 days, then deleted with their stored data. The trace page shows the date. Spans that never became a trace are deleted after the same 30 days.
- Tests you save keep the starting data rebuilt from their trace until you delete them.
- Delete trace removes the trace, its stored data and any spans still arriving. Check Also delete the tests saved from it to remove those too. The API does the same with
DELETE /v1/traces/<id>, and?tests=1. - Download what Ancha stored gives you exactly what is kept for a trace.
Who can reach it
- Ingest keys can only add traces to your workspace. They cannot read anything.
- Deleting traces needs a signed-in session or an admin API key. See Login and API keys.
- Traces and tests are readable only from your account, in the console or with your API keys.