Your knowledge stays yours
Every Zeus client works in its own isolated environment, hosted in Canada. On every request, the database, your role and the content's own labels decide what you can see. Every answer can be traced to its sources.
Book a DemoWhere your data lives
Your organization has its own tenant: a logically isolated part of the database. Your memories, documents and records exist only inside it, and your own administrator decides who has access.
Stored in Canada
Hosted on Microsoft Azure in the Canada Central region. Backups stay in Canada too.
Encrypted at rest and in transit
AES-256 encryption at rest. TLS 1.2 or higher in transit. The database refuses unencrypted connections.
Your own tenant
No other client can query, view or reach data inside your tenant. ALDC staff don't access client content in the normal course of business.
Closed network
The database is not shared with public-facing services or third-party apps. It sits behind a firewall, and every connection must authenticate.
Point-in-time recovery
Automated backups with 35-day point-in-time restore.
Production stays in production
Client data is never copied into staging, test or analytics environments. Automated tests run on synthetic data.
Three checks on every request
The three checks run in order, and none can override another. Before any result reaches you, a final authorization pass checks it again. Anything that fails is removed and logged.
1. Tenant isolation
- Row-level security on every tenant table, enforced by PostgreSQL itself
- Your tenant is bound to the database connection before any query runs
- Keyword, semantic and entity search are filtered to your tenant before ranking
- Fail-closed: a request without a valid tenant gets zero results
2. Role-based access
- Every client user has a personal, scoped key, so every action traces to a named person
- Four roles (platform admin, tenant admin, member, viewer) govern read, write, delete and search
- Admin rights stop at one tenant and never reach colleagues' personal workspaces
3. Content classification
- Records carry sensitivity and visibility labels that further limit who can see them
- Labels are set when content comes in and can't be changed afterwards
Guarding what goes in and what comes out
Personal information
Personal information is detected, and masked in anything shared.
No stray credentials
Content that looks like an API key, password or token is rejected.
Safe outbound requests
Any web address Zeus is asked to fetch is checked against private and internal networks first.
No training on your data
Zeus retrieves your knowledge at answer time. Your data is never used to train an AI model.
Cited answers
Every answer shows the documents, meetings or data it drew from.
Audit trails
Out-of-scope access attempts, settings changes and the sources behind answers are all recorded.
Security in every change
Reviewed, automated releases
Every production change goes through an automated pipeline with mandatory review. Nothing is deployed by hand.
Checked before deployment
Every change is checked by static analysis, secret scanning and an automated security review.
Isolation tested every time
Tests for tenant isolation and authorization run against a real database on every change.
Hardened hosting
Applications run in containers on Azure, as non-root users and with only the files they need.
Managed secrets
Infrastructure secrets live in Azure Key Vault. Stored connector credentials are encrypted.
Connector audit trail
Every connector sync is recorded: what was synced, when and for whom. Records are kept for a set period.
Bring your security team to the demo
Book a 30-minute demo. We'll walk through isolation, access control and audit trails on a live environment.
Book Your Demo