QR payloads are not saved as a cookie-based project history. The current build has no AdSense or Google Analytics tags. WordPress and preview functions may use their own functional storage.
2. QR tools and your input
The current QR generator, image reader and CSV tools do not use cookies or local storage to keep a saved-project history of your QR input, logo, uploaded QR image or CSV content. These tasks use browser memory while the page is open.
Downloading a file saves it through your browser or device's normal download function. That file is not a cookie and is not removed merely by deleting this website's cookies.
3. Functional website storage
WordPress authentication, administrative sessions and draft-preview functionality may use cookies or other storage to keep their session or preview state. These functions are separate from the QR payload itself.
Storage behavior can depend on whether you are signed in, whether a draft is being previewed, and the website configuration. No fixed list of cookie lifetimes is claimed here without a verified configuration-specific inventory.
5. Managing your choices
Your browser can show, restrict or remove stored website data. The exact controls depend on the browser. Removing functional cookies may sign you out or end a draft-preview session; it does not recall a QR code or delete files you have downloaded.
If an advertising-consent interface is introduced, it should provide the choices applicable to the services and visitors concerned. Browser controls and Google Ads Settings serve different purposes; neither is a substitute for a site's required consent handling.
6. Changes and related notices
Cookie and storage disclosures should be checked when authentication, advertising, analytics or other integrations change. See the Privacy Policy for the broader treatment of website requests and the Contact page for the current communication status.