Skip to content
Skip to content
AUDIENCE AND SEGMENTATION

Your b2b contact data just became someone else's evidence

Italy's regulator did not simply fine a data vendor. It ordered every Italian record erased, and the reasoning walks straight down the trail from the seller to whoever uploaded the file.

Summarise with
Set as preferred source on Google
17 min read
Quick answerItaly's Garante fined Lusha €2 million and ordered every Italian record erased, rejecting legitimate interest. Buying b2b contact data now carries buyer-side risk, because your ad platform already made you warrant you had the right to upload it.
Section 01

What the Garante actually ordered about b2b contact data

b2b contact data

A fox does not fight the fence, it finds the gap in the hedgerow. Growth teams have foraged the same gap for a decade: buy b2b contact data from a vendor with a slick interface, upload it, let the platforms do the rest. In July the fence moved.

The Garante per la protezione dei dati personali adopted its ordinanza ingiunzione against Lusha Systems Inc. on 14 July 2026, registered as provvedimento n. 542, doc. web n. 10275035. The penalty reads "euro 2.000.000,00 (due milioni/00)", described in the same text as "pari al 10% del massimo edittale", ten per cent of the statutory maximum, which the decision quantifies at euro 20.000.000 under Article 83(5).

The money is the least interesting part. Article 58(2)(f) supplied "il divieto di ogni ulteriore trattamento" of records on people in Italy acquired without an adequate legal basis. Article 58(2)(g) supplied "la cancellazione", erasure of that same population. Article 58(1)(a) required the company to report back "entro il termine di 60 giorni dalla notifica". A fine is a line in a ledger. An erasure order is a hole in a database.

Euros, millions: the penalty against the statutory maximum it was drawn from
Bar chart comparing a two million euro penalty with the twenty million euro statutory maximumFine imposed: 2Legal maximum: 2020151050Fine imposedLegal maximum
The takeaway is proportion, not precedent: the Garante set this fine at ten per cent of the maximum available to it, so €2m is a deliberately restrained figure and should not be read as a going rate for b2b contact data cases. Figures verbatim from the Garante decision of 14 July 2026. The erasure order runs on its own 60-day clock, which no euro scale can share.
0 days

to tell the regulator the records are gone, counted from notification of the order, not from the day the story reached your feed

Garante, provvedimento n. 542 of 14 July 2026

The sources named in the file will look familiar

The decision sets out where the records came from, and the list reads like a product diagram rather than a rogue operation. LinkedIn and Salesforce are named as the principal platforms, supplemented by blogs, professional sites and forums. Alongside them sit a "Community Program" in which members share contact details, and API integrations with client systems including Gmail, Outlook and Outreach.

Coverage has been careful to frame this at the category rather than the culprit. PPC Land notes that weekly verification, algorithmic email construction, purchased phone numbers and inbox integrations are standard components of sales intelligence tooling. The architecture the Garante examined is the architecture most b2b database providers sell, which makes this a b2b contact data story rather than a Lusha story.

Section 02

Why we bought it from a reputable provider stopped being a defence

Here is the paragraph that should move budget. At point 91 the decision records that the vendor is a controller because it sets the purposes and the means, then adds that its clients may use the data obtained for their own purposes "in qualità di autonomi titolari del trattamento", as independent controllers. That is the regulator drawing a line from the seller's database to the buyer's ad account and labelling both ends.

The Garante pressed the point when explaining why it also ordered publication: the way the records were gathered "è suscettibile di produrre effetti e di riverberarsi anche sui successivi trattamenti" carried out by the vendor's clients. Effects that echo downstream, into everyone who bought the file.

The regulator went upstream because that is where the tap is. Buyers are downstream, visible, and holding the bucket.
folkfox, on reading enforcement as a supply chain

None of which kills legitimate interest. The Court of Justice held in Case C-621/22, decided 4 October 2024, that a purely commercial interest can qualify, provided it is lawful, the processing is necessary, and the balance does not tip against people who could not reasonably expect it. Article 6(1)(f) was never a magic word, and EDPB Guidelines 1/2024 set out the same three cumulative conditions.

The Garante failed the first condition before reaching the third. If commercial contact requires consent under national law, an interest that depends on disclosing contacts for exactly that purpose cannot itself be lawful. The ICO frames the same test as purpose, necessity and balance, and is blunt that a person's interests usually win where "they wouldn't reasonably expect you to use the information in that way". Identical test, different national marketing rules, different answer.

One more wrinkle worth naming. LinkedIn heads the list of sources, and LinkedIn's User Agreement already forbids members from using "software, devices, scripts, robots or any other means or processes" to scrape or copy profiles and other data. Two rulebooks, one behaviour, and neither of them is your contract with the vendor.

