Resold contacts: checking lead provenance, consent and duplicates

A file of contact details does not establish that an advertiser has received usable enquiries. A person may have asked about another service, agreed to hear from another organisation, or already opted out. Before any communication starts, the review must separate a demonstrable request from a record that cannot be used. This guide produces four working documents: a batch record, acceptance rules, a decision log and a calculation of the full cost of an accepted result.

The legal discussion is limited to the United Kingdom and draws on public ICO guidance reviewed on 17 October 2026. It does not establish that the same arrangement is permissible in the EU, Russia or another country. The illustrative US-dollar budgets are independent assumptions, not UK market prices or currency conversions. This is an operational review method, not a legal assessment of a particular list. No real personal details appear in the examples.

What to establish before receiving a list

Separate three events: someone provided information; an intermediary transferred it; your organisation established that it may use it for a specified purpose and communication channel. The first two do not prove the third. A request for a quotation, a newsletter subscription and permission to receive offers from several companies describe different situations. Do not assign the same “consent present” flag to every record.

The ICO explains that a seller's assurance of compliance is insufficient. Buyers must examine provenance, collection circumstances, the information shown to individuals and consent records where consent is claimed. Information should not be used when the supporting explanations are unsatisfactory. A commercial agreement does not replace that assessment. Source: ICO guidance on collecting information and generating leads.

Request a description of the process and redacted evidence before personal data is transferred. Identify the country, recipient category and communication channel. Do not apply the rules for email automatically to telephone calls or postal advertising. Electronic marketing also requires assessment of the applicable PECR requirements. If the team cannot establish the basis for the particular operation, the pilot does not start.

For an affiliate programme, first write a precise enquiry definition and source restrictions. In our AffiliateCore platform, that document can inform discussion of your own offer's conditions; registration itself neither verifies nor legitimises a purchased list. Keep the completed record when proceeding to advertiser registration with AffiliateCore.

A batch record you can fill in

Create a separate record for each identifiable delivery. “October list” is insufficient: batches collected through different forms or permissions need separate identifiers. The following is an editorial recommendation for your internal process, not a built-in AffiliateCore feature.

• Batch: internal reference, supplier, original collector and accountable person at the advertiser.
• Scenario: product, country, recipient category, purpose and permitted communication channel.
• Provenance: collection page or other route, dates, form version, privacy notice and separate consent wording where required.
• Transfer: named organisations, permitted recipients and purposes, intended number of recipients and restrictions on further use.
• Evidence: references to protected records, time of the individual's action, wording version and integrity checks.
• Commercial event: exact accepted-enquiry definition, price, exclusions, review deadlines and grounds for reversal.
• Objections: responsible person, handover channel and exclusion from later deliveries.
• Access and retention: authorised viewers, storage location, retention period and basis for deletion or restricted preservation.

Use internal record identifiers instead of names, email addresses or phone numbers in shared analysis. Keep supporting evidence separately with restricted access. Do not automatically treat a hashed contact as anonymous: matching can still create identification risks. Do not upload the original list to a shared chat or unrelated service simply to check duplicates.

Acceptance without automatically starting a campaign

1. Agree the criteria before delivery. State whether payment buys a file row, a permissible contact or a confirmed enquiry. This method uses the last definition. Unknown provenance means “not accepted”, not a discount.
2. Examine the evidence. Match the form version, date and intended recipient to the proposed use. Sampling can uncover a problem but does not prove that the remaining records are usable. The required support must exist for each record that is used.
3. Check uniqueness. Distinguish a repeated row, a repeat from a previous delivery and a genuine new enquiry from the same person. Normalisation must not erase the meaning of the request. In a dispute, preserve both original references and the reviewer's decision.
4. Check communication restrictions. Apply current objections and restrictions before any permissible contact. A supplier update must not remove an existing exclusion without a verified basis.
5. Separate import from authorisation. A file can pass format validation while remaining unusable. Test imports with synthetic records; do not send messages to real individuals to test the system.
6. Record the result. Each row needs a status, reason, criteria version, timestamp and accountable reviewer. Only permitted records enter the agreed handling process.

Useful working statuses are “received, not in use”, “under review”, “accepted”, “rejected” and “acceptance reversed”. Reasons must survive status changes. New evidence that undermines the basis for processing requires the affected processing to stop, regardless of whether the supplier's invoice has been settled.

ICO guidance describes consent as freely given, specific, informed and demonstrated through an unambiguous action. Acknowledging a privacy notice does not, by itself, establish marketing consent. Context and age matter too: do not turn a contextual recommendation about timing into a universal expiry period. Source: ICO guidance on planning direct marketing.

Educational scenario 1: a cheap batch that is rejected

A fictional supplier offers 100 home-service enquiries at USD 3 each, a total of USD 300. Before purchasing, the advertiser requests a redacted evidence package: the form description, version history and 20 evidence examples without contact details. Every result below is invented for instruction; it is not a customer case study or market benchmark.

The review identifies three forms. One names only the intermediary; another concerns a different product; the third has no evidence of the wording actually shown to the visitor. The team does not conclude that all 100 records are unlawful. It records that the proposed use has not been adequately supported. The supplier's clarification does not resolve the gaps. The decision is to decline the contact file and start no communications.

