Key points
- Building a prospect database requires compliance with GDPR obligations on personal data protection and consent.
- The data minimisation principle means collecting only the data strictly necessary for the intended purpose (surname, first name, email, telephone).
- The distinction between B2C and B2B prospecting determines how consent must be obtained and which contact methods are allowed.
- When targeting individuals, prospecting by email or SMS in principle requires prior consent that is freely given, informed, specific and unambiguous, which rules out pre-ticked boxes.
- The information provided must state the purpose, the retention period, the identity of the controller, individuals’ rights and the possibility of withdrawing consent.
- The record of processing activities must state, in particular, the purposes, the categories of individuals and data, the time limits for erasure and, where possible, the security measures.
Managing a prospect database is a powerful lever for any business that wants to grow. However, the building and use of these databases call for close attention to the legal and regulatory obligations under the GDPR and to personal data protection. For any organisation, respecting consent and individuals’ rights is not only an ethical imperative but also a mark of compliance, especially since the European regulation on data protection became applicable on 25 May 2018. Here is a full overview of the recommended methods for building your contact list, processing the information and putting in place a sales prospecting strategy that complies with the regulations.
Table of Contents
ToggleCore GDPR principles applied to sales prospecting
The GDPR and database compliance require every business or organisation to adopt good practice when collecting and managing customer and prospect data. The data minimisation principle means collecting only the information strictly necessary for the intended purpose when creating databases.
In this demanding regulatory context, businesses may find it useful to seek the assistance of a GDPR law firm to keep control of the legal and technical aspects when building and managing contact files. Each controller must also make sure that processing is secure and transparent, for both B2B and B2C operations. The distinction between prospecting individuals and prospecting professionals determines how consent must be obtained and which contact method the law allows.
Data minimisation and lawfulness: what data can you collect for prospecting?
When building a prospect database, you should limit collection to relevant data that is not excessive. Common fields generally include surname, first name, email and telephone number. In a B2B context, some business data may be considered less sensitive, but compliance with the principles of proportionality remains essential.
To avoid any excessive collection, it is wise to document the intended purposes. The record of processing activities, mandatory for many organisations, must state, in particular, the purposes, the categories of individuals and data, the time limits for erasure and, where possible, a description of the security measures.
Consent and information: informing people to protect them better
When targeting individuals, one of the pillars of electronic prospecting remains obtaining prior consent, required by Article L. 34-5 of the French Postal and Electronic Communications Code (Code des postes et des communications électroniques) (in French) for marketing messages sent by email, SMS or automated calling system. This consent must be freely given, informed, specific and unambiguous, which rules out the use of pre-ticked boxes.
The information provided to data subjects must include several essential elements: the purpose of the collection, the retention period, the identity of the controller, their rights (access, rectification, objection, erasure) and the possibility of withdrawing consent at any time. This approach does much to build prospects’ trust in the organisation. There are also resources explaining how to demonstrate GDPR compliance effectively (in French) through rigorous and appropriate documentation.
Building a prospect database: technical compliance requirements
Creating a prospect database means ensuring the traceability of actions carried out at every stage of the data lifecycle. Data security is an integral part of the legal obligations and must translate into concrete measures to prevent leaks, loss or unauthorised access.
There are several ways to build up a prospect file while remaining compliant with the regulations: direct collection through opt-in forms on the website, physical events, business exchanges, or the purchase or rental of databases, subject to stricter precautions.
Manual or automated collection: advantages and limits
Manually entering information from business meetings offers stronger assurance of reliability and relevance. It allows you to inform the person precisely at the time of collection and to obtain their explicit agreement in accordance with the GDPR. However, this process can be time-consuming and ill-suited to large volumes.
On the other hand, automated solutions through newsletter sign-ups, downloads or account creation save time, but call for heightened vigilance on proof of consent and transparency towards the prospect.
Selling, buying and renting prospect lists: what restrictions apply?
The purchase and rental of databases intended for sales prospecting are strictly regulated. Any company that sells or transfers lists must ensure the lawful origin of the information, that consent was obtained and that the end user can easily exercise their rights.
To limit the risks, you are advised to require the supplier to provide:
- A written undertaking on GDPR compliance and data security
- Documentation showing that the individuals in the file were given information and gave their consent
- A contractual limitation of permitted uses, in particular for B2C prospecting
In the event of non-compliance, liability may fall on the seller as well as the buyer if a claim is brought or a penalty is imposed by the CNIL (French data protection authority).
Managing individuals’ rights and the controller’s obligations
Smoothly handling requests relating to the rights of access, objection, portability or erasure is a crucial challenge for database compliance. These requests must be handled promptly, without unnecessary obstacles, and sometimes lead to the amendment or even outright deletion of the contact record.
Traceability of requests, regular updating of the database and purging “inactive” data (prospects who no longer respond) are recommended practices to limit the holding of obsolete data and ensure fair processing.
Documentation and internal data protection policy
Putting in place a clear internal personal data protection policy strengthens control of legal risks and improves the company’s reputation. Drawing up formal procedures for obtaining consent, for listing upcoming processing operations and for responding to a breach ensures a proactive stance towards the regulations.
Beyond the legal aspects, raising all staff’s awareness of the GDPR fosters a culture of respect for individual freedoms and prepares the organisation to deal effectively with any inspection by the competent authorities.
B2B versus B2C: what are the differences for prospecting?
In sales prospecting, distinguishing between B2B and B2C approaches is of major importance. Under the legislation, electronic marketing to professionals benefits from a relative relaxation: opt-out may be sufficient, provided the message is genuinely related to the person’s professional role.
Conversely, in B2C, prior opt-in is the rule for prospecting by email or SMS, except for customers approached about similar products or services from the same company. Any departure from this exposes you to heavy penalties, which explains the CNIL’s heightened vigilance over mass campaigns and purchases of consumer lists.
Frequently asked questions on building a prospect database and the GDPR
What documents should you keep to prove that a prospect database is compliant?
The traceability of actions carried out on a prospect database relies on keeping several key items. You should keep:
- The record of processing activities, setting out the purposes and the categories of data
- The history of consents received (email, paper signature, electronic trail)
- Proof of the information provided to data subjects
- Logs of responses to requests to exercise rights
A summary table can make this easier to see:
| Document | Purpose |
|---|---|
| Record of processing activities | Description of processing operations |
| Proof of consent | Legal justification |
| Record of information provided | Transparency towards the individual |
| History of rights requests | Compliance with GDPR obligations |
How do you obtain valid consent under the GDPR?
Valid consent requires that the person has received clear information about the use of their data and can tick the consent box themselves, separately from any general terms and conditions of sale. The request must remain separate from other purposes, with no ambiguity about the type of communication to expect.
- Detailed information at the time of collection
- No pre-ticked box
- Easy withdrawal of consent
- Archiving of proof of acceptance
Following these steps carefully limits the organisation’s risk of challenges to the lawfulness of the file.
What are the main penalties for failing to comply with the GDPR?
In the event of non-compliance when creating or using a prospect database, several types of penalties may be imposed. They vary according to the seriousness of the breaches found:
- Formal notice to comply
- Administrative fine of up to €20 million or 4% of annual worldwide turnover, whichever is higher
- Publication of the penalty and, before the courts, compensation for the damage suffered by the data subjects (Article 82 GDPR)
A table summarises the risks:
| Type of penalty | Consequence |
|---|---|
| Fine | Up to €20 million or 4% of annual worldwide turnover |
| Bringing into compliance | Obligation to correct promptly |
| Civil compensation | Compensation for the damage |
What should an internal policy on protecting prospects’ data contain?
A protection policy dedicated to managing customer and prospect data must set out in writing:
- The GDPR-compliant collection procedure (initial information and consent)
- The process for handling rights of access, rectification and erasure
- The security commitments applicable to the database (authentication, restricted access rights, backups)
- A continuous training plan for teams handling personal data and a protocol for suspected breaches or data loss
Documenting these points makes compliance easier during inspections and limits the risks linked to uncontrolled sales prospecting.