Section 03

Article 14 is the quiet killer for bought lists

Everyone argues about Article 6. The provision that bites the buyer is Article 14, which governs what you must tell people when the data did not come from them. It has no drama in it, so nobody reads it, and it is the article that turns purchased b2b contact data into a mailing obligation.

The timing is the sharp edge. Article 14(3) requires the information within a reasonable period and at the latest within one month, or at the first communication if the data are used to contact that person, or at first disclosure if the data are passed to another recipient. Set those triggers beside a normal outbound sequence: your first touch is often the deadline, and an upload is a disclosure.

Now the honest part, because it cuts against the easy version of this story. The Garante did not fine the vendor over Article 14. At point 207 it archived the alleged breaches of Articles 7, 13(1)(a), 13(1)(c) and 14 outright. The provision that left no scent on the seller is the one that lands on the buyer, who now holds records it never collected and has told nobody it holds them.

For each way a record enters your b2b contact data pipeline, the question to answer and the action to take before the next upload.
Where the record came fromThe question you must answerWhat to do before the next upload
Bought from a sales intelligence vendorWhich lawful basis did the vendor rely on, and does it survive the marketing rules where the person sits?Get the legitimate interest assessment in writing and dated, and note the countries it does not cover
Scraped or inferred from a public profileDid the platform's terms permit that collection, and would the person expect to hear from you?Segment these out of every upload until you have an answer, then suppress rather than leave dormant
Email built by algorithm from a company patternWas a person ever involved in creating this address, or did software guess it?Stop using guessed addresses for outbound, and keep them out of every audience file
Shared through a community or credit-swap schemeWhose inbox was scanned to produce it, and did that person agree to the sharing?Treat as high risk: pull from advertising audiences first, then from the CRM
Collected first-party from your site, event or productDo you hold the record of consent, or the notice you actually served?Keep, timestamp the basis, and make this the segment you grow

Article 14(5) offers relief where the information proves impossible or disproportionate to provide, and every vendor will point at it. Lean carefully. That exemption was drafted for archiving and research, not for the ordinary case where you know the address because contacting it is the whole reason you hold it.

Then Article 21, absolute in a way that is easy to underrate. Object to direct marketing and "the personal data shall no longer be processed for such purposes". No balancing, no override, no appeal to pipeline pressure. If suppression lives in the email tool but not in the audience files you push to ad platforms, you have honoured the objection in one channel and broken it in another.

Section 04

The upload is where b2b contact data becomes ad-account exposure

This is the passage most growth teams have never read, and it takes ninety seconds. Upload a list for targeting and Google's Customer Match policy requires you to ensure your privacy policy "discloses that you share customer data with third parties to perform services on your behalf", to obtain consent for that sharing where the law or Google's own consent policies require it, and to comply with all applicable laws. You are not a passive uploader there. You are the party making the promise, and the promise is about provenance.

Google is blunter still about where the records may come from. Its Customer Match guidance says you "may only upload customer information that you collected in the first-party context, such as information you collected from your websites, apps, physical stores, or other situations where customers shared their information directly with you". Purchased b2b contact data is, by definition, not that. It arrived third-party, and no amount of enrichment makes it first-party afterwards.

Where youtube audience targeting quietly inherits the problem

Now watch the file travel, because this is where a paper problem becomes a media problem. Customer Match is not confined to search. Google Ads Help describes it as letting you "use your first-party online and offline data to reach and re-engage with your customers across YouTube and Google video partners". A bought list becomes a video audience, and youtube audience targeting built on purchased records inherits every provenance question attached to the file.

That reaches further than the usual audience targeting debate about scale and frequency, because the exposure is not a performance question. It is a paperwork question with a media budget attached. Paid teams routinely rebuild one seed list across Meta, Google and video partners, so a single questionable file propagates into four platforms before anyone asks where row 4,812 came from.

One record, five hands, and where the legal weight lands
A route map, not a measurement: this traces the path a single purchased record can travel and the obligation attaching at each stage, drawn from the sources cited in this article rather than from any dataset. Illustrative, and deliberately simplified.

Read the map the way a fox reads a trail: every stage leaves a print, and prints are what an investigation follows. The vendor's paperwork does not travel with the record into your ad account. Your warranty does.

Section 05

The audit to run this week, and what still survives

Outbound is not dead, and anyone saying otherwise is selling a course. What died is the comfortable idea that a vendor's reputation is a lawful basis. The work now is provenance: following the tracks back, per record, to where your b2b contact data came from and what you may do with it.

