Security

What we do with your data, exactly

A security company should be specific about its own. This is how the hosted platform works today, and what it does not have.

Your model API key

Encrypted before storage

Your model key is encrypted with AES-256-GCM and bound to your account, so a ciphertext copied to another account does not decrypt.

Never sent back

After you save it, the browser only ever receives the last four characters. You can replace or remove it at any time.

Used only for your runs

The key is decrypted in memory for your own scans and enforcement calls. We do not make model calls on a shared key.

The platform

  • Sign-in is handled by Firebase Authentication, with Google or email and password.
  • The database is closed to browsers. Scans, layers and keys are reachable only through the backend, which checks that they belong to you.
  • A proxy layer URL works for anyone who has it and spends your model quota. Treat it like a secret.
  • Target URLs are resolved and checked before any outbound request, and loopback, private and link-local addresses are rejected.
  • Per-account rate limits and a monthly test quota apply.
  • The command-line tools are static and run on your machine. They need no account and no key.

What we do not have

So you can decide with accurate information.

  • No SOC 2 or ISO 27001 report.
  • No single sign-on, role-based access or audit-log export.
  • No uptime commitment. The hosted platform is free and provided as is.
  • Scan results include the prompts sent to your endpoint and its responses. Do not point scans at systems that return data you cannot store with a third party.