Legal · effective 16 November 2026
Security
How Intelysis protects accounts, provider keys, and request data, and how to report a vulnerability.
Provider keys
Bring-your-own-provider keys are encrypted at rest with AES-256-GCM and are never returned to the browser after they are saved. The console only shows whether a key is configured. A provider key is decrypted only in the request path that needs it.
API keys
Intelysis API keys are shown once at creation. Only a SHA-256 hash is stored. Revoke a key immediately if it is exposed; revocation takes effect for new requests.
Sessions and accounts
Console sessions use an HttpOnly, Secure, SameSite=Lax cookie. Passwords are stored as salted hashes. Login attempts are rate-limited per address and per account. We recommend a unique password and a password manager.
Tenant isolation
Console data is resolved from the session's organisation, not from a client-supplied organisation id. Internal server-to-server routes require a separate dashboard token and are not exposed in the browser bundle.
Transport and infrastructure
The public site and API are served over HTTPS with HSTS, frame restrictions, content-type protection, and a content-security policy. Hosting is provided by OVHcloud in the EU. We keep dependencies patched and review access to production systems.
Request data
We record the metadata needed to produce usage, savings, and request reports. We do not use customer request content to train our own models. Provider keys and request content are not sold or shared for advertising.
Reporting a vulnerability
If you believe you have found a security issue, email [email protected] with reproduction steps and the affected URL. Please do not access other customers' data, disrupt the service, or publish details before we have had a reasonable chance to respond. We will acknowledge a good-faith report and work with you on disclosure.
This page is product policy, not a substitute for advice from a qualified lawyer in your jurisdiction.