skip to content

~/legal/privacy

Privacy Policy

The short version: we store your account, and masked findings from your sweeps. We do not store your source code or any full secret, we do not sell data, and we do not train models on it.

last updated September 2, 2026

1. Who we are

Leaksweep is operated by Leaksweep Inc., a Delaware C-Corporation with its principal office at 1644 Platte Street, Suite 400, Denver, CO 80202, United States. In this policy, "Leaksweep", "we", and "us" mean Leaksweep Inc.. For the personal information described here, we are the controller (GDPR) and the business (CCPA/CPRA).

This policy covers leaksweep.net, the Leaksweep console, and the sweep API (together, the "Service"). A plain-language companion lives at your data. If the two ever disagree, this policy controls.

2. Information we collect

Information you give us

  • Account data: email address, name, and a salted scrypt hash of your password. If you sign in with GitHub or Google, we receive your name, email, avatar URL, and the provider's account ID. We request identity scopes only and never request repository access.
  • Plan and billing data: your plan, billing interval, and subscription status. Card details are collected by Stripe on its own hosted page and never reach our servers.
  • Messages: what you send through the contact, help, careers, and early access forms, or by email.

Information generated by a sweep

  • Masked findings: each detected secret reduced to its first four and last four characters (less for short values), the detector that matched, severity, verdict, and the reasoning summary.
  • Fingerprints: a keyed HMAC-SHA256 digest of each secret, truncated, used to tell on a re-sweep whether the same secret is still present. It can not be reversed into the secret.
  • Locations and excerpts: file path, line number, and a redacted excerpt of about five lines around the finding, with secrets and other high-entropy tokens masked.
  • Run history: timestamps, input type (paste, archive, or repo URL), file and line counts, the public repo URL if you gave one, and summary counts per run.

Information collected automatically

  • Request metadata: IP address, user agent, timestamp, route, and response status, kept in short-lived server logs for security and rate limiting. Logs do not contain request bodies.
  • Cookies: strictly necessary session cookies only. See the cookie policy.

3. Information we never collect or store

  • Your source code. Pasted code, uploaded archives, and fetched public repos are processed in memory and discarded when the request ends.
  • Any secret in full. Masking happens inside the scanner before display, storage, logging, or any model call.
  • Repository access tokens. We do not ask for them.
  • Payment card numbers.
  • Advertising identifiers, cross-site tracking data, or third-party analytics profiles.

We also never test a detected credential against the service that issued it. We have no way to learn whether a masked finding is valid, and we do not try.

4. How we use information

  • To provide the Service: run sweeps, show findings, compute re-sweep delta, generate remediation steps and CI configuration, and produce exports.
  • To operate accounts: authenticate you, enforce plan limits, process payments, and send transactional email such as verification, password reset, and receipts.
  • To secure the Service: detect abuse, enforce rate limits, investigate incidents, and enforce the defensive-only rule in our Terms.
  • To support you: answer tickets and messages.
  • To improve detection: we review aggregate, non-identifying counts such as how often a detector fires or a verdict is noise. We do not review your findings individually unless you ask us to in a support request.

We do not sell personal information. We do not share it for cross-context behavioral advertising. We do not use your data, masked or otherwise, to train machine learning models, and we do not permit our providers to do so.

5. Model providers and masked context

The reasoning layer of Leaksweep calls a third-party language model through its API. The router is model-agnostic, so the specific provider can change. The provider in use right now is shown on the status page.

What is sent to the model for each candidate:

  • the detector name and the masked value,
  • an entropy figure and the file path,
  • a redacted excerpt of the surrounding lines.

What is never sent: the full secret, the whole file, your name, your email, or your account ID. We use provider API terms under which inputs and outputs are not used for training. If no model is available, the Service falls back to a rules-only mode and sends nothing.

