Skip to main content

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

NameWhat it doesWhen it is setHow long
qrverse_cookie_consentRemembers your choice in the cookie banner.When you choose1 year
qrv_analytics_state, qrverse_anon_session_idTells the page whether analytics is allowed, and holds a random anonymous ID that ties your banner choice to a later sign-up.When you chooseUntil you clear browser data
geo_country, geo_cityYour country (and city, when your network provides it), used to attribute analytics.Before you choose1 hour
qrv_attribWhere you came from: landing page, campaign tags and referrer, so that a later sign-up can be credited.Before you choose1 year
qrv_landingThe page you first landed on. Only our server can read it.Before you choose30 days
_gcl_awGoogle 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 ID90 days
_ga, _ga_*Google Analytics identifiers.Only after you accept analytics400 days
dtCookieblg3p10p, dtPCblg3p10p, dtSablg3p10p, rxvtblg3p10pPerformance measurement (Dynatrace): links the pages of one visit and how fast they load. The names end in a short code that is specific to our application.Only after you accept analyticsUntil you close the browser
rxVisitorblg3p10pPerformance measurement (Dynatrace): a random visitor ID that recognises your browser during one visit. The name ends in the same application code.Only after you accept analyticsUntil you close the browser
dtCookieblg3p10p, dtSablg3p10p, rxvtblg3p10p, rxVisitorblg3p10p, rxvisitidblg3p10pPerformance measurement (Dynatrace): the agent also keeps its session data in the tab (session storage), under its own keys. Like the cookie names, these keys end in a short code that is specific to our application.Only after you accept analyticsUntil the tab closes
dtTAB_blg3p10pPerformance measurement (Dynatrace): gives the tab a random ID (session storage). Only after you accept analytics; before that the Dynatrace script is not loaded.Only after you accept analyticsUntil the tab closes
dtCFG_blg3p10p_29f86aefa162a1b9Performance measurement (Dynatrace): the Dynatrace script keeps its own settings in your browser (local storage), only after you accept analytics. They contain nothing about you. The name ends in our application code and an application ID. Removed when you withdraw your consent.Only after you accept analyticsUntil you clear browser data
dtCM_blg3p10pPerformance measurement (Dynatrace): the script's own note in your browser (local storage) that it was switched on after you accepted analytics. Whether it may measure is decided by your cookie choice, not by this note. It is removed when you withdraw your consent.Only after you accept analyticsUntil you clear browser data
sentryReplaySessionError investigation (Sentry Session Replay): identifies the replay session of this tab. Only a small share of visits is recorded, with all text and media hidden.Only after you accept analyticsUntil the tab closes
qr_uuidAn anonymous visitor ID on the pages that open after a QR code scan.On pages after a scan1 year
qrv:wizard_started_anonRemembers within the tab that you started the QR code creator.In the QR code creatorUntil the tab closes
sb-*Keeps you signed in (Supabase).After you sign inWhile you are signed in
qrverse_active_teamRemembers the workspace you used last.After you sign in1 year
qrv_aff_dismissed_v1, qrv_aff_session_countLimits partner recommendations to three per session and remembers that you dismissed one.Only if you allow Affiliate, on the page after a free scan1 day
qrv_create_v2_abThe variant of the creator you were shown, when a creator test is running.In the QR code creator90 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. The Dynatrace script loads only after you accept analytics: it then comes from a Dynatrace server (https://dok.js-cdn.dynatrace.com), which sees your IP address and browser but receives no cookies, and its measurements travel through our own server to Dynatrace; the cookies it sets are in section 3. Among the entries it then keeps in your browser, all listed in section 3, are dtCFG_ in localStorage (its configuration) and dtTAB_ in sessionStorage (an ID for the tab); they are removed when you withdraw your consent. Your browser sends nothing to Dynatrace until you accept analytics. After you accept analytics, Sentry Session Replay also records about 1 in 100 visits for error investigation, with all text and media hidden; its key is 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.