The vendor audit, in the order that finds problems fastest
01. Inventory every source

List every tool that has ever written a contact into the CRM: browser extensions, enrichment plugins, the free trial someone ran in 2023. Most teams find three sources they had forgotten and one nobody can name.

02. Stamp provenance per record

Add a source field and a date-acquired field, then backfill. B2b contact data without provenance is not a lead, it is an unpriced liability sitting inside your content and lifecycle programme.

03. Ask each vendor three questions in writing

Which lawful basis, which countries it covers, which authority has ever reviewed it. Ask for the dated legitimate interest assessment itself. Silence is an answer, and so is a sales deck sent in reply.

04. Reconcile suppression across channels

Every objection recorded in the email tool must appear in the audience files pushed to ad platforms. Export both, compare, expect the gap to embarrass someone.

05. Quarantine before you delete

Move purchased and inferred records into a segment that cannot be exported, uploaded or mailed. Quarantine buys time to take advice. Deletion does not buy it back.

06. Rebuild from observed behaviour

Replace bought seeds with people who visited, watched, downloaded or asked. Smaller, slower, and the only version you can defend line by line.

No provenance, no notice, no defence

Head of growth at a mid-market fintech. Name, work email, mobile, job title, seniority, location. Source field blank. Acquired through an enrichment tool nobody in the current team chose, with no record of any notice served and no date. It converts at 0.4%, and it is the row that takes an hour to explain to a regulator.

Provenance, notice and a defensible basis

Same job title, different origin. Downloaded a pricing teardown on 12 June, saw the notice at the point of the form, agreed to follow-up, opened three emails, booked a call. Source field populated, basis timestamped, suppression honoured everywhere. Fewer rows, and every one survives the question you would rather nobody asked.

What survives is narrower and better. First-party data collected behind a notice people actually saw. Real opt-ins with a timestamp. Audiences assembled from behaviour you observed on your own property rather than records you purchased from someone who observed it on somebody else's. That is the quiet quarry worth stalking, and it is the discipline behind folkfox paid social services and our PPC work.

If the number still has to be hit this quarter, the honest substitute is not a better b2b contact data file. It is more surface area: demand you can capture through SEO and GEO, a proposition sharp enough that people identify themselves, which is a brand strategy problem before it is a media one, and creative worth watching. Teams in fintech marketing have worked this way for years, which is why they blink less at rulings like this one.

Faced with a shortfall, the temptation is to buy one more file and promise it is the last. That is how a den fills with things you cannot explain. Take the decision to counsel, run the audit, and if you want a second pair of eyes on the pipeline first, start a conversation with folkfox.

Questions

Frequently asked questions

What did Italy's Garante actually decide about Lusha?

On 14 July 2026, in provvedimento n. 542, the Garante fined Lusha Systems Inc. €2 million, banned further processing of records on people in Italy acquired without an adequate legal basis, ordered erasure, and required compliance to be reported within 60 days of notification.

The Garante's decision against Lusha Systems on 27 July highlights inferred-address and spam-trap risks.

Does this ruling mean buying b2b contact data is illegal now?

No. It means the vendor's legal basis is not automatically yours. The decision records that clients who buy the data use it as independent controllers, so you carry your own obligations for notice, lawful basis and objection handling once the file reaches your systems.

Why is Article 14 the provision that matters to buyers?

Article 14 applies where personal data did not come from the person concerned, which is exactly what a purchased record is. It requires you to tell them, at the latest within one month, or at your first contact with them, or when you first disclose the data to another recipient.

Can I still upload a bought list as a Custom Audience or Customer Match list?

Read the terms first, because the platform puts the warranty on you, not on the vendor who sold you the file. Google's Customer Match policy requires your privacy policy to disclose that you share customer data with third parties, and its guidance says you may only upload information collected in the first-party context, which a bought record is not.

How does this affect youtube audience targeting specifically?

Customer Match audiences run across YouTube and Google video partners, so a purchased list uploaded for search can end up powering video buys too. The provenance question follows the file into every surface it reaches, video included.

What should a growth team do first, this week?

Stamp provenance on every record, quarantine anything purchased or inferred so it cannot be exported or uploaded, reconcile suppression between the email tool and the ad platforms, and ask each vendor in writing for its dated legitimate interest assessment. Then take the ruling to a lawyer.

Keep reading

Read more on this topic

Know where every record came from?

folkfox audits the pipeline, rebuilds the audience from behaviour you actually observed, and keeps the growth number in view while you do it.

The den

Where to?

Pricing

Choose a section. Enter opens it, Escape continues reading.

Cookie preferences

folkfox uses data the way we use strategy: only when it earns its place.