From the journal

Data broker registration, lawful resale and deletion duties: a global guide

A data broker or lead-generation platform needs a lawful route for each stage of its product: acquiring records, matching and enriching them, supplying them to a customer, and responding when a person objects or asks for a correction or deletion. The buyer also needs permission for its intended use. Registration, where required, is one part of that assessment.

34 min read

A platform may combine public records, purchased datasets and submitted business contacts, then sell subscriptions or exports. Its launch decision changes with the fields it holds, the relationship with each person, the purposes selected by seller and buyer, the countries involved and the marketing channel. A professional-contact directory, a consumer-profile product and a service processing only for customers need different controls. The comparison below covers North America, Europe, Asia, the Middle East, Africa, Latin America and Oceania.

The most useful starting document is a source-and-use schedule. For every dataset, identify the original collector, source, collection date, fields, notice or permission, proposed enrichment, buyer purpose, recipient locations and withdrawal history. Use that schedule to approve a defined product and to exclude unsupported fields or uses. The need for this operation-specific assessment follows from the different purpose, consent and accountability rules, including the GDPR, California Consumer Privacy Act (CCPA), Kenyan Data Protection Act and Australian Privacy Act.

1. Choose the product and identify the responsible actors

An independent seller normally decides why records are collected and combined, what its product contains and who may use it. Those decisions commonly make it a controller, responsible party, organisation or agency under local privacy law. A purchaser choosing a new purpose can have its own responsibilities. A customer-only provider needs instructions and actual restrictions on reuse to qualify for the applicable processor or operator treatment. GDPR Articles 4 and 28; POPIA sections 1 and 20–21; Singapore PDPA sections 2 and 4.

Map activity and control as well as customer location. Singapore's guidance addresses data activities in Singapore; the Indian Digital Personal Data Protection (DPDP) Act test, which had not commenced as at 21 November 2026, includes foreign processing linked to offering goods or services to people in India. The Dubai International Financial Centre (DIFC) and Abu Dhabi Global Market (ADGM) use their own incorporation or establishment/processing connections. These tests require an entity and data-flow map before expanding a catalogue. Singapore guidance; DPDP section 3; DIFC Article 6; ADGM scope guidance.

  • Professional-contact catalogue. Conditions to establish before release: Work fields and professional purposes; exact local exclusion or processing basis; source evidence; accurate roles; buyer-specific outreach permission. Changes requiring a fresh assessment: Personal contact details, private interests, sensitive inferences, unrelated promotion or another recipient jurisdiction.
  • Consumer enrichment and resale. Conditions to establish before release: Lawful acquisition and each enrichment/resale purpose; adequate notice; any required consent or sensitive-data condition; effective rights and recipient controls. Changes requiring a fresh assessment: More intrusive attributes, children, eligibility decisions, new purposes, channels or onward buyers.
  • Processing solely for a customer. Conditions to establish before release: Customer instructions, segregated records and outputs, lawful inputs, security, assistance with rights, and no independent catalogue reuse. Changes requiring a fresh assessment: Pooling across customers, selecting a new purpose or selling the same information independently.

The EU Data Governance Act (DGA) adds a different classification for genuine data intermediation. Article 2(11)(a) excludes a service obtaining, aggregating, enriching or transforming data to add substantial value and licensing its own resulting product without establishing a commercial relationship between holders and users. A neutral service establishing those relationships may instead engage notification and neutrality duties under Articles 10–12. Apply that test to the actual service and retain the separate privacy assessment. DGA.

The existing analysis of a Kenyan fintech marketplace and EU data intermediation addresses that structural choice. A business selling its own compiled profiles should begin with the acquisition, resale and rights conditions discussed here.

2. Determine which registrations and formalities apply

Data broker registration requirements vary by actor and activity. California incorporates its general privacy-law business thresholds. Other US states use different tests. Some jurisdictions require general controller registration, an information officer or prior authorisation for a particular operation. The platform should record the relevant definition and its supporting facts for each entity.

US state broker registration

California covers a qualifying business knowingly collecting and selling third-party personal information about consumers with whom it lacks a direct relationship. As at 21 November 2026, its threshold alternatives include gross annual revenue above $26,625,000, buying, selling or sharing information of 100,000 or more consumers or households, or deriving 50% or more annual revenue from selling or sharing personal information. The territorial, corporate and other statutory conditions also apply. A low-revenue platform can qualify under another limb. CCPA section 1798.140(d); inflation adjustment; broker statute.

