Ask before building
A product manager describes the planned feature in plain language and gets the verdict, what blocks the build, what is required before the build and what is already covered, with next steps.
An AI agent for a first compliance assessment. Describe a product feature and it drafts an assessment against the GDPR and the EU AI Act.
A demonstration, not legal advice. The hosted demo runs on free tiers and may take a minute to wake up. Please enter no real personal data; see the privacy notice.
A product manager describes the planned feature in plain language and gets the verdict, what blocks the build, what is required before the build and what is already covered, with next steps.
The DPO reviews each draft in a queue: amend, approve, request changes to the feature, or reject.
Describe a feature; get a structured draft.
Worker
searches the law in a grade-and-retry loop (agentic RAG), calls tools through a role gate, drafts the assessment
Reviser
takes over after the DPO requests changes: reads the product manager's revised feature and drafts version 2
The agent pauses; the DPO has the last word.
Pause
every full assessment stops at a checkpoint and waits for review
Decision
approve · request changes · reject, after editing severities and wording; the DPO's decision resumes the run
Organisation
facts and lessons from the DPO's rulings, read by the agent at the start of every run; what is remembered is chosen by the DPO, never taken from the feature text
Person
each user's own preferences for future assessments, saved by the user
Written on approval only
the DPO's approval is the one action that creates a record
What it holds
title, verdict, risk level, DPIA, AI Act class, who requested and who approved
Seven evaluation sets with 100 synthetic inputs, run against the deployed configuration on 27 October 2026 (retrieval re-run on 3 November). Scored three ways: exact rules against the test data; an AI judge with a rubric, from a model family the app never uses; and a blind human check of five cases.
Where it falls short: the right finding sometimes sits one severity step too high or too low, and the verdict field is stricter than the findings beneath it. Read the full report.
A compliance tool has to practise what it checks. Every statement below can be verified in the public repository: the code, the model configuration and the gateway's documents and settings saved as evidence.
The input screen redacts e-mail addresses, phone numbers, bank account and card numbers before any model call.
The gateway account allows only zero-retention endpoints and no training on requests, and every request carries that policy itself; a reranker that could not meet it was replaced.
The database is hosted in Frankfurt. Conversations and their saved state are deleted after 30 days by a scheduled job, and a person can have their data deleted on request.
Product manager and DPO see different screens and the agent may call only the tools the signed-in role allows.
Prompt injections and off-topic text are refused at the door; every citation in a draft is checked against the law's text, the output gets a disclaimer, and the evaluation caught 14 of 14 planted inputs.
Sign-in through Google with PKCE and a signed eight-hour session. The privacy notice, public in the app, says what is collected, where it goes and how to ask for deletion.
Hybrid retrieval over the two regulations (vector and keyword search, fused, then re-ranked), a tool gate that limits what each role may call, a checkpointer that makes the human pause durable, and long-term memory in the same database. The repository has the technical design, the UI notes, the evaluation method and the compliance evidence.