Skip to main content
RAVIONIX Beta, home

Security & trust

Privacy claims you can check.

Some of this you can check yourself: watch the network traffic and you'll see a password never leaves your browser, only its hash. The rest describes how our servers are built. We plan to publish the extension source so more of it can be checked.

RAVIONIX is not currently SOC 2 or ISO 27001 certified, and no completed third-party attestation is implied. No controls have been independently assessed and no penetration test has been done yet. The Trust Center documents the current controls and certification roadmap.

  • Raw content is processed, not stored

    Raw URLs and messages are processed transiently to produce a verdict and are not stored in the RAVIONIX database. Analysis involves an AI provider. We keep a one-way hash, the verdict and the AI's reasoning, plus required operational metadata. If a check is rated a scam with 80%+ confidence, we also keep the website's domain name, never linked to you.

  • Passwords never leave the device

    Your browser hashes the password; we receive only the hash and send Have I Been Pwned just its first 5 characters. Only that 5-character prefix is kept.

  • No cloud keys held (coming soon)

    When AWS posture launches, scanning will use a customer-owned read-only role with a per-tenant ExternalId, assumed for fifteen minutes. No access keys will be stored.

  • Locked audit log

    A database trigger blocks edits and deletes. Entries are kept for up to two years and removed only by a scheduled retention job.

  • Export and delete your data

    Account holders can export or delete their data from settings, without contacting support. The same tools serve California privacy requests.

  • PCI DSS SAQ A scope

    When paid plans launch, payments will be handled through a hosted provider flow designed to keep RAVIONIX eligible for PCI DSS SAQ A scope. Eligibility and the applicable annual assessment remain subject to verification.

Privacy built into the architecture

Architectural properties, described as they are today. We plan to publish the extension source.

  • Raw content is not storedProcessed to produce a verdict, never stored by us (our AI provider may keep it up to 30 days for safety review). We keep a hash, the verdict and the AI's reason — plus the site name of links rated a scam with 80%+ confidence, never linked to you
  • Passwords never leave the deviceHashed in the browser, checked by k-anonymity
  • No AWS keys held (coming soon)When AWS posture launches: a customer-owned read-only role, assumed for 15 minutes
  • Every agent run recordedSchema-validated output; cached and non-reasoning checks skip the model entirely
  • Export and delete your dataAccount holders can do it from settings, without contacting support
  • WCAG 2.2 AA targetWe work toward WCAG 2.2 AA and fix accessibility issues as we find them. Not independently audited yet.

These are current implementation properties. Where a control is planned rather than in place, the module and roadmap sections say so explicitly.