Isolated services
Technical integrations remain separate from the end user's interface and account.
Trust center
Security designed as a system control, not a slogan.
ANTARES minimizes data exposure and keeps inference on configured cloud services. This page describes the current technical baseline; it does not represent an acquired certification.
Encryption and secure transport
TLS in transit, managed database encryption at rest and secrets stored in a cloud vault.
Workspace isolation
Permissions and queries are designed with tenant-aware scoping and least privilege.
Reduced retention
History can be disabled; retention periods follow data minimization, with user-requested deletion.
Essential technical audit
Security, usage and administrative events are logged without recording secrets or unnecessary content.
Controls before provider requests
Rate limits, budgets, validation and policies are applied before forwarding requests.
Data flow
From browser to model, with explicit boundaries.
Input. The authenticated request passes validation, rate limits and balance checks.
Routing. The router selects only adapters and models declared operational.
Output. The response returns with cost and latency metadata; retention follows the account policy.
Limits to understand
Risks are not concealed.
- Outputs are probabilistic and may be inaccurate: important decisions require human verification.
- Forwarded data may be processed by different subprocessors depending on the selected model.
- The provider serving each request, its role and where it processes data are published in the sub-processor list; retention periods are set out in the Privacy Notice.
- ANTARES may be used from the age of 14; under 18 a parent or legal guardian must authorise the account. The service is not authorised for prohibited or high-risk uses without a dedicated compliance process.