Security and data

Where the data lives,what leaves, what we do not have.

For whoever IT and legal ask. On one page: what stays with you, what reaches the AI model, what Burebi can do in the ERP, who can change a rule and what we do not have yet.

Security sheet (PDF, Romanian)

The diagram, in one place

What stays, what goes

Where	What
Stays on your machine	The database, the knowledge graph, the company's definitions, the log and the secrets. Different companies run in separate instances: each has its own data, graph, secrets and assistant memory.
Reaches the AI model	The question, the necessary context and the result already computed by code, so it can be worded. The company's database and definitions are not copied to the model. What Anthropic does with what it receives is set by its own terms, which differ for a subscription and for the API.
On our servers	No customer data, in today's production setup (17 Oct 2026). The gateway to our server is switched off; answers pass only through the AI model.

What Burebi can do in the ERP

It reads the data, on the company's definitions.
In the ERP it only adds, with confirmation on every run and a dedicated user with explicit rights.
Sending anything outside the company and writing to the ERP stay permanently at the “Approval” level of autonomy: Burebi prepares, the person approves.

Who can change what

A company rule changes through a single door: hypothesis, demonstration on today's data, a check by code and the click of a named person. Irreversibility ceilings change only through code.
Every command that changes data leaves a row in the audit log, chained by hash. Every action is signed with the name of the person working at the station; a role (“System”) is not accepted as a name.
Rules and knowledge are withdrawn, not deleted: with a version, a reason and who did it; restoring returns to the same hash. Personal data can be deleted, leaving a trace without content.

What we do not have, said from the start

Certifications. The product holds no certification: neither “ISO 27001”, nor “ISO 42001”, nor “SOC 2”. We do not invoke them.

Installing without us. Installing on a new machine is not ready yet. In the pilot, we do it together with your IT.

Defined continuity. Who provides your support and updates if we stop is not yet defined. It is set in the contract.

A data engine other than Oracle. Today the method is specific to Oracle databases (3 of 3 pillars, 7 Oct 2026).

For every figure on this page, the date and the basis are in Evidence.

Questions for IT or legal?

Send us their list. We answer in writing, with the date, and where we do not know yet we say “we do not know yet”.

Write to us