6. Legal bases (EEA, UK, Switzerland)

  • Contract: account data, sweep data, and billing data, to deliver the Service you signed up for.
  • Legitimate interests: request metadata and abuse signals, to keep the Service secure and available; aggregate detector statistics, to improve accuracy. We rely on this basis only where your rights do not override it.
  • Legal obligation: tax and accounting records.
  • Consent: only where we ask for it explicitly, for example a product update list. You can withdraw it at any time.

7. Sharing and subprocessors

We share personal information only with:

  • Vercel Inc. (United States): hosting, compute, and storage.
  • The configured model provider (United States): masked context only, as described in section 5.
  • Stripe, Inc. (United States): payment processing, when paid plans are enabled. Stripe is an independent controller for card data.
  • A transactional email provider, when one is enabled: your email address and the message content, to deliver account email.
  • Authorities, when we are legally required to, and only to the extent required. Because we do not hold source code or full secrets, we can not produce them.
  • A successor entity in a merger, acquisition, or asset sale. We will notify you before your information becomes subject to a different policy.

Each subprocessor is bound by a data processing agreement. We update this list before a new subprocessor begins processing.

8. Retention and deletion

  • Sweeps and findings: kept until you purge the sweep or the account.
  • Account data: kept while the account exists.
  • Server logs: up to 30 days.
  • Support and contact messages: up to 24 months.
  • Billing records: as long as tax law requires, typically seven years, held mostly by Stripe.

Purging a sweep or an account is a real delete against our primary store. There is no soft-delete window and no recovery. We keep no separate backups beyond the durability our storage provider maintains internally. You can purge from Settings at any time without contacting us.

9. Security

Data is encrypted in transit with TLS 1.2 or higher and encrypted at rest. Passwords are hashed with scrypt. Every read of a sweep checks ownership. Repo fetches are restricted to github.com and gitlab.com, and archive extraction is capped per file and in total. The full description, including what we do not have yet, is on security. No system is perfectly secure. If we learn of a breach affecting your personal information, we will notify you and the relevant regulator as the law requires.

10. Your rights

Everyone

You can export your data as one JSON file and delete your account from Settings, on any plan, without asking us.

California (CCPA/CPRA)

  • Right to know what personal information we collect, use, and disclose.
  • Right to delete and right to correct.
  • Right to opt out of sale or sharing. We do neither, so there is nothing to opt out of.
  • Right to limit use of sensitive personal information. We use account credentials only to authenticate you.
  • Right not to be discriminated against for exercising these rights.

In the last 12 months we collected identifiers (name, email, IP address), account credentials, commercial information (plan and payment status), and internet activity (request metadata), from you directly and from your use of the Service, for the purposes in section 4, and disclosed them only to the service providers in section 7.

EEA, UK, and Switzerland (GDPR)

  • Access, rectification, erasure, restriction, and portability.
  • Objection to processing based on legitimate interests.
  • Withdrawal of consent where processing relies on it.
  • Complaint to your local supervisory authority.

To exercise any right, write to hello@leaksweep.net from your account email. We verify requests against that email, respond within 30 days (45 where CCPA allows), and do not charge a fee. An authorized agent may act for you with written permission.

11. Children

The Service is for professional software work and is not directed at anyone under 16. We do not knowingly collect personal information from children. If you believe a child has created an account, write to us and we will delete it.

12. International transfers

We are based in the United States and process data there. If you use the Service from outside the US, your information is transferred to the US. For transfers from the EEA, UK, and Switzerland we rely on Standard Contractual Clauses (and the UK Addendum) with our subprocessors, and on the EU-US Data Privacy Framework where a subprocessor is certified.

13. Changes to this policy

If we make a material change, we will email account holders and post a notice in the console at least 14 days before it takes effect. The date at the top shows the latest revision. Earlier versions are available on request.

14. Contact

Leaksweep Inc.
Attn: Privacy
1644 Platte Street, Suite 400
Denver, CO 80202, United States

Privacy questions: hello@leaksweep.net
Security reports: security@leaksweep.net
Phone: (303) 555-0164