Privacy Policy
QRViz is designed to run primarily in your browser. QR content, design settings, uploaded logos, and optional saved presets remain on your device unless you intentionally export a file, create or share a link that exposes configuration in the URL, or otherwise share the result. We do not use user accounts or intentionally store your QR payloads on our servers. We do use Yandex Metrica to understand overall site usage, traffic sources, and product performance.
This Privacy Policy applies to visitors, users, and others who access or use QRViz and any related pages, tools, or resources on this site.
For privacy questions or requests, contact us at sergeissolod@gmail.com. If local law requires us to identify a specific legal entity or postal address, that information should appear in the site footer, legal notice, or contact section.
QRViz is a browser-based QR code generator. Its core functionality is local-first: the text, URLs, Wi-Fi data, contact details, event data, design settings, colors, shapes, frames, and uploaded logos you use to generate a QR code are processed on your device in the browser.
By default, we do not require account registration, and we do not intentionally send the QR payload itself to our servers for storage just to generate the code. This is a practical privacy benefit of the product architecture, but it does not make the final QR destination private once you choose to publish, print, or share it.
Depending on how you use the generator, local processing may include the QR content you enter, visual customization settings, uploaded logos or images used in preview or export, and optional presets or recent settings saved in your browser for convenience.
If your browser storage is cleared, local presets or saved settings may disappear. Because this information remains on your device unless you intentionally share it, its availability may also depend on your browser, private mode settings, extensions, and device-level storage behavior.
To make the generator easier to use, the site may store a limited amount of product state on your device, such as the last selected QR type, visual settings, consent preferences, or optional saved presets. This may use browser features such as localStorage, sessionStorage, or similar client-side storage.
This local browser storage is different from server-side storage: it is generally controlled by your browser and device. You can usually delete it through your browser settings.
Some generator features may let you reopen or share a QR configuration through a link that stores state in the URL. This is convenient, but it also has privacy implications.
If sensitive data is included in a shareable URL, that URL may be visible to anyone you send it to, may appear in browser history, may be captured in screenshots or support messages, and may be processed by analytics or third-party systems that can access the page URL. Do not use share links for secrets, passwords, private tokens, confidential contacts, or any data you would not want exposed through a link.
If you upload a logo or image to style a QR code, that file is intended to be handled locally in your browser for preview and export rather than uploaded to our servers as part of the normal generator flow.
When you export, download, print, copy, or otherwise share the resulting QR code or linked destination, you are intentionally distributing that result. At that point, privacy depends not only on the generator but also on where the file is stored, who receives it, and what the QR code opens after it is scanned.
We do not intentionally require you to create an account to use the core generator. We do not intentionally collect payment card data, identity documents, home addresses, or the contents of your QR payloads for server-side storage as part of the standard local generation flow.
We also do not intentionally include uploaded logos in publicly shareable generator links. You remain responsible for the content you encode, export, or distribute.
We use Yandex Metrica to understand how the site is used, including page visits, traffic sources, pages viewed, general usage patterns, technical diagnostics, aggregate performance, and product improvement metrics.
Depending on configuration, Yandex Metrica may process technical and usage data such as page URL, referrer URL, browser and device information, operating system details, interaction events, cookies, and browser-side identifiers or storage values related to analytics.
We use analytics to improve usability, measure demand, detect errors, understand which pages are useful, and support product decisions. We do not intend to use Yandex Metrica to transmit the actual content of your QR payloads, private messages, uploaded logo files, or secret values as custom parameters.
The site may use cookies or similar technologies for analytics and limited product functionality. Some analytics-related identifiers may also be stored in local browser storage rather than only in traditional cookies.
Where required by applicable law, optional analytics should be loaded only after the necessary consent has been obtained. In other jurisdictions, analytics may be used on another lawful basis permitted by local law. You can also limit or block analytics through browser settings, extensions, content blockers, or by declining optional analytics where a consent interface is provided.
Where data protection laws such as the GDPR or similar laws apply, we rely on one or more lawful bases depending on the context: your consent where required for optional analytics or cookies, our legitimate interests in operating, securing, and improving the site where permitted, and compliance with legal obligations where applicable.
The purely local processing that takes place in your own browser to generate a QR code for your requested action is generally part of providing the functionality you chose to use. If local law imposes a different or more specific requirement, that law controls.
We do not sell your personal information in the ordinary sense of selling data for money. We do not operate a user-data marketplace, and we do not intentionally disclose your locally generated QR payloads to our servers as part of normal browser-based generation.
However, we do use Yandex Metrica as an analytics provider. As a result, analytics-related technical and usage data may be processed by Yandex in connection with the service. If you open third-party destinations through your QR code, those third-party websites or apps will handle data under their own privacy practices.
Because analytics and internet infrastructure may involve providers, networks, and systems located in multiple jurisdictions, analytics-related data may be processed in jurisdictions outside your country. The applicable provider's contractual and legal framework may govern those transfers.
If a law applicable to your use requires additional notices, transfer safeguards, or consent mechanisms, those requirements should be understood as supplementing this policy.
We do not intentionally retain your QR payloads on our servers as part of the core local generation flow because the product is designed to run in the browser.
Local data stored in your browser remains there until you delete it, your browser removes it, or the underlying browser storage expires. Analytics retention may depend on Yandex Metrica settings, its retention practices, and applicable law.
Depending on where you live, you may have rights to request access to personal data, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about how your data is processed.
Because the core QR generation flow is designed to stay on your device, we may not be able to retrieve or reproduce locally stored QR content that never left your browser. For analytics-related requests that concern data we control, contact us at sergeissolod@gmail.com. We may need enough information to verify the request and understand which data or interaction it relates to.
The site is not intended to knowingly collect personal data from children in violation of applicable law. If you believe a child provided personal data to us through a contact channel or another non-local feature, contact us so we can review the situation and respond appropriately.
If local law imposes special consent or notice requirements for minors, those requirements may supplement this policy.
We take reasonable steps to reduce privacy risk through the product architecture, including keeping the core QR generation flow local in the browser whenever possible. But no website, browser environment, extension ecosystem, device, or internet transmission can be guaranteed to be completely secure.
You should avoid encoding or sharing secrets unless you are comfortable with the risk profile of the destination, the sharing method, and the people who may receive or scan the code.
We may update this Privacy Policy from time to time to reflect legal, technical, or product changes. The latest version will be published on this page. Last updated: 2026-03-27.
If a change materially affects how personal data is handled, we may provide additional notice where required by applicable law.