22.04.2025
Legal

To make a website GDPR-compliant, you need to list the data collected, define a legal basis for each processing operation, inform visitors, manage cookies and secure data. This guide details the 10 points to check.

To make a website GDPR-compliant, you need to identify the personal data collected, define the legal basis for each processing operation, inform visitors, manage cookies properly and put in place appropriate security measures. Compliance is not just a matter of adding a cookie banner or a privacy policy.
The General Data Protection Regulation (GDPR) has applied since 25 May 2018. It governs the collection and use of natural persons' personal data, including on websites, e-commerce shops and applications.
A simple contact form may be concerned. The same applies to a customer account, a newsletter sign-up, an audience measurement tool or a booking service.
How do you know whether your site meets its obligations? What information must appear on forms? Do you need consent for every collection? And how do you configure analytics tools and advertising trackers correctly?
ID Interactive is a digital agency based in Arradon, near Vannes (Morbihan), since 2006, and a Google Partner, Meta Business Partner and Shopify Partner. The agency supports companies in the design and technical development of their websites, in particular on forms, trackers, hosting and security.
This guide presents ten essential checks to prepare a website's GDPR compliance, to be adapted with the data controller and, where necessary, its data protection officer.
The GDPR is a European regulation that governs the processing of personal data.
Personal data is any information relating to an identified or identifiable natural person.
In particular, it may be:
Health data, political opinions, religious beliefs and certain other categories of data enjoy special protection.
The GDPR concerns sites that process personal data falling within its scope.
This may include:
The regulation does not apply only to large companies.
A small or medium-sized business may also be concerned as soon as it processes personal data under the conditions set out in the GDPR.
No. There is no universal, mandatory GDPR certification that automatically declares an entire website compliant.
Certification mechanisms may exist within specific scopes, but they do not replace analysis of the processing, responsibilities and measures actually implemented.
Compliance must be documented, applied and maintained over time.
The first step is to draw up an inventory of the processing operations on the site.
You need to examine forms, user accounts, analytics tools, advertising solutions, third-party services and data recorded by applications.
For each processing operation, identify:
Example: a contact form collects a prospect's name, email address and message in order to respond to their request.
The site must explain how this information is used and avoid asking for data unrelated to the request.
The record of processing activities documents the main operations carried out on personal data.
Article 30 of the GDPR sets out this obligation, with certain exemptions for organisations with fewer than 250 employees.
However, these exemptions remain limited, particularly when processing is not occasional, involves risks or concerns certain sensitive data.
In practice, the regular management of customers, prospects or employees generally justifies documentation in the record.
A record template can make the work easier, but it must be adapted to the processing actually carried out.
A completed record is not enough, on its own, to make the site compliant.
All processing of personal data must be based on an appropriate legal basis.
The GDPR provides for six main legal bases.
The choice depends on the actual purpose and circumstances of the processing.
Consent should not be selected systematically.
Not necessarily.
When someone uses a form to request a quote or information about a service, the processing may, depending on the context, be based on pre-contractual measures taken at their request or on another appropriate legal basis.
You need to distinguish between processing their request and any later use of their contact details for prospecting purposes.
Data collection must always be accompanied by clear information.
Adding an "I accept the GDPR" box replaces neither the choice of an appropriate legal basis nor a compliant information policy.
The information must be accessible and understandable at the time the data is collected.
In particular, the GDPR requires the following to be communicated:
This information can be organised in several layers.
For example, a short notice can appear under a form, along with a link to a more complete privacy page.
Here is a framework to customise:
"The information collected in this form is used by [company name] to process your request. It is intended for the people authorised to respond to it and, where applicable, for authorised service providers. To find out the legal basis, how long your data is kept and how to exercise your rights, see our privacy policy."
This wording is a drafting example, not a notice that is legally sufficient in every case.
It must be completed according to the legal basis, recipients, retention periods and actual processing arrangements.
Cookies and other trackers are used in particular to remember certain preferences, provide features or measure browsing.
Not all cookies require prior consent.
The rules depend above all on their purpose and use.
The rules on trackers fall in particular under Article 82 of the French Data Protection Act, in conjunction with the GDPR for the processing of personal data.
When consent is required, the site must in particular:
In particular, the CNIL recommends that "Accept all" and "Refuse all" buttons be offered with a comparable degree of simplicity.
Misleading interfaces that deliberately make refusal harder must be avoided.
The CNIL generally recommends keeping the choice expressed by an internet user for six months, whether it is acceptance or refusal.
This is a recommendation to be assessed according to the context of the service, not a universal legal period of validity for consent.
The technical lifetime of cookies is a separate question.
For certain audience measurement tools that may be exempt from consent, the CNIL provides separate recommendations on the lifetime of trackers and the retention of the information collected.
The six-month recommendation for remembering the choice should therefore not be confused with the thirteen months applicable to certain audience measurement trackers.
Websites often use external tools: Google Analytics 4, Google Tag Manager, Meta Pixel, YouTube videos, interactive maps, chats or automation solutions.
These tools may lead to the collection of personal data or access to information stored on visitors' devices.
You therefore need to study how they work, their purposes and their settings.
You should not assume that Google Analytics 4 is automatically exempt from consent.
The CNIL provides for a possible exemption for certain audience measurement solutions, under strict conditions.
In particular, the tool must be limited to audience measurement on behalf of the publisher, comply with the conditions relating to the data collected and not allow certain cross-referencing or cross-site tracking.
The actual configuration must be assessed.
Using a technical consent mode does not, on its own, replace obtaining legally valid consent when it is required.
Embedding an external video or map may lead to data exchanges with the provider even before the visitor interacts with the content.
It may be necessary to delay loading certain features until the user has made a choice.
One solution, for example, is to show placeholder content explaining why activating the service requires an action.
However, compliance depends on the actual configuration and the trackers concerned.
Personal data must not be kept indefinitely.
The data controller must determine a period proportionate to each purpose, or criteria for setting it.
These periods may differ between:
Some data may be archived to meet legal obligations or preserve rights, under the applicable conditions.
Depending on the circumstances, people have in particular the right:
Not all of these rights apply in the same way to every processing operation.
No.
A person may request the deletion of certain data, but the organisation may in certain circumstances have to or be able to keep it, in particular because of legal obligations or to establish, exercise or defend legal claims.
The request must be examined according to the legal basis, the purpose and the applicable exceptions.
In principle, the organisation has one month to respond to requests to exercise rights, with certain possibilities of extension provided for by the GDPR.
A professional site must therefore offer an effective way to contact the data controller and have an internal procedure for handling requests.
Article 32 of the GDPR requires appropriate technical and organisational measures to be implemented according to the risks.
Security is not just a matter of installing an HTTPS certificate.
A site may transmit data in encrypted form while having vulnerabilities in its administration or storage.
Relevant measures may include in particular:
Protections must be adapted to the nature of the data, the risks and the organisation's resources.
A personal data breach may affect its confidentiality, integrity or availability.
The organisation must document any breaches identified.
When a breach presents a risk to people's rights and freedoms, it must be notified to the CNIL without undue delay and, where possible, within 72 hours of the data controller becoming aware of it.
When the risk to people is high, they must also be informed, subject to the exceptions provided for.
Preparing this procedure must be part of organising the site's security.
The data controller is the organisation that determines the purposes and essential means of the processing.
The processor processes personal data on its behalf, as part of a service.
For a website, the providers concerned may include:
The legal role of each must be determined according to the activities actually carried out.
When a provider acts as a processor within the meaning of the GDPR, Article 28 requires a contractual framework.
In particular, the contract must define the conditions of processing, the parties' obligations, security measures and arrangements for sub-processors.
It may also set out the conditions for returning or deleting the data after the service.
The data controller remains responsible for checking that its processors provide sufficient guarantees.
No.
Hosting located in France or in the European Economic Area can make certain constraints easier to manage, but it does not guarantee that the processing as a whole is compliant.
In particular, you need to check:
Data hosted in France may be subject to an international transfer in certain configurations.
The analysis must therefore cover the whole processing chain, not just the address of the data centre.
When personal data is transferred to a third country, the applicable legal mechanisms must be checked.
Depending on the case, this may be:
For the United States, the Data Privacy Framework allows certain transfers to organisations that are actually certified and covered by the adequacy decision.
The recipient's membership and the scope of the transfer must be checked.
You need to distinguish the information that identifies a site's publisher from the information about the processing of personal data.
These two sets of information serve different purposes.
This information can be organised in several ways, provided it remains accessible, complete and understandable.
The privacy policy must match the processing actually carried out.
In particular, it may include:
You should not copy a generic privacy policy without checking that it suits the site.
For example, an e-commerce site using payment, shipping and marketing services does not carry out the same processing as a showcase site with just a contact form.
GDPR compliance is an ongoing process.
Adding a new tool, creating a form, changing hosting or installing a module can change the processing carried out.
The company must therefore plan an appropriate organisation.
The data protection officer, or DPO, supports the organisation in implementing and monitoring its obligations.
Appointing one is mandatory in certain cases, in particular for public bodies and for certain activities involving regular and systematic monitoring on a large scale or large-scale processing of special categories of data.
It is not mandatory for every company with a simple website.
Even when it is not mandatory, a DPO can be appointed voluntarily.
A data protection impact assessment (DPIA) assesses the risks a processing operation presents for people's rights and freedoms.
It is mandatory in particular when the processing is likely to result in a high risk or appears on the lists of processing operations for which a DPIA is required.
It should not be presented as a formality automatically imposed on every site that collects sensitive information.
Whether a DPIA is needed depends on the characteristics of the processing, its context and the applicable rules.
Yes.
Health data enjoys enhanced protection under the GDPR.
Its processing is in principle prohibited, unless one of the exceptions provided for in Article 9 applies and the other legal requirements are met.
Depending on the situation, processing may be permitted in particular in the context of care, specific obligations or valid explicit consent.
Explicit consent is therefore neither the only possible exception nor a general authorisation to freely process health data.
The projects concerned must also examine the applicable sector-specific rules.
In some cases, in particular for hosting personal health data under the conditions set out in the French Public Health Code, using an HDS-certified host may be mandatory.
Whether a DPIA is needed and the hosting requirements must be studied according to the planned processing.
The GDPR provides for several corrective measures and levels of penalties.
Depending on the breach, the authorities may in particular issue reprimands, compliance orders, processing restrictions or administrative fines.
For certain categories of infringements, the caps set by Article 83 reach:
For companies, the higher reference amount applies in the cases provided for by the regulation.
These amounts are caps, not automatic penalties.
Any penalty depends in particular on the nature, gravity, duration and circumstances of the breach.
To prepare an audit, the main checks can be grouped together in a checklist.
This checklist is a starting point.
It does not replace a compliance analysis that takes into account all the processing carried out by the organisation.
A digital agency can work on the technical and editorial aspects needed to implement the decisions taken by the data controller.
For example, ID Interactive can support a website project on several aspects:
Defining the legal bases, analysing the company's own obligations and legally validating the documents are the responsibility of the data controller, supported where necessary by its DPO or legal adviser.
Entrusting technical implementation to a provider does not automatically transfer all GDPR responsibilities to that provider.
Data protection by design, or privacy by design, means taking privacy and security requirements into account before going into production.
During a website creation or redesign project, it is particularly useful to define the data actually needed, access rights and the configuration of third-party services.
This approach avoids having to deal with all GDPR questions once the site has already been published.
The choice of hosting helps control risks and processing.
ID Interactive can study a project's technical requirements and the operating conditions associated with the chosen providers. In particular, the agency offers French hosting and cloud for the sites it develops.
However, hosting choices must be assessed together with all processing, access and any transfers.
A website cannot be declared GDPR-compliant solely on the basis of a cookie banner, a privacy page or an HTTPS certificate.
The analysis must cover the data actually processed, its legal basis, the information provided, the tools activated, the contracts, the security measures and the company's organisation.
Technical checks must be compared with documentary and legal obligations.
This process must also be repeated when the site and the services connected to it change.
To study the technical adjustments needed for your website, you can contact ID Interactive to present your environment and your needs.
Article originally published on 9 August 2020.
Elle peut l’être. Le RGPD définit la donnée personnelle comme toute information se rapportant à une personne physique identifiée ou identifiable, et l’adresse IP en fait partie lorsque les conditions d’identification sont réunies. L’appréciation dépend du contexte et des moyens dont dispose celui qui traite la donnée pour identifier la personne concernée.
Non. Le consentement préalable n’est requis que pour les traceurs non exemptés, comme la publicité ciblée ou la mesure publicitaire. Un cookie de session strictement nécessaire ou un cookie de panier e-commerce n’y est généralement pas soumis. Certains outils de mesure d’audience peuvent aussi en être exemptés, sous conditions strictes et selon leur configuration.
Le responsable du traitement doit répondre en principe dans un délai d’un mois à compter de la réception de la demande. Ce délai peut être prolongé de deux mois, compte tenu de la complexité et du nombre de demandes, la personne concernée devant alors être informée de la prolongation et de ses motifs dans le délai d’un mois.
Non, pas automatiquement. Le responsable du traitement détermine les finalités et les moyens essentiels ; le prestataire qui traite des données pour son compte est sous-traitant. L’article 28 du RGPD impose alors un contrat encadrant le traitement, et le responsable reste tenu de vérifier que ses sous-traitants présentent des garanties suffisantes.
En règle générale, non. Depuis l’application du RGPD, la déclaration préalable à la CNIL a laissé place à une logique de responsabilisation : l’organisme documente lui-même sa conformité, notamment par le registre des activités de traitement (article 30) et, si nécessaire, par une analyse d’impact. Des formalités propres à certains traitements demeurent possibles.