How We Use Cookies on QR-Verse
Last updated: 29 April 2026
This policy lists the cookies, browser storage and third-party requests QR-Verse uses. We measured them on the live site in three states: before you choose in the cookie banner, after Reject all, and after Accept all. Where something is set before you choose, the table says so.
1. What Are Cookies
Cookies are small files that a website stores on your device. Browser storage (localStorage and sessionStorage) works the same way. Both can keep you signed in, remember a choice or measure how the site is used.
2. How We Use Cookies
The cookie banner has four categories: Necessary, Analytics, Marketing and Affiliate. Necessary cannot be switched off. The column "When it is set" shows what happens before you choose, after you choose and after you sign in.
3. The cookies and storage we set
| Name | What it does | When it is set | How long |
|---|---|---|---|
| qrverse_cookie_consent | Remembers your choice in the cookie banner. | When you choose | 1 year |
| qrv_analytics_state, qrverse_anon_session_id | Tells the page whether analytics is allowed, and holds a random anonymous ID that ties your banner choice to a later sign-up. | When you choose | Until you clear browser data |
| geo_country, geo_city | Your country (and city, when your network provides it), used to attribute analytics. | Before you choose | 1 hour |
| qrv_attrib | Where you came from: landing page, campaign tags and referrer, so that a later sign-up can be credited. | Before you choose | 1 year |
| qrv_landing | The page you first landed on. Only our server can read it. | Before you choose | 30 days |
| _gcl_aw | Google Ads click ID, only when the link you came from carries one. | Only after you accept marketing, and only when the link carries a Google Ads click ID | 90 days |
| _ga, _ga_* | Google Analytics identifiers. | Only after you accept analytics | 400 days |
| dtCookie, dtPC, dtSa, dtLatC, rxvt | Performance measurement (Dynatrace): links the pages of one visit and how fast they load. | Only after you accept analytics | Until you close the browser |
| rxVisitor | Performance measurement (Dynatrace): a random visitor ID that recognises a returning browser. | Only after you accept analytics | 1 year |
| qr_uuid | An anonymous visitor ID on the pages that open after a QR code scan. | On pages after a scan | 1 year |
| qrv:wizard_started_anon | Remembers within the tab that you started the QR code creator. | In the QR code creator | Until the tab closes |
| sb-* | Keeps you signed in (Supabase). | After you sign in | While you are signed in |
| qrverse_active_team | Remembers the workspace you used last. | After you sign in | 1 year |
| qrv_aff_dismissed_v1, qrv_aff_session_count | Limits partner recommendations to three per session and remembers that you dismissed one. | Only if you allow Affiliate, on the page after a free scan | 1 day |
| qrv_create_v2_ab | The variant of the creator you were shown, when a creator test is running. | In the QR code creator | 90 days |
4. Third Party Cookies
Before you choose, and also after Reject all, every page contacts Sentry (error monitoring, legitimate interest), Cloudflare Web Analytics (static.cloudflareinsights.com) and Google: the Google tag loads and sends page-view pings in consent mode, with all storage denied and without Google Analytics cookies, to Google Analytics and to Google's advertising domain (pagead2.googlesyndication.com). Google Analytics sets its cookies and sends full measurements only after you accept analytics. After you accept analytics, the Ahrefs script (https://analytics.ahrefs.com, Singapore) also loads and counts which pages are visited; Ahrefs says it measures without cookies. Dynatrace performance measurement also switches on after you accept analytics: its script comes from our own domain and its measurements travel through our own server to Dynatrace; the cookies it sets are in section 3. Fonts are served from our own domain. Supabase sets session cookies only when you sign in. You can change your choice at any time with the "Cookie preferences" link in the footer.
5. More Information
Hopefully that has clarified things for you. If there is something that you aren't sure whether you need or not, it's usually safer to leave cookies enabled in case it does interact with one of the features you use on our site.
For more information, feel free to contact us via our Contact page.