Privacy Policy
QRViz is designed to work primarily in your browser. The QR content you enter, your design settings, local presets, and uploaded logos are intended to stay on your device unless you intentionally export a file, publish the result, or create or share a link that exposes configuration in the page URL. We do not require user accounts for the core generator, and we do not intentionally store your QR payloads on our servers as part of the ordinary local generation flow. We do use Yandex Metrica to understand site usage, traffic patterns, product performance, and general demand.
This Privacy Policy applies to visitors, users, and others who access or use QRViz, including the generator, related use-case pages, guides, contact flows, and other resources available on this site.
For privacy-related questions or requests, you may contact us at sergeissolod@gmail.com.
QRViz is created and operated by Sergey Solod.
QRViz is a focused browser-based static QR code generator built to help people create clean, export-ready QR codes without unnecessary account friction, dashboards, redirect layers, or campaign-management complexity.
QRViz is designed as a browser-first QR code generator. In the ordinary product flow, the content you enter and the styling choices you make are processed in your browser on your device.
By default, the service does not require account registration and does not intentionally send your QR payload to our servers merely to generate the QR code.
This architecture improves privacy in practical terms, but it does not make the destination encoded in the QR code private once you choose to share, publish, print, export, or distribute it.
Depending on how you use the generator, local browser-side processing may include QR content such as URLs, text, email data, phone data, SMS content, Wi-Fi details, contact cards, event details, map data, payment-related references, and similar destination inputs.
Local browser-side processing may also include design settings such as size, colors, shapes, gradients, frames, logo placement, readability settings, export preferences, recent setups, and optional saved presets.
If your browser storage is cleared, if you switch devices, if you use restrictive browsing modes, or if your environment blocks local storage, locally saved presets or recent configurations may disappear.
To make the product easier to use, QRViz may store a limited amount of state on your device, such as the last selected QR type, design settings, local presets, recent setups, or consent preferences.
This may use browser-side technologies such as localStorage, sessionStorage, or similar client-side mechanisms.
That browser-side storage is generally controlled by your browser and device rather than by us, and you can usually clear it through your browser settings.
Certain generator features may allow you to reopen or share a configuration through a link that preserves the current QR content and design settings in the URL or through URL-based state.
That convenience has privacy consequences. If sensitive information is placed into a shareable link, that information may become visible to anyone who receives the link, may appear in browser history, may be included in copied URLs, may be captured in screenshots or support messages, and may be accessible to analytics, browser extensions, workplace monitoring tools, or third-party systems that can see the page URL.
You should not use share links for passwords, private tokens, secret credentials, confidential contacts, internal-only endpoints, sensitive payment data, or any other information 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 in the ordinary product flow.
Uploaded logos are intended to remain local to your device and are excluded from share links in the ordinary generator workflow.
When you export, download, copy, print, or otherwise distribute a QR code or the destination it points to, you intentionally move that result into the world outside the local generator. At that point, privacy depends not only on QRViz but also on where the exported asset is stored, who receives it, and what happens when the destination is opened after scanning.
We do not intentionally require user accounts to use the core generator.
We do not intentionally require server-side storage of your QR payloads in order to generate a standard static QR code in the ordinary browser-based flow.
We do not intentionally collect payment card details, identity documents, home addresses, or uploaded logo files as part of the normal local generation workflow.
We use Yandex Metrica to understand how the site is used, including traffic sources, page visits, page performance, feature demand, interaction patterns, general product usage, diagnostics, and aggregate product-improvement signals.
Depending on configuration, analytics technologies may process technical and usage information such as page URL, referrer URL, browser and device information, operating system details, on-page interaction events, cookies, and browser-side identifiers or storage values related to analytics.
We do not intend to use analytics to transmit the actual contents of your QR payloads, uploaded logo files, private messages, or secret values as custom analytics parameters.
QRViz may use cookies or similar technologies for analytics and limited product functionality. Some identifiers related to analytics or product state may also be stored in browser-side storage rather than only in traditional cookies.
Where applicable law requires prior consent for non-essential analytics technologies, such technologies should be activated only after the required consent has been obtained.
You may also be able to limit or block analytics through browser settings, browser extensions, content blockers, or by declining optional analytics where a consent interface is available.
We process information to operate the website, maintain and improve the generator, support usability, preserve core product functionality, understand demand, diagnose problems, prevent abuse, and protect the service.
We may also process information to respond to support requests, review bug reports, understand product questions, and improve the clarity of the site, guides, and generator experience.
Where necessary, we may also process information to comply with applicable law, respond to lawful requests, and protect rights, safety, and legitimate interests.
Where data protection laws require a lawful basis for processing personal data, we may rely on one or more lawful bases depending on context, including consent where required for optional analytics or cookies, 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 for the QR code you choose to generate is generally part of providing the functionality you requested, subject to any stricter requirement imposed by applicable law.
We do not sell personal data in the ordinary sense of selling data for money, and we do not operate a user-data marketplace.
We may use third-party providers for hosting, infrastructure, delivery, analytics, security, or similar operational needs. Those providers may process limited technical or analytics-related data to the extent reasonably necessary to operate and protect the service.
If you scan or publish a QR code that opens a third-party website, application, file host, payment destination, social platform, or other external service, that destination will process data under its own terms and privacy practices, not under this Privacy Policy.
Because analytics and internet infrastructure may involve providers, networks, and systems located in multiple jurisdictions, technical or analytics-related data may be processed in jurisdictions outside your own country.
Where applicable law requires additional notices, safeguards, transfer mechanisms, or consent with respect to such transfers, those requirements supplement this Privacy 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 primarily in the browser.
Local data stored in your browser remains there until you delete it, your browser removes it, or the relevant browser storage is otherwise cleared or 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 additional information about how your personal data is processed.
Because the core QR generation flow is designed to remain on your device, we may not be able to retrieve or reproduce locally stored QR content that never left your browser.
For privacy-related requests concerning data we control, contact sergeissolod@gmail.com. We may require enough information to verify the request and understand which interaction or data it concerns.
The site is not intended to knowingly collect personal data from children in violation of applicable law.
If you believe that a child has provided personal data to us through a contact channel or another non-local feature, contact us so that we can review the situation and respond appropriately.
We take reasonable steps to reduce privacy risk through the product architecture, including keeping the core QR generation flow local in the browser whenever reasonably possible.
However, no website, browser environment, extension ecosystem, device, local storage system, 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, the distribution context, and the people who may receive or scan the code.
We may update this Privacy Policy from time to time to reflect legal, technical, operational, or product changes.
The latest version will be published on this page. Last updated: April 9, 2026.
If a change materially affects how personal data is handled, we may provide additional notice where required by applicable law.