Zero-Retention DNC Scrubbing for LATAM Lists
DNC LATAM · Compliance guides
Zero-retention DNC scrubbing means the vendor checks the list against the official registry and does not keep your phones afterward. On DNC LATAM, that guarantee is attached to synchronous v1. The audit artifact you still receive is a dated screening record: counts and metadata, never the numbers.
This is a privacy and evidence page, not a claim that you can skip counsel. Product contract: DNC API. Artifact: screening records.
What v1 promises
After a v1 request we do not retain the source list or the per-number
result. Only approved aggregate usage and bounded non-phone request
metadata may remain. You can see the posture on the response,
including errors, through x-retention: zero and
Cache-Control: no-store.
That is the opposite of a "we will store your scrubs forever so you can re-download the phones" product. If you need the per-number determination later, you keep the Scrub Result on your side. We keep the privacy-safe record of the check.
What the screening record is for
A complaint or a client audit asks: which country, which official context, when, how many prohibited / safe / invalid. The screening record answers those questions without becoming a second copy of the calling list. Field rules live in the product domain: no phone inputs, no per-number results, no enumerable phone-derived hashes on that record.
It is not a legal opinion, not a certification of compliance, and not
authorization to call. safe_numbers_to_call means the
number was not on the selected official registry at check time.
v2 and CSV are bounded, not the same sentence
Durable v2 exists so a large scrub can be retrieved after admission. Panel CSV exists so ops can run a file without wiring code. Both have explicitly bounded encrypted lifecycles. Do not quote "zero-retention" for those surfaces. Quote the current docs. Surface split: API vs CSV.
Why this matters next to official registries
Foreign teams already hesitate to upload +52 / +54 / +57 books to a random "list wash" vendor. Official REPEP, No Llame, and RNE checks still have to happen. Zero-retention v1 is how you run the government source without creating a parallel phone archive at the vendor. Argentina and Mexico enforcement are complaint-shaped. You want your evidence, not our copy of the consumer's number. AAIP enforcement. PROFECO fines.
What you still store
- Your calling list and dialer logs, under your retention policy.
- The Scrub Result if you need per-number proof later.
- Consent and opt-out files, which we do not host as a CRM.
- The screening record we return, indexed by campaign and date.
Legal entity: Estudio Miotti, Argentina. No invented social profiles. About. Buy the country you dial, from $500/month at 10,000 checks. Coming end of September: Spain, Australia, and Singapore. Same privacy story will apply when those APIs are live. They are not live today.
Questions, answered
What does zero-retention mean on DNC LATAM? +
For synchronous v1, we do not keep your source list or per-number result after the request. Only approved aggregate usage and bounded non-phone request metadata may remain. Responses advertise x-retention: zero and Cache-Control: no-store, including on errors.
Do you keep a screening record with phone numbers? +
No. The screening record is counts and metadata: country, official registry context, outcome aggregates. It never contains phone numbers or enumerable phone-derived hashes.
What about v2 and CSV? +
Durable v2 and panel CSV scrub have their own explicitly bounded encrypted lifecycles. They are not the v1 zero-retention guarantee. Read the current API docs for those surfaces.
Is this a US TCPA archive product? +
No. We are not a National DNC scrubber and we do not sell a phone-level audit database. Keep whatever call-recording and consent archive your counsel requires on your side.
When should privacy-sensitive teams buy? +
When you need an official LATAM registry check without leaving a copy of the calling list with the vendor. From $500/month per country at 10,000 checks.