.agentgov folder and are never sent to us, unless you choose to share a project's report: then that report (counts, titles, severities and file names with line numbers; no code, prompts or file contents) is kept on our server behind an access code until you delete it. Our server keeps your sign-in email, your organisation's rules and requests while it exists, and anonymous counts; from it your computer downloads only the know-how. Analytics cookies are set only if you say yes.Who is responsible
agentgov is a service of Innovate d.o.o., Ljubljana, Slovenia. We are the controller of the personal data described here. Questions, requests and complaints: the contact form.
How the service works, in data terms
The agentgov app runs on your own computer. Your coding agent starts it inside your project folder. It reads that folder read-only (never .env files, keys or version-control internals), and keeps everything it makes in a .agentgov folder inside the project: the Agent Inventory, the check runs and their findings, the live tests, the registry, the decisions, the gates and the exported documents. When a step needs judgement, your own coding agent reads the code and answers with the model you already use; we run no AI model. Your coding agent reads your code with the model you chose under your own terms with that provider, not through us. The app's dashboard is served on your computer only, behind a one-time key.
The app contacts our server for four things: to sign you in (it keeps the sign-in in your user settings folder, readable only by your user; signing out deletes it), to download the know-how (what to look for in code, how to grade it, the AI Act questions, safe arguments for live probes, documentation templates; cached on your computer so the app works offline), to check your licence (a status and a date, cached for a day), and, when you belong to an organisation, for Teams (below). Nothing about your project goes with those requests.
Live tests run on your computer: the app starts your own server or agent from its code on 127.0.0.1 after your yes, in a test-mode environment, or connects to a private test address you choose (production addresses are refused), and calls its tools. What it records (which tool, a summary of the arguments' shape and of the result, never the raw result) stays in .agentgov.
Sharing a report is your choice. If you ask for it ("share the report"), the app first shows you exactly what would be uploaded and sends nothing until you agree, once per project and again whenever the report would include something new. It then uploads that project's report: the app's name, counts of agents, tools, models and MCP servers, the score and the findings (title, severity, category, consequence, status and up to three file names with line numbers each), the live test summary, the registry's tools and policies, the gate, the AI Act tier and obligations, and the last decisions in words. Never your code, prompts, file contents, secrets or tool results; email addresses, query strings, long numbers, key-like strings and money amounts are removed on your computer and again on our server. The report is shown at one stable link on agentgov.si that opens only with its access code, which we email to your signed-in address. Later publishes replace it at the same link, with at most one update email a day. It is kept until you delete it ("delete the report"), which removes every version and the code.
Teams. An organisation's admin creates it on our server and invites people by email. We keep the organisation's name, who its members are (their sign-in accounts and roles), its rules, its requests (the title, what, category, tools, data and reason a member wrote, the decision and its conditions, an attached report link), the watch records a member's computer sends (the names, transports and a hash of the MCP servers configured on it; never arguments, environment or secrets; sent only when the member agreed or the rules require it), and when the weekly digest was last sent. Requests are the member's own words, cleaned; the app never puts files, prompts or customer records in them.
What we keep, and for how long
| What | Why | How long |
|---|---|---|
| Your email address, and a contact record created when you connect (the name your tool reports, the date) | To sign you in with a one-time link, to send you your report links and Teams mails, and to know who uses the service (legitimate interest, Art. 6(1)(f) GDPR; the sign-in itself is part of providing the service, Art. 6(1)(b)) | 3 years from your last sign-in, or until you ask us to delete it |
| Your GOV on status: whether the GOV tools are on for your account | To unlock the GOV tools (providing the service) | While your account exists |
| Shared reports: the report as described above, its versions and its access code | So the link you share works (you asked for it, Art. 6(1)(b)) | Until you delete the report or your account |
| Teams records: the organisation, its members, rules, requests, decisions, attached report links, watch records | So the organisation's rules reach its members and its requests get answered (providing the service) | While the organisation exists; a member's records go when they leave or the organisation is deleted |
| A contact-form message: your name, your email, the message | To answer you | Sent to us by email and kept in our mailbox as long as the conversation needs |
| Rate-limit counters: a one-way hash of the network address or of the account, with a count | To keep the service up under floods | At most 24 hours |
| Anonymous counts: page views, install-line copies, tool and know-how calls, per day | To see what is used (legitimate interest) | 400 days; they carry no identifier |
Everything that is only about your project, from the inventory to the documents, lives on your computer, in .agentgov, under your control. We never receive it.
Emails
We send you the sign-in link and code, a welcome mail on your first connection, your report link and its access code, Teams mails (an invitation, a request waiting for you if you are an admin, the decision on your request if you are a member, the weekly digest for admins), and our reply when you write to us. No newsletter, no marketing.
Cookies and browser storage
The site sets no cookie by itself. Your choice on the consent banner and the install tab you last opened are kept in your browser's local storage. Google Analytics, when it is switched on at all, loads cookieless until you click Allow; saying no later deletes its cookies. The report pages and the Teams pages set one technical cookie each (the access code, your session) so you do not have to type them again; they are HttpOnly and not used for anything else.
Anonymous counts
When you open a page, copy an install line or click a main button, the page sends a small anonymous signal to our server: the page path, an event name and, on arrival, a coarse source such as "google" or "direct". The server adds one to a daily total and keeps nothing else: no cookie, no IP address, no identifier. A short-lived one-way hash of the network address, valid for one minute, protects the counter against floods.
Who helps us
| Service | What it does for us | Where |
|---|---|---|
| Cloudflare, Inc. | Hosts this site and the server, stores the records above, including shared reports and Teams records | Global edge network; EU Standard Contractual Clauses |
| Resend, Inc. | Sends the sign-in, report-link, Teams and contact-form emails | United States; EU Standard Contractual Clauses |
| Google Ireland Ltd. (Google Analytics) | Visit statistics, only if analytics is switched on and you click Allow | EU / United States; EU-US Data Privacy Framework |
We do not sell personal data and do not share it with anyone else, except where the law requires it.
Your rights
You can ask for a copy of your data, its correction or deletion, a restriction of processing, data portability, and you can object to processing based on legitimate interest. Write to us through the contact form; we answer within one month. Deleting your contact record also ends your sign-in and your membership of any organisation. You may also complain to the Slovenian data protection authority, the Information Commissioner (Informacijski pooblaščenec, www.ip-rs.si), or the authority where you live.
About the findings
Every finding, score and AI Act tier agentgov shows is a reading of your code by your own coding agent, to be checked against the file and line it names. A code reading, not a legal opinion.
Changes
If what we keep changes, this page changes first, with a new date at the top.