Cookie notice
Last updated: 24 August 2026
Template — needs legal review. This is a starting point drafted to match how the product actually works. Have a qualified professional review it before you launch or apply to AdSense.
QRFable uses as little browser storage as it can get away with. Here's exactly what's stored and why.
Strictly necessary storage
We store a single authentication token in your browser's local storage under the key `qrforge_token`. It keeps you signed in between visits and is removed when you log out. Without it, logging in wouldn't work.
This is local storage rather than a cookie, which means it is never automatically sent to any third party.
Advertising cookies
When advertising is enabled on the free-tier redirect interstitial, the ad provider may set cookies on that page to measure impressions and limit repeat ads. These are set by the provider, not by us.
This applies only to the interstitial page shown after scanning a free-tier dynamic code — not to the generator or your dashboard.
Analytics
We do not run third-party analytics or tracking pixels on the site. Scan statistics shown in your dashboard are derived from server-side redirect logs, not from cookies placed on scanners' devices.
Managing storage
You can clear site data at any time through your browser settings. Doing so will log you out but will not affect any QR codes you've saved.