California's direct-relationship rules require the person's intentional interaction with the business. Merely obtaining a record or handling a privacy request does not create that relationship. A platform with some direct customers can still broker information acquired outside those interactions. A colleague submitting another person's contact does not establish that person's intentional relationship with the seller. 11 CCR sections 7601–7602.

  • California. Main registration distinction: Apply the incorporated CCPA business definition and the indirect-data/direct-relationship test. Filing and fee position: Annual registration from 1–31 January after a brokerage year. The 2026 fee is $6,000, plus payment-processing charges. Delete Request and Opt-out Platform (DROP) operations have been a separate duty since 1 August 2026.
  • Texas. Main registration distinction: Business and Commerce Code Chapter 510 applies alternative indirect-data revenue tests: more than 50% of revenue, or revenue from processing/transferring indirectly collected data of more than 50,000 individuals in the statutory period. Apply the definitions and exclusions. Filing and fee position: Register before covered business; $300 initial and annual renewal, with certificate expiry on the issuance anniversary.
  • Vermont. Main registration distinction: As at 21 November 2026, its definition does not import California's general revenue threshold. Filing and fee position: Annual filing by 31 January, $100. Enacted changes from 1 January 2027 introduce a 30-day initial filing rule, 1 July renewal, $900 fee and $20,000 bond, alongside definition changes.
  • Oregon. Main registration distinction: Its broker law has specific relationship/service exclusions and an exemption for activity involving only listed sources, including public professional information or lawful government records. Filing and fee position: Register before covered activity; $600 initial/renewal. Approval ordinarily expires 31 December that year; approval after 1 November expires 31 December the following year. Apply for renewal at least 30 days before actual expiry.

Sources: California programme and final regulations; Texas Chapter 510; Vermont programme and Act 138 of 2026; Oregon regulator guidance. The Texas statute was redesignated from Chapter 509 in September 2025. Vermont's deletion-platform study does not create a live California-style portal. Oregon's original broker law and registration rules require a separate screen from its consumer-privacy law. Adding private profiles can defeat the only-public-professional-source registration exemption. The consumer law has its own scope, rights and sale prohibitions.

Registration and other formalities outside the US

  • Canada and Quebec. Relevant requirement for this business: The Personal Information Protection and Electronic Documents Act (PIPEDA) has general accountability duties. Quebec separately registers enterprises meeting its personal-information-agent definition, which concerns files and specified credit/character/reputation/solvency reporting. Test that definition before including or excluding a contact seller. PIPEDA; Quebec sections 70–79.1.
  • EU and UK. Relevant requirement for this business: The GDPR framework requires applicable records, security, impact assessment and data protection officer (DPO) arrangements. The UK also has an annual data-protection fee subject to exemptions; published tiers are £52, £78 and £3,763. DGA notification requires the separate intermediation test. GDPR; ICO fee guidance; DGA.
  • Kenya. Relevant requirement for this business: A business wholly or mainly engaged in direct marketing falls within mandatory registration even where the ordinary small-entity exemption would otherwise matter. Controller and processor roles require separate analysis. Certificates last 24 months. Registration Regulations, regulation 13 and Third Schedule.
  • South Africa. Relevant requirement for this business: Register the information officer and obtain prior authorisation where the activity triggers of the Protection of Personal Information Act (POPIA) apply. A consumer direct-marketer registry has its own phased rollout. POPIA sections 55 and 57–58; October 2026 rollout announcement.
  • DIFC. Relevant requirement for this business: Controllers and processors within DIFC Law's applicable scope must assess Article 14(7)'s processing-notification requirement, with annual renewal and relevant updates under the service requirements. DIFC Articles 6 and 14. As at 21 November 2026, the non-regulated-entity schedule lists US$750 initial, US$250 annual and US$50 amendment fees; other categories and nil-fee changes differ. DIFC notification service.
  • ADGM. Relevant requirement for this business: As at 21 November 2026, the regulator fee page lists US$300 registration and US$300 annual renewal for the applicable controller regime. Determine the actual establishment and activity connection. ADGM fees; scope guidance.
  • Saudi Arabia. Relevant requirement for this business: Domestic controller-registration rules include processing as a principal activity, which is material to a data business. A foreign-controller service is available; its existence alone does not resolve every foreign entity's binding registration trigger. Controller rules; foreign service.
  • Singapore, Hong Kong, India, Brazil, Mexico, Chile, Australia and New Zealand. Relevant requirement for this business: The general frameworks do not establish one shared broker-registration model. Apply their own governance and sector rules. India's commenced consent-manager framework is specific to that role; Chile's Article 22 register under Law 19.628 concerns public-body databases. The enacted reform's sanctions and certified-compliance register functions were prospective as at 21 November 2026 under the commencement position described in section 10. PDPA; PDPO; DPDP Rules; LGPD; Mexican private-sector law; Chilean Law 19.628; Law 21.719; Australian Act; NZ privacy-officer guidance.

Germany adds a material requirement for data trading: section 38(1) of the Federal Data Protection Act (BDSG) can require a DPO for business processing undertaken for transfer, including anonymised transfer, regardless of headcount. Apply this to the actual controller or processor activity.

Kenya's ordinary small-entity exemption requires both turnover or revenue below KSh5 million and fewer than 10 employees, and does not protect listed activities. Its fee schedule has registration/renewal pairs of KSh4,000/2,000, 16,000/9,000 and 40,000/25,000, depending on category. Classify staff, turnover and dual roles before calculating the payable amount. Registration Regulations.

