Cookie policy
Last updated Oct 11, 2026
This page lists every cookie and every item of browser storage SEO for SaaS sets, and why. For how we handle personal data in general, see our privacy policy.
The short version
With your consent, we use Meta's and OpenAI's advertising cookies to see which of our ads, on Meta's apps and in ChatGPT, bring people to SEO for SaaS. Until you accept them in our cookie banner, they're not set.
With your separate consent, we use Microsoft Clarity to see how people use our website, sign-up and setup, so we can fix what gets in their way. Until you accept it, it doesn't load.
You can accept, reject, or change your choice at any time under "Cookie settings" at the bottom of every page of our website.
We count visits with Plausible Analytics, which sets no cookies and stores nothing on your device.
The dashboard sets only the cookies it needs to sign you in, keep you secure, and remember how you left the sidebar.
Cookies that are strictly necessary for a service you asked for don't need your consent. Every other cookie needs it before it's set or read, and that's what the banner asks for.
Cookies on our website and docs (seoforsaas.dev, docs.seoforsaas.dev)
| Name | What it does | How long | Type |
|---|---|---|---|
sfs_consent | Remembers your cookie choices, so we don't ask again on every page. It holds a random ID, your choices, and the date | 6 months, then we ask again | Strictly necessary, first party, shared by seoforsaas.dev and its subdomains |
_fbp | Meta's browser ID: tells Meta which visits and sign-ups come from the same browser, so we can see which ads work | 90 days | Advertising, first party, set by Meta's script. Only after you accept |
_fbc | The click ID from the Meta ad you clicked, if you came from one | 90 days | Advertising, first party, set by Meta's script. Only after you accept |
_fbleid | Meta's event ID for linking a visit to a later conversion | 7 days | Advertising, first party, set by Meta's script. Only after you accept |
__oppref | The reference of the ChatGPT ad you clicked, if you came from one | 30 days, restarted when you come from another ChatGPT ad | Advertising, first party, set by OpenAI's script. Only after you accept |
__obref | OpenAI's random ID for your browser on our website, so a later sign-up can be linked to the ad | 1 year | Advertising, first party, set by OpenAI's script. Only after you accept |
__oaiq_consent | OpenAI's script remembers whether you allowed ad measurement | 30 days | Advertising, first party, set by OpenAI's script. Only after you accept |
__oaiq_domain_probe | OpenAI's script checks which domain it can set its cookies on, then removes it | 1 minute | Advertising, first party, set by OpenAI's script. Only after you accept |
_clck | Clarity's ID for your browser, so visits on different days count as one visitor | 1 year | Analytics, first party, set by Clarity's script. Only after you accept Analytics |
_clsk | Joins the pages you view in one visit into one session | 1 day | Analytics, first party, set by Clarity's script. Only after you accept Analytics |
Meta pixel (only if you accept)
If you accept, our website loads Meta's pixel from connect.facebook.net. It sends Meta the pages you view on our website with the cookies above, your IP address, and your browser's user agent, and it may keep short-lived values in your browser's session and local storage. We've turned off Meta's automatic events, so it doesn't report your clicks or form entries. When you then create an account or subscribe, our server tells Meta about it, with the same cookies, your IP address and user agent, one-way codes made from your email address and your account ID, and, for a subscription, the amount paid. Meta can also read the cookies it sets on its own sites (for example fr on facebook.com) under its own cookie policy.
We use this to measure which of our ads lead to sign-ups and subscriptions, and Meta uses it to show our ads to people likely to be interested. Meta Platforms Ireland Limited and we are joint controllers for collecting this data and sending it to Meta; what Meta does with it afterwards is covered by Meta's privacy policy. Details are in our privacy policy.
The pixel never runs in the dashboard. If you reject or later withdraw your consent, we stop loading it, delete its cookies from your browser, and send Meta nothing more about you. One exception: a subscription checkout you started while you had accepted is still reported when you pay, because the payment page is Stripe's and we can't see your choice there.
OpenAI pixel (only if you accept)
If you accept, our website also loads OpenAI's measurement pixel from bzrcdn.openai.com. It sends OpenAI the pages you view on our website and the page that linked you to them, with the __oppref and __obref cookies above, your IP address, and your browser's user agent. It also keeps your consent state in your browser's local and session storage (oaiq_consent). When you then create an account or subscribe, our server tells OpenAI about it, with the same two cookies, your IP address and user agent, one-way codes made from your email address and your account ID, and, for a subscription, the plan, the amount and the currency.
We use this to measure which of our ads in ChatGPT lead to sign-ups and subscriptions. What OpenAI does with the data it receives is covered by OpenAI's privacy policy. Details are in our privacy policy.
The pixel never runs in the dashboard. If you reject or later withdraw your consent, we tell the pixel, delete its cookies and stored consent state from your browser, stop loading it, and send OpenAI nothing more about you. The same exception as for Meta applies: a subscription checkout you started while you had accepted is still reported when you pay.
Microsoft Clarity (only if you accept Analytics)
If you accept Analytics, our website, the sign-up and sign-in pages, and the setup steps after them load Microsoft Clarity from clarity.ms. Clarity records how you use these pages: the pages you view, where you click, how far you scroll, and how you move the pointer, along with your browser, device, approximate location from your IP address, and the address of the page or ad that brought you. We can replay these visits and see them as heatmaps. Clarity masks what you type and doesn't record it, and we've set it to mask the text on the page too. It doesn't run in the dashboard: if you go there straight from setup, we reload the page without it. It doesn't load on pages for accepting an invitation, and we remove the click ID of a Meta or ChatGPT ad from the page address before it loads.
Besides the cookies above, Clarity's script can set Microsoft's own cookies on clarity.ms and other Microsoft domains (such as MUID, CLID, ANONCHK, MR and SM) under Microsoft's privacy statement.
We use this to find what confuses people on our pages and fix it. Microsoft keeps recordings for 30 days and heatmap totals for up to 13 months. Details are in our privacy policy.
If you reject or later withdraw your consent, we tell Clarity, delete its cookies from your browser, and stop loading it.
Cookies on the dashboard (app.seoforsaas.dev)
| Name | What it does | How long | Type |
|---|---|---|---|
__Secure-better-auth.session_token | Keeps you signed in | 7 days, renewed while you use the dashboard | Strictly necessary, first party |
__Secure-better-auth.session_data | A short-lived signed copy of your session, so pages load without a database check each time | 5 minutes | Strictly necessary, first party |
__Secure-better-auth.state | Protects Google sign-in from forged requests | 5 minutes, only while you sign in with Google | Strictly necessary, first party |
gsc_pkce | Proves that the browser finishing a Search Console connection is the one that started it | 10 minutes, only while you connect Search Console | Strictly necessary, first party |
sidebar_state | Remembers whether you collapsed the sidebar | 7 days | Functional, first party, set when you toggle the sidebar |
The session cookies can't be read by scripts on the page and are sent only over HTTPS.
Browser storage (not cookies)
Some settings are saved in your browser's local storage. They stay on your device, aren't sent to us, and you can clear them anytime in your browser settings.
| Key | What it does | Where |
|---|---|---|
docs.tab | Remembers the code language you picked in an example (for example Python), so every example shows it | Docs and dashboard, set when you pick a tab |
articles.columns | Remembers which columns you chose in the articles table | Dashboard, set when you change columns |
Plausible Analytics
We use Plausible Analytics to count visits to our public website (seoforsaas.dev and docs.seoforsaas.dev) and the app at app.seoforsaas.dev. Plausible doesn't use cookies, browser cache, local storage, or any other identifier stored on your device. It counts unique visitors with a code that changes every day and can't be linked across days. See Plausible's data policy and our privacy policy.
Cloudflare Turnstile on the sign-in page
The sign-in form uses Cloudflare Turnstile to tell people from bots. It loads from challenges.cloudflare.com. Cloudflare says Turnstile doesn't use cookies to collect or store information; it may keep a short-lived value in your browser's session storage for the duration of the check. See Cloudflare's Turnstile privacy addendum.
Paying through Link
When you subscribe, you go to a checkout page run by Link (Sold through Link, LLC, a Stripe company) on Stripe's own domain. Cookies set there are Stripe's and Link's, under their own cookie policies, not ours.
Cloudflare's network
Our site runs on Cloudflare. If Cloudflare's bot protection is turned on for our site, Cloudflare can set its own strictly necessary security cookies, such as __cf_bm or cf_clearance, to tell people from bots. See Cloudflare's cookie list.
How to control cookies
Use "Cookie settings" at the bottom of any page of our website to accept, reject, or withdraw consent, for ad measurement and analytics separately; withdrawing is as easy as giving it. You can also block or delete cookies in your browser settings. If you block the session cookies, you can't sign in to the dashboard. The website and docs work without any cookies.
Contact
Questions about this policy: support@seoforsaas.dev.












