What Athena can access.
Athena receives only the access the workflow needs. The deployment documents every model, API, tool, database, data type, service identity and administrative permission involved.
// Trust, security and independent verification
Where Athena is connected to sensitive data, action or decision paths, the review should identify what it can access, where it runs, what it stores, which connections it makes, who controls the keys, how it fails, how evidence is verified and how it is removed. Coverage is deployment-specific.
The Trust Centre brings those answers together. Public legal and privacy documents remain openly available. Detailed architecture, security and assurance material can be supplied through the appropriate customer review process.
// Trust Centre
Athena receives only the access the workflow needs. The deployment documents every model, API, tool, database, data type, service identity and administrative permission involved.
You choose: an Aelethion-managed EU region, your own cloud account, on-premise or air-gapped. The data-flow documentation states what stays inside your boundary.
Customer-controlled and on-premise deployments keep all business data, logs, keys and evidence inside your environment. Hosted deployments document what is stored, where, for how long, who can access it and how it is deleted.
You hold the signing material and retain your evidence independently of Aelethion. Key generation, custody, rotation and recovery follow your deployment.
In a customer-controlled deployment, network paths depend on the interfaces, updates, licensing and support arrangements agreed for that configuration. An air-gapped configuration with local model weights is designed to operate without external connections. Hosted deployments document their required connections before production.
Evidence is verified offline with the public key and the free verifier. The reviewer needs no Aelethion account and no connection to our servers.
// Trust Centre
// Trust Centre
// Trust Centre
In an Aelethion-managed EU region.
Region, storage, support access, keys, retention and external connections are documented for the service.
Inside the customer's cloud account or dedicated environment.
The customer controls the configured infrastructure, network policy, data stores, keys and evidence stores.
Inside the customer's data centre or private environment.
Customer-controlled operation with only the approved model, database, update and support paths enabled.
Inside a disconnected customer environment.
No external connection during normal operation; local dependencies and offline installation, update and licensing procedures apply.
// Trust Centre
// Trust Centre
// Trust Centre
// Trust Centre
Explains what personal data Aelethion collects, why it is processed, how it is protected and retained, the lawful bases relied upon and the rights available to data subjects.
Sets out the contractual terms governing access to and use of Athena and related services, including customer responsibilities, acceptable use, intellectual property, availability, liability and termination.
Governs Aelethion's processing of personal data on behalf of business customers, including documented instructions, confidentiality, security measures, sub-processors, assistance, breach notification, deletion and audit rights.
Identifies third parties used to provide relevant infrastructure or operational services, the purpose for which each is used and the location or transfer mechanism relevant to processing.
Explains the cookies and similar technologies used on the public website, their purpose and the controls available to the visitor.
Explains how to report a suspected security issue, the information to include and how Aelethion coordinates responsible disclosure.
A one-page checklist for digital labour platforms preparing for the Platform Work Directive: which decisions are in scope, whether a human takes them, the reasons and review owed to the worker, and what you can prove.
The following material is supplied as relevant to the selected deployment and the stage of the customer review:
Summarises architecture, controls, responsibilities and operating model.
Customer review
Shows components, trust boundaries, data types, storage, connections and evidence paths.
Under NDA where appropriate
Identifies service identities, permissions, ports, endpoints, storage and administrative access.
Customer review
Explains installation, configuration, supported control points, failure behaviour and removal.
Customer review
Explains signed delivery, approval, rollback and restricted-environment operation.
Customer review
Explains the sealed record, the verification sequence, the keys and the checks.
Public or customer review, depending on the item
Allows the customer to run verification and tamper-detection tests before production use.
Evaluation review
Shows how the evidence supports each named obligation.
Customer review
Describes escalation, recovery, responsibilities, data handling and decommissioning.
Customer review
Some security material contains sensitive architecture or test details and may require an NDA or an active customer review. Public documents remain accessible without a sales process.
Choose a valuable workflow that needs stronger control or a provable human decision. We will agree the relevant Athena modules, integration boundary, evidence limits, acceptance tests, timetable and commercial scope in writing.