In South Africa, prior authorisation can matter before enrichment. POPIA section 57(1)(a) applies where a unique identifier will be used for a different purpose from collection and with the aim of linking information processed by other responsible parties. Check both elements. The October 2026 official consumer-registry announcement sets marketer registration during September–December 2026, transitional cleansing during December 2026–April 2027 and consumer pre-emptive blocking from May 2027. POPIA; NCC announcement.

3. Keep B2B exclusions within their exact limits

“B2B data privacy” (business-to-business data privacy) covers several different legal outcomes. A work address can be personal information even when a customer buys it for business development. Product design should separate professional contact fields from private details and inferred consumer attributes.

  • Singapore. What the professional-contact distinction actually does: Defined business contact information is excluded from specified Parts of the Personal Data Protection Act (PDPA). The definition concerns business contact details and the purpose for which they were provided. Private numbers, household interests and inferred wealth do not become business contact information merely by association with an employee. PDPA sections 2 and 4(5).
  • Canada. What the professional-contact distinction actually does: PIPEDA section 4.01 applies where use is solely for communicating or facilitating communication relating to employment, business or profession. Provincial wording differs. Consumer enrichment can defeat the relied-on route. PIPEDA; BC law; Quebec law.
  • Mexico. What the professional-contact distinction actually does: The published regulations contain a narrow professional/representation-contact exclusion with listed fields and a stated purpose. Apply it only consistently with the replacement 2025 statute; private profiling needs ordinary permission. Regulation Articles 4–5; statutory framework.
  • EU and UK. What the professional-contact distinction actually does: Named work contacts remain personal data. Establish the applicable lawful basis, notice, purpose and objection arrangements. The customer's channel permission is a further inquiry. GDPR; UK GDPR.
  • Australia. What the professional-contact distinction actually does: Trading in personal information can remove the small-business exemption, subject to the actual consent/legislation exceptions. The employer-record exemption concerns the employer's own qualifying acts; a broker cannot inherit it simply by selling employee records. Privacy Act sections 6D and 7B.
  • New Zealand. What the professional-contact distinction actually does: Apply the agency's necessity, collection, purpose, notice and disclosure rules to identifiable work contacts. A business publication can support a particular exception while other requirements continue. IPP 1; IPP 2; purpose/disclosure principles.
  • South Africa. What the professional-contact distinction actually does: POPIA protects natural persons and, where applicable, juristic persons. A B2B label does not remove its processing conditions or electronic-marketing rules. POPIA sections 1, 3 and 69.

In Hong Kong, for supplying data to another direct marketer, the seller needs the prescribed written notice and written consent, including the relevant data, recipient and marketing-subject classes. A narrow historical enforcement stance about corporate-only approaches should not determine a product's legal design. PDPO sections 35J–35K.

4. Prove the source and resale purpose

Preserve what made a source public, who published it, why it was published and which terms governed access. Then test the intended enrichment and disclosure. A source licence, privacy permission and outreach permission address different obligations.

In the EU, public availability does not supply an Article 6 basis. Legitimate interests require a lawful interest, necessity and a balance that respects the person's interests and rights. The Court of Justice of the European Union's KNLTB judgment confirms that a commercial interest can qualify, while preserving those cumulative requirements. The October 2026 professional-address reconstruction guidance of France's Commission nationale de l'informatique et des libertés (CNIL) makes expectations and source visibility important: privacy controls, restricted access and a person's absence from identifiable professional sources can undermine the proposed use. GDPR Articles 5–6; C-621/22, paragraphs 38–57; CNIL reconstruction guidance.

Brazil likewise permits legitimate interests for qualifying ordinary data under the General Data Protection Law (LGPD), Articles 7 and 10. Its purpose, strict necessity, expectations and safeguards must support the actual operation. Article 7 preserves restrictions on publicly accessible information and specific sharing-consent requirements where consent is the basis. Sensitive data needs an Article 11 route. LGPD; ANPD legitimate-interest guidance.

Mexico's replacement law defines publicly accessible sources by reference to public consultation provided for by law. An older regulation's broad internet wording cannot expand that newer definition. A seller must also assess the separate controller-to-controller transfer conditions in Articles 35–36. Apply Articles 35–36 to the proposed transfer separately from the collection basis. Mexican law, Articles 2, 9 and 35–36.

New Zealand's information privacy principles (IPPs) 10–11 permit certain public-publication uses and disclosures only where they would not be unfair or unreasonable in the circumstances. Australia separately requires lawful and fair collection, reasonable necessity, applicable indirect-collection conditions and a permitted use or disclosure. NZ purpose/disclosure rules; Australian APPs 3 and 6; OAIC collection guidance.

Oregon adds a specific condition when obtaining information from a public body. From 5 June 2026, the body generally needs a broker's written assurance against onward sale or transfer for the specified federal immigration-enforcement use. The law preserves mandatory public-records/court disclosures and information available to the public on the same terms. The source transaction and onward-use restrictions must fit that assurance. Oregon Laws 2026, chapter 96.

Kenya and Saudi Arabia impose decisive additional gates

Kenya's section 37 permits commercial use with express consent, or written-law authorisation with the prescribed information to the person. A general legitimate-interest assessment cannot replace that specific condition. Purchased permission must cover the actual commercial use and be supported by the collection record. General Regulation 15(1) also expressly refers to collection from the person. A buyer of an independently compiled list needs a supported route under that provision before treating it as ready for direct marketing; the regulation's disjunctive wording must be read with section 37's express-consent or written-law gate. Kenyan Act section 37; General Regulations 14–18.

Saudi Personal Data Protection Law (PDPL) Article 26 limits marketing processing to non-sensitive data collected directly from the person with consent. The general public-source and legitimate-interest provisions must be read alongside that rule. A model built on scraping or buying independent marketing lists cannot assume it satisfies the direct-collection condition. A purpose-specific lead collected with the required consent, or a genuine instructed service, presents a different set of facts. Saudi PDPL Articles 10, 25–26.

Consumer repurposing requires particular care

Quebec expressly excludes commercial or philanthropic prospecting from its compatible-secondary-use route. Establish the required consent or another actual statutory authority for the relevant use and disclosure. In South Africa, assess the lawful basis, indirect-collection ground and compatibility of further processing separately, together with any identifier-linking authorisation. Quebec sections 12–14; POPIA sections 11–15 and 57.

For United Arab Emirates (UAE) federal/onshore processing, the Decree-Law uses consent and specified exceptions; it supplies no general B2B or legitimate-interests exemption. Its public-data exception concerns data made public by the person. The official UAE telemarketing announcement additionally describes a consumer-data trading prohibition involving reprocessing for marketing calls. Consumer telemarketing-list sales require resolution of that specific restriction before release, including for relevant free-zone companies; ordinary privacy consent alone does not establish that route. Federal Decree-Law 45/2021; official telemarketing announcement.

DIFC and ADGM require separate privacy analyses. DIFC permits recognised bases, including a properly assessed legitimate interest, with additional sensitive-data conditions. Its Article 34 requires information and an express opportunity to object before first disclosure for third-party direct marketing. ADGM's regulator guidance also requires a basis and gives direct-marketing objections specific protection. National UAE channel rules must be assessed alongside the applicable free-zone framework. DIFC law Articles 9–13 and 34; ADGM guidance; ADGM rights guidance.

Oregon's consumer-privacy law imposes product prohibitions. Since 1 January 2026, a covered controller may not sell the specified precise-location data or personal data of an under-16 consumer where it knows or wilfully disregards the age. The under-16 rule also bars targeted advertising and profiling for legally or similarly significant decisions. Consent does not authorise those prohibited operations. Apply the statutory data definitions, location exclusions and the separate consumer-law scope test. Oregon Laws 2025, chapter 251; consumer scope and thresholds; manufacturer amendment.

India's commencement date changes the answer

India's DPDP framework has staged commencement. Most core ordinary-processing duties in sections 3–17 are scheduled for 13 May 2027 under the November 2025 notification. The Consent Manager framework has operated since 13 November 2026, according to the launch announcement of India's Ministry of Electronics and Information Technology. The existing sensitive personal data or information (SPDI) framework remains relevant during transition. Apply Rule 3's categories and its public-domain/statutory-publication proviso before classifying information as SPDI. For covered data, Rule 6(4)'s further-disclosure restriction constrains the recipient's resale chain. Other applicable laws and source restrictions remain relevant. SPDI Rules. Ordinary work names and email addresses should be separated from SPDI rather than given one blanket classification. Commencement notification; DPDP Rules; SPDI Rules; government transition confirmation.

Build for the DPDP purpose, consent, notice and rights conditions before they commence. Its public-data exclusion is limited to publication by the person or someone legally required to publish. It does not create a general business-contact exclusion or a GDPR-style general legitimate-interests route. DPDP Act sections 3–7.

5. Make notice and rights handling part of the product

Indirect collection creates an immediate operational question: who tells the person, what information must they receive and when? Under GDPR Article 14, the ordinary deadline is a reasonable period within one month, brought forward by first contact or first disclosure. A large list does not by itself establish an exception. In New Zealand, IPP 3A has required reasonable steps for indirect-collection notice since 1 May 2026, subject to its actual exceptions, including specified publicly available information and prior complete-awareness cases. Each collector in a chain needs evidence supporting its own position. GDPR Article 14; OPC IPP 3A guidance.

A workable notice should connect the individual to the controller, source, purposes, categories, recipients, retention and rights required by the applicable law. If a supplier gives notice for a downstream collector, obtain the actual wording and delivery evidence. A contractual promise to handle transparency is useful only when the resulting process satisfies the local rule.

