GVNR · Install · Configure · The record · Teams (soon) · Add to your AI · How it compares · Stop an agent overspending · Block dangerous commands · Watch a plan · FAQ

GVNR trust

Trust and security

How GVNR keeps your team's data, who else processes it, and how to reach us about security. What each part collects is in the privacy notice.

What GVNR is built to do

• Decide on your computer. The plugin's rules, spend limits and loop check run on the machine the agent runs on. Nothing leaves it until you sign in, and losing the network never allows more: the local rule decides alone.
• Send decisions, not content. Receipts carry the verdict, rule, tool, model, tokens, spend and project, never command text, file contents or prompts. Your sign-in token is kept in a file only you can read.
• In chat, show teammates the work, not the person. The GVNR connector returns task titles and who holds what. It never returns anyone's cost, spend, prompts, idle time or email address. The Enforcer web app shows people on a plan more: how long each attempt ran, when a hold runs out, progress notes and evidence (privacy notice).
• Keep AI judgment optional. Jev by TypeSafe is off unless a workspace admin turns it on, and the spend guard never uses it.

The record you can check

Every decision the plugin makes, allows included, becomes a receipt. Each receipt carries a SHA-256 hash of the previous receipt's hash followed by its own entry, so each install's receipts form a chain. Edit or delete one line and the chain breaks where you did.

• /enforcer-governor:verify walks your local file and names the first line that does not add up.
• Signed in, your workspace recomputes each install's chain on its own, so a line edited or missing before it arrived shows.
• On the server, the database accepts new receipt lines only and refuses edits and deletes.
• If the plugin cannot read its own state, it still records a refusal, without a hash, and verify counts that line as unverifiable rather than as a break.

The chain shows tampering. It does not stop someone with access to your computer deleting the local file. Receipts shows a real one.

How the connector protects a team

• Each person signs in as themselves. Every teammate's AI acts with that person's own scoped token, which they approve and can revoke. The connector never runs signed-in people on a shared account.
• Only the permissions it needs. Reading the plan needs read access. Starting a plan, taking and finishing tasks, approving, assigning, inviting and joining, and setting your name each need their own permission, listed on the consent screen.
• Plans, and your own name. It cannot reach spend records or other account records, and none of its tools deletes anything.
• A plan link shows the plan and does nothing else. A read-only plan link shows titles, states and first names, never emails, costs or prompts. Nobody can join or change the plan from it, it expires, an editor can turn it off, and Enforcer keeps only a hash of it.
• Teammate text is data. Titles, summaries, criteria and names are cut to one printable line, stripped of invisible characters that could hide instructions, and labelled for the AI as information from teammates, not instructions to follow.

Who processes data for us

Not ours to list: the AI app each person connects GVNR to. It receives what that person's AI reads through the connector, under that person's own agreement with its provider.

Report a security issue

Email security@gvnr.io with what you found, how to reproduce it and what it affects. Please give us a reasonable chance to fix it before you tell anyone else, and do not access other people's data or disrupt the service while testing. We will not pursue good-faith research that follows these rules. Our security.txt has the same contact.

Contact

• Help with GVNR: support@gvnr.io
• Privacy questions and requests: privacy@gvnr.io
• Security reports: security@gvnr.io

GVNR is made by Instruxi Limited (UK company number 13781404) and built on Enforcer.

An Instruxi solution. Verified against Enforcer Governor v2.8.3 on 30 September 2026. Runs in Claude Code today; other harnesses are coming. Nothing leaves your machine until you sign in to an Enforcer workspace. Next: Privacy, The record, Terms. Enforcer, the identity and authorization service, is at enforcer.instruxi.dev. Privacy · Terms · Trust · Cookie settings