THREADSIGNALLEGAL
Cookie Policy
Last updated 25 August 2026.
Threadsignal uses a small number of cookies. Here is each one, who sets it, and when it expires.
The cookies we set
| Name | Set by | Purpose | Expires |
|---|---|---|---|
| session-id | Threadsignal | Groups page views into one visit for analytics | When the browser session ends |
| _ga | Google Analytics | Distinguishes one browser from another for analytics | About 2 years, Google's default |
| _ga_MWCX8V271R | Google Analytics | Holds analytics session state for this site | About 2 years, Google's default |
| __dpl | Threadsignal | Identifies which deployment of the site served the page | Session |
| __cf_bm | Cloudflare | Distinguishes people from bots, protects the site from automated abuse | About 30 minutes |
| Sign-in session | Threadsignal | Keeps you signed in between visits | Until you sign out |
| Stripe cookies | Stripe | Set on Stripe's own checkout and billing pages, not on threadsignal.ai | Per Stripe |
Other storage, and what blocking cookies does
- We also use your browser's session storage to remember your scroll position while you move between pages. It is cleared when you close the tab.
- We use Google Analytics, which is a third-party analytics service and sets the Google cookies listed above. What Google does with that data is governed by Google's own policies.
- Blocking cookies will still let you read the site and use the free comparison tool. It will prevent you from staying signed in.