Cookie Policy
Last updated 2 October 2026. How PeekLaunch uses cookies and browser storage. Also see the privacy policy.
Ask AI:ChatGPTClaudePerplexityGrok
Effective date: 2 October 2026
Last updated: 2 October 2026
Overview
PeekLaunch uses cookies and similar browser technologies to provide essential website functionality, maintain secure sessions, and remember recent product visits. This policy explains what these technologies do and how you can manage them.
- Session cookies keep you signed in with Google (Auth.js) or email (Supabase).
- First-party cookies remember recent Visit clicks and whether today's site count has already been recorded.
- PeekLaunch does not load Google Analytics, Tag Manager, an affiliate cookie, or an advertising SDK.
- There is no cookie-consent banner and no in-app cookie preference center.
- Google sign-in and Dodo checkout may set cookies on their own domains.
What are cookies?
Cookies are small pieces of data a site stores in your browser. They can keep a session, protect forms, remember a visit, or let an external service finish sign-in or payment.
- First-party cookies are set by PeekLaunch on peeklaunch.com.
- Third-party cookies or storage are controlled by Google, Dodo, or an embedded video host, on their domains.
- localStorage and sessionStorage are similar browser stores. They are not cookies, but this page covers them because they persist data on your device.
Strictly necessary
These support sign-in. Blocking them signs you out or stops Google / email login. PeekLaunch does not offer a toggle to turn them off while staying signed in.
authjs.session-token / __Secure-authjs.session-token- Purpose
- Google / Auth.js session (JWT). Chunked names may end with .0, .1, and so on.
- Lifetime
- Up to 14 days, refreshed about every 24 hours while you keep using the site.
- Set by
- PeekLaunch (Auth.js). Secure cookies in production.
authjs.csrf-token / callback cookies- Purpose
- CSRF protection and the post-login redirect back to PeekLaunch.
- Lifetime
- Short-lived around the sign-in flow (Auth.js defaults).
- Set by
- PeekLaunch (Auth.js)
sb-*-auth-token- Purpose
- Supabase email session after you confirm the address. The project ref is part of the name.
- Lifetime
- Managed by Supabase SSR while the email session is valid.
- Set by
- PeekLaunch via Supabase
| Name | Purpose | Lifetime | Set by |
|---|---|---|---|
authjs.session-token / __Secure-authjs.session-token | Google / Auth.js session (JWT). Chunked names may end with .0, .1, and so on. | Up to 14 days, refreshed about every 24 hours while you keep using the site. | PeekLaunch (Auth.js). Secure cookies in production. |
authjs.csrf-token / callback cookies | CSRF protection and the post-login redirect back to PeekLaunch. | Short-lived around the sign-in flow (Auth.js defaults). | PeekLaunch (Auth.js) |
sb-*-auth-token | Supabase email session after you confirm the address. The project ref is part of the name. | Managed by Supabase SSR while the email session is valid. | PeekLaunch via Supabase |
Product visits and site count
These are first-party. They are not advertising or affiliate identifiers. Blocking them does not sign you out.
pl_visited- Purpose
- Recent live product slugs after you use Visit, so upvote eligibility can work.
- Lifetime
- 90 days, last 80 entries. Path=/, SameSite=Lax.
- Set by
- PeekLaunch
pl_day- Purpose
- UTC date so the header site-visit count is not incremented twice the same day.
- Lifetime
- 2 days (Max-Age 172800). Path=/, SameSite=Lax. Readable by the page so a second request can be skipped.
- Set by
- PeekLaunch
| Name | Purpose | Lifetime | Set by |
|---|---|---|---|
pl_visited | Recent live product slugs after you use Visit, so upvote eligibility can work. | 90 days, last 80 entries. Path=/, SameSite=Lax. | PeekLaunch |
pl_day | UTC date so the header site-visit count is not incremented twice the same day. | 2 days (Max-Age 172800). Path=/, SameSite=Lax. Readable by the page so a second request can be skipped. | PeekLaunch |
Third-party cookies
PeekLaunch does not set advertising cookies on peeklaunch.com. External sites may still set their own cookies when you leave PeekLaunch or load their player.
- Google sign-in: if you choose Google, accounts.google.com may set cookies under Google's cookie notice.
- Dodo checkout: payment opens Dodo's checkout URL (not an in-page PeekLaunch card form). Dodo may set cookies on its domain. Card data never touches PeekLaunch servers.
- Product videos: a listing may embed YouTube (youtube-nocookie.com), Loom, or Vimeo. Playing that embed can let that host set cookies on its domain.
- Ask AI: buttons open ChatGPT, Claude, Perplexity, or Grok in a new tab. Those sites use their own cookies.
PeekLaunch does not run an affiliate referral cookie and does not load an analytics pixel.
Local storage and similar
peeklaunch:visited(localStorage): recent product ids after Visit, last 80 entries, so the browser can remember a visit if the cookie is missing. This can include product ids. It is not used to track you across other websites.peeklaunch-signup-email(sessionStorage): the email you typed on sign-up or sign-in, so the confirm-email screen can prefill it. It lasts until you close the tab.
PeekLaunch does not use IndexedDB or a service worker for tracking. The browser may cache pages and images on its own. Clear site data in the browser to remove cookies, localStorage, and sessionStorage for peeklaunch.com.
Managing cookies
PeekLaunch has no in-app cookie switch. Use your browser to inspect, block, or delete cookies and site data. If you block the session cookies above, sign-in will not work. Blocking pl_visited can reset Visit / upvote memory.
Browser settings are not a substitute for a consent banner if a future optional cookie would legally require one. PeekLaunch does not currently load that kind of optional tracking cookie.
Privacy signals
PeekLaunch does not implement special handling for Do Not Track or Global Privacy Control. Available controls are: browse without an account, block cookies in the browser, and delete site data. Personal data, sharing, and rights are explained in the privacy policy. Account rules are in the Terms. Launch questions are on the FAQ.
Policy updates
We may update this Cookie Policy when our website functionality, integrations, or use of browser technologies changes. We will update the last-updated date when the policy changes (2 October 2026). PeekLaunch does not email every visitor about cookie-policy edits.
Ask about browser storage
If you have questions about how PeekLaunch uses cookies or similar technologies, contact us at peeklaunch.com@gmail.com.