QR2Call
Cookie Policy
Last updated: May 13, 2026
How We Use Cookies
QR2Call uses limited first-party cookies and local browser storage to keep the product working, remember display preferences, reduce abuse, and measure QR scan and action attribution.
First-Party Attribution Cookie
We may set a cookie named qr2call_visitor. It contains a
random identifier, not your name or phone number. On the server, we log
only a hashed version of that identifier so we can estimate repeat
visitors, scan activity, call-button clicks, website clicks, quote
clicks, and campaign performance.
Local Storage
The dark/light mode preference may be stored in your browser using local storage. This keeps the interface consistent when you return.
Session Cookies
If you sign in to the customer portal, QR2Call may set a secure first-party session cookie so you can stay logged in and access your QR links, analytics, and backlink controls.
hCaptcha
hCaptcha may use cookies or similar technologies to detect automated abuse and verify that a visitor is human. hCaptcha operates under its own privacy and cookie practices.
What We Track
For QR attribution, we may store the QR ID, campaign label, business phone number, optional tracking number, call target, clicked action, approximate location from hosting/CDN headers when available, device context, referrer, and timestamps. A call click does not prove a call was completed unless a connected call-tracking provider reports the completed call.
Your Choices
You can block or delete cookies in your browser settings. Some abuse prevention, analytics, preference, or attribution features may be less accurate if cookies are disabled.
Contact
Questions can be sent to info@mobily.io.