Access to your system

We read, we never write. The limit is enforced before any request leaves our servers.

Read-only, enforced in code: Every request to Odoo passes an allowlist before it leaves the platform. Only read methods are allowed; any attempt to create, edit or delete is refused inside the platform and never reaches your system.
Guarded by a test that attempts a write and confirms it is refused before the network.
We do not open your documents: When a check needs to know whether a product or lot has a document, we read the attachment’s name, type and date only. Reading attachment content is refused in every check, and so is an "all fields" read on attachments.
Your system key never passes through your browser: The connection key is kept in an isolated secrets vault and used on our servers only while your report is prepared. If the vault cannot be reached, the request stops rather than continuing without it.

Numbers and AI

Software computes, AI explains, an accountant approves.

Every number comes from your data, or reads "not available": Deterministic software computes every figure from your data before the AI sees anything. The AI writes the narrative only, in a template that leaves it no room to add a number of its own.
An integrity gate checks every number in the narrative: if it cannot find its source in the computed data, the report is flagged for review.
Your ledger rows never reach the AI model: Raw transactions are aggregated on the platform’s server; what reaches the model is computed figures, capped in size for each report type. Which model providers may process client data is set by a written policy the code enforces.
A draft until a named accountant approves it: Every report is a watermarked draft until a registered reviewer approves it by name. Reports support decisions; they are not a formal audit opinion, and every report says so.

Record integrity

A chained log that exposes edits and deletions: Everything in your organisation’s account is recorded in a log mathematically linked to the entry before it, one chain per organisation. Any edit or deletion, even straight in the database, shows up and is located.
Tried in production: a row edited with a direct database command was detected.
Approval is bound to the approved version: A report’s approval is bound to a fingerprint of its content. Regenerate the report and the approval drops automatically, so no signature ever covers content its signer did not see.

Isolation and operations

Full isolation between organisations: Ask for another organisation’s data and the answer is "not found", not "forbidden", so you cannot even tell it exists. Isolation is tested automatically with every update.
Least privilege: Platform services run under non-administrative accounts with every extra system privilege removed, verified on the running servers.
Backups we have actually restored: We restored a full copy of the platform databases onto a clean server and confirmed it works, rather than only taking backups.
More than 7,900 automated tests before every update: No update reaches clients until all of them pass. The platform runs 361 checks across 22 reports today; these figures are read straight from the platform code (2026-10-26).

We list it here because a professional buyer will ask, and because trust starts with not overstating.

The platform has not yet had an independent penetration test by an outside firm.
We do not hold a SOC 2 or ISO 27001 certification.
The data processing agreement (DPA) and the sub-processor list are being drafted with legal counsel and will be published here once in force.

Email security@seg-audit.com and please do not disclose it publicly. We reply within 72 business hours.

Last updated: 2026-10-26