Who is responsible
agentgov is a service of Innovate d.o.o., Ljubljana, Slovenia. We are the controller of the personal data described here, except for your activity in an organisation, where your organisation decides (below). Questions, requests and complaints: the contact form.
Who decides
For your activity in an organisation, your organisation decides what is collected and why; we keep and process it on its behalf. Ask your IT team first; you can also write to us. The rules for that processing are in the terms.
How the service works, in data terms
For IT teams. An admin creates the organisation on our server, chooses its rules and invites people by email. Each person connects the AI app they already use to agentgov. From then on their agent reads the rules at the start of a session, asks IT before work that needs approval, and reports what it does in one short sentence about the kind of work. Our server also notes, by itself, when the app connects and which agentgov tools the agent calls. The dashboard shows the organisation's admins who is connected and what their agents reported.
Computers set up by IT. On company computers with Claude Code, Codex or Cursor, IT may deploy settings files and a small reporting script. The script reads the app's report on the computer, keeps only the names (the event, the tool, the connector, the session, the person) and sends nothing else; our server refuses any other field, and keeps nothing for a person who has not joined the organisation.
For developers. The agentgov app runs on your own computer, started by your coding agent inside your project folder. It reads that folder read-only (never .env files, keys or version-control internals) and keeps what it makes in a .agentgov folder inside the project. Your own coding agent does any judging with the model you already use; we run no AI model. The app contacts our server to sign you in, to download its know-how, to check its licence, and for your organisation's rules. Nothing about your project goes with those requests. Sharing a report is your choice: if you ask for it, the app first shows you exactly what would be uploaded (counts, titles, severities and file names with line numbers; never code, prompts, file contents or secrets) and sends nothing until you agree. The report opens only with its access code, which we email to you, and is kept until you delete it.
What IT sees, and what it never sees
The same lists are on every invitation mail and join page.
What IT sees
- That you joined, your role, and the display name IT gives you.
- Which AI app you use agentgov in, and when.
- The names of the tools and connectors your agent uses.
- On a computer IT has set up (Claude Code, Codex, Cursor): every tool your app uses, by name, reported by the computer.
- The list of servers the agentgov app on your computer reports, if you send it.
- Which company rule was hit.
- Your requests and IT's answers.
- Your "I'm stuck" notes.
- One short sentence your agent writes about the kind of work ("drafting an email to a client").
What IT never sees
- Your messages.
- What the AI answers.
- Your files, and what you paste.
- Commands and their details.
- Tool inputs.
- Your passwords.
- agentgov does not receive or store them.
How much IT sees depends on the app, and on whether IT set up the computer:
| App | agentgov sees | agentgov never sees | Rules enforced by the app |
|---|---|---|---|
| Claude Code + IT's managed settings | every session start and end; the name of every tool the agent uses (built-in and connectors) and its server; the permission mode; calls to agentgov; the agent's short reports | prompts, answers, file contents, commands, tool inputs and outputs — the reporting script reads the app's report on the computer, keeps only the names and sends nothing else | the rules marked Enforced (allowed connectors, models, the skip-all-permissions mode, company-only settings); those marked Partly enforced in part (common forms of a command are stopped, other forms are not) |
| Codex + IT's requirements and hooks (not yet checked on a real account) | session start and end; tool names; calls to agentgov; the agent's short reports | the same as above; hosted tools such as web search are not covered by Codex hooks | the rules marked Enforced or Partly enforced for Codex (approval policies, sandbox modes, the allowed connectors) |
| Cursor + IT's hooks file | session start and end; shell runs and connector calls after they ran (names only); calls to agentgov; the agent's short reports | the same as above | none generated (agentgov's Cursor hooks only watch); settings in Cursor's admin console on Enterprise plans |
| claude.ai, Claude desktop, ChatGPT | the connection, every call to agentgov, the agent's short reports | everything else the agent does: other connectors, files, web search, the chat | only what the app's own admin console offers; agentgov shows the steps |
| VS Code, Windsurf and other apps | the connection, every call to agentgov, the agent's short reports | everything else | none |
| Any app without agentgov connected | nothing; the person shows as not connected | everything | none |
What we keep, and for how long
| Who | What, and why | How long |
|---|---|---|
| Everyone who signs in | Your email address and when you signed in, to sign you in with a one-time link or code and to send you the mails below (providing the service, Art. 6(1)(b) GDPR). If you sign in on your own, not because a company invited you, also a contact record (the name your app reports, the date), to know who uses the service (legitimate interest, Art. 6(1)(f)) | 3 years from your last sign-in, or until you ask us to delete it |
| People in an organisation (employees) | Your email (shown in full to your organisation's admins only), your role and display name, when you joined; the AI apps you use agentgov in and when; the names of tools and connectors your agent uses; rule hits; your requests and IT's decisions; your "I'm stuck" notes; one short sentence your agent writes about the kind of work; when IT asks for it, the names of the connectors set up in your app. From every sentence, request and note we remove email addresses, phone and card numbers, IBANs, long numbers, links, file paths, file names and anything shaped like a key; the agent is told not to write names. Kept on your organisation's behalf (below) | Activity and the connector list 180 days at most (your organisation may choose less), and the connector list goes at once when you leave or are removed; requests, decisions and the admin log 3 years; "stuck" notes 90 days; everything goes when the organisation is deleted |
| Computers set up by IT | For each session and tool call: the app, the tool name, the connector name, the time, which person (as the computer says). The reporting script reads the app's report on the computer, keeps only these names and sends nothing else; our server refuses anything else. Kept only for people who joined | As above |
| Invitations | The address IT typed, who invited, when | Until accepted; blanked 30 days after it expired or was revoked |
| Organisations | Name, rules and their history, settings, reporting keys (stored only as a fingerprint) | While the organisation exists |
| Developers who share a report | The report of one project, 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 |
| Anyone who writes to us | Your name, your email and the message from the contact form, to answer you | Sent to us by email and kept in our mailbox as long as the conversation needs |
| Everyone | 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 |
| Visitors | Anonymous counts: page views, install-line copies, tool calls, per day, to see what is used (legitimate interest) | 400 days; they carry no identifier |
Retention runs every day: what is older than the limit is deleted. Deleting an organisation deletes its rules, people, requests and activity at once.
Where it is stored
Organisation data is stored in the EU (Cloudflare Durable Objects, EU jurisdiction), in one separate store per organisation. Sign-in records and shared reports are kept on Cloudflare's network.
Seeing your own data
If you are in an organisation, sign in at your join page, open your organisation and choose What IT sees about me: your apps, your last events exactly as IT sees them, your requests and IT's answers, your "stuck" notes. Download my data gives you all of it as a file. From the same page you can leave the organisation.
We don't market to employees
If you sign in because your company invited you, we don't add you to our own contact list, we don't mail you about our other products, and we don't send your use to Google Analytics.
Emails
We send the sign-in link and code; invitations; for admins, a welcome mail, requests waiting, people stuck connecting and the Monday digest; for members, the decision on their request; for developers, their report link and its access code; and our reply when you write to us. No newsletter, no marketing.
Cookies and browser storage
This site sets no cookie by itself. Your choice on the consent banner and the 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 dashboard, the join pages and the report pages set one technical cookie each (your session, or the report's access code) so you do not have to sign in again; they are HttpOnly and not used for anything else.
Anonymous counts
When you open a page, copy an address 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 and stores the records above. Organisation data is kept in Durable Objects in Cloudflare's EU jurisdiction | Organisation data in the EU; the rest on its global network; EU Standard Contractual Clauses |
| Resend, Inc. | Sends the sign-in, invitation, request, decision, digest, report-link and contact-form emails | United States; EU Standard Contractual Clauses |
| Google Ireland Ltd. (Google Analytics) | Visit statistics on this site, only if analytics is switched on and you click Allow; never for people signing in because a company invited them | 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. We tell organisations' admins before we add a service that handles their data.
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. For your activity in an organisation, ask your IT team first; you can also write to us through the contact form, and we answer within one month. 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 developer app's findings
Every finding, score and AI Act tier the developer app 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.