Cookie policy
Last updated: 2026-10-15
Cookies are small files a website stores in your browser; the browser's local and session storage are similar technologies, and the same rules apply to them. QR Boost uses very few: the technical ones it needs to work and the two identifiers of our own audience measurement. We don't use Google Analytics or any third-party, advertising or tracking cookies, so there's nothing to accept.
Technical cookies (always on)
They don't need consent because the service can't work without them.
| Cookie | Purpose | Duration |
|---|---|---|
__Host-sid |
Keep you logged in | Browser session, or 400 days if you choose to stay signed in |
otp_email, login_prefs |
Remember your email and preferences while you enter the login code | 15 minutes |
g_oauth |
Protect Google sign-in | 10 minutes |
lang |
Remember your language | 1 year |
We also keep your theme preference (light or dark) in your browser's local storage and, while you create a QR code before logging in, its settings (deleted when you close the tab).
Audience measurement (no consent needed)
To count visits, the website itself keeps two random identifiers in your browser that say nothing about you:
| Name | Where | Purpose | Duration |
|---|---|---|---|
qrb-visita |
Session storage (sessionStorage) | Count visits | Until you close the tab |
qrb-navegador |
Local storage (localStorage) | Count different people and how many come back | 13 months from creation; not renewed |
They're only used for QR Boost's audience statistics: they aren't combined with your account or any other data, aren't used for advertising and aren't shared with third parties, and the data collected is deleted after 25 months. That's why they're exempt from consent (art. 22.2 of the Spanish LSSI, as set out in the Spanish Data Protection Agency's January 2024 guide on audience measurement). Details in the privacy policy.
How to delete them
You can delete the cookies and identifiers at any time by clearing this site's data in your browser settings. If you delete the session cookie, you'll need to log in again.