Use the correct clock and recipient rule

  • EU. Selected response or notice rule: Rights normally one month, with the statutory two-month extension where justified. What happens downstream: Article 19 requires notification of correction, qualifying erasure or restriction to recipients unless impossible or disproportionate. Marketing objection stops that purpose, including related profiling. GDPR Articles 12 and 16–21.
  • UK. Selected response or notice rule: The ordinary rights framework remains one month, with statutory start-time/clarification rules and permitted extensions. Controllers also have complaint-handling duties from 19 June 2026. What happens downstream: Apply correction/erasure/restriction notification and marketing objection on their own conditions. A complaint must be acknowledged within 30 days under the commenced 2026 rules. DUAA; commencement instrument.
  • Hong Kong. Selected response or notice rule: The statute sets ordinary 40-day access/correction periods. What happens downstream: Section 35L creates a written downstream stop-notice mechanism for third-party direct marketing; correction notification has separate conditions. PDPO sections 19, 23 and 35L.
  • Singapore. Selected response or notice rule: Apply the specific withdrawal, access, correction and retention provisions. What happens downstream: Section 22 specifies correction propagation to relevant recipients from the preceding year, subject to exceptions. Withdrawal duties for agents/intermediaries differ from independent-buyer erasure. PDPA sections 16 and 21–25.
  • DIFC. Selected response or notice rule: Indirect notice normally within one month or earlier contact/disclosure; rights normally one month with a permitted two-month extension. What happens downstream: Article 36 requires recipient notification of correction, erasure or restriction unless impossible or disproportionate. DIFC Articles 30 and 33–36.
  • ADGM. Selected response or notice rule: The regulator's guide specifies two months for indirect notice/rights and a possible one-month rights extension, subject to earlier notice triggers. What happens downstream: The guide requires relevant recipient notification and cessation for direct-marketing objection. ADGM rights guide.
  • Kenya. Selected response or notice rule: General Regulations specify 14-day indirect notice and a seven-day access period; other rights have their own periods. What happens downstream: Third-party-marketing restriction requests have a seven-day rule; section 40 and regulations govern correction/erasure notification. Act; General Regulations 6–18.
  • Brazil. Selected response or notice rule: Article 19 distinguishes immediate simplified confirmation/access from a complete response within 15 days. What happens downstream: Article 18 §6 requires immediate communication of the specified correction, deletion, anonymisation or blocking to agents with whom the data was shared so that they repeat the procedure, unless communication is proved impossible or would involve disproportionate effort. LGPD.
  • Mexico. Selected response or notice rule: Decisions on access, rectification, cancellation and opposition requests generally within 20 working days; favourable action within 15 working days, with justified statutory extensions. What happens downstream: Cancellation/blocking and ultimate erasure differ; communicate required corrections/cancellations to recipients. Consumer-law refusal of further transfer also matters. Private-sector law; Consumer Law Articles 16–18bis.
  • Australia. Selected response or notice rule: Australian Privacy Principle (APP) duties commonly use a reasonable period. The regulator's usual 30-day guidance is not a universal statutory deadline. What happens downstream: APP 13.2 correction notification depends on an individual request and another APP-entity recipient, with exceptions. APP 7 also addresses stopping facilitation of another organisation's marketing. APPs 7 and 12–13; OAIC guidance.
  • New Zealand. Selected response or notice rule: Correction decisions ordinarily within 20 working days. What happens downstream: IPP 7(5) requires notification of correction or a correction statement to every disclosee so far as reasonably practicable. OPC correction guidance; IPP 7.

Canada, South Africa and Saudi Arabia add their own recipient conditions. PIPEDA requires appropriate correction communication; British Columbia (BC) specifies recipients from the preceding year. Quebec Civil Code Article 40 requires prompt notice of rectification to recipients from the preceding six months and, where applicable, the source, including notice of a contested rectification request. Quebec Civil Code. POPIA's section 24 notification depends on effects on decisions and reasonable practicability. Saudi implementing regulations require recipient notification for specified correction, destruction and withdrawal events. These differences make one undifferentiated “delete everywhere” instruction unreliable. PIPEDA Schedule 1; BC section 24; POPIA section 24; Saudi implementing regulations Articles 7, 8 and 12.

Covered Oregon controllers must support the statutory opt-out signal for sale and targeted advertising. They must also stop processing after consent revocation as soon as practicable and no later than 15 days. These are separate from Oregon's broker-registration declaration. Amended ORS 646A.578.

California DROP requires a continuing process

California brokers have been required to operate DROP since 1 August 2026. As at 21 November 2026, the access cycle and relevant response period are 45 days. The rules address matching, indirect inferences, service-provider/contractor instructions, persistent suppression, unmatched request identifiers and status reporting. An unmatched request must still be checked against newly acquired information before sale or sharing. Reimporting the same person from another supplier does not reset the obligation. Delete Act section 1798.99.86; final DROP regulations; operational guidance.

Assembly Bill 883 (AB883) changes the relevant operational periods to 30 days from 1 January 2027. The statutory independent audit starts 1 January 2028 and repeats every three years. The audit mechanics noticed on 13 November 2026 remained proposed as at 21 November 2026. Separately, final CCPA risk-assessment rules have applied since January 2026, including prior assessment for new selling/sharing activity. Continuing pre-2026 processing has a 31 December 2027 assessment deadline under those rules. Keep those obligations in separate calendar entries. AB883; Delete Act audit provision; audit consultation; final CCPA regulations.

