How does Orygent protect my data?
Each company’s data is separated in the database by its own access rules, and the browser never connects to the database directly. Money, contracts and access changes always pass a person.
Updated:
Where is the data boundary?
Every request runs on the server in the context of the company and the person.
- Row-level security is enforced on every table; without context, the answer is empty.
- The browser talks only to the API; no service key is used in the app.
- Secrets are shown once; only their digests are stored.
Who approves?
Critical steps always go to a person, and these rules cannot be turned off.
- Payments, contracts, commitments in the company name, access changes and requests to another SET platform need approval.
- Approvals that involve money and authority changes ask for a second verification.
- An approval becomes invalid if the content changes or it expires.
Why can the record not be edited?
Each record line carries a digest of the one before; the chain is verified on export.
- The record is append-only; updates and deletes are blocked in the database.
- Actions taken by the system are labelled as such.
- Exports come as CSV, with a report on whether the chain is intact.
What does Orygent not do?
- It does not make financial or legal decisions.
- It does not approve on behalf of a person.
- It does not move money.
- It does not treat the text of an e-mail or document as instructions.
What has been measured?
This page describes how the product is built. Independent audits, certifications or performance results are not written here until they are published.