Cookie Policy
Last updated: 29 August 2026
This page lists the cookies TestKase sets, grouped by purpose, and below the tables it describes the data we keep in your browser’s local and session storage. Analytics and advertising cookies are not set until you accept them. Two things load before you make a choice and you should know about them: Google reCAPTCHA, which scores form submissions for abuse, and Google’s sign-in library on our sign-in and sign-up pages. You can change your cookie choice at any time:
Strictly necessary
Required for authentication, session handling, invitation links, abuse prevention on forms, maintenance access, and remembering your cookie choice. These are not offered as a choice in our consent banner. You can still block or delete them in your browser, but doing so will sign you out and break parts of the site.
| Cookie | Provider | Purpose | Type | Retention |
|---|---|---|---|---|
| cc_cookie | TestKase (first-party) | Stores your cookie consent choice so the banner does not reappear on every visit. | HTTP cookie | 182 days |
| accessToken | TestKase (first-party) | Keeps you signed in. Set by our API, HttpOnly, so it cannot be read by scripts in the page. | HTTP cookie | 1 hour |
| refreshToken | TestKase (first-party) | Obtains a new access token without asking for your password again. HttpOnly and scoped to the /api/v1/auth path. | HTTP cookie | 14 days |
| inviteToken, inviteTokenExpiry | TestKase (first-party) | Temporarily remembers a project invitation, and when it lapses, while you sign up. | HTTP cookie | 1 day |
| tk_unlock | TestKase (first-party) | Lets a member of our team, or anyone we have given an unlock link to, reach the site while it is in maintenance mode. Set on .testkase.com so one unlock covers every TestKase subdomain. | HTTP cookie | 30 days |
| g_state | Google Identity Services | Set by Google's sign-in library to remember that you dismissed the sign-in prompt. Only relevant on our sign-in and sign-up pages. | HTTP cookie | Up to 6 months (Google-managed) |
| reCAPTCHA tokens | Google reCAPTCHA v3 | Prevents automated abuse on forms (newsletter, AI search, signup). It is loaded on every page rather than only on the page with the form, so that an abuse score is already available by the time a form is submitted. It is used only for abuse prevention, never for advertising or analytics. | HTTP cookie | 6 months (Google-managed) |
Analytics
Google Analytics 4 — measures page views, traffic sources, and feature usage so we can improve the product. No personal identifiers are stored in these cookies.
| Cookie | Provider | Purpose | Type | Retention |
|---|---|---|---|---|
| _ga, _ga_* | Google Analytics 4 | Distinguishes unique users and tracks which pages and features are used. | HTTP cookie | 2 years |
| _gid | Google Analytics 4 | Distinguishes users for a single day. | HTTP cookie | 24 hours |
Marketing
Google Ads conversion tracking — tells us which ads led to sign-ups so we do not spend on campaigns that do not work.
| Cookie | Provider | Purpose | Type | Retention |
|---|---|---|---|---|
| _gcl_au | Google Ads | Measures conversions from Google Ads campaigns so we can evaluate ad performance. | HTTP cookie | 90 days |
| _gac_* | Google Ads | Campaign-level attribution for Google Ads. | HTTP cookie | 90 days |
| _gcl_aw, _gcl_gb, _gcl_dc | Google Ads | Click identifiers Google Ads may set when you arrive from an ad. Removed automatically if you decline the Marketing category. | HTTP cookie | 90 days |
Preferences
Small UX choices like remembering your last-used product area.
| Cookie | Provider | Purpose | Type | Retention |
|---|---|---|---|---|
| testkase_last_product | TestKase (first-party) | Remembers the last product area you used so you do not have to re-select it. | HTTP cookie | 1 year |
Local and session storage
Cookies are not the only thing a site can keep in your browser. We also use your browser’s local storage and session storage. None of it is sent to a third party, and all of it stays on the device you are using. It falls into three groups:
- Sign-in state. While you are signing in or signing up we keep the email address you entered, and flags recording that a verification or password reset is in progress, so that a refresh does not lose your place. We also keep the reason you were last signed out, so we can explain it. These are cleared on sign-out.
- Handover to our browser extension. If you install the TestKase Chrome extension, we place your access and refresh tokens in session storage for the moment it takes the extension to collect them. Session storage is cleared when you close the tab.
- Interface preferences. The project you last had open, the filters and page number on each list, and the widths of resizable panels in Live and Automate. These exist only so the product looks the way you left it.
Clearing site data in your browser removes all of it.
Managing cookies in your browser
Most browsers let you block or delete cookies directly from settings. Doing so may log you out of TestKase and disable some features. For browser-specific instructions see aboutcookies.org.
Third-party privacy policies
Changes to this policy
If we add, remove, or change the category of any cookie, we will re-prompt you via the banner so your consent stays current. See our Privacy Policy for the full picture of how we handle your data.