Draft
Security and trust
ELOS holds some of the most sensitive knowledge an engineering organization has. This page describes how we protect it, in plain terms, and what is yours to control.
On this page
Our principles
- Your data serves only you. It is used to run your workspace and nothing else.
- Least privilege, everywhere. People, service accounts and AI see only what their role and scope allow.
- Evidence by default. Every change is recorded in a log you can verify.
- We state what is true today. Anything we don't yet provide is not claimed here.
Workspace isolation
Each customer gets a private workspace. Isolation is enforced by the database itself on every table that holds customer data, so a request made in one workspace cannot read or change another workspace's rows, even if application code has a bug. Automated cross-workspace tests cover this isolation.
Access control
- People sign in through OpenID Connect; ELOS keeps no passwords for them.
- Role-based permissions (administrator, manager, engineer, auditor and custom roles) are combined with attribute-based read scope, so a role can be limited to particular teams, service tiers or services.
- Service accounts use role-scoped keys that can be rotated, disabled or deleted.
- Privileged access is time-bound and expires on its own. Access requests pass multi-level approval with separation of duties.
Audit
Changes are written to an append-only audit log. Each entry is chained to the one before it with a cryptographic hash, so any alteration or deletion is detectable. Administrators and auditors can verify the chain from the product.
Encryption and secrets
- Personal data is encrypted with per-person keys, which lets ELOS erase a person's data by destroying their key.
- Ask ELOS conversations and personal memory are encrypted before they are stored.
- Credentials for the tools you connect are kept in a dedicated secrets store, never in the application database.
- Traffic is encrypted in transit and stored data is encrypted at rest.
AI and your data
Ask ELOS answers from your own knowledge, reads only what the person asking may read, and never takes an action without a person confirming it. ELOS does not train AI models on your data. The full account, including how AI model providers are used, is on AI and your data.
Your data controls
- Retention periods you set, with legal hold for records that must be kept.
- Erasure of a person's data on request.
- Full export of your workspace data.
- Administrators choose which data domains AI may read, and can turn them off.
Our own access
Our operations console manages workspaces (plan, status, suspension) and has no function for reading your workspace content. Access to production infrastructure is limited to the people who operate the service, and is logged. We access your content only to provide support you request, or where the law requires it.
Compliance
ELOS is designed to help you meet your obligations under the EU and UK General Data Protection Regulation, India's Digital Personal Data Protection Act 2023, and the California Consumer Privacy Act as amended by the CPRA: data minimisation, purpose limitation, access and erasure rights, retention control and an auditable record of processing. ELOS does not currently hold third-party certifications. We will list them here once they are independently assessed. We sign a data processing agreement with customers who need one.
Report a vulnerability
If you believe you have found a security issue, please tell us. See our security disclosure policy for scope, safe harbour and how to reach us.
Related: AI and your data · Privacy policy · Sub-processors