Test mode is a fully isolated copy of every domain object: applicants, verifications, checks, webhook deliveries, outbound emails. Nothing created in test mode touches live data or your billing wallet. The test-data purge wipes that copy in one step.
Open the test-data tool
Section titled “Open the test-data tool”Open Developers → Test data in the console. The tool is owner+admin only and only operates in test mode — the live-mode view shows a “Switch to Test mode” notice in place of the purge panel. See Modes and regions for the mode model.
What gets deleted
Section titled “What gets deleted”The purge removes every test-mode row owned by your organization:
- Applicants and the encrypted PII attached to them.
- Verifications, checks, assessments, and rule evaluations.
- Webhook deliveries, attempts, and retry state.
- Outbound emails recorded under test mode.
It does not touch:
- Live-mode data of any kind.
- Webhook subscriptions, workflow templates, or API keys (configuration of record).
- Organization membership or roles.
- Audit-log entries — the purge itself emits an audit row so the action is recoverable as evidence even though the data is not.
Run a purge
Section titled “Run a purge”- Switch the sidebar to Test mode.
- Open Developers → Test data.
- Click Purge test data. A confirmation dialog opens.
- Type
DELETEinto the confirmation field. The confirm button stays disabled until the string matches exactly. - Click Purge test data. The dialog locks while the workflow starts.
The purge runs as a durable workflow — once started, it completes even if you close the browser tab. Larger organizations may take several minutes to drain.
Who can run it
Section titled “Who can run it”- Owner and Admin roles can run the purge.
- Manager, Member, and Viewer roles see the page but cannot start the action.
The role gate is enforced on the page, in the workflow dispatcher, and in the audit-log emission. A non-owner who knows the BFF endpoint cannot bypass the page-level check.
Audit trail
Section titled “Audit trail”Every purge emits an account.test_data.purged audit row tagged with the actor, the organization id, and the row counts removed per table. The log is visible to organization owners and admins under Activity in the sidebar.
When not to run it
Section titled “When not to run it”The purge is irreversible. Before running:
- Make sure no integration test in CI is mid-flight against this organization’s test mode.
- Make sure no demo or pilot is using the test data you are about to delete.
If you want to keep some test verifications and drop others, do it one at a time from the Applicants list. There is no partial-purge option here.