Security and privacy programme
ISO 27001 and GDPR programme in progress. EU hosted.
Your policy, applied to every app your teams build with AI.
Upload or write your rules. NEKOD checks each app against them and shows the line or setting behind every result, so you sign off with a record you can show.
Book a DemoYour policy is written. Showing it was applied is the hard part.
Rules on paper, apps in useThe apps your business teams built with AI were never checked against the policy you wrote.
Evidence gathered by handEach review means screenshots, interviews and a spreadsheet. It takes weeks, and it is out of date when it is done.
Questions that take a project to answerWhich apps touch personal data? Who approved them, and on what basis? Audit asks, and the answer takes weeks.
Before
Without NEKOD
Apps go live one at a time, and nobody holds the whole picture.
Every app checked against your own rulesYour policy, not a generic checklist. Edit a rule and check again.
Evidence behind each findingThe line of code or setting that passed or failed, next to the rule it was checked against.
A trail you can hand to auditWho approved each app, when, and on what evidence, in one place.
After
With NEKOD
Upload or write your rules. NEKOD checks each app against them and shows the line or setting behind every result, so you sign off with a record you can show.
Discover, Control, Approve, Monitor
Discover
See the apps your teams built, and which ones touch personal or sensitive data.
Control
Your written policy becomes checks. You review how each rule was read.
Approve
Sign off with the evidence beside each result, or send the app back with what to fix.
Monitor
Change a rule and check again, so the record stays current.
What each approval keeps, ready for audit.
One place for the rule, the evidence and the decision, instead of screenshots and an email thread.
- 01
The rule
The line of your written policy the app was checked against, and how that rule was read, as you signed it off.
- 02
The evidence
The line of code or setting that passed or failed, next to the rule it was checked against.
- 03
The decision
Who approved the app or sent it back, when, and the reason they gave.
- 04
The recheck
When you edit a rule, check the apps again. The new result sits next to its evidence, so the record stays current.
Trust, by design
Data handling and AI safety
Data stays read-only by default. Customer data is hosted in the EU.
Granular access control
Scoped, read-only access by default. Single sign-on is on the roadmap.
Audit and oversight
Evidence for each check, with a recorded approval you can show to risk, audit or the board.
“I got hacked. That's a good thing. They found nothing on DoneThat.”
Christoph Hartmann
Founder, DoneThat
Common questions
You see how each rule was turned into a check, and you sign that off. Every result shows its evidence, so you can test our reading yourself. No app is approved without a person.
Your written policy, as a document or as rules you type in. You decide which rules apply to which apps.
Edit the rule and check the apps again. The new result sits next to the evidence, so the record stays current.
A person, always. NEKOD shows the evidence. The approver signs off or sends the app back with what to fix.
Every app checked against your rules, with a record you can show.
In 30 minutes we show a policy check with the evidence behind it, and the approval record you can hand to audit.