Cookie policy
Last updated:
A cookie is a small file a website stores in your browser. QRZeta uses only the essential ones plus the advertising cookies that fund the free service.
1. Cookies we use
| Cookie | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
__Host-qs | QRZeta | Keeps you signed in to "My dynamic QR codes". Only set if you sign in. | 30 days of inactivity (max 90) | Strictly necessary |
__cf_bm | Cloudflare | Tells humans from bots and protects the site from attacks. | 30 minutes | Strictly necessary |
| Turnstile | Cloudflare | Bot check when you request an access code. Runs inside a challenges.cloudflare.com frame. | Session | Strictly necessary |
__gads, __gpi, __eoi | Google AdSense | Serve ads, cap how often you see each one and measure performance. | Up to 13 months | Advertising |
IDE, DSID, test_cookie | Google (doubleclick.net) | Personalized ads based on your visits to this and other sites. | Up to 13 months | Advertising |
Google may use other cookies besides these. The full list is at how Google uses cookies.
2. Consent
Strictly necessary cookies are required for the site to work and do not need consent. In the European Economic Area, the United Kingdom and Switzerland, advertising cookies are only used if you accept them in the consent notice; if you decline, Google may show non-personalized ads.
3. How to manage them
- Google personalized ads: Ads Settings.
- Other ad vendors: www.aboutads.info.
-
Your browser lets you view, block and delete cookies in its privacy settings. If you block
__Host-qsyou will need to request a code every time you manage your dynamic QR codes.
More about how we process your data in our Privacy policy.