Separate business facts from information about people
Start by identifying what you actually need. A list of incorporated companies, their sectors and generic switchboard numbers is different from a profile of named owners containing personal mobile numbers, opinions and inferred financial difficulties. Sole-trader records and named professional contacts can identify individuals even where the context is entirely commercial. A work address is not automatically outside UK GDPR.
As a suggested design exercise, make two columns: information necessary for the service and information that is merely available. If you are building a supplier directory, geographical coverage and service categories may answer the customer’s question without collecting private contact details. If you are assessing potential clients, avoid attaching speculative personal labels just because an automated enrichment tool offers them.
Document a purpose before collecting at scale
Choose a lawful basis for each intended use of personal data, not just for the download. Ordinary legitimate interests may be appropriate for some proportionate commercial activities, but requires a purpose, necessity and balancing assessment. Consider the original context, reasonable expectations, likely impact and safeguards. The recognised legitimate interest basis is confined to specified statutory purposes; it is not a shortcut for general lead generation.
A useful internal approval sheet describes the source, fields, intended users, publication or contact plans, retention and potential harm. Ask what changes if thousands of separate records are combined into a searchable profile. Collection that looked modest on each source website may become substantially more intrusive when aggregated. Screen for the need for a data protection impact assessment before deploying high-risk profiling.
Treat purchased data as a supplier-risk decision
A broker’s promise that a list is “GDPR compliant” does not establish that your particular use is lawful. Ask how and when records were obtained, what people were told, what permission evidence exists and whether it covers your organisation and communication channel where required. Check freshness, accuracy, suppression handling and the route for complaints. Keep evidence rather than relying on a salesperson’s reassurance.
Before importing a sample, specify your acceptance tests. Reject records that cannot be traced to a credible collection process. Quarantine uncertain entries rather than allowing the sales platform to contact them automatically. A contract can allocate responsibilities and remedies, but cannot replace a missing lawful basis or valid permission. Renew the checks when a supplier changes its sourcing method.
Plan the explanation people are entitled to receive
Where personal information comes from another source, Article 14 normally requires privacy information within a reasonable period, no later than one month, with earlier triggers where you communicate with the person or disclose the information. The explanation includes the source and whether it was publicly accessible, alongside the other required information. Putting a notice somewhere on your website does not automatically satisfy the duty to provide it.
There are exceptions, but “there are too many people to contact” is not a self-proving exemption. Assess the precise conditions and safeguards before relying on one. Operationally, keep the date each record entered your system and the event that triggers notification. This makes it possible to distinguish records awaiting a justified first contact from records that have silently sat in a database for months.
Collection and marketing permission are different checks
A lawful basis for holding a contact does not necessarily permit sending marketing through every channel. PECR sets additional requirements for electronic messages and telephone calls. Corporate subscribers, sole traders and some partnerships are treated differently for email marketing. A publicly displayed address is not consent, and a bought-in record does not acquire the existing-customer soft opt-in merely because you purchase it.
Build channel eligibility into the campaign process before drafting messages. Check relevant telephone preference registers and your own objections where calls are proposed. For email, record whether the applicable route is consent, a properly evidenced exception or the corporate-subscriber position. Named corporate contacts still have UK GDPR protections. Do not send an otherwise prohibited promotional email merely to ask for marketing consent.
Keep corrections and objections attached to the record
People can object to processing for direct marketing, including related profiling. Stop that use and retain only the limited suppression information needed to avoid contacting them again, where justified. Deleting every trace of an objection can cause the same person to reappear in the next purchased list. Ensure imports are screened before being made available to campaign tools.
Our practical recommendation is to keep source, confidence and last-check fields separate from sales notes. A job title inferred from an old page should not become an unquestioned fact. Give directory subjects an accessible correction route and record what was corrected across downstream copies. An opt-out facility is useful, but it does not retrospectively legalise a collection or disclosure that was unlawful from the start.
Check the permissions that privacy law does not settle
UK GDPR is only part of a scraping assessment. Copyright, database rights, website terms, confidentiality and access restrictions can raise separate issues. A link back to the source is not a universal licence to reproduce text, photographs or an entire database. Do not bypass authentication or technical restrictions on the assumption that a commercial benefit to the source creates permission.
Before scaling, test a limited documented dataset, review actual outputs and establish a stop mechanism for unreliable sources. Record what the system must never collect, publish or infer. The sensible commercial asset is a dependable information service with defensible provenance, not the largest possible contact file. Complex scraping, sensitive profiles and disputed permissions need specialist advice before launch.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.