Cookies policy
This policy describes how rankboo.st, operated by ScalePlant Group, uses cookies and similar technologies on our website.
Last updated: 11 June 2026
1. What are cookies?
Cookies are small text files stored on your device when you visit a website. Similar technologies — such as local storage, session storage, and pixels — may serve comparable purposes. They help sites remember preferences, keep you signed in, process payments securely, and understand how pages are used.
2. How we use cookies
We group cookies into strictly necessary cookies (required for sign-in, security, dashboard state, and payments), analytics cookies (to understand marketing page usage), and third-party authentication or payment cookies set when you interact with Google or Stripe.
Analytics cookies (Google Analytics and Microsoft Clarity) are loaded in production only when configured. Where required by law, we will ask for consent before placing non-essential analytics cookies.
3. Cookie table
The table below lists cookies and closely related identifiers that may be set when you use rankboo.st. Exact names can vary slightly by browser, deployment environment (HTTP vs HTTPS), and Auth.js version.
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
| authjs.session-token / __Secure-authjs.session-token | rankboo.st | Keeps you signed in to your dashboard (Auth.js session) | Session or up to 30 days | Strictly necessary |
| authjs.csrf-token / __Host-authjs.csrf-token | rankboo.st | Protects sign-in and form submissions against cross-site request forgery | Session | Strictly necessary |
| authjs.callback-url | rankboo.st | Remembers where to redirect you after authentication | Session | Strictly necessary |
| rb_active_website | rankboo.st | Stores your selected website in the dashboard | 30 days | Strictly necessary |
| next-auth.session-token (legacy alias) | rankboo.st | Legacy session cookie name used by some Auth.js configurations | Session | Strictly necessary |
| __Secure-next-auth.session-token (legacy alias) | rankboo.st | Legacy secure session cookie on HTTPS deployments | Session or up to 30 days | Strictly necessary |
| __Host-next-auth.csrf-token (legacy alias) | rankboo.st | Legacy CSRF protection cookie for Auth.js | Session | Strictly necessary |
| __stripe_mid | Stripe | Fraud prevention and payment session identification on checkout | 1 year | Strictly necessary (payments) |
| __stripe_sid | Stripe | Fraud prevention during an active payment session | Session | Strictly necessary (payments) |
| NID, SID, HSID, SSID, APISID, SAPISID (Google OAuth) | Set when you choose Sign in with Google; used for authentication | Varies (Google policy) | Strictly necessary (OAuth) | |
| _ga | Google Analytics | Distinguishes users for usage analytics on marketing pages | 2 years | Analytics |
| _ga_* | Google Analytics | Persists session state for Google Analytics 4 | 2 years | Analytics |
| _clck | Microsoft Clarity | Persists Clarity user ID for returning visitors | 1 year | Analytics |
| _clsk | Microsoft Clarity | Connects multiple page views into a single session recording | Session | Analytics |
| CLID | Microsoft Clarity | Identifies the first-time Clarity user on this browser | 1 year | Analytics |
| ANONCHK | Microsoft Clarity | Indicates whether Clarity cookies are enabled | Session | Analytics |
| MR | Microsoft Clarity | Used by Clarity to determine whether to refresh the visitor cookie | 7 days | Analytics |
| SM | Microsoft Clarity | Synchronises Clarity identifiers across Microsoft domains | Session | Analytics |
4. Third-party cookies
When you sign in with Google, Google may set its own cookies according to Google's privacy policy (opens in new tab). When you subscribe or manage billing, Stripe may set fraud-prevention cookies as described in Stripe's privacy policy (opens in new tab).
5. Managing cookies
You can control cookies through your browser settings — including blocking, deleting, or limiting third-party cookies. Blocking strictly necessary cookies may prevent you from signing in, staying logged in, selecting an active website, or completing checkout.
To opt out of Google Analytics across sites, visit Google's opt-out browser add-on (opens in new tab). For Microsoft Clarity, see Microsoft's privacy statement (opens in new tab).
6. Updates
We may update this policy when our tooling, integrations, or legal requirements change. The "Last updated" date at the top reflects the latest revision.
7. More information
For how we handle personal data more broadly, see our Privacy policy and Terms and conditions.