Trust

Privacy architecture

A privacy product that uploads your prompts to check them for privacy problems isn't a privacy product. ShieldWays is architected so we couldn't read your content even if we wanted to.

Detection happens on your device

The detection engine — pattern matching, Luhn validation, SSN range checks, secret-prefix matching, entropy analysis — is packaged inside the extension and runs as a content script in your browser tab. Your text is scanned in place, in the page, and never serialized off the device. There is no “send to cloud for analysis” path in the codebase.

Zero-knowledge audit design

When AI Guard acts on something, it emits an audit event so you (and your team, on Team plans) can see that protection is working. That event is content-free — it describes the shape of what happened, never the substance:

{
  "type": "secrets",          // detection category
  "action": "block",          // warn | redact | block
  "domain": "chatgpt.com",    // where it happened
  "ts": "2026-07-02T09:14:07Z"
}

That’s the whole event. From it you can answer “how many secrets did we block on ChatGPT last week?” — but nobody, including us, can answer “which secret was it?”

What is transmitted

Content-free audit events: detection type, action, domain, timestamp.
Your configuration (enabled categories, actions, per-tool rules, custom keywords and regex) — synced between dashboard and extension.
Account data: email, plan tier, session tokens.

What is never transmitted

Prompt text, or any text you type into AI tools.
The matched sensitive values themselves, or redacted originals.
Keystrokes, page content, screenshots, or browsing history.

Redaction is local too. When Redact replaces a credit card number with a placeholder, the substitution happens in the page. The original value is discarded on the spot — it isn’t stored, logged, or sent anywhere.

Where data lives

Supabase — your account, configuration, and content-free audit events are stored in our Supabase backend.
Your browser — the extension keeps a local copy of your configuration and session in Chrome’s extension storage, so protection works offline and never blocks on a network call.

Authentication without token copying

You sign in once, on the ShieldWays dashboard. The extension picks up that session from your own logged-in dashboard page and stores it in extension storage — it only ever moves from your browser to your browser. The extension’s background worker keeps the session fresh by refreshing it against Supabase; you don’t re-enter credentials in the extension.

UI isolation

Everything ShieldWays draws on a page — the pill, the popover — lives inside an isolated shadow DOM root. Host-page CSS and scripts can’t restyle it, spoof it, or read into it.