skip to content

~/help

Help center.

Short answers to the questions that come up when a sweep finds something. If yours is not here, open a ticket at the bottom.

01 / getting started

Getting started

help/first-sweep

How do I run my first sweep?

Sign in, open the console, and pick an input: paste code, upload a .zip or .tar.gz archive, or (on Dev and Team) give a public GitHub or GitLab URL. The pattern engine pulls candidates, masks each one at the moment it is found, and the reasoning layer rates what is left. A typical sweep returns in well under a minute.

help/make-archive

How do I make a repo archive to upload?

Use git archive from the repo root. It packs only tracked files at the commit you name, so node_modules, build output, and your local .git directory stay out. For a tarball, swap the format for --format=tar.gz -o repo.tar.gz.

$ git archive --format=zip -o repo.zip HEAD

help/size-limits

What are the size limits?

Free: paste up to 200 KB, archives up to 1 MB. Dev and Team: archives up to 4 MB. Inside an archive, any single file over 512 KB is skipped and extraction stops at a fixed total, which is also what guards against zip bombs. If your archive is too big, archive a subdirectory: git archive -o api.zip HEAD:services/api.

02 / findings

Findings

help/masking

How does masking work?

A secret of 12 or more characters is reduced to its first four and last four, like sk_l••••••••YhJ9. Values of 8 to 11 characters keep only two on each side, and anything shorter is fully dotted, because first-4 plus last-4 of a short password is the password. Masking happens inside the scanner, before display, storage, or any model call. There is no setting that reveals the full value.

help/noise

Why was a finding marked noise?

The reasoning layer saw context that says the value is not a live credential: a placeholder like your-api-key-here, a test fixture path, a documented example such as AKIAIOSFODNN7EXAMPLE, or entropy too low for the claimed key type. Every noise verdict is listed with its reason and is never hidden. If you know better, treat it as real and rotate. The verdict is advice, not a gate.

03 / rotation and history

Rotation and history

help/first-move

A key leaked. What do I do first?

Rotate or revoke it at the issuer. Do that before you delete the line, before you rewrite history, before you tell anyone. A pushed key should be treated as read by a scraper. Then check the provider audit log for use you do not recognize, redeploy with the new value from env, and only then clean history. The ten minute runbook has the order.

help/history-purge

How does the git history purge plan work?

On Dev and Team, each finding carries the exact git filter-repo command for its file path or value, the force-push, and the re-clone note for collaborators. Leaksweep does not run it for you and never touches your remote. Purging history lowers exposure in clones and search. It does not un-leak the key, which is why rotation comes first.

$ git filter-repo --replace-text expressions.txt

help/resweep

How does re-sweep delta work?

Each finding stores a keyed HMAC fingerprint of the secret, never the secret. On re-sweep, a fingerprint that is gone is marked sealed, one that is still present stays remaining, and a new one is flagged as introduced. A sealed secret that reappears is unsealed. Re-sweeps do not count against the Free plan quota.

04 / billing and account

Billing and account

help/cancel

How do I cancel?

Open Settings and use the plan controls, or write to support@leaksweep.net from your account email and we cancel it the same business day. You keep paid features until the end of the billing period, then the account drops to Free. Your sweeps stay until you purge them.

help/purge

How does purge work?

Purging a sweep deletes its masked findings, fingerprints, excerpts, and run history. Purging the account (Settings, type PURGE) deletes the profile, every sweep, and the email index entry in one request. Both are real deletes. There is no soft-delete window and no way for us to restore it. Details on your data.

05 / ticket

Still stuck. Open a ticket.

Goes to the support inbox. Team plan tickets are answered within one business day, everyone else within two.

before you send

Never paste a full secret into a ticket. The masked value and the file path are enough for us to find it. If you already pasted one somewhere, rotate it now.

other channels

$ 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.