Privacy Consent Doesn't Equal DNC Consent

DNC LATAM · Compliance guides

No — agreeing to a privacy policy or a data-processing consent checkbox does not satisfy Mexico’s REPEP rules or Argentina’s No Llame rules. Those are two different consent regimes that answer two different questions: a privacy policy covers whether a company may collect and process someone’s personal information, while REPEP and No Llame cover whether a company may call that person for marketing. A customer can agree to one and never address the other, and US teams expanding into Latin America routinely assume the first covers the second.

Two different questions, two different rules

Privacy and data-protection consent answers the question “can you hold and use my information?” It typically covers what data a company collects, how long it’s kept, who it’s shared with, and what rights the person has over it. That consent usually comes from a checkbox, a signup form, or an account agreement, and it’s the kind of consent most US compliance teams are used to documenting because it overlaps heavily with how GDPR- and CCPA-style programs are built.

Do-not-call consent answers a narrower, different question: “can you call or message this specific number for marketing?” In Mexico, that question is governed by the opt-out model our guide to consent in Mexico walks through — a number is callable unless it’s on the REPEP registry or the person has directly opted out, and no privacy agreement is part of that test either way. In Argentina, the same question runs through the No Llame registry, with a documented, dated consent record able to override a registration in a complaint review — a specific evidentiary standard explained in consent to cold-call in Argentina, and not one a generic privacy-policy acceptance meets.

Agreeing to a privacy policy says nothing about either test. It doesn’t register or de-register a number, and in Argentina it doesn’t carry the specificity a documented-consent override needs — a blanket “I agree to the privacy policy and marketing communications” clause is not the same thing as a dated record tied to a phone number and a calling purpose.

Why US teams conflate the two

The confusion is understandable. In a lot of US compliance programs, the privacy policy and the marketing-consent checkbox live on the same form, get signed at the same time, and get stored in the same consent-management system. Over time, “we have consent” starts to mean one undifferentiated thing, and a team moving fast into a new market reasonably assumes that whatever satisfies that bucket at home satisfies it everywhere.

It doesn’t transfer, for the same structural reason covered in our breakdown of TCPA vs. Mexico and Argentina DNC rules: these are separate legal frameworks built around different mechanics, and a document that checks a box in one framework has no defined role in the other unless that framework specifically says so. A privacy policy’s marketing-communications clause is a statement about consent to process data for marketing purposes in general — it was never written to function as a dated, number-specific calling authorization, and a regulator reviewing a REPEP or No Llame complaint isn’t going to treat it as one.

What a privacy policy actually covers

A privacy policy, and the consent attached to it, typically establishes:

  • What categories of personal data a company collects and why.
  • How long that data is retained and how it’s secured.
  • Whether and with whom the data is shared, including vendors and processors.
  • What rights the person has to access, correct, or delete their data.

None of that is about whether a specific phone number can be dialed for marketing on a given date. A company can be fully compliant on every one of those points and still violate REPEP by calling a registered number, or still fail a No Llame review because the only “consent” on file is a generic policy acceptance with no date or call-purpose tied to it.

What actually satisfies REPEP and No Llame

Satisfying the actual do-not-call rule requires the mechanics our Mexico and Argentina guides describe: a current registry scrub before dialing, and — where consent is being used as cover for a registered number — a dated, number-specific record of that consent, not a general privacy-policy acknowledgment. Those are operational and evidentiary requirements a privacy consent flow was never designed to produce on its own.

What this means operationally

For a compliance or legal team auditing a Latin America calling program against its privacy stack:

  1. Don’t let “consent” in your CRM mean one thing. Separate the data-processing consent record from any marketing-call consent record, even if they’re collected on the same form.
  2. Scrub the registry regardless of privacy-policy status. A privacy agreement has no bearing on REPEP or No Llame registration status, so it can’t substitute for the scrub.
  3. If you’re relying on consent to override a registration, make the record specific. A dated record tied to a phone number and a stated purpose is what holds up; a privacy-policy checkbox timestamp generally is not.
  4. Audit your vendor contracts, not just your own forms. If a lead vendor’s privacy consent language is doing double duty as their claimed “DNC clearance,” that’s the same mismatch covered in our piece on purchased lead lists and DNC clearance — data consent and dialing clearance are two separate claims a vendor has to support independently.

The practical takeaway: treat privacy consent and do-not-call consent as two separate compliance tracks with two separate records, not one box to check. DNC LATAM’s registry checks and dated screening records cover the do-not-call side specifically — they confirm a number was clear on the call date, which is a different and narrower claim than anything a privacy policy makes.