Security
Last updated 5 November 2026 · Operated by OPNYX SOLUTIONS · reachout@opnyx.com
Governeto sits in the path of your AI agents, so it is held to the standard of a security control. This page says what the service does today. It lists only measures that are in the product.
At a glance
| Question | Answer today |
|---|
| Where is the data? | The API and its database run on Oracle Cloud Infrastructure in the Hyderabad region, India. The website and the console are served by here.now. |
| Encrypted in transit? | Yes. HTTPS everywhere, plain HTTP redirected, and browsers told to use HTTPS only (HSTS, one year) on the website and the API. |
| Secrets at rest? | AI engine keys sealed with AES-256-GCM. Passwords as salted scrypt hashes. Agent keys and sessions only as hashes. |
| Kept apart from other customers? | Yes. Every record belongs to one organisation, and a request for another organisation's record is answered as if it did not exist. |
| Used to train AI? | No. Your record is never sold, never used to train AI models, and the site and console carry no advertising or analytics trackers. |
| Where are agents checked? | On the developer's own machine first. Rules that read words block there, before the model sees the text. |
| Can we delete everything? | Yes. An administrator erases the record with RESET DATA, and we close an account on request. |
| Which frameworks? | 86 built-in rules mapped to 10 frameworks, SOC 2, HIPAA, GDPR, PCI DSS and the EU AI Act among them, with evidence you can hand to an auditor. |
1. Each organisation is walled off
- Every record belongs to one organisation, and every read of it is scoped to that organisation.
- A request for another organisation's record is answered as if the record did not exist.
- Each person, device and agent connection is tied to its organisation, and a device's id is computed with the organisation's id, so the same machine is a different device in another organisation.
2. Sign-in
| Control | What Governeto does |
|---|
| Ways in | Google, Microsoft, an email address proved by a link sent to it, or a password. |
| Microsoft | A Microsoft account opens only the Governeto account it was linked to. An address alone never opens an account. |
| Passwords | Kept only as a scrypt hash with a salt per person. |
| Wrong passwords | Counted per email and address, and refused after 10 tries in 15 minutes. |
| Sessions | Kept only as a hash. A console session ends after 12 hours. |
| In the browser | The sign-in token. While somebody signs in with Google, Microsoft or an email, Firebase holds its record in that tab until the sign-in ends or the tab closes, and the installed app keeps a copy of the page itself. Records, settings and the background picture are on the server, under the organisation. |
| Roles | Administrator, member and viewer. An organisation always keeps one active administrator. |
3. Keys
| Control | What Governeto does |
|---|
| Agent keys | Kept only as a hash, and revoked with one press. |
| AI engine keys | Sealed with AES-256-GCM in the database, never held in the browser. Only the last four characters are shown. |
| Copied keys | A key bound to a device is refused on any other machine. |
| Credentials in commands | Removed from a command before it is stored. |
4. Devices and agents
- One agent on one device for one person is one agent connection, and every connection has a switch. A connection switched off is refused at every door, and nothing is recorded for it.
- The machine sends a one-way hash of its id, never the id itself.
- The connect file and hook run on the customer's machine as plain, readable scripts.
- What leaves a machine is listed in the console before anything is connected, and in our Privacy Policy.
5. In transit
- Every address is served over HTTPS with a valid certificate, and plain HTTP is redirected to HTTPS.
- Browsers are told to use HTTPS only, for a year, on the website and the API (HSTS).
- An address the service is asked to reach is checked first, and private and internal addresses are refused.
6. Accountability
- Changes to rules, people, connections and settings are written to an audit trail.
- Evidence can be exported as PDF, JSON or CSV, with every time in UTC and in the reader's zone.
- Rules are mapped to the frameworks they support, such as the OWASP Top 10 for LLM applications, the EU AI Act, NIST AI RMF, ISO/IEC 42001, GDPR, PCI DSS, SOC 2 and HIPAA. A mapping shows which rule supports which requirement. It is not a certificate.
7. What leaves a developer's machine
- Before each tool call: which agent, the machine's name and the hash of its device, the project folder's name, the session id, the tool's name, and one line about the call: the command, the path or the address.
- Before each prompt: its words only when a rule reads words. Otherwise only that there was one.
- When a rule reads words: up to 8,000 characters of the text being checked, which can be a prompt, a reply, what a tool is given or what it returned. Text that is only judged is not stored, and an administrator can switch those rules off.
- At the end of a turn: the model and the token counts.
- Never: the key file, the machine's raw id, or anything while the agent is idle.
8. If Governeto cannot be reached
- The hook on the machine waits up to 25 seconds for a verdict.
- An administrator chooses what happens next, on the Rules page. Fail closed: a call that could not be checked is refused. Otherwise it goes ahead, and the hook says on the agent's screen that it was not checked.
- Rules that read words are kept on the machine and block there, so a pasted secret or personal number is stopped even while the server is slow.
9. Where data lives and who processes it
| Provider | What for |
|---|
| Oracle Cloud Infrastructure, Hyderabad | Runs the API and its database. |
| here.now | Serves the website and the console, and carries the console's requests to the API. |
| Google Firebase, Microsoft | Sign-in with Google, Microsoft or an email address. |
| Paddle | Merchant of Record: checkout, invoices, tax and refunds. |
| The AI engine your organisation picks | Judges a text when a rule needs it, on your organisation's own key. |
| Slack | Announces a held call, only when an administrator sets a webhook. |
The full list, with the data each one sees, is in section 4 of our Privacy Policy.
10. Compliance: the evidence your auditors ask for
- 86 built-in rules mapped to 10 frameworks: the OWASP Top 10 for LLM applications, OWASP Agentic Security, the EU AI Act, NIST AI RMF, ISO/IEC 42001, GDPR, PCI DSS, SOC 2, HIPAA and GLBA.
- Every call's verdict, by person, device and agent, exported as PDF, CSV or JSON, with every time in UTC and in the reader's zone.
- Risky commands held for a named person to approve, and the approval kept on the record.
- A mapping shows which rule supports which requirement of your own audit. Governeto itself is not SOC 2 or ISO/IEC 27001 certified today. For a security questionnaire, write to reachout@opnyx.com.
11. How each release is checked
- A release that touches sign-in, keys, payments or the walls between organisations gets a focused security review before it ships.
- Each finding is reproduced with a test that fails first, then fixed and deployed. Every high-severity finding so far was fixed before its release went out.
- Security headers on the live site and API are checked after each release: HSTS, no-sniff and no referrer on the site; HSTS, no-sniff and a refusal to be framed on the API.
12. Report a vulnerability
If you believe you have found a security problem, please tell us through the contact form or at reachout@opnyx.com before you make it public. Please use a test organisation of your own, and do not read or change data that is not yours. Our contact details are also published at /.well-known/security.txt.