Skip to main content
If sensitive data reaches Arize AX, you can remove it by deleting the spans that contain it. Use the GraphQL API to delete everything a project ingested over a date range, or the REST API when you know the specific span IDs.

Delete by date range (GraphQL)

The deleteData mutation takes the project’s modelId, a startDate and endDate in UTC, and a deleteType of PRODUCTION to delete spans. startDate is inclusive and endDate is exclusive. Both dates are strings in the RFC 3339 full-date format, such as "2026-12-03". Deletion can take up to an hour to complete.

Delete by date range (arize-toolkit)

The arize-toolkit Python package wraps the same deleteData mutation for use from a script.

Delete by span ID (REST API)

The delete spans endpoint accepts 1 to 5,000 span IDs per request, and deletion is permanent. start_time and end_time narrow the search for those IDs. They default to two years ago and now. The response lists deleted_span_ids and not_deleted_span_ids along with a completed flag. When completed is false, retry the request. Resubmitting IDs that were already deleted is safe.

Prevent future ingestion

Sensitive data can be masked or redacted before it is sent to Arize AX, which keeps it from being ingested in the first place.