The website track: four practical GDPR items
GDPR (Regulation (EU) 2016/679, applicable since 25 May 2018) sets four practical requirements:
- Lawful basis and minimisation (Art. 6, Art. 5(1)(c)). Every processing operation needs one of the six lawful bases, and data collected must be limited to what is necessary. Marketing and consultation consent are separate, never bundled (Art. 7(4)).
- A privacy policy that matches reality (Art. 12–14). The policy must match what the site actually does — a copied template claiming unused practices is itself a risk. Art. 13 requires purposes, retention, recipients and rights to be stated at collection.
- Consent evidence (Art. 7). Who consented, when, and to what must be retrievable — Art. 7(1) requires the controller to demonstrate consent. This site's lead system is built to that standard (timestamp plus source path). Withdrawal must be as easy as giving consent (Art. 7(3)).
- A rights process (Art. 15–17, Art. 20, Art. 12(3)). Access, rectification, erasure and portability requests need a defined entry point and timeline. Art. 12(3) requires action within one month, extendable by two months for complex cases, reasons given within the first month.
The AI track: classify first, then build
The EU AI Act (Regulation (EU) 2024/1689, in force since 1 August 2024) grades applications by risk: unacceptable (prohibited), high, transparency, and minimal or no risk — the Commission's four levels.
Conversational support, content generation and internal assistants are usually not high-risk, but they carry transparency duties: a chatbot user must be told they are interacting with an AI system (Art. 50), and AI-generated content must be identifiable, with deep fakes clearly labelled. The industry calls this tier "limited risk"; the regulation uses no such name.
High-risk has two routes (Art. 6): AI as a safety component of an Annex I product needing third-party assessment (Art. 6(1)); and the Annex III use cases (Art. 6(2)): recruitment screening (4(a)), creditworthiness assessment (5(b), fraud detection excluded), and others. High-risk systems require risk management, data governance, documentation, logging, deployer transparency, human oversight and post-market monitoring (Art. 9–14, 72); deployers must assign oversight to competent, trained, authorised natural persons (Art. 26). Design this in at project start — retrofitting costs far more.
Two details matter. First, Art. 6(3) excepts Annex III systems posing no significant risk and doing only one of four narrow functions — but profiling is always high-risk. Second, the timeline: generally applicable since 2 August 2026, but the Digital Omnibus (Regulation (EU) 2026/1744, in force 27 July 2026) pushed Annex III duties to 2 December 2027, Annex I to 2 August 2028.
Four points most often missed on the website side
- Analytics must sit behind consent. Statistics and marketing scripts loading before consent are the most common European website violation. The consent gate is ePrivacy Directive Art. 5(3) (as amended in 2009): accessing information on a user's device requires prior consent. Consent management must block unconsented loading, not just show a banner.
- Contact forms must say what happens. Purpose, retention period, who can access the data, and how users exercise deletion and export rights belong next to the form and in the privacy page (Art. 13).
- AI chat and support widgets need a data-flow check. Where visitor input goes, who processes it, where it is stored, and whether it trains models — covered by a data processing agreement (Art. 28).
- Cross-border transfers need an assessment on file. When headquarters sit outside Europe and data flows back to China, Chapter V (Art. 44–49) requires a valid transfer mechanism (adequacy decision, safeguards such as SCCs, or a derogation); a transfer impact assessment is usually filed as well.
Where this meets GEO
Solid compliance is a visibility asset: consistent, factual privacy and company pages help engines judge trustworthiness. Technical foundations matter: in Negency's flagship measurement of 30 Chinese exporter companies' global homepages (a single-day sample on 30 October 2026, measuring technical website visibility only, not brand mention rates in AI answers), machine readability averaged 69.2 (median 68.5), 17 of 30 sites had no JSON-LD at all. Source: Flagship Report 2026, Issue 1. The Negency team does this work in European automotive and manufacturing.
Penalties: know the scale first
GDPR fines for core breaches run up to €20 million or 4% of worldwide turnover, whichever is higher (Art. 83(5)); under the AI Act, prohibited practices draw up to €35 million or 7%, other infringements up to €15 million or 3% (Art. 99). Those are ceilings, not typical fines.
This is a summary of common requirements, not legal advice; implementation needs counsel familiar with EU data law. Preparing the engineering facts first — a data-flow map and a retention table — speeds that up.