Full review cost: an analyst for three hours at USD 10, or USD 30; a specialist for two hours at USD 20, or USD 40; and USD 5 for protected document handling. Total: USD 75. No list payment, transfer fee or message cost is incurred because those operations never occur. The example assumes no additional non-recoverable taxes or charges; a real estimate must list them separately if applicable.

Accepted enquiries: zero. Paid enquiries: zero. Subsequent reversals: zero. Cost per accepted enquiry is undefined because its denominator is zero. Dividing USD 75 by the 100 proposed rows does not establish an acquisition cost. The unspent USD 300 is an avoided purchase, not demonstrated profit or proven avoided damage.

The stopping condition was reached before purchase: insufficient evidence for the intended purpose, organisation and channel. Reconsideration requires a verifiable package and a fresh assessment. Renaming the file, lowering the price or promising to replace complained-about records does not change the decision. There is nothing to scale.

Educational scenario 2: a pilot with acceptance reversals

A different fictional process begins with a clearly described request to a specified company. Before the pilot, specialists establish that the chosen process is appropriate in the UK; this assumption does not establish permission for the reader's own operation. The batch contains 80 records. The agreed price is USD 6 per finally accepted enquiry, rather than per delivered row.

Pilot materials include a form specifying the service, recipient and purpose; its version history; a batch record; and a decision register. A synthetic record tests the technical route and is excluded from commercial totals. Real enquiries are handled only through a permitted process after evidence and restrictions have been checked. The team sets two working days for initial review and seven days for reconciliation. These are fictional contract terms, not statutory deadlines or AffiliateCore promises.

The first review identifies 12 duplicates of previously accepted requests, eight records with insufficient evidence and ten enquiries outside the agreed service. The categories do not overlap: 80 − 12 − 8 − 10 = 50 provisionally accepted. Five of those 50 are subsequently reversed following confirmed acceptance errors. Final result: 45 accepted, 30 initially rejected and five reversed. Each of the 80 records is counted once.

Costs are USD 270 to the supplier, calculated as 45 × USD 6; USD 40 technical preparation; USD 50 provenance review; USD 60 handling of permitted enquiries; USD 10 allocated tool costs; and USD 20 other contractual charges. Total: USD 450. All non-recoverable taxes and costs assumed in this example are included. No separate AffiliateCore commission is assumed. Add actual platform or intermediary charges only from confirmed terms.

Full cost per accepted enquiry is USD 450 / 45 = USD 10. Final acceptance is 45 / 80 = 56.25%. Reversals among provisionally accepted enquiries are 5 / 50 = 10%. That last measure is not the overall rejection rate. Revenue, sales and return on investment remain unknown: an accepted enquiry is not yet a customer.

Before starting, the team set a USD 450 budget and a USD 11 ceiling for the full cost of an accepted result. The pilot meets these limits, but the sample is small. The decision is only to consider another limited batch, not to declare the channel successful. That batch needs its own budget, evidence review and reconciliation. A confirmed problem with permission stops the affected processing even when the economics look attractive.

If five reversals do not reduce the actual supplier invoice, the supplier cost becomes 50 × USD 6 = USD 300. Total cost rises to USD 480 and the cost per accepted enquiry to approximately USD 10.67. Agree the adjustment rules in advance; do not automatically report the more favourable version.

Terms to include in the acceptance agreement

This is a working template for review, not a ready-made legal contract: “Batch [reference] relates to [product, country, recipient and channel]. The payable result is [precise event]. Evidence of provenance and permissible use is provided through [procedure and access controls]. Initial review takes [period]. Duplicates are defined by [criterion and window]. Reversals and invoice adjustments follow [conditions]. Objections are passed to [contact within timeframe]. Further disclosure is restricted to the agreed lawful scope. Retention and deletion follow [basis and period].”

Add a complaint procedure: stop the affected communication, preserve only necessary evidence with restricted access, establish the record's origin, refer the request to the responsible person and check other records from the same form. Do not make the individual prove that they never consented. Do not message a questionable list in an attempt to obtain fresh consent.

The ICO also explains the need to respect objections and marketing opt-outs. A limited suppression record helps prevent reintroduction through the next delivery; it must not become a new marketing audience. Source: ICO guidance on respecting preferences.

A decision that can be checked

Before discussing an affiliate offer in our AffiliateCore platform, prepare a completed batch record and a de-identified calculation covering both invoice-adjustment scenarios. Existing advertisers can sign in to AffiliateCore and compare their prepared terms with the available process for their own offer. Consent verification, suppression records and supplier investigations remain separate responsibilities of your team; this article does not claim that the platform automatically performs them.

• The country, product, recipient, purpose and channel are defined.
• Provenance is reviewed before contact details are used.
• An enquiry, marketing consent and a supply agreement are distinct.
• Duplicates are distinguished from legitimate repeat enquiries.
• Objections are applied before contact and in later batches.
• Costs include review, labour, tools, fees and reversals.
• A zero result is not hidden by dividing by proposed rows.
• Stopping conditions apply regardless of price.
• The next pilot has independent limits and checks.

Practical assignment: complete the batch record for one proposed delivery without uploading anyone's contact details. If you cannot establish who collected the information, what the person saw and why your company may perform the intended action, the output is a list of missing evidence and a decision not to use the information until that evidence has been checked.