Processing boundary
During a synchronousPOST /v1/scrub:
- The API receives the phone-number array over HTTPS.
- Phone numbers exist only in request memory.
- Inputs are normalized and checked against the selected registry.
- The API returns
prohibited_numbers_to_call,safe_numbers_to_call,invalid_numbers, and aggregatesummary. - Request memory is released.
Durable v2 retention
POST /v2/scrub must persist encrypted input temporarily so work can survive
a disconnected request, deploy, retry, or country maintenance window:
- An attached input is eligible for purge when the job terminalizes. An upload with an unknown outcome becomes due for revalidation by exact canonical identity at the 24-hour active-job/input hard cap measured from admission. A failed cleanup remains retryable and observable until exact absence is verified.
- A successful encrypted result remains retrievable for 7 days measured from successful terminalization.
- Non-phone job metadata remains for 30 days measured from terminalization.
- Every v2 response, including errors, uses
x-retention: transient-encrypted, neverzero; v1 and v2 are separate retention modes.
What is persisted for v1
DNC LATAM persists only operational and aggregate information required for authentication, billing, reliability, and usage reporting:- Organization and hashed API-key records.
- Aggregate counts for total checked, prohibited, and invalid inputs.
- Country, timestamps, and non-sensitive request metadata.
- A keyed, non-reversible idempotency fingerprint.
- Raw phone numbers.
- Request bodies.
- Response arrays.
- Raw API keys.
- Raw idempotency keys.
Idempotency under ZDR
Because completed responses are not stored, an exact completed retry is recalculated in memory. The API returnsIdempotency-Replayed: true and does
not charge or record usage a second time.
Your responsibilities
Zero data retention at DNC LATAM does not automatically remove data from your own systems. Review:- Application and proxy logs.
- Error trackers and APM payload capture.
- Queue and retry storage.
- Support tickets and screenshots.
- Analytics and observability events.
- AI prompts, coding assistants, and chat transcripts.
Documentation-site boundary
The Mintlify API reference is configured insimple mode. It displays schemas
and copyable examples but does not submit requests, API keys, or phone-number
payloads through Mintlify.
Run real scrubs only from the customer’s controlled environment directly
against the documented v1 or v2 endpoint.