
DPOLens gives your AI the text of privacy law, clause by clause, so an answer quotes the clause it relies on instead of paraphrasing it from memory.
Every clause has a stable key, such as gdpr:art-17:para-1, with the law's version and the date it came into force, so a citation can be checked and still reads the same after the law changes. This is the DPOLens community version: public law only, free, with no account and no token.
Example path →
https://mcp.dpolens.com/This is the DPOLens community version. It searches GDPR and the UAE's data protection law, and returns the clause itself, word for word, with the key, document and version to cite it by. An organisation that runs DPOLens itself searches its own policies beside the law, with a log of every question and every change: github.com/alkhatibdev/dpolens.
Search DPOLens before writing or changing code that collects, stores, logs, shares or deletes personal data, and before answering a question about what a policy or the law requires.
Personal data includes names, email addresses, phone numbers, postal addresses, identity document numbers, payment details, location, device identifiers, IP addresses, and anything else that can be linked back to a person.
Do not answer from memory. A remembered article number is not a citation, and the version in force here may not be the version you were trained on.
Quote the clause you relied on and give its key, document and version, so the person reading your code can check it.
Questions that work well:
how long can we keep a deleted user's account data do we need consent to log IP addresses for debugging what has to happen when somebody asks for a copy of their data
Start with . Use when a result points at another clause, or when you need the whole of an article rather than the part that matched. and say what this version can cite at all.
None in the store listings or on the server