Encrypted screening data
Sensitive subject, finding, and source fields are encrypted before they are stored.
Adverse media requests combine identity data and risk information. The product is designed to keep both out of public surfaces and routine logs.
Sensitive subject, finding, and source fields are encrypted before they are stored.
New API keys are shown once. Only a keyed hash is kept for later authentication.
Workspace access is checked on each account and API request, with separate platform admin controls.
Request logs exclude names, birth dates, phone numbers, email addresses, search phrases, and evidence excerpts.
Asynchronous work uses bounded retries, idempotency, and atomic usage controls.
Screenings expire under a defined retention window and customers can delete completed records sooner.
Share your access, retention, deployment, and audit requirements before rollout.