Cookies and Local Storage
What TextSetu stores in your browser, why, and how to control it.
Last updated 2026-08-26
Most of what TextSetu stores in your browser is not a cookie. We use localStorage, which is covered by the same rules, so this page describes both.
This marketing site (textsetu.com)
This site is a set of static pages. Our own server sets no cookies. There is no advertising, and nothing here tracks you across other sites.
Your consent choice
| Key | Type | Purpose | Cleared |
|---|---|---|---|
textsetu_consent | Strictly necessary | Records which categories you allowed and when you decided, so we do not ask again on every page | Manually, or when our categories change |
This is written to localStorage only once you make a choice in the banner. It holds a version number, a timestamp and the list of categories you allowed — nothing that identifies you, and it is never sent anywhere.
Analytics
When analytics is enabled on this site we use PostHog, in one of two modes. When no analytics is configured for a build, neither mode runs and the banner does not appear, because there would be nothing to decide.
Anonymous page views — runs whatever you choose. We count which pages are opened. In this mode PostHog is configured to write nothing to your browser: no cookie, no localStorage, and an identifier that exists only in memory and is discarded when the page unloads. Two page views cannot be joined into a visit, and two visits cannot be joined into a person. We also strip your IP address from the event.
We run this without asking because it stores and reads nothing on your device, which is what the consent rule for cookies governs. If you would rather it did not run at all, a content blocker will stop it — most recognise PostHog — and so will "Do Not Track" or Global Privacy Control.
Analytics with a cookie — only if you accept. Accepting adds a cookie and localStorage entry, so a returning browser can be told apart from a new one and we can see how people move through the site across visits. This is what the banner is asking for, and it is off until you turn it on.
In both PostHog modes, and unlike the application:
- Autocapture is off. We record page views, not every element you click.
- PostHog session recording is off.
- You are never identified. No user ID, email or name is sent, and nothing is shared with
app.textsetu.com. - Processing takes place on PostHog's US Cloud region.
Analytics with Google Analytics — only if you accept
When a build is configured with a Google Analytics measurement id, accepting the analytics category also loads Google Analytics 4. Rejecting or ignoring the banner means the Google tag is never requested at all — there is no anonymous mode for it, and it does not run in the background before you decide.
Google is the processor for this, not us. It sets its own cookies, _ga and _ga_<id>, which distinguish a returning browser from a new one and expire after two years. They are set on this hostname only, so they are not shared with app.textsetu.com.
- Enhanced measurement is off. We send one page view per page. Scrolling, outbound clicks, file downloads and form interactions are not collected.
- Google Signals and ad personalisation are off, so nothing here is used for advertising or joined to a Google account, and this site does not follow you across other sites.
- You are never identified. No user ID, email or name is sent.
- Google discards the IP address after deriving a coarse location from it, and does not store it.
Turning analytics off later stops further collection and clears the _ga* cookies.
Session recording (Microsoft Clarity) — only if you accept
Separately from the above, and only if you switch it on, we use Microsoft Clarity to record and replay visits so we can see where the site confuses people.
This is the most invasive thing on the site, so be clear on what it means. Clarity captures your mouse movement, clicks, scrolling and the pages as they render on your screen, and reconstructs the visit as a watchable replay. It also produces heatmaps. It sets its own cookies, typically _clck and _clsk, and Microsoft is the processor — the recording is held by them, not by us.
It is off by default, it is a separate switch from analytics, and rejecting or ignoring the banner means the Clarity script is never requested at all.
Turning it off later stops any further recording and clears Clarity's _cl* cookies and localStorage entries. It cannot un-send a recording already made — email hello@textsetu.com and we will ask Microsoft to delete it.
Withdrawing
Change your mind at any time with Cookie settings in the footer of any page. Withdrawing analytics drops you back to the anonymous mode above, stops Google Analytics, and clears PostHog's ph_* entries along with Google's _ga* cookies; withdrawing session recording stops Clarity and clears its _cl* entries.
The application (app.textsetu.com)
Stored by TextSetu itself
Our server does not set any cookies. The application stores four values in localStorage, all of them strictly necessary or functional:
| Key | Type | Purpose | Cleared |
|---|---|---|---|
access_token | Strictly necessary | Your signed-in session. A JSON Web Token, valid for 7 days by default | On sign-out |
current_org_id | Strictly necessary | Which organisation you are currently working in | On sign-out |
sidebar_collapsed | Functional | Remembers whether you collapsed the sidebar | Manually |
i18nextLng | Functional | Remembers your interface language | On sign-out |
None of these are used for tracking or advertising, and none are shared with a third party.
Stored by PostHog (analytics)
The application loads PostHog for product analytics when it is configured in a production build. PostHog sets its own cookie and localStorage entries, typically named ph_*.
You should know exactly what this does, because it is more than page counting:
- Autocapture is enabled. PostHog automatically records interactions such as clicks and page views, rather than only events we explicitly define.
- Signed-in users are identified. When you sign in we send PostHog your user ID, email address and name, and associate your events with your organisation.
- Processing takes place on PostHog's US Cloud region.
Consent. We do not currently show a consent banner in the application before PostHog loads. If you are in the EEA or the UK, analytics of this kind normally requires your consent first. We are treating this as a defect rather than a design decision, and are working on it. In the meantime, you can block it using the controls below, and you can ask us to delete your analytics profile by emailing hello@textsetu.com.
Sentry
Sentry is used for error monitoring in the web, admin and server applications. It collects diagnostic data when something goes wrong, which can include your user ID and details of the request that failed. It is not used to track you across sites.
Controlling this
- Change your choice on this site with Cookie settings in the footer of any page. You can allow or refuse each non-essential category individually.
- Clear or block storage in your browser settings. Clearing
localStorageforapp.textsetu.comsigns you out. - Block analytics with a content blocker, or by enabling "Do Not Track" or "Global Privacy Control" in your browser. Most blockers recognise PostHog.
- Ask us to delete your analytics profile at hello@textsetu.com.
Blocking the strictly necessary entries will stop you being able to sign in.
Changes
We will update this page whenever what we store changes. The date at the top reflects the current version.