Skip to main content
DNC LATAM offers zero-data-retention synchronous scrubbing and encrypted, time-limited durable jobs. Choose the mode whose lifecycle matches your needs.

​
Processing boundary

During a synchronous POST /v1/scrub:
  1. The API receives the phone-number array over HTTPS.
  2. Phone numbers exist only in request memory.
  3. Inputs are normalized and checked against the selected registry.
  4. The API returns prohibited_numbers_to_call, safe_numbers_to_call, invalid_numbers, and aggregate summary.
  5. Request memory is released.
Phone numbers are not written to the DNC LATAM database or application logs. Every v1 application response, including successful results and errors, uses the zero-retention mode header:

​
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, never zero; v1 and v2 are separate retention modes.
CSV scrubs remain panel-only and use their separately documented temporary storage lifecycle.

​
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.
DNC LATAM does not persist for v1:
  • 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 returns Idempotency-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.
Never paste live API keys or customer phone lists into an AI assistant. Give the assistant the public documentation, OpenAPI URL, Agent Skill, and synthetic examples instead.

​
Documentation-site boundary

The Mintlify API reference is configured in simple 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.