DNC LATAM processes customer phone numbers with zero data retention.
Processing boundary
During a 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 aggregate summary.
- Request memory is released.
Phone numbers are not written to the DNC LATAM database or application logs.
Every API response includes:
What is persisted
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:
- 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:
