Three kinds, and you decide about the second and the third. The ones that sign you in and remember a choice you made are set without asking, because they only do what you asked for. Google Analytics and Fastlane, which tell us how people find and use this site, are set only if you accept on the bar at the bottom of the page. Only then does our customer portal also tell Google Analytics whether your visit led to a sign-up, a checkout, a purchase or a sales or partnership question. Accept also loads the pixels of Meta and OpenAI, which tell them whether our own ads on Facebook, Instagram and in ChatGPT bring visits, sign-ups, checkouts and purchases, and for Meta also sales or partnership questions; there is no separate answer for analytics alone. Decline and nothing is loaded from Google, Fastlane, Meta or OpenAI at all — not a cookie, not a request. You can change your answer at any time, with the Cookie choice control in the footer of every page on seoandchill.com.
This summary is provided for convenience only. The full text below is the legally binding document — if this summary and the full text ever differ, the full text prevails.
This Cookie Policy explains which cookies and similar technologies SEO AND CHILL uses on our website (seoandchill.com), in our customer portal (app.seoandchill.com) and on our live demo (demo.seoandchill.com).
Cookies are small text files a website stores in your browser. Local storage and session storage are similar: they keep a small piece of information in your browser for one website.
We split what we use into three groups, and you only get asked about the second and the third.
Strictly necessary. Signing you in, keeping that session safe, remembering a choice you made such as light or dark, and the security check our host runs against automated traffic. Under Dutch and EU law these do not need your consent, because they do only what you asked for. They are set either way.
Analytics, only with your consent. We use Google Analytics 4 to see how many people visit, which pages they read, which plan button they click and how they got here. It is how we find out whether anything we write is worth writing. When you check a site on our landing page, Google Analytics also learns that you did, whether the site runs WordPress and which SEO plugin we found on it (the event site_check), but never the address of the site. With the same consent, our customer portal tells Google Analytics when a visit leads to a sign-up, a checkout, a purchase or a sales or partnership question, so we can see which pages lead to customers (see Third Parties). That is not strictly necessary, so we ask first, on a bar at the bottom of the page.
With the same consent we also use Fastlane, which counts visits to our pages: which page, where the visit came from, the screen size and language of your browser, the campaign tags in the link, how far down the page you scrolled and how long you stayed. It keeps a random visitor ID and a session ID in your browser’s local storage to tell visits apart (see What We Use). It does not see your sign-ups, checkouts or purchases.
Our own ads in ChatGPT, only with Accept. The bar has two buttons, Decline and Accept, and no separate answer for analytics alone: Accept covers the analytics above and our ads together. Accept also loads OpenAI’s pixel, which tells OpenAI whether our own ads in ChatGPT bring people who visit, start a checkout, sign up or buy, so we can see which ads work and OpenAI can show our ads again to people who came here. The pixel reports each page you view and keeps two IDs in cookies: a random ID for your browser and, if you came from one of our ads, a reference to that ad click (see What We Use). With each page view go the address of the page and the one you came from, each without the part after a question mark, and, if your browser allows it, OpenAI’s own cookies on openai.com: the ones OpenAI sets under its own cookie policy when you visit openai.com or sign in to ChatGPT, such as oai-sc, with which it can recognise your browser and, if you signed in to ChatGPT in it, your account; and two short-lived security cookies, __cf_bm and _cfuvid, which OpenAI’s servers set themselves when the pixel loads (see What We Use). It also picks up an email address or a name you type into a form on this site, such as the one for our newsletter, and sends it hashed: turned in your browser into a code from which it cannot be read back, but which OpenAI can compare with the hashed details of its own users. OpenAI states that its pixel hashes these in your browser and never sends them in clear. That is a setting of OpenAI’s that we cannot switch off, which is why the pixel only ever runs after Accept. With the same answer, our customer portal tells OpenAI when you sign up, start a checkout or complete a purchase (see Third Parties).
Our own ads on Facebook and Instagram, also only with Accept. Accept also loads Meta’s pixel, which tells Meta whether our own ads on Facebook and Instagram bring people who visit, check a WordPress site on our landing page, ask us a sales or partnership question, start a checkout, sign up or buy, so we can see which ads work and Meta can show our ads again to people who came here. The pixel reports each page you view, and a view of our pricing page as such, and keeps two IDs in cookies: a random ID for your browser and, if you came from one of our ads, a reference to that ad click (see What We Use). If you came from one of our ads and choose Accept only on the next page, our own script writes that reference, from the link of the ad. With each page view go the address of the page and the one you came from, and, if your browser allows it and you use Facebook or Instagram, Meta’s own cookies from facebook.com (such as fr), which Meta sets under its own cookie policy and uses to recognise your account. Meta’s pixel reads no forms on this site: its automatic matching of form fields and its automatic events are switched off in Meta’s settings, and the code on the page sends only the page views named here and, when you check a WordPress site on our landing page, the event SiteCheck, with only the name of the SEO plugin we found on it, never the address of the site. With the same answer, our customer portal tells Meta when you sign up, ask us a sales or partnership question, start a checkout or complete a purchase (see Third Parties).
Until you answer, nothing from Google, Fastlane, Meta or OpenAI is loaded. We do not merely hold back the cookie: none of their scripts is requested at all, so none of them sees you. That is a deliberate choice; the more common setup loads the script straight away and only withholds the cookie.
If you decline, we record that one choice and nothing further happens. Declining costs exactly one click, the same as accepting, and no button is made to stand out.
If you accepted earlier and change your mind, we delete the cookies and IDs of what you no longer accept and reload the page. The reload is the point: once the script of Google, Meta or OpenAI is running in a page it cannot be switched off from the outside, so we replace the page with one where it never started. From that moment nothing more is sent, with one narrow exception: a checkout you had already started before changing your mind is still reported once when its payment comes in, because we linked it to your visit at the moment you started it and cannot see your later choice from there.
Apart from the pixels of Meta and OpenAI behind Accept, we use no cookies or pixels for advertising. Anything we add next, we will ask you about again, rather than quietly widening a yes you already gave.
| Name | Where | Why | How long |
|---|---|---|---|
| __Host-sc_session | app.seoandchill.com | Keeps you signed in to your account | 30 days, or until you sign out |
| __Host-sc_signup | app.seoandchill.com | Lets the browser you signed up with confirm your new account with one click | 24 hours |
| __Host-sc_device | app.seoandchill.com | Remembers that this browser signed in to your account with your password, or chose a new password, so someone trying passwords on your email address cannot lock you out of it. It holds a random code; we keep a hash of that code, together with a hash of your email address, linked to your account. When you change your email address, we forget every browser that signed in with the old one | 1 year after you last signed in with your password, or chose a new one, in this browser |
| __Host-sc_oauth | app.seoandchill.com | Protects “Sign in with Google” against forged requests | 10 minutes |
| __Host-sc_theme | app.seoandchill.com | Remembers your light/dark choice in your account, only once you pick one | 1 year |
| sc-theme | seoandchill.com and its subdomains; the site and the live demo read it | Remembers your day/night choice, so the site and the live demo look the same, only once you pick one | 1 year after your last visit; in Safari 7 days |
| sc-theme (local storage) | seoandchill.com | A copy of your day/night choice in your browser | Until you clear it |
| mctaHide (session storage) | seoandchill.com | Remembers that you closed the sign-up bar on mobile | Until you close the tab |
| Vercel security check | seoandchill.com | Only if Vercel, our host, shows you a security check because your visit looked automated: remembers that this browser passed it, so you are not asked again. Set by Vercel | 1 hour |
| sc-consent | seoandchill.com | Remembers your answer on the bar (with Accept, analytics and the pixels of Meta and OpenAI), and when, so we stop asking and can show you your own answer. Set whichever you choose, including when you decline. The customer portal reads it too, so that it reports nothing about you to Google Analytics, Meta or OpenAI that you did not accept | 13 months |
| _ga _ga_WG9NW42F5M | seoandchill.com | Only if you accept. Google Analytics: tells a returning browser apart from a new one. Because it is set on seoandchill.com it also travels to app.seoandchill.com. The customer portal loads no Google script; it reads this cookie only to credit a sign-up, a checkout, a purchase or a sales or partnership question to your visit | 13 months |
| am_vid (local storage) | seoandchill.com | Only if you accept. Fastlane: a random ID that tells a returning browser apart from a new one | Until you clear it or withdraw your consent |
| am_sid am_st (local storage) | seoandchill.com | Only if you accept. Fastlane: a random ID for your visit and the time it started; a new visit starts after 30 minutes without activity | Until you clear it or withdraw your consent |
| _fbp | seoandchill.com and its subdomains | Only with Accept. Meta’s pixel: a random ID that tells a returning browser apart from a new one. Because it is set on seoandchill.com it also travels to app.seoandchill.com. The customer portal loads no Meta script; it reads this cookie only to credit a sign-up, a sales or partnership question, a checkout or a purchase to your visit | 90 days, or until you withdraw your consent |
| _fbc | seoandchill.com and its subdomains | Only with Accept, and only if you came from one of our ads on Facebook or Instagram. Meta’s pixel: the reference to that ad click, taken from the link of the ad, by the pixel or, if you accept on the next page, by our own script. The customer portal reads it in the same way | 90 days, or until you withdraw your consent |
| __obref | seoandchill.com and its subdomains | Only with Accept. OpenAI’s pixel: a random ID that tells a returning browser apart from a new one. Because it is set on seoandchill.com it also travels to app.seoandchill.com. The customer portal loads no OpenAI script; it reads this cookie only to credit a sign-up, a checkout or a purchase to your visit | 1 year, or until you withdraw your consent |
| __oppref | seoandchill.com and its subdomains | Only with Accept, and only if you came from one of our ads in ChatGPT. OpenAI’s pixel: the reference to that ad click, taken from the link of the ad. The customer portal reads it in the same way | 30 days, or until you withdraw your consent |
| __oaiq_consent | seoandchill.com and its subdomains | Only once you chose Accept. OpenAI’s pixel: whether it may measure. Yes after Accept; no after you withdraw, so that the pixel also stops in another tab you still have open | 30 days |
| oaiq_consent (local storage) | seoandchill.com | Only once you chose Accept. OpenAI’s pixel: the same yes or no, kept in your browser | Until you clear it; a new answer overwrites it |
| __oaiq_domain_probe | seoandchill.com | Only with Accept. OpenAI’s pixel: a test to find the domain it may set its cookies on, deleted straight away | 1 minute at most |
| oaiq_cs:… (session storage) | seoandchill.com | Only with Accept. OpenAI’s pixel: notes that it already started during this visit | Until you close the tab or withdraw your consent |
| __cf_bm _cfuvid | bzr.openai.com and bzrcdn.openai.com | Only with Accept, and only if your browser allows cookies from other sites. Set by OpenAI’s servers, not by us, when the pixel loads: security cookies that go along with the pixel’s next requests | 30 minutes (__cf_bm), until you close your browser (_cfuvid) |
| wordpress_sec_… wordpress_logged_in_… | demo.seoandchill.com | Sign you in to the live demo automatically, as a demo user | Until you close your browser |
| seochill_theme (local storage) | demo.seoandchill.com | Keeps the screens of the demo in the light or dark of the site | Until you clear it |
| seochill_kiosk_tour | demo.seoandchill.com | Remembers that you ended the guided tour of the demo’s Home, so it does not start again | 30 days |
| seochill_kiosk_tours | demo.seoandchill.com | Remembers which tours of the other demo screens you ended | 30 days |
| seochill_kiosk_from | demo.seoandchill.com | Remembers whether you came from our site or its preview, so the demo’s way back takes you there | Until you close your browser |
| wp-settings-… wp-settings-time-… | demo.seoandchill.com | Set by WordPress for the demo account: its choices on WordPress’s own screens. The demo does not keep what your browser sends back | 1 year |
| seochill_kiosk_theme | demo.seoandchill.com | The demo’s own day/night cookie until October 9, 2026. It is no longer read and expires by itself | Gone by November 9, 2026 at the latest |
| seochill_kiosk_bypass | demo.seoandchill.com | Only for the SEO & Chill team: lets an administrator into the demo without its limits | 15 minutes |
Google Analytics sets a cookie on our own pages only after you accept; Fastlane keeps its IDs in local storage instead, under the same consent, and Meta and OpenAI set their cookies only after Accept (see below). Google’s script runs on seoandchill.com only. Our customer portal loads none: when you sign up, start a checkout or complete a purchase there, or send a sales or partnership question through our contact form, the portal tells Google Analytics that it happened, credited to your visit — and only if you accepted. It sends no name, no email address, no account or customer number: only what happened, and for a purchase the plan, the amount, the currency and the order number. Our preview environments send nothing at all. Google acts as our processor for it, under Google’s data processing terms, which we accepted on 26 September 2026. Your IP address reaches Google as part of the connection, is used to work out a rough location and is then discarded rather than logged. We have switched off sharing this data with Google’s advertising products, and Google Signals is off — both in Google’s settings and in the code on the page. Details are in our Privacy Policy.
When you pay, you continue to Stripe’s checkout page (checkout.stripe.com), where Stripe sets its own cookies under its own cookie policy. Error reports to Sentry use no cookies. Subscribing to our newsletter sends your email address from your browser to Klaviyo, our email provider; that sets no cookie either.
Fastlane is run by Possibility Studios Pty Ltd, trading as Fastlane, of Sydney, Australia. Its script runs on seoandchill.com only, after you accept, and sends what it counts to Fastlane’s own servers; our customer portal and our preview environments load none of it. Your IP address reaches those servers with the connection. Fastlane acts as our processor for it, under the terms we accepted when we opened our account on 27 September 2026. If you withdraw your consent, we remove its IDs from your browser and reload the page.
Meta, for our own ads on Facebook and Instagram, only after Accept. Its pixel runs on seoandchill.com only and reports each page you view, and a view of our pricing page, to Meta, with its two cookies, your browser and, as with any request, your IP address; with them go the address of the page and the one you came from, and, if your browser allows it and you use Facebook or Instagram, Meta’s own cookies from facebook.com (such as fr), which Meta sets under its own cookie policy and uses to recognise your account. When you check a WordPress site on our landing page, it also sends the event SiteCheck, with only the name of the SEO plugin we found on it, never the address of the site. Our customer portal loads none of it: when you sign up, send a sales or partnership question through our contact form, start a checkout or complete a purchase there, the portal tells Meta that it happened, with the pixel’s two cookies and your browser; for all but a purchase also your IP address; for a sign-up how you signed up, for a question its kind, for a checkout and a purchase the plan you chose, and for a purchase the amount and the currency. When you sign up, or start a checkout or buy while signed in, it adds your email address, hashed: turned into a code from which it cannot be read back, but which Meta can compare with the hashed details of its own users. A question through the contact form and a checkout as a guest go without it. Each report carries our own reference to it, so that Meta can recognise a report it already received: your account number for a sign-up, Stripe’s ID of the payment session for a checkout or a purchase, and a random code for a question. It never sends the address itself or your name. To report a purchase, we keep the pixel’s two cookies and your browser beside the checkout you started for at most 24 hours; your IP address is not kept. Our preview environments send nothing. For collecting this on our website and in our customer portal and passing it on, Meta Platforms Ireland Limited and we are joint controllers, under Meta’s Business Tools Terms and the Controller Addendum they include, which we accepted on 9 October 2026. What Meta then does with it is Meta’s responsibility as a controller of its own: it uses the data to measure and deliver our ads, to build audiences for them and for its own purposes, under its own privacy policy, and you can exercise your rights about that with Meta. If you withdraw your consent, we remove its cookies and reload the page; the narrow exception for a checkout you had already started applies here too. Details are in our Privacy Policy.
OpenAI, for our own ads in ChatGPT, only after Accept. Its pixel runs on seoandchill.com only and reports each page you view to OpenAI, with its two cookies, your browser and, as with any request, your IP address; with them go the address of the page and the one you came from, without the part after a question mark, and, if your browser allows it, OpenAI’s own cookies on openai.com: the ones it sets when you visit openai.com or sign in to ChatGPT, such as oai-sc, with which OpenAI can recognise your browser and, if you signed in to ChatGPT in it, your account, and the security cookies __cf_bm and _cfuvid that its servers set when the pixel loads; and an email address or name you type into a form on this site, hashed in your browser (see What You Choose). Our customer portal loads none of it: when you sign up, start a checkout or complete a purchase there, the portal tells OpenAI that it happened, with the pixel’s two cookies and your browser, for a sign-up or a checkout also your IP address, for a checkout and a purchase the plan you chose, and for a purchase the amount and the currency. When you sign up, or start a checkout or buy while signed in, it adds your email address, hashed in the same way; a checkout as a guest goes without it. Each report carries a random code of its own, not one of our numbers. It never sends the address itself, your name, or an account, customer or order number. To report a purchase, we keep the pixel’s two cookies and your browser beside the checkout you started for at most 24 hours; your IP address is not kept. Our preview environments send nothing. OpenAI Ireland Limited receives this as a controller of its own, not as our processor, under OpenAI’s Conversion Terms and the Ad Tools Data Processing Addendum they include, which we accepted on 9 October 2026. We decide to collect this on our website and pass it on, and we are responsible for that part; what OpenAI then does with it is OpenAI’s responsibility: it uses the data to measure and deliver our ads, to build audiences for them, and to improve its own services, under its own privacy policy, and you can exercise your rights about that with OpenAI. If you withdraw your consent, we switch the pixel off, which keeps that “no” in your browser, remove its other cookies and reload the page; the narrow exception for a checkout you had already started applies here too. Details are in our Privacy Policy.
Our emails. The emails we send through Postmark, such as the sign-up confirmation, a password reset, the emails about your plan and the setup emails, contain a small invisible image, so we see whether an email was opened. In most of them each link also goes through Postmark’s own address, so we see which links were clicked; the exceptions are the emails about your password, email address or account, the confirmation of your purchase and the email about a failed payment. This sets no cookie in your browser. See section 6e of our Privacy Policy.
Change your answer whenever you like. There is a Cookie choice control in the footer of every page on this site, and one here:
Either control reopens the bar; declining there is one more click, and it also deletes the cookies and IDs of what you had accepted before and stops the measurement on the spot, except that a checkout you had already started is still reported once when its payment comes in (see What You Choose).
Beyond that, most browsers allow you to:
If you block the strictly necessary cookies above, you cannot sign in to the customer portal or use the live demo.
We said on this page that before adding analytics or any cookie that is not strictly necessary, we would update it first and ask for your consent where the law requires it. That is what happened on 26 September 2026, when Google Analytics was added behind the consent bar described above.
On 28 September 2026 we widened it: since then the customer portal also reports sign-ups, checkouts, purchases and sales or partnership questions to Google Analytics, credited to your visit. A yes given before that date did not cover this, so we do not treat it as one: everyone who accepted earlier is asked again, with a bar that says so. A no given before that date stays a no.
On 6 October 2026 we added Fastlane under the same consent, as described above. A yes given before that date did not name Fastlane, so we do not treat it as one: everyone who accepted earlier is asked again. A no given before that date stays a no.
In October 2026 we started counting opens and clicks in the emails we send through Postmark, as described under Third Parties.
On 9 October 2026 we added OpenAI’s pixel for our own ads in ChatGPT, as an answer of its own: Accept all, beside Analytics only. A yes given before that date did not name OpenAI, so we do not treat it as one: everyone who accepted earlier is asked again. A no given before that date stays a no.
On 11 October 2026 our host Vercel started showing a security check to visits that look automated. A browser that passes it gets a strictly necessary cookie for one hour (see What We Use); it needs no consent, and we use it for nothing else.
On 11 October 2026 we added Meta’s pixel for our own ads on Facebook and Instagram, under the same Accept all as OpenAI’s. A yes given before that date did not name Meta, so we do not treat it as one: everyone who accepted earlier is asked again. A no given before that date stays a no.
On 12 October 2026 we described more fully what OpenAI’s pixel sends, after measuring it: with each page view also go the address of the page you came from and, if your browser allows it, OpenAI’s own cookies on openai.com, with which OpenAI can recognise your browser and, if you signed in to ChatGPT in it, your account. We did not change the pixel or how we use it, but a yes given before that date did not cover this, so we do not treat it as one: everyone who accepted earlier is asked again. A no given before that date stays a no.
In October 2026 we gave the bar just two buttons, Decline and Accept. Accept covers what Accept all covered: analytics and the pixels of Meta and OpenAI together. There is no longer a separate answer for analytics alone. If your current answer is still Analytics only (this page shows your current answer), it stays as it was until it runs out or you change it with Cookie choice in the footer.
On 16 October 2026 we added a check to our landing page: you enter a website and we read its homepage. With Accept, Google Analytics learns whether the site runs WordPress and which SEO plugin we found on it, and for a WordPress site Meta’s pixel learns the name of that plugin; neither gets the address of the site. A yes given before that date did not cover this, so we do not treat it as one: everyone who accepted earlier is asked again. A no given before that date stays a no.
The same promise still stands for anything we add next. Any other changes will also be posted on this page.
For questions regarding cookies, contact:
