Legal

Cookie policy

QRwise only sets cookies that are strictly necessary for the service to work. We use no analytics, advertising or tracking cookies of our own, so there is no cookie banner.

Cookies we set

All of them are first-party, HTTP-only (not readable by scripts) and sent only over HTTPS in production.

NamePurposeDuration
cq_sessionKeeps you signed in to your account.30 days, or until you sign out
wsRemembers which workspace you have open in the dashboard.1 year
qrw_guestOnly 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 after the visitor enters the right password, so it is not asked again.12 hours

These cookies are exempt from consent under article 22.2 of the Spanish LSSI and the ePrivacy Directive because they are needed for a service you asked for. Blocking them in your browser stops sign-in from working.

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 QRwise 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

A link owner can add tracking pixels (Meta, Google Analytics 4, LinkedIn or TikTok) to one of their links. Only on those links, a short QRwise page loads the owner's scripts before redirecting, and those providers may set their own cookies. The link owner decides this and is responsible for any consent it requires. Links without pixels redirect directly and set no cookies.

More information

How we handle personal data is explained in the privacy policy. Questions: info@clariva.tech.

Last updated 20 November 2026