Your choices
We group non-essential cookies and tags into three categories:
- Analytics: Google Analytics 4 and Site Qwality real user monitoring, our own product.
- Advertising: Google Ads conversion tracking and PromoteKit affiliate attribution.
- Session recording: Microsoft Clarity and our own session replay.
In the European Economic Area, the United Kingdom and Gibraltar, none of these loads until you accept it. You can accept all, reject all or choose per category. We treat every visit to siteqwality.de and siteqwality.it, and every visit from a browser set to a Europe/ time zone, as being in this region. A time zone is not a precise location, so we err on the side of asking.
Everywhere else, these categories are on by default and you can turn them off.
You can change your choice at any time with Cookie preferences at the bottom of every page. On siteqwality.com your choice also applies to docs.siteqwality.com and the dashboard. Your choice is stored only in a cookie in your browser; we keep no server-side copy.
Global Privacy Control and Do Not Track. On our marketing sites we treat either signal as a refusal of all three categories, in every region. On docs.siteqwality.com and in the dashboard, either signal stops our real user monitoring. Google tags use Google Consent Mode, so they receive your choice before they run.
Cookies we set
| Cookie | Category | Purpose | Duration |
|---|---|---|---|
sq_consent | Strictly necessary | Stores your consent choice for each category, the policy version you saw and when you chose. | 180 days |
sq_region | Strictly necessary | Records whether your time zone is in the region where we ask for consent (eu or row). | 1 day |
sq_theme | Preference | Remembers the light or dark theme if you choose one. | 1 year |
sq_locale_dismissed | Preference | Remembers that you dismissed the language suggestion. | 1 year |
sq_ft | Analytics | Records where your first visit came from (source, campaign, referring site and landing page) so we can see which channels lead to sign-ups. If you create an account, it is stored once with the account. It holds no name, email or identifier. | 90 days |
On siteqwality.com, sq_consent, sq_theme and sq_ft are shared with our subdomains so docs and the dashboard follow the same settings. Our real user monitoring also stores a session in your browser; its keys are listed under the SDK below.
Third-party tags on our marketing sites
| Provider | Category | Purpose |
|---|---|---|
| Google Analytics 4 | Analytics | Measures which pages are visited and where visitors come from. |
| Google Ads | Advertising | Measures sign-ups that follow an ad. |
| Microsoft Clarity | Session recording | Records how visitors use our marketing pages, and produces heatmaps. Not loaded in the dashboard. |
| PromoteKit | Advertising | Credits the affiliate who referred you. Also loads in the dashboard, and the referral identifier is saved with your billing record if you subscribe. |
These providers set and control their own cookies. See their policies for details and opt-outs. docs.siteqwality.com loads none of these tags.
Forms. Our contact form and the forms on our “Is it down?” pages use Cloudflare Turnstile to block spam. It loads only when you start using a form, and Cloudflare then receives your IP address and browser details.
Our own real user monitoring
We use Site Qwality real user monitoring on our websites, docs and dashboard. It is first-party: data goes to our own infrastructure. It records pages viewed, referrer, clicks, performance, errors and request timings, with query strings removed from URLs. In the dashboard it also records your user and account identifiers, never your email address. Session replay records the page as you see it, masks form inputs and, in the dashboard, hides email addresses, long numbers and one-time secrets. It needs the Analytics category, and replay also needs Session recording. If you withdraw consent, the site deletes its session keys on your next page view.
Browser storage in the dashboard
The dashboard uses your browser’s local and session storage for:
- Sign-in (strictly necessary): your session token, sign-in and two-factor challenges in progress, and, for partners, which client account a tab is viewing. Clearing these signs you out.
- Preferences: interface state such as theme, sidebar, view modes, saved filters and your cached profile. Clearing these only resets the interface.
Storage set by our SDK on a customer’s website
When a website uses Site Qwality real user monitoring, our SDK can store the following first-party items on that website. None contains a name or email address.
| Name | Type | Purpose | Duration |
|---|---|---|---|
_sq_s | Cookie (or local or session storage) | Random session identifier and session state, shared across the tabs of one visit. | Session ends after 15 minutes idle or 4 hours; the cookie expires 4 hours after last use |
_sq_aid | Local storage | Random anonymous visitor identifier, so repeat visits count as one visitor. | 13 months |
_sq_w, _sq_act | Session storage | Tab identifier and active time in the tab. | Until the tab closes |
_sq_cfg_<app> | Local storage | Copy of the website’s SDK settings. Holds nothing about you. | No expiry; refreshed when older than 5 minutes |
_sq_bgt, _sq_bgr, _sq_rcap, _sq_cb | Local or session storage | Counters that cap how much data the SDK sends per session. | Replaced each session |
_sq_t | Cookie or storage | Tests whether storage works. | Deleted immediately |
_sq_optout | Local storage | Records that this browser opted out on that website. | Until the website opts back in |
sq_debug | Local storage | Turns on console logging, only when the page address contains sq_debug=1. | Until cleared |
The website operator controls the SDK, including whether it waits for consent. While consent is pending or refused, the SDK stores nothing except _sq_optout and sq_debug, and sends no data. When Global Privacy Control is on and the website honors it (the default for new applications), the SDK keeps its session in session storage, sets no visitor identifier and records no replay. The SDK does not read Do Not Track. To stop the SDK on a website, contact that website’s operator; our Privacy Policy explains why. Technical details are in the SDK documentation.
Managing cookies in your browser
You can also block or delete cookies in your browser settings. Blocking ours only resets your theme and language settings, but deleting sq_consent means we will ask for your choice again.
Changes and contact
We update this policy when the cookies or tags we use change, and revise the date above. Questions: privacy@siteqwality.com. See also our Privacy Policy, Subprocessors and Data Retention.