
Compliance Checklist for Selling Leads to Third Parties
Use this compliance checklist for selling leads to third parties to protect consent records and buyer contracts. Call (510)-663-7016 for guidance.
By Valerie Lawson
Selling leads is a high stakes business. One weak consent record, one missing disclosure, or one buyer that does not meet state licensing rules can turn a profitable campaign into a regulatory liability. The compliance checklist for selling leads to third parties below is built for lead sellers, publishers, and network owners who transfer data to advertisers, buyers, or downstream partners. It focuses on the obligations that matter most: consent at capture, data broker disclosures, privacy choices, audit trails, state level rules, and buyer contracts. Work through each item before your next lead transfer, and treat the checklist as a living document that changes as state privacy laws expand.
Start With Consent at the Point of Capture
Every lead sale begins with a consent event. If the consent language at the point of capture does not match how the lead will actually be used, the entire downstream transfer is exposed. Regulators and plaintiffs look at the exact words a consumer saw, when they saw them, and what they agreed to. Vague language such as "we may share your information with partners" is increasingly treated as insufficient for lead sales, especially in regulated verticals like mortgage, insurance, solar, and legal.
The consent must be specific enough to cover the sale or transfer of the lead to third parties, and it must name the categories of recipients or describe them clearly. It should also identify the purpose of the transfer, such as contacting the consumer about a mortgage quote, an insurance offer, or a home improvement service. If your lead flow uses Ping & Post or Host & Post distribution, the consent must cover distribution to multiple buyers, not just one. A platform such as AstoriaLeads can help publishers and network owners manage distribution, but the consent language itself must be built into the capture experience before any ping or post occurs.
Use this short checklist for consent language at capture:
- Consent includes an affirmative action, such as a checked box or a clear submit button, and is not buried in a privacy policy.
- Language names the categories of third parties that may receive the lead, or describes them as marketing partners in a way that is specific to the vertical.
- Language covers the sale or transfer of data, not just sharing for analytics or service providers.
- Consent is separate from other terms, so a consumer can agree to the lead transfer without agreeing to unrelated conditions.
- The capture page records the exact version of the consent text shown at the time of submission.
After the list, review the flow for dark patterns. Pre-checked boxes, confusing double negatives, and consent walls that block access to content can invalidate the consent record. The safest approach is a clear, plain language statement that explains what the consumer is agreeing to and who may contact them. Test the language with real users and keep a screenshot of every version. That screenshot becomes evidence in an audit or dispute.
Data Broker Disclosure and Privacy Choice Obligations
Several state laws treat lead sellers as data brokers or as businesses that sell personal information. That classification triggers disclosure and choice obligations that go beyond the point of capture. California, Vermont, and Texas have data broker registration regimes, and state privacy laws in California, Colorado, Connecticut, Virginia, and other states give consumers the right to opt out of the sale of their personal information. If you sell leads, you need a process for receiving and honoring those requests, even when the request comes after the lead has already been transferred.
A practical compliance checklist for selling leads to third parties should include a data broker disclosure review. Confirm whether your business meets the definition of a data broker in each state where you operate. If it does, complete the registration and maintain the required records. Even if registration does not apply, the privacy choice obligations may still apply because the sale of leads is a sale of personal information under many state privacy laws. The disclosure should appear in your privacy policy, and the opt out mechanism should be easy to find and use.
Keep these points in mind when building the privacy choice process:
- Provide a clear opt out of the sale or sharing of personal information, and honor it within the time required by each state law.
- Pass opt out signals downstream to buyers and partners so the lead is suppressed from future sales.
- Maintain a suppression list that is checked before any new transfer occurs.
- Document how opt out requests are received, processed, and confirmed to the consumer.
- Review privacy policy language annually, and update it when you add new verticals, buyers, or distribution models.
Record keeping is where many lead sellers fall short. You need an audit trail that connects a specific lead to a specific consent event, a specific buyer, and a specific transfer time. That trail should include the capture URL, the consent text version, the timestamp, the IP address where appropriate, and the buyer or buyers who received the lead. If a consumer complains or a regulator asks questions, the audit trail is your defense. Build it into your lead management system from the start, and test it by pulling a random sample of leads each month to confirm the records are complete.
State Level Rules That Go Beyond Federal Law
Federal law sets a floor, not a ceiling. The Telephone Consumer Protection Act governs calls and texts, and the FTC Act prohibits deceptive practices. But state laws add requirements that directly affect lead sales. Florida's telemarketing law, for example, imposes specific consent and record keeping rules for calls to Florida residents. California's privacy law gives consumers rights over the sale of their data. Washington's commercial telephone solicitation rules are strict. New York and other states have their own do not call and disclosure requirements. A single national consent form is rarely enough.
The compliance checklist for selling leads to third parties should include a state by state review for every vertical you serve. Mortgage, insurance, solar, education, auto finance, and legal leads each carry additional rules. Mortgage leads may involve licensing and disclosure requirements under the Real Estate Settlement Procedures Act and state mortgage laws. Insurance leads may involve state insurance department rules on lead generation and producer licensing. Legal leads may involve attorney advertising rules and state bar guidance. Education leads may involve rules on recruiting and financial aid disclosures. The vertical matters as much as the state.
Here is how to operationalize the state review:
- Map every state where you capture leads, and list the verticals active in each state.
- Identify the consent, disclosure, and record keeping rules that apply to each state and vertical combination.
- Update the capture language and the privacy policy to address the strictest applicable requirement.
- Build state specific suppression rules into your distribution platform so leads from restricted states are routed only to compliant buyers.
- Review the map quarterly, because state legislatures add new rules every year.
After the numbered list, connect the state review to your buyer contracts. If a buyer is not licensed in a state where you sell leads, the transfer should be blocked. If a buyer uses an autodialer or artificial voice, the consent standard may be higher. If a buyer resells leads, the downstream transfer must be covered by the original consent. Your platform should enforce these rules automatically where possible, and your contracts should make the buyer responsible for complying with the rules that apply to their use of the lead.
Vendor and Buyer Contracting Considerations
Contracts are the last line of defense in a lead sale. A strong contract does not replace consent, but it allocates responsibility and creates remedies when something goes wrong. The compliance checklist for selling leads to third parties should include a contract review for every buyer, every downstream partner, and every vendor that touches the lead data. The contract should define the permitted use of the lead, the vertical and geographic scope, the consent standard, and the audit rights.
Key contract terms include representations and warranties that the buyer will comply with applicable law, including the TCPA and state telemarketing and privacy laws. The contract should require the buyer to honor opt outs and suppression lists, and to notify you promptly if a consumer revokes consent. It should include indemnification for claims arising from the buyer's use of the lead, and it should give you the right to audit the buyer's compliance. Data security terms should cover encryption, access controls, and breach notification. If the buyer resells leads, the contract should require flow down obligations to downstream recipients.
On the vendor side, review contracts with capture partners, call centers, and technology providers. Confirm that the vendor's consent language matches your requirements, that the vendor maintains records for the required retention period, and that the vendor will cooperate with audits. A performance marketing platform such as AstoriaLeads can support Ping & Post distribution, Pay Per Call campaigns, and phone verified leads, but the contract still needs to define who is responsible for consent, disclosure, and suppression. Put the responsibilities in writing, and review the contracts annually.
Finally, build a routine. Run the compliance checklist for selling leads to third parties before launching a new vertical, before adding a new buyer, and before changing consent language. Keep a compliance file for each campaign that includes the consent screenshots, the contract, the state review, and the audit trail samples. When a regulator or a plaintiff asks questions, that file is the difference between a manageable dispute and a costly one. Compliance is not a one time project. It is a repeatable process that protects your business and the consumers who trust you with their information.