Cookie
Policy

1. 1. What cookies are

   Cookies are small files a site stores in your browser to remember preferences or keep you signed in. Local storage (localStorage) is similar, but the data stays on your device and does not travel to the server.

2. 2. Essential site cookies

   NEXT_LOCALE — stores the language you chose (Portuguese or English), so the site opens in the same language on your next visit. First party, valid for 1 year.

   This is the only cookie a visitor to the public pages (landing, blog, legal pages) gets from us, and only after switching language.

3. 3. Essential product cookies

   sb-…-auth-token — keeps you signed in after logging in with Google or GitHub. First party, set by Supabase, our authentication provider. Valid until you sign out or for up to 400 days without use. During sign-in there is also sb-…-auth-token-code-verifier, which protects the exchange with the provider and is gone when it ends.

   pm_stripe_oauth_state, pm_posthog_oauth_state, pm_slack_oauth_state, pm_hubspot_oauth_state, and pm_intercom_oauth_state — set only while you connect the matching integration, to ensure the provider's response belongs to the connection you started. They last at most 10 minutes and are deleted as soon as the connection completes.

   sidebar_state — remembers whether the dashboard's side menu is open or closed. First party, 7 days.

   Without these cookies, sign-in and integrations do not work. Because they are strictly necessary for the service you asked for, they do not depend on consent.

4. 4. Local storage

   theme — the dashboard theme (light, dark, or system).

   pm_tour_seen:<screen> — remembers you have seen a screen's guided tour, so it does not show again.

   pitch-theme — the theme chosen on Keep's pitch page.

   keep_cookie_notice_v1 — remembers you have closed the cookie notice.

   This data stays in your browser only and is not sent to us or to third parties.

5. 5. Support chat (Crisp)

   Support chat is provided by Crisp and is not loaded when you open the site: until you click the chat button, no Crisp code or cookie is on the page.

   When you click, Crisp stores the cookie crisp-client/session/… and a few crisp-client/… keys in local storage, to keep the conversation across pages and visits. From then on, the chat loads by itself on later visits, so you can see the ongoing conversation. This data belongs to Crisp and follows its privacy policy (crisp.chat/en/privacy).

   To go back to the initial state, clear the site's data in your browser.

6. 6. Audience measurement

   We use Umami (cloud.umami.is) to count visits in aggregate. Umami stores no cookie or anything else in your browser and collects no personally identifiable data.

   We do not use Google Analytics, Meta Pixel, Hotjar, or any advertising or cross-site tracking tool. If we ever add something that requires consent, this policy will change first and we will ask for your permission.

7. 7. How to manage them

   You can view, block, or delete cookies and local storage at any time in your browser settings. Blocking NEXT_LOCALE makes the language be detected on every visit; blocking the product cookies prevents sign-in and connecting integrations.

8. 8. Changes and contact

   This policy changes whenever a cookie is added, removed, or changes its lifetime, with a new effective date at the top.

   Questions: vinicius@usekeep.dev.

This document is the current version. Changes are published here with a new effective date.