Ordinary CCPA deletion and DROP are also separate routes. Section 1798.105 has its own collection scope, exceptions and third-party notifications. DROP's service-provider and contractor provisions should not be turned into an unsupported promise that every independent historical buyer export has been recalled. Buyer contracts and recipient records must support the additional actions required by the applicable law and agreed product terms. CCPA section 1798.105; DROP regulations.

6. Separate deletion, suppression and lawful retention

Deletion removes the information to which the applicable duty extends. Correction changes inaccurate information or adds the legally required statement. Suppression records a restriction so the person is not marketed to, resold or reconstructed again where the rule requires cessation. Lawful retention preserves only information still needed for a permitted legal purpose, with restricted access and a defined end event.

Australia and New Zealand illustrate why these categories matter. Their retention and correction frameworks can require destruction, de-identification or correction without creating a general GDPR-style right to erase every accurate record on demand. Mexico's cancellation process distinguishes blocking during the relevant liability period from erasure. A legal hold must be scoped to its actual purpose; it does not by itself justify continued commercial use. Australian APPs 11–13; NZ IPP 7; NZ IPP 9; OPC correction and deletion guidance; Mexican cancellation provisions.

Use the following operating sequence, with responsibilities stated in the supplier and buyer agreements.

  • Intake: procurement. Required record or action: Source and field manifest; original licence, notice and permission; collection date; purposes and restrictions. Quarantine unsupported material.
  • Approval: legal and product. Required record or action: Country/role classification, source and enrichment basis, sensitive-data conditions, notice, registration, transfer and buyer-channel approval.
  • Delivery: release owner. Required record or action: Dataset version, record identifiers, buyer, purpose, location, access/download time and onward permissions. Connect the delivery to a correction/suppression channel.
  • Request: rights owner. Required record or action: Request type, receipt date, appropriate identity checks, applicable clock, responsible parties and reason for any permitted extension or refusal.
  • Execution: data operations. Required record or action: Correct, delete, restrict or suppress the relevant data and derivatives; isolate lawful retention; handle restored backups before renewed commercial use.
  • Propagation: distribution owner. Required record or action: Notify the legally required recipients and contractually covered buyers; record delivery, acknowledgement, action, exceptions and onward instructions.
  • Reimport control: engineering. Required record or action: Apply the minimum justified suppression identifiers to refreshed sources, regenerated profiles and exports, with access and retention controls.
  • Assurance: governance. Required record or action: Test the permitted delivery paths, investigate missed instructions and false matches, and substantiate any claim that downstream action is complete.

This is a recommended common operating design. The preceding country rules determine which actions are statutory, their recipients and their deadlines. A seller should distinguish “instruction sent”, “buyer acknowledged” and “execution confirmed” in its records and representations.

7. Check the buyer's outreach permission before calling a list usable

A buyer's ability to contact a person can be narrower than its ability to hold a record. Approval should identify the buying entity, actual relationship, message purpose, channel and recipient category.

  • France. Buyer condition that changes the value of a lead: CNIL's guidance permits relevant professional electronic prospecting with information and opposition conditions; consumer electronic prospecting generally needs prior consent or the exact own-customer exception. Consumer telephone prospecting moved to prior consent from 11 August 2026, subject to statutory exceptions. Electronic guidance; telephone guidance.
  • Germany. Buyer condition that changes the value of a lead: Section 7 of the Act against Unfair Competition (UWG) requires prior express consent for electronic-mail marketing, including B2B, subject to the narrow own-customer/similar-offering exception. Business calls use a separate presumed-consent test. UWG section 7.
  • UK. Buyer condition that changes the value of a lead: Regulation 22 of the Privacy and Electronic Communications Regulations (PECR) distinguishes individual subscribers from corporate subscribers. Sole traders and some partnerships need separate treatment. Named staff contacts still engage UK GDPR; the buyer must honour objections and identify the sender. PECR regulation 22; ICO B2B guidance.
  • Canada. Buyer condition that changes the value of a lead: The conspicuous-publication route in Canada's Anti-Spam Legislation (CASL) requires publication by or caused by the person, no refusal statement and relevance to the business role. A stand-alone purchased list does not establish a buyer's existing customer relationship. CASL; CRTC guidance.
  • United States. Buyer condition that changes the value of a lead: CAN-SPAM reaches commercial B2B email and requires the prescribed sender and opt-out controls. Unsubscribe requests must be honoured within ten business days; suppressed addresses have transfer restrictions. Calls/texts need a separate technology- and consent-specific screen. FTC guidance.
  • Singapore. Buyer condition that changes the value of a lead: Do Not Call (DNC) business-purpose exclusions and bulk-email Spam Control rules need separate analysis. A work number used to sell personal products is not cleared merely by being a work number. PDPC DNC guidance; IMDA guidance.
  • Australia and New Zealand. Buyer condition that changes the value of a lead: Their conspicuous-publication routes have cumulative business-role and no-refusal conditions. The buyer needs address-level evidence and a relevant message. Australian withdrawal uses five business days; New Zealand uses five working days. Australian Spam Act; DIA guidance.
  • South Africa. Buyer condition that changes the value of a lead: Apply POPIA section 69 consent or the buyer's own qualifying customer relationship, with the prescribed collection, similar-offering and opt-out conditions. Maintain the consumer objection and registry controls. POPIA section 69.
  • Kenya. Buyer condition that changes the value of a lead: Establish section 37 commercial permission and a supported route under Regulation 15, including its direct-collection wording, notice and consent conditions. Provide the required stop mechanism and implement direct-marketing restrictions. Kenyan Act; General Regulations 14–18.
  • Mexico, Brazil and Chile. Buyer condition that changes the value of a lead: Add consumer objections and the relevant channel/registry rules. Mexico's Public Registry to Avoid Advertising, Brazil's sector and state measures, and Chile's No Molestar and numbering rules have different scope. Mexican Consumer Law; São Paulo law; Chilean consumer law; 2026 numbering rules.

