skip to content

~/legal/cookies

Cookie Policy

Three cookies, all strictly necessary, all first party. No advertising cookies. No third-party analytics cookies. That is why there is no consent banner.

last updated September 2, 2026

1. What this covers

This policy explains the cookies that Leaksweep Inc. sets on leaksweep.net and in the Leaksweep console. A cookie is a small text file a site stores in your browser. It supplements our Privacy Policy.

2. The cookies we set

All three come from Auth.js, the library that handles sign-in. None of them is set until you visit a sign-in page or sign in. A visitor who only reads the marketing site gets no cookies from us.

cookie
authjs.session-token
__Secure-authjs.session-token on HTTPS
purpose
Keeps you signed in. Holds a signed, encrypted session token (JWT). HttpOnly, SameSite=Lax, and Secure on HTTPS. Set only after you sign in.
duration
30 days, refreshed while you are active. Removed on sign out.
cookie
authjs.csrf-token
__Host-authjs.csrf-token on HTTPS
purpose
Cross-site request forgery protection for the sign-in and sign-out forms. Holds a random token and its hash. HttpOnly, SameSite=Lax.
duration
Session. Cleared when the browser closes.
cookie
authjs.callback-url
__Secure-authjs.callback-url on HTTPS
purpose
Remembers which page to return you to after sign-in, including after a GitHub or Google redirect. HttpOnly, SameSite=Lax.
duration
Session. Cleared when the browser closes.

On HTTPS, which is how production is always served, Auth.js adds a prefix to each name: __Secure- for the session and callback cookies, __Host- for the CSRF cookie. The prefix tells the browser to refuse the cookie over an insecure connection. The purpose does not change.

3. What we do not set

  • No advertising or retargeting cookies.
  • No third-party analytics cookies. We do not load Google Analytics, tag managers, session replay, or social pixels.
  • No cross-site tracking of any kind. We do not sell or share personal information.
  • No fingerprinting as a substitute for cookies.

Because every cookie here is strictly necessary to provide a service you asked for (signing in), consent is not required under the ePrivacy rules, and we do not show a banner.

4. Browser storage

Leaksweep does not currently write to your browser's local storage or session storage. If a future release keeps an interface preference there, it will stay on your device, will never hold a secret or an identifier, and will be listed on this page first.

5. Stripe

When paid checkout is enabled, payment happens on a page hosted by Stripe. Stripe sets its own cookies there, for fraud prevention and to run the checkout. They are set on Stripe's domain, only on its hosted checkout page, and are governed by Stripe's cookie policy. Leaksweep pages do not load Stripe scripts.

6. GitHub and Google sign-in

If you choose to sign in with GitHub or Google, you are redirected to their site, where they use their own cookies under their own policies. We receive only the identity result they send back.

7. Controlling cookies

You can block or delete cookies in your browser settings. If you block ours, the marketing site keeps working, but you will not be able to stay signed in to the console. Signing out deletes the session cookie immediately.

8. Changes and contact

If we ever add a cookie that is not strictly necessary, we will update this page and ask for consent before setting it. Questions: hello@leaksweep.net, or by mail to Leaksweep Inc., 1644 Platte Street, Suite 400, Denver, CO 80202, United States.