QRLynx Cookie Policy: Cookies, Storage and Tracking Choices

Last updated: October 7, 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.
Optional services include Microsoft Clarity for site-usage analysis. QRLynx uses Google Ads and Google Analytics for advertising and purchase measurement when enabled and when you allow Google measurement. Google ad personalization is kept off. Microsoft Advertising and Meta Pixel provide conversion and remarketing measurement under the separate optional-tag choice.
For visitors in the EEA, UK, and Switzerland, Microsoft Advertising and Meta Pixel do not load unless the visitor accepts optional tags.

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_google_measurement_v1`	Stores your separate Google measurement choice in a cookie and local storage.	Cookie: up to 1 year. Local storage: until changed or cleared.
`qrlynx_signup_measurement`	Short-lived, HttpOnly confirmation of a newly created account. It is checked before a signup measurement attempt and is not sent to advertising providers.	Up to 10 minutes

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 supports Microsoft Clarity for product-usage analysis, Google Ads and Google Analytics for advertising and purchase measurement, and Microsoft Advertising and Meta Pixel for conversion and remarketing measurement. Each tag also has a platform enable switch. Google measurement requires its own explicit choice, even if you previously accepted the general cookie banner. It can include page visits, ad click identifiers, registrations, purchase values and an opaque purchase identifier used to avoid counting the same purchase twice. Google ad personalization is kept off.

For visitors in the EEA, UK, and Switzerland, Microsoft Advertising and Meta Pixel do not load unless the visitor accepts optional tags. Declining optional tags does not disable account, QR creation, redirect, or billing features. This page will be updated if the active tracking configuration changes.

When enabled and allowed by the applicable consent choice, Microsoft Clarity may set first-party cookies such as _clck and _clsk, and third-party Microsoft cookies, to connect eligible public-page visits for heatmaps and session replay. In the EEA, UK, and Switzerland, Clarity requires an affirmative optional-analytics choice before it loads. Declining optional analytics keeps Clarity off. See the Microsoft Privacy Statement and our Privacy Policy for data use and retention.

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. Where optional tags are allowed, the separate Google measurement prompt lets you allow or refuse Google measurement. Use the Ad measurement choices button to change that Google choice. Refusing optional tags also prevents Google measurement. Changing a choice stops future application-controlled measurement; it does not remove data already received by a provider. 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.