Cookie Policy
How QRLynx uses first-party cookies, browser storage, and optional third-party tags.
Last updated: July 29, 2026
Jorbox LLC operates QRLynx. This policy explains the cookies and browser storage used on qrlynx.com and QRLynx account pages. It also explains the optional analytics and advertising tags that the platform can support.
Summary
- QRLynx uses first-party cookies for sign-in, security, workspace selection, account preferences, and consent choices.
- Some interface settings and recent activity stay in your browser's local storage rather than in a cookie.
- Microsoft Clarity, Google Ads, and Microsoft Advertising tags are disabled sitewide as of July 29, 2026.
- Visitors in the EU, EEA, and UK are asked to accept or decline optional tags before those tags can load.
First-party cookies used by QRLynx
| Cookie | Purpose | Typical duration |
|---|---|---|
session_token | Keeps an authenticated QRLynx session active. This cookie is HttpOnly and is not available to browser scripts. | Up to 30 days |
is_logged_in | Lets the interface recognize that a session exists without exposing the session token. | Up to 30 days |
active_workspace_id | Remembers the selected personal or team workspace for signed-in users. | Up to 1 year |
qrlynx_cookie_consent | Remembers whether optional analytics and advertising tags were accepted or declined. | Up to 1 year |
qrlynx_sidebar and qr_list_view_mode | Remember account navigation and QR-list layout choices. | Up to 1 year |
qrlynx_dashboard_seen | Remembers whether the signed-in dashboard has already shown its first-visit state. | Up to 1 year |
qrlynx_last_login_method | Reminds the browser which sign-in option was selected most recently. | Up to 1 year |
qr_consent_[QR ID] | When a QR owner enables a consent screen and the scanner chooses to remember the choice, this cookie prevents the same consent screen from repeating for that QR. | Up to 30 days |
QRLynx protects account-changing requests by checking the request origin and content type. It does not set a separate CSRF-token cookie.
Browser storage that is not a cookie
QRLynx uses browser local storage for device-specific preferences such as theme, the cookie-consent choice, QR editor settings, and recent scanner history. These entries remain in that browser until the feature clears them, you clear site data, or the browser removes them. Browser storage does not follow you to another device.
Optional analytics and advertising tags
QRLynx can support three optional tags: Microsoft Clarity for product-usage analysis, Google Ads for conversion and remarketing measurement, and Microsoft Advertising for conversion and remarketing measurement. All three tags are disabled sitewide as of July 29, 2026. QRLynx does not use Google Analytics.
If an optional tag is enabled later, QRLynx applies the stored consent choice before loading it for visitors in the EU, EEA, and UK. Declining optional tags does not disable account, QR creation, redirect, or billing features. This page will be updated if the active tracking configuration changes.
Third-party services
Some third parties may use their own cookies or browser storage when you choose their service. This can include Google, Microsoft, LinkedIn, or Apple during OAuth sign-in, and Stripe during checkout or billing management. Their own policies control that third-party storage. Cloudflare Turnstile may also process browser and network signals when a form needs bot verification, but it is not used as an advertising tag.
Managing your choices
You can accept or decline optional tags from the QRLynx consent banner when it is shown. You can also clear QRLynx cookies and site data from your browser settings. Blocking the authentication or workspace cookies can sign you out or prevent account preferences from working. Blocking optional tags does not affect the core QRLynx service.
Changes to this policy
QRLynx may update this policy when cookie names, purposes, providers, retention periods, or applicable requirements change. The date at the top will change only when the policy receives a substantive update.
Contact
Questions about QRLynx cookies or tracking choices can be sent to support@qrlynx.com or through the QRLynx contact page. The broader handling of personal information is explained in the QRLynx Privacy Policy.
By Ahmad Tayyem · Last updated: