Cookies we set
All of them are first-party and HTTP-only (not readable by scripts). The sign-in, workspace and guest cookies are only sent over HTTPS. None of them is used to track you across websites or shared with anyone.
| Name | Purpose | Duration |
|---|---|---|
cq_session | Keeps you signed in to your account. | 30 days, or until you sign out |
qw_oauth | Only while you continue with Google, Apple or Microsoft: ties the provider's answer to this browser (security codes for that one sign-in, and a promotional code you are about to redeem). | 10 minutes |
qw_onetap | Only when the Google One Tap prompt is offered: a one-time security code that ties Google's answer to this browser. | 10 minutes |
qw_oauth_pending | Only if a sign-in provider did not confirm your email address: lets the sign-in link we email you connect that provider in this browser only. | 20 minutes |
ws | Remembers which workspace you have open in the dashboard. | 1 year |
qrw_edit | Only after you make an editable QR code on the home page without an account: holds its secret edit key so you can change it from this browser, and moves it to your account when you sign up or sign in. | 400 days, or until it moves to your account |
qrw_edit_hint | Set together with qrw_edit, without any secret: tells the home page to show your editable QR code again. | 400 days, or until it moves to your account |
qrw_guest | Only in browsers that made a guest link before 20 November 2026: remembers those links so they can move to your account when you sign in. No longer set for new visitors. | 30 days |
lp_<link id> | Set on a password-protected link (on our domain or the link owner's custom domain) after the visitor enters the right password, so it is not asked again. Holds a token derived from the link, never the password. | 12 hours |
qwc_<workspace id> | Only on links whose owner added retargeting pixels: remembers whether the visitor accepted or refused them, so the question is not asked again for that owner's links. | 6 months |
These cookies are exempt from consent under article 22.2 of the Spanish LSSI and article 5(3) of the ePrivacy Directive because they are strictly necessary for a service you asked for. Blocking them in your browser stops sign-in, or the password-protected link, from working.
Following an ordinary QRlanza link or scanning a QR code sets no cookie at all (only links with retargeting pixels set the consent cookie above).
Google sign-in
When Google sign-in is enabled, only the sign-in and sign-up pages load Google's sign-in script (only if you are not signed in) to offer the One Tap prompt. That script sets two strictly necessary cookies on our domain: g_csrf_token, which protects the One Tap answer against forgery (session), and g_state, which remembers that you closed the prompt so it is not shown again too soon. Google may also read its own cookies on accounts.google.com to show the accounts you are signed in to. See the privacy policy.
Local storage
When you press "Make it editable" under a static QR code on the home page, the address you typed is kept in your browser's local storage under qrw_pending_editable, so the dashboard can offer it once you have an account. It is read only by QRlanza pages in your browser, is never sent to us by itself, expires after one day and is removed as soon as it is used or dismissed.
Tracking pixels added by link owners
When a link owner adds retargeting pixels (Meta, Google, LinkedIn, TikTok), we ask visitors for consent before loading them and store their choice for 6 months in a first-party cookie (qwc_…); Global Privacy Control and Do Not Track are treated as a refusal. The link owner is the controller of the data those pixels collect. Only if the visitor accepts, a short QRlanza page loads the owner's scripts before redirecting, and those providers may set their own cookies, governed by their policies. Links without pixels redirect directly and set no cookies.
More information
How we handle personal data is explained in the privacy policy. Questions: support@qrlanza.com.
Last updated 21 November 2026