A compliant page must above all allow a person to understand who edits the site, why your data is requested, how to exercise your rights and what choices exist for trackers.
| Point to check | What we need to see | If it's not clear |
|---|---|---|
| Site identity | Editor, manager, contact, host and easy way to reach a person. | Priority complete the legal notices and check the contact links. |
| Personal data | Purposes, legal basis, retention period, recipients and rights of individuals. | Rewrite the privacy policy with short, verifiable sentences. |
| Cookies and trackers | Choice to accept, refuse, configure, with permanent access to modifying the choice. | Check the banner, categories, proof of consent and retention period. |
| Evidence | Update dates, text version, history of changes and log of requests received. | Create an internal file with captures, dates, published texts and responses sent. |
Read the full page to link site clarity, evidence and customary obligations.
Detailed pageCompliance often intersects with domain names, cybersecurity, or reporting.
See the expertiseIndicate the URL, the doubt observed, the captures and the date of observation.
Write to usANRDI informs, supports and guides. It does not replace a competent authority, an official reporting platform, AFNIC, a lawyer or a court decision.