Legal

Cookie Policy

Last updated October 22, 2026

1. Overview

This Cookie Policy explains how SlashPeak, Inc. ("SlashPeak", "we", "us") uses cookies and similar technologies, such as browser local storage, on our website and in the SlashPeak application (together, the "Service"). It should be read with our Privacy Policy, which explains how we handle personal data more broadly.

SlashPeak uses strictly necessary cookies — the kind required to keep you signed in and your session secure — and, only if you accept, analytics cookies from PostHog that show us how the product is used. We do not use advertising cookies, cross-site tracking cookies, or cookies that sell or share your data with ad networks.

2. Cookies we use

The table below lists every cookie the Service sets, what it does, how long it lasts, and whether it needs your consent.

CookiePurposeDurationType
__Secure-slashpeak.session_tokenKeeps you signed in and identifies your account on each request.7 days, renewed while you use the app (shorter if your account owner sets an idle timeout)Strictly necessary
__Secure-slashpeak.stateSet only while you sign in with Google or Microsoft. It protects the sign-in from forgery.5 minutesStrictly necessary
slashpeak.connectionRemembers which warehouse connection you picked, so every page shows the same one.1 yearStrictly necessary
ph_<project token>_posthogSet by PostHog only if you accept analytics. Holds a random visitor ID so we can see how the product is used and fix errors.1 yearAnalytics (consent required)
slashpeak.impersonateSet only for SlashPeak support staff who open an account in read-only support mode.SessionStrictly necessary

3. What cookies are

A cookie is a small text file that a website stores in your browser. Cookies let a site recognize your browser between page loads, so it can keep you signed in or remember a choice.

Cookies are either "first-party" (set by the site you are visiting) or "third-party" (set by another company). Cookies are also either "session" cookies, which are deleted when you close your browser, or "persistent" cookies, which stay until they expire or you delete them.

All the cookies in the table below are first-party cookies. Our analytics provider, PostHog, sets its cookie on our own domain; it is not a third-party advertising cookie. Two embedded services load their own content in a frame or script and may set their own cookies, which this table does not list: Cloudflare Turnstile on the sign-in, sign-up, and brochure forms, and the Cal.com booking calendar on the demo page and in the sign-up demo step. They are covered by those providers' policies, and we do not use them for advertising.

4. Categories of cookies

We group the cookies we use into two categories.

  • Strictly necessary: required to sign you in, keep your session secure, and remember settings you asked for, such as your selected warehouse connection. These cookies are always on. Under most privacy laws they do not need your consent, because the Service cannot work without them. They never store personal data beyond what is needed for the function.
  • Analytics (consent required): set by PostHog only if you choose "Accept all". They help us count visits, see which features are used, and find and fix errors. They are off by default and stay off until you opt in.
  • Not used: we do not use advertising, retargeting, social-media tracking, or cross-site profiling cookies.

5. Analytics and PostHog

We use PostHog, a product analytics service, to understand how people use the Service and to catch bugs. PostHog starts in an opted-out state. Until you accept, it sets no cookie, stores no visitor ID, and sends no usage events or error reports from your browser.

If you accept, PostHog stores a random visitor ID in a cookie and may record events such as page views, button clicks, and unhandled browser errors. It may also record technical details like your browser type, device type, screen size, and the page URL. Events are linked to your account only after you sign in, so that we can understand usage by account.

We do not use PostHog to record the contents of the data in your connected warehouse. We access your warehouse metadata only as described in our Privacy Policy, and that data is never sent to PostHog. PostHog is listed on our Subprocessors page.

6. Local storage and similar technologies

Interface preferences — such as your color theme and whether the sidebar is collapsed — are saved in your browser's local storage, not in a cookie. This data stays on your device, is never sent to us, and isn't used for tracking.

PostHog also keeps your cookie choice (accepted or rejected) in local storage, so the cookie notice does not appear again once you have decided. We do not use web beacons, tracking pixels, or device fingerprinting.

7. Managing cookies

Analytics are off until you choose "Accept all" in the cookie notice. If you choose "Decline all", PostHog sets no cookie and sends no events from your browser. Your choice is saved and remembered on that browser.

To change your choice, clear this site's cookies and local storage in your browser's settings. The notice will appear again the next time you visit, and you can choose again.

You can also control cookies in your browser. Most browsers let you view, block, or delete cookies, and many let you block cookies for specific sites. Blocking all cookies may stop parts of the Service from working. Strictly necessary cookies cannot be blocked without also blocking sign-in, and clearing them will sign you out. Browser help pages explain how to do this for Chrome, Firefox, Safari, and Edge.

8. Your rights

Depending on where you live (for example, the European Economic Area, the United Kingdom, or California), you may have rights over the personal data that analytics cookies collect. These include the right to access it, correct it, delete it, object to its use, and withdraw consent at any time. Withdrawing consent does not affect processing that happened before you withdrew it.

To use any of these rights, email [email protected]. Our Privacy Policy explains these rights in more detail and how to contact your local data protection authority.

9. Changes to this policy

If we ever add a cookie for a new purpose, we'll update this page and, for anything beyond strictly necessary cookies, ask for your consent first. We will change the "Last updated" date at the top of this page whenever the policy changes materially.

Questions about cookies?

Reach out any time — we're happy to explain exactly what each cookie does.

Email us