French consumer-call permission also expires: the decree limits the specified consent validity to one year and requires three-year evidence retention, subject to its legal-defence exception. Carry the actual consent scope, date, expiry and withdrawal status into the campaign system. Germany separately requires consumer-call consent evidence to be retained for five years from grant and after each use; that evidence period does not itself grant five years of calling permission. French decree Article 2; German UWG section 7a.

India's telecom regime adds sender, header, template and consent requirements. Its September 2026 amendment has staged provisions, and the November 2026 amendment separately postpones new regulation 35A until notification. Check the operative provision for each campaign. TRAI sender guidance; Third Amendment; Fourth Amendment.

A buyer using profiles for credit, insurance, employment or housing eligibility requires a distinct product assessment. Keep those uses outside an ordinary contact licence until the applicable consumer-reporting, discrimination and decision rules have been addressed. A contractual description cannot determine the statutory character of the actual use.

8. Treat every new recipient jurisdiction as a new decision

An international disclosure can require both a processing basis and a transfer route. Map the seller, buyer, hosting, remote access and onward recipients. A contractual governing-law clause does not remove mandatory rules connected with those operations.

EU transfers need the applicable GDPR Chapter V route. UK transfers need the UK framework, including the changes commenced in February 2026. Quebec requires a privacy impact assessment and written agreement for qualifying communication outside Quebec, which can include another Canadian province. GDPR Articles 44–49; DUAA and commencement; Quebec section 17.

Brazil's January 2026 adequacy decision provides a route within its terms for transfers to EU states, Iceland, Liechtenstein, Norway and the covered EU institutions and bodies. For other routes, apply LGPD Article 33 and the regulations of Brazil's National Data Protection Authority (ANPD). When using ANPD standard clauses, preserve the prescribed text and transparency conditions. LGPD; Resolution 19; Resolution 32.

Australian APP 8 ordinarily requires reasonable steps to ensure overseas-recipient compliance and can leave the disclosing entity accountable, subject to the statutory exceptions. New Zealand's IPP 12 applies to the specified IPP 11 disclosure grounds and offers defined routes, including comparable protection. An overseas service acting solely for the agency needs the separate section 11 assessment; a foreign buyer using data independently changes the facts. Australian APP 8 and section 16C; NZ IPP 12.

Saudi Arabia's transfer regulation requires particular attention to its specified safeguard cases. Standard clauses should not be assumed to authorise a continuous resale operation to unrelated foreign buyers. Identify an adequate destination or an actual applicable route, then check onward transfer and risk-assessment requirements. DIFC, ADGM and UAE federal law have their own transfer mechanisms. Saudi transfer regulation; DIFC Articles 26–27; ADGM guidance; UAE Articles 22–23.

For US data, screen two distinct federal regimes. 15 USC section 9901 restricts covered brokers making personally identifiable sensitive data of US residents available to specified foreign-adversary recipients and controlled entities; it has its own definitions and no bulk threshold. 28 CFR Part 202 separately regulates covered brokerage involving government-related or bulk US sensitive data and countries of concern or covered persons. For certain permitted brokerage to other foreign recipients, section 202.302 requires an onward-brokerage prohibition in the contract and reporting of known or suspected breach. US Code; regulation; official CFR.

9. Put the permissions and rights process into the licence

A buyer or seller should be able to answer the following questions before signing or accepting a new delivery.

  • Who collected each field, and which document or statutory condition permits collection, enrichment and the particular onward use?
  • Does the actual notice or consent identify the purpose, recipient and channel sufficiently for the relied-on rule?
  • Are work contacts, private details, sensitive attributes and inferred data separated in the product schema?
  • Can each exported record be traced to its source version, buyer and permitted onward recipients?
  • How will a correction, objection, withdrawal or deletion reach every party required to act, and what evidence will show the result?
  • Which fields or records may be retained for a lawful purpose, by whom, until when and with what access restrictions?
  • What happens when a source permission is withdrawn, a buyer changes use, a registration trigger is crossed or a new country is added?

These questions should produce documents and controls. Use the following term sheet to turn the approved model into a licence and operating schedule.

  • Dataset and provenance. What to specify: Sources, fields, dates, versions, transformation history and excluded records. Why it matters: Makes source permission, quality and later corrections traceable.
  • Permitted uses. What to specify: Approved matching, enrichment, display, export and resale; audiences, channels, territories, prohibited fields/uses and any source-specific onward-use assurance. Why it matters: Connects the licence to actual source conditions and statutory prohibitions, including applicable Oregon consumer-sale and public-body rules.
  • Evidence and warranties. What to specify: Actual notice/consent/source documents, acceptance checks, applicable consent expiry and evidence-retention periods, and precise authority warranties. Why it matters: Warranties provide remedies between parties; the underlying permission still has to exist and remain valid for the intended use.
  • Party roles. What to specify: Controller/responsible-party and processor/operator roles by operation, with required statutory terms. Why it matters: Independent reuse changes obligations even if the agreement retains a service label.
  • Onward supply. What to specify: Approved recipients, destinations, equivalent restrictions and export/recipient records. Why it matters: Supports lawful transfer and subsequent rights instructions.
  • Quality and updates. What to specify: Refresh method, error process, disputed records, correction statements and delivery evidence. Why it matters: Makes the statutory accuracy and recipient duties operational.
  • Rights and suppression. What to specify: Intake owner, applicable local clock, execution, recipient notice, acknowledgement, exceptions and reimport prevention. Why it matters: Distinguishes legal duties from any additional negotiated service level.
  • Retention and termination. What to specify: Return/deletion events, restricted legal holds, expiry, backups and evidence. Why it matters: Prevents retained compliance records continuing as commercial profiles.
  • Security and incidents. What to specify: Access, confidentiality, safeguards, incident cooperation and applicable reporting responsibilities. Why it matters: Keeps data and evidence protected throughout the chain.
  • Assurance and remedies. What to specify: Proportionate evidence access, audits, corrective action, feed suspension, termination and negotiated liability. Why it matters: Provides a response to unsupported provenance or a buyer unable to honour restrictions.
  • Change approval. What to specify: New fields, purposes, recipients, countries and technologies; approval before affected use. Why it matters: Preserves the facts on which the original legal route depended.

Some contract terms are expressly required by law, including California's sale/share protections, GDPR processor terms, South African operator security agreements and Kenyan processor/sharing agreements. Other provisions above are recommended commercial controls. Identify that distinction in the drafting and test enforceability under the chosen governing law. CCPA section 1798.100(d); GDPR Article 28; POPIA section 21; Kenyan General Regulations 21 and 24–25.

If the buyer wants to train a model or build a retrieval product, add a separate permission assessment. The AI data-licence terms for training, fine-tuning and RAG address those operations. An ordinary lead-generation grant should say whether such reuse is excluded or separately approved.

10. Maintain a dated launch and change calendar

The law in force and a later implementation date can point to different product decisions.

  • In force as at 21 November 2026: New Zealand IPP 3A from 1 May 2026; California DROP from 1 August 2026; UK controller-complaint duties from 19 June 2026. Action for the platform: Ensure those workflows exist for covered activity. OPC; DROP; UK commencement.
  • 10 December 2026: Australian automated-decision privacy-policy transparency. Action for the platform: Assess whether a computer program makes or directly and substantially contributes to a decision significantly affecting rights/interests using personal information. Prepare the required policy information where triggered. Decisions from commencement can be covered even where the program arrangement or data collection came earlier. OAIC; amending Act, Schedule 1 Part 15.
  • 1 January 2027: California's relevant DROP periods reduce to 30 days; Vermont's new registration package begins. Action for the platform: Update processing cadence, registration calendar, definition tests, fee and bond planning. AB883; Vermont Act 138.
  • 13 May 2027: most core Indian DPDP processing duties scheduled to commence. Action for the platform: Complete the consent/notice/rights and processor redesign while continuing existing obligations. Gazette notification.
  • 1 January 2028: California's statutory triennial DROP audit begins. Action for the platform: Preserve evidence ahead of the audit; monitor the separate proposed audit mechanics. Delete Act; consultation.
  • Chile: published reform scheduled for 1 December 2026; postponement bill at presidential approval as at 21 November 2026. Action for the platform: Treat the proposed 15 October 2027 date as pending until the legislative change is completed. Law 21.719; official bill record.

Chile is particularly consequential for a public-source product. Its Law 19.628, in force as at 21 November 2026, has specified public-source and direct-commercial-communication exceptions. The enacted reform replaces that design with a fuller basis, purpose, rights and transfer regime, including a qualified legitimate-interest route. Prepare a basis and recipient record that can support continued operations under the new framework. A proposed delay does not suspend existing rights or consumer objections. Law 19.628 Articles 4–5 and 12; reform.

The practical launch decision is a defined permission set: these fields, from these sources, for these purposes, to these buyers, in these places, with these rights controls. Keep every expansion tied to evidence and an accountable owner.

Prepare for a scoped review

For a scoped review with Licentium's Data Protection & GDPR for AI service, bring the source inventory, data-flow map, original notices and consent records, supplier and buyer terms, intended markets, and the proposed correction, suppression and deletion workflow.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.