About RGPD.click — Why This Project Exists
1. Why RGPD.click Exists
RGPD.click is an independent initiative created to make the GDPR more tangible, readable, and directly applicable in daily practice.
While working across IT infrastructure, systems engineering, cybersecurity, technical support, and software development, I repeatedly observed the same structural bottleneck: official legal texts are publicly accessible, yet bridging the gap from abstract statutory rules to concrete operational decisions remains arduous.
The vision behind RGPD.click stems from this insight. The platform was designed to facilitate seamless, frictionless navigation:
The project has grown into a comprehensive, structured knowledge base combining full GDPR articles, Court of Justice of the European Union (CJEU) case law, European Data Protection Board (EDPB) guidelines, operational playbooks, interactive micro-tools, and a specialized documentary assistant.
I develop and maintain the platform independently, including its technical architecture, interactive tooling, regulatory monitoring pipelines, and content structuring. The project operates with complete autonomy and is not affiliated with any European institution, supervisory authority, or commercial law firm.
2. Who Is Behind the Project
I develop and publish RGPD.click under the pseudonym Matsetop.
My background is rooted in IT systems, networks, technical support, web development, and process automation. I am particularly drawn to intersectional areas where technology meets regulatory compliance: data privacy, operational security, IT governance, and structured knowledge engineering.
RGPD.click originated as a personal research and self-training project, before evolving into a publicly accessible, structured documentation platform.
Unambiguous Positioning: I am neither an attorney nor a member of a supervisory authority. This platform is not intended to provide or substitute for individualized legal counsel.
The core mission is distinct: delivering a clear, traceable, and authoritative working base directly linked to primary legal sources, empowering anyone navigating or applying the GDPR to find reliable operational direction.
3. What the Platform Provides
Today, RGPD.click unites several complementary components built for IT practitioners, Data Protection Officers (DPOs), software engineers, and digital law professionals:
- The Complete Official Statutory Corpus: All 99 articles and 173 recitals of the GDPR faithfully transcribed from the Official Journal of the European Union (EUR-Lex CELEX:32016R0679).
- Landmark CJEU Case Law Analyses: From foundational rulings (Google Spain, Schrems II) to recent jurisprudence (Österreichische Post, KNLTB, Legal Newsdesk Sweden, Jautiva).
- 10 Structured Operational Guides: DPIA methodology, DPO appointment and governance, 72-hour data breach handling, international data transfers, cookies & Consent Mode v2, Article 30 records, Article 28 DPA contracts, data subjects rights management, legitimate interest assessments (LIA), and AI web scraping.
- In-Depth Doctrinal & Analytical Articles: A specialized blog examining operational friction points (EU AI Act, publicly accessible web data, digital age of consent, employee offboarding, web scraping).
- Interactive Decision-Support Micro-Tools: Decision trees (legal basis, DPIA requirement, cookie classification, processor evaluation), statutory deadline calculator (Art. 12.3), and LIA balancing framework.
- Specialized Documentary Assistant (Public Lexi): An interactive system engineered to navigate the legal corpus and provide exact, verified citations.
4. Source Selection & Documentary Hierarchy
To guarantee authoritative reliability, RGPD.click enforces a strict principle of systematic traceability, anchoring all substantive statements to verifiable official sources:
Visual Distinction: Across the entire platform, legally binding statutory provisions are clearly distinguished from non-binding guidance or consultation drafts.
5. AI Usage & Editorial Transparency
Committed to high transparency standards regarding artificial intelligence technologies — reflecting the transparency duties codified in digital regulations such as Article 50 of the EU AI Act —, RGPD.click maintains a strict distinction between two separate AI use cases:
💬 A. Public Lexi: Visitor Documentary Assistant
RAG Architecture: For website visitors, Lexi acts as an interactive assistant powered by Retrieval-Augmented Generation (RAG). Responses are grounded exclusively in pre-indexed statutory articles, recitals, and case law.
Post-Generation Anti-Hallucination Guard: A deterministic validation filter verifies every cited legal reference prior to rendering, rejecting unauthorized inventions or phantom article numbers.
Privacy & Zero Data Retention: Queries are processed exclusively through APIs covered by enforceable Zero Data Retention commitments (Groq ZDR and OpenRouter with explicit opt-out data_collection: deny). No user prompt is ever retained or reused for model training.
Absence of Legal Advice: Lexi serves a purely educational and documentary purpose. Its outputs do not constitute legal advice and must always be cross-referenced against the official source texts provided.
🖋️ B. Editorial Lexi: AI-Assisted Production Pipeline
Selected doctrinal analyses and background essays published in the blog are drafted with the assistance of a locally deployed language model orchestrated via automated workflow pipelines (n8n). To ensure rigorous legal substance, publication follows a strict, iterative multi-step process:
- Structural Validation: Rigorous document schema verification (YAML frontmatter, metadata tags, header hierarchy, and source integrity).
- Adversarial Legal Audit: An independent AI instance critically reviews drafted passages with strict instructions: eliminate over-interpretations, enforce doctrinal accuracy under current positive law, and mandate removal or reservation on any unconfirmed case citations.
- Bounded Correction Loop: If critical issues are identified during the audit, the draft enters a targeted revision cycle strictly capped at 3 iterations maximum to prevent drift or infinite feedback loops. Persistent ambiguities require direct human resolution prior to release.
- Scope of the System: This mechanism functions as an additional editorial quality gate to enhance draft rigor; it does not constitute an infallible guarantee of absolute legal certainty.
- Transparency on External Validation: Automated, real-time citation cross-checking against external live legal databases (EUR-Lex, Curia, or EDPB registries) is currently in development as part of the technical roadmap.
6. Quality Control & Continuous Maintenance
European digital law and privacy standards evolve continuously through CJEU judgments and regulator guidance:
- Case Law Monitoring: Ongoing review of rulings delivered by the Court of Justice of the European Union to update corresponding doctrine and guidance.
- EDPB Watch: Timely integration of newly adopted guidelines, opinions, and consultation documents.
- Comprehensive Automated CI Test Suite: An end-to-end automated testing suite (unit tests, backend assertions, static SEO/SSOT/HTML linters, anti-hallucination citation guards, and Playwright E2E checks) runs on every commit to enforce DOM parity, link integrity, and accurate deadline computations.
- Rapid Remediation: Any identified inaccuracy, typographical error, or regulatory change is promptly resolved and redeployed via the GitHub repository.
7. Limitations & Independence
RGPD.click is an independent technical, civic, and educational initiative.
The platform is neither affiliated with, nor sponsored or subsidized by, any public authority, European institution, or commercial enterprise. All analyses, architectural decisions, and interactive utilities are developed with complete editorial freedom.
Contents provided on this website are intended for general information and methodological reference. They do not replace formal legal advice tailored to specific factual circumstances by a qualified legal professional.
8. Contact & Inquiries
This project is continuously maintained and improved. To report an error, suggest a practical case study, or submit a technical inquiry: