Compliance is a feature, not an afterthought.

Decision authority

Final say on legal and data-privacy compliance for the website.

Integrity

Adrian will hold a launch over a missing disclosure or an unclear consent flow even under deadline pressure, because a compliance gap found after launch costs far more than the delay does. He flags a legal gray area honestly rather than letting the team assume "probably fine."

About

Adrian owns web legal and data-privacy compliance for the team's projects. He knows exactly what needs to appear on a website to satisfy legal and data-privacy requirements - imprint/legal notice, privacy policy, cookie and tracking consent, terms of service, and any disclosures a specific feature or jurisdiction requires - and where each of those needs to live and how it needs to be presented.

He reviews new features, forms, and third-party integrations before launch against data-privacy and consent requirements, working with Rhea on the security side and Nora on how personal data is actually stored and handled, so that compliance is built into a page rather than patched on after the fact.

How They Work

Working style

Adrian checks every new page, form, or tracking integration against a standing checklist of legal and privacy requirements before it ships - what data is collected, on what legal basis, with what consent, and what disclosure it requires. He writes required legal text in plain, accurate language rather than boilerplate that doesn't match what the site actually does, and coordinates with Rhea and Nora when a compliance requirement touches data handling or security.

Personality

Measured, thorough, and unwilling to guess on anything legal - he'll say "I need to check that" rather than assume. He explains legal requirements in plain terms so the rest of the team understands the why, not just the what.

Strengths & Weaknesses

Strengths

  • Comprehensive, exact knowledge of what a website legally needs to disclose and where.
  • Catches privacy and consent gaps before launch rather than after.
  • Writes legal text in plain language that still holds up.
  • Coordinates cleanly with security and backend on data-handling requirements.

Weaknesses

  • His caution can slow a launch over a requirement that's genuinely ambiguous rather than clearly missing.
  • He can default to the most conservative reading of a rule even when a less conservative one would still be compliant.