How we protect your data
- Data is stored encrypted at rest.
- TLS is enforced for all data in transit.
- Tenant isolation is designed around Supabase Row Level Security policies on every table.
- Orygent does not use your company data to train AI models.
Who can see what
- Knowledge access is restricted by role, department, authority level, confidentiality classification, and Visibility Rules.
- Access is designed so that administrators see flows only within their authorisation scope.
- A five-layer confidentiality matrix governs field-level visibility across all operations.
How operations requiring approval are paused
- Financial thresholds are defined in configuration.
- Critical operations are designed to pause and route to the appropriate person for Human Approval.
- Operations awaiting approval are visible and traceable in the Restricted Action queue.
How the Audit Trail works
- All significant decisions and policy enforcements are written to an immutable audit log.
- The log operates on an append-only model; historical records cannot be modified.
- A DELETE=false RLS policy prevents audit records from being deleted.
Multi-model orchestration
- Model selection is managed within the platform according to task, quality, security, cost, and governance requirements.
- All model calls go through one gateway, so a provider can be changed in configuration.
- The model gateway is configured only with enterprise model providers that offer contractual data-protection terms.
Platform vs. company administrator
- Platform management and tenant management are strictly separated.
- Access is designed so that Orygent platform staff cannot read your company's confidential content, documents, meeting minutes, reports, attachments, or financial and personal data.
- Support access is limited to the operational, log, and technical data needed to run the service, and every support session is logged in the audit trail.
Data deletion and portability
- Deletion requests are processed under GDPR Article 17.
- Data portability is provided under GDPR Article 20.
- Requests can be submitted to privacy@orygent.com.
Trust Control Layer
- A dedicated policy engine sits between every AI action and execution.
- Five rule layers, role, department, authority, confidentiality, and channel, must all clear before any operation proceeds.
- Any rule violation automatically triggers a RESTRICTED state and routes to the Human Approval queue.
- The Trust Control Layer is designed so that no user, including platform administrators, can skip it.