skip to content

~/your-data

What we keep, what we never touch.

Two columns, no adjectives. If a field is not in the left column, we do not store it.

the ledger

Stored. Never stored.

stored

email
// to sign you in and reach you
name
// shown in the console
password hash
// scrypt, salted. never the password
plan
// free, dev, or team, plus billing period
masked findings
// first 4 + last 4 of each secret
fingerprints
// keyed HMAC, used for re-sweep delta
file paths and line numbers
// where each finding sits
redacted excerpts
// 5 lines around a finding, tokens masked
run history
// timestamps, counts, risk score per run

never stored

source code
// processed in memory, dropped at request end
archives
// .zip and .tar.gz are never written to disk
full secrets
// masked in the scanner, before anything else
repo contents
// fetched public repos are not cached
oauth repo tokens
// sign-in asks for identity scopes only
card numbers
// handled by Stripe on its own page
ad or tracking profiles
// no ad cookies, no third-party analytics

// one stored finding, in full:

{
  "detector": "stripe_live_key",
  "masked": "sk_l••••••••YhJ9",
  "fingerprint": "9c41e0b7a2d35f6e8810",
  "file": "scripts/seed.ts",
  "line": 22,
  "verdict": "live risk",
  "severity": "critical"
}

lifecycle

Retention, export, purge.

retention

Sweeps and their masked findings stay until you purge them, because re-sweep delta needs the fingerprints. Account data stays while the account exists. Support email is kept for 24 months. Server logs carry no request bodies and roll off within 30 days.

export

export.json

Settings has one export button. It downloads a single JSON file with your profile and every sweep exactly as stored, which means masked. Available on every plan.

training

Never used to train models.

Not ours, not a provider's. Model calls go over API terms that exclude training on inputs, and those inputs are masked context to begin with.

purge on delete

Delete means delete.

// no soft delete. no 30 day bin. no restore.

  • >Sweep purge removes that sweep's masked findings, fingerprints, excerpts, and run history in one request.
  • >Account purge (Settings, type PURGE) removes your profile, every sweep, and your email index entry, then signs you out.
  • >Both are real deletes against the primary store. We keep no separate backups beyond the durability our storage provider maintains internally, and we have no way to restore a purged record.
  • >If you have a paid plan, cancel it first or write to support@leaksweep.net. Stripe keeps its own payment records as the law requires.

subprocessors

Who else touches it.

Three, and one of them only when billing is on. We add to this list before a new one goes live, not after.

hosting, compute, storage

Vercel

Everything in the stored column, encrypted at rest. Source code passes through request memory only.

reasoning layer

Configured model provider

Masked context only: detector name, masked value, entropy, file path, redacted excerpt. No full secret, no whole file, no account identity.

payments, when enabled

Stripe

Your email and what you pay for. Card details go to Stripe directly and never touch our servers.

The legal version is the privacy policy. How the service is secured is on security. Export and purge live in Settings.

$ leaksweep init

Sweep your code before someone else does.

Three sweeps a month on the free tier. No card. Secrets masked from the first byte.