Security

Most tools ask you to trust them. promptShield is built so you don't have to: the privacy guarantee is something you can verify with your own eyes, offline, in under a minute.

Last reviewed: November 11, 2026

The core guarantee

Your documents are processed entirely on your own machine. Detection, redaction, encoding, and export all run on a local engine bound to 127.0.0.1 (loopback). No document content, detected value, or redacted output is ever transmitted to our servers or to us. Your documents never leave your machine.

Don't trust us. Verify it.

Because everything runs locally, our central privacy claim is demonstrable in front of a client, an auditor, or a CISO. No NDA, no architecture review, no leap of faith.

  1. Disconnect from the network. Open a document and run detection, redaction, encoding, and export. All four still work with no connection.
  2. Open a network monitor (Windows Resource Monitor, Wireshark, Little Snitch). Process a document end to end and filter by the app. Everything that carries the document stays on 127.0.0.1 loopback. Anything else that goes out (license and update checks, add-on downloads, in-app notices, anonymous usage statistics, crash reports) contains nothing from the document.
  3. Run ExifTool on the exported file. The metadata is stripped: no author, no software trail, no hidden history.

What our servers actually see

We run a licensing server, and we are deliberate about what reaches it. For account and billing it sees exactly what it needs and nothing more; for your documents it sees nothing at all.

  • Account data: your email address, and (for paid plans) billing details processed by Stripe. We never store card numbers.
  • License data: a SHA-256 machine fingerprint used to enforce device limits, plus subscription state. No document activity.
  • Anonymous usage counts: aggregate numbers (documents processed, file types, app version), switchable off in the desktop app under Settings → License → Privacy & Legal, never sent at all on air-gapped installs.
  • Document content: never. No file, no detected value, no redacted output, ever reaches our infrastructure.

How it's engineered

  • Local-only processing: the detection and redaction engine runs as a sidecar on loopback, reachable only by the desktop app on the same machine.
  • TLS everywhere: all licensing and account traffic is encrypted in transit.
  • Ed25519-signed licenses: license blobs are cryptographically signed and verified offline, so the app keeps working without a live server.
  • Hashed credentials: passwords are bcrypt-hashed; authentication runs through Firebase Auth.
  • Signed binaries: the Windows app and its components are Authenticode-signed, and updates are SHA-256 + signature verified before they install.
  • Scrubbed crash reports: error reports have personal data removed before transmission and never include document content.

Who else holds your data

Six companies process account and support data on our behalf. They are the sub-processors named in our Privacy Policy and authorized in the Data Processing Agreement, and each one receives only what its own job requires.

Google Cloud
Hosting and database
Firebase Authentication
Sign-in and passwords
Stripe
Payments and invoices
Resend
Account email
Anthropic
Support chat and replies
Sentry
Crash reports

Your documents reach none of them. Detection and redaction run on your own machine, so there is nothing to upload and nothing for a processor to keep.

The binding list is the one in the Data Processing Agreement.

Reporting a vulnerability

We welcome scrutiny from security researchers. If you believe you've found a vulnerability, email us and we'll work with you to confirm and address it. Please give us a reasonable window to remediate before any public disclosure. Reach us at security@promptshield.ca.

Related

Try the desktop app

"Anonymized" and "pseudonymized" are different things under the GDPR, and only one of them takes a document out of scope. Our guide walks through which is which, and what a regulator actually looks for.

Read the guide

Three quarters of small law firms now use AI and 55% have no policy governing it. Our guide covers what a ten-person practice can actually enforce, and how to end up with a record rather than an assertion.

Read the guide