Privacy policy
Last updated:
This policy explains how Ez QR (ezqr.vn) handles your data when you use the website. In short: the QR content you enter is processed in your browser and is never sent to Ez QR’s servers; if you create an account we store your email address; the site shows Google ads, and Google uses cookies to serve them.
The QR codes you create
Everything you type into the generator (links, text, Wi-Fi names and passwords, contact cards, phone numbers, events…) and any logo you upload is processed in your browser. Ez QR does not send, store or see this content. A static QR code holds the content in the image itself, so it does not depend on our servers. To understand how the tool is used, your browser only sends an anonymous counter when you create or download a code: the QR type (for example Wi-Fi) and the download format (PNG, SVG, PDF) — never the content, and not linked to you or your account.
The only exception is the map in the location QR generator:
- Map images are loaded from OpenStreetMap’s servers (tile.openstreetmap.org), so OpenStreetMap receives your IP address and the map area you view.
- When you search for an address, the search text is sent to OpenStreetMap’s Nominatim service. OpenStreetMap’s policy: https://osmfoundation.org/wiki/Privacy_Policy
- When you use your current location, your browser asks for permission. The coordinates are only filled into the form on your device and are not sent to Ez QR’s servers.
Data stored on your device
- Language cookie (NEXT_LOCALE): remembers the language you chose. This cookie is necessary for the site to work.
- If you sign in: the session cookie and the sign-in security cookies (see Accounts).
- Browser storage (localStorage): remembers your QR style (colours, dot style, frame…) so it stays the same when you switch QR types. It stays in your browser only; you can remove it by clearing site data in your browser settings.
Advertising and Google cookies
Ez QR shows Google AdSense ads to keep the service free. This means:
- Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
- Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.
- You may opt out of personalised advertising by visiting Google Ads Settings: https://adssettings.google.com
- You can also opt out of other third-party vendors’ use of cookies for personalised advertising at https://www.aboutads.info/choices or https://www.youronlinechoices.eu
- How Google uses data when you use its partners’ sites: https://policies.google.com/technologies/partner-sites
Google’s ad code runs on the same page as the QR generator. Ez QR does not share your QR content with Google, but technically, code running on a page can read what is shown on that page. If what you enter is very sensitive (for example a Wi-Fi password), you can use an ad blocker or a private window.
For users in the European Economic Area, the UK and Switzerland, Google may show a consent message before using advertising cookies.
Dynamic QR codes and abuse reports
A dynamic QR code holds an Ez QR short link (ezqr.vn/…). The destination set by the owner is stored on Ez QR’s servers. When it is created or edited, and again daily, the destination URL is sent to Google Web Risk / Safe Browsing to check for phishing or malicious pages.
When someone scans a dynamic QR code, the server records the scan: time, device type, operating system, browser and referring page (if any). The IP address is not stored: the server only uses it for a few seconds to prevent abuse, to estimate the country and province/city (with a local DB-IP database, nothing is sent elsewhere), and to compute a hash that changes every day to count unique scans, then discards it. Referring pages are stored as a domain only. Detailed scans are kept for up to 90 days; daily totals are kept until the QR code is deleted.
When you send an abuse report, we store the report and your email if you provide it, only to handle that report.
Server logs and Cloudflare
Like any website, our server keeps technical logs of each request (IP address, time, page requested, browser). Logs are used only for operations, abuse prevention and troubleshooting, and are deleted after 14 days.
Traffic passes through Cloudflare, which speeds up and protects the site. Ez QR uses Cloudflare Web Analytics to count page views; it does not use cookies. Cloudflare’s policy: https://www.cloudflare.com/privacypolicy/
Accounts (optional)
You do not need an account to create static QR codes. If you sign in (to save QR codes and use dynamic QR codes), Ez QR stores:
- Your email address. When you sign in with Google we also receive your name and profile picture from your Google account; we never receive your password or access any other data in your Google account.
- Your sign-in session, kept in a secure (HttpOnly) cookie and in our database, expiring after 30 days. A helper cookie (ezqr_signed_in) only records that you are signed in so the menu shows correctly; it holds no personal data.
- When you sign in by email, the sign-in link is sent through the email service Resend (https://resend.com/legal/privacy-policy). The link expires after 15 minutes.
Account data is stored on Ez QR’s servers and used only to run your account. We do not sell personal data and do not send marketing emails. You can export your data or delete your account yourself in Account settings (see Your rights).
Your rights
Under data protection law you have the right to be informed, to access, correct and delete personal data about you, and to withdraw consent. Without an account, Ez QR stores almost no personal data about you; most of it lives on your own device and you can delete it yourself. If you have an account, go to My QR codes → Settings to download all your data (a JSON file) or delete your account: you are signed out at once, dynamic QR codes stop working, and all data is permanently deleted after 30 days. For anything else, email [email protected].
Ez QR is not directed at children under 16 and does not knowingly collect their data.
Changes and contact
When this policy changes, we update this page and the date above. For any privacy question, contact [email protected].
See also: Terms of use