Security is a design constraint at QueryOn, not a feature tier. This page describes, plainly, how the platform protects your data today.

Data isolation

QueryOn is multi-tenant. Every tenant's data is scoped by tenant identity at the database layer — row-level security policies plus explicit tenant filters in every query path, so one customer's brands, questions and results are never visible to another.

Encryption

All traffic is encrypted in transit with TLS; plain HTTP redirects to HTTPS everywhere.
Third-party credentials you store with us (for example publishing and provider keys) are encrypted at rest; they are decrypted only at the moment of use and never returned to the browser.
Authentication uses signed, expiring tokens.

Your response archive

Raw engine responses are archived immutably with engine, model version and timestamp. The archive exists so you can audit what an assistant said about your brand at a point in time — we treat it as evidence, and it is scoped to your tenant like everything else.

Operational practices

Infrastructure runs on hardened cloud servers with access restricted to named operators over SSH keys; no shared passwords.
Secrets are configured per environment and never committed to source control.
Payments, when enabled on your plan, are processed by Stripe; card details never touch QueryOn's servers.
Transactional email is delivered by Resend.

What we do not claim

We do not currently hold SOC 2 or ISO 27001 certification, and we will not imply otherwise. If your procurement process requires specific attestations, write to us and we will walk you through our controls directly.

Reporting a vulnerability

If you believe you have found a security issue, email hello@kavio.tech with the details. We read every report, we will respond, and we ask for reasonable time to fix before public disclosure. Good-faith research conducted without harming other tenants' data will never be met with legal threats.