1. What this policy covers
This policy covers the website at www.upiqrgenerator.online and the browser-based UPI QR code generator provided there. It describes information involved when you visit a page, fill in the form, create a QR, use a download or sharing feature, and how site analytics work. It also explains the limits of what we can see and what remains with your browser or payment provider.
UPI QR Generator is an independent tool for creating a payment request image. It is not a bank, a payment service provider, or a UPI app. We do not hold funds, start a bank transfer for you, or receive a transaction result. A payer completes a payment in their chosen UPI app, under that provider's own privacy terms. If you follow an external link from this site, the destination is governed by its own policy.
The site is intended for people who are legally able to use UPI payment services available to them. It is not designed to collect information from children. If you are using a shared device, remember that another person may be able to see what remains on screen or what you saved to the device after you leave the site.
2. Details entered into the generator
The form can ask for an optional payee or business name, a UPI ID, an optional payment amount, and an optional note. It also offers alternate address modes that accept a bank account number with IFSC, an Aadhaar number, or an Indian mobile number. These details are used by JavaScript in your browser to build a UPI payment link and draw a QR code. The generator does not submit those fields to our server for code creation.
The values stay in the page's current memory while you are working. We do not create an account for you, store a payment profile, or save the form to our database. Closing or reloading the page clears the form in normal use. Your browser, device, password manager, or extensions may have their own behavior, and we do not control those products. Avoid entering payment information on a device you do not trust.
We use simple input checks, such as checking that a UPI ID resembles a payment address and that an amount is a positive rupee figure. These checks do not confirm who owns an address. They also do not establish that a receiving account is active or that every UPI app will accept a particular address format. Before asking someone to pay, scan the finished QR with your own app and check the recipient details it displays.
3. What is inside a QR code or payment link
A generated QR image is meant to be read by another person's payment app. It necessarily contains the payment address and either the name you entered or the address used as a fallback display name. If you added an amount or note, those may be present in the encoded payment link too. The card preview also prints the payee name and address as readable text. Anyone who can access the image or link can potentially inspect that information, whether they received it from you, found it on a public sign, or saw it in a shared document.
This matters most with alternate address modes. A bank account number, Aadhaar number, or mobile number may be encoded into the QR even when the input is visually masked on the form. Do not use these modes if you are unwilling to disclose the underlying address to people who scan or inspect the code. A UPI ID can be a more suitable public payment address when one is available.
When you download a PNG, SVG, or printable card, the file is created in your browser and saved according to your browser's download settings. When you copy a payment link, it goes to your device clipboard. If you use your device's share sheet, the information goes to the app or person you select. We cannot remove a file, message, or printed code after you share it.
4. Information used to deliver the site
Like other websites, this site must receive a request from your browser to send its pages and assets. The hosting and network providers involved in delivering it may process technical data such as your IP address, browser and device information, the requested URL, request time, and security signals. Those records can be needed to provide the site, prevent abuse, investigate errors, or comply with applicable obligations.
We use Cloudflare Workers to host the website. Cloudflare may process request and security data as part of that service. The retention and handling of those infrastructure records depend on the provider's services and settings. The generator's payment form is separate from this ordinary page delivery: creating a code does not make a server request with the payee name, UPI ID, account number, Aadhaar number, mobile number, amount, or note.
We may review broad operational information such as whether the site is available and whether assets return errors. Such information helps keep the service usable. It should not be confused with access to your bank account or to payment outcomes; the site has neither.
5. Site analytics and session replay
The site loads Google Analytics 4 and Microsoft Clarity when a page opens. Google Analytics helps us understand visits and page use. Clarity provides aggregated interaction insights and session replay so we can see where visitors have difficulty using a page. There is no separate analytics permission prompt before these scripts run.
We do not intentionally send payment form values as analytics events. The generator form and displayed payment address are marked for masking from Clarity session replay. Even with masking, analytics providers may receive technical information about the browser, device, page, and interaction with the site during a visit. They may use cookies or similar technologies under their own terms. Their data practices and retention settings are described in the Google Privacy Policy and Microsoft Privacy Statement.
If you prefer to limit analytics, you can use browser privacy settings or extensions to block third-party scripts or cookies. Clearing cookies or site data may remove identifiers stored on your device, but it does not delete records a provider has already received. Review the linked provider policies for their data controls.
6. Search verification and indexing
The site includes verification tags for Google Search Console and Bing Webmaster Tools. These tags help establish site ownership with those services. They do not contain your payment form values. Search engines may crawl and index public pages, including the home, About, and Privacy pages, based on their own policies and our public site metadata.
The site publishes a sitemap and robots instructions so search engines can discover the three public pages. A public webpage can appear in search results even when you have never used the generator. The form values you type are not added to page URLs or the sitemap. Search verification tags are separate from Google Analytics and Microsoft Clarity. The tags help verify site ownership, while the analytics scripts load when you visit.
7. Your choices and data control
You can use the generator without making an account. To avoid sharing a sensitive payment address, choose a UPI ID that you are comfortable showing to payers and decide where you distribute the finished image. You can clear the form by refreshing the page and remove downloaded files or copied links from your own device using its normal controls. If you have printed a code, remove the printout when the address is no longer valid.
The site does not present an analytics permission prompt. You can use browser settings or extensions to block third-party scripts or cookies, clear stored site data, or limit tracking. These controls may affect how other sites work too. Blocking analytics does not prevent the technical requests needed to load the website itself.
Privacy rights can vary by location. Because the generator does not maintain user accounts or a payment details database, there may be no payment form record for us to access or delete. Data held by your bank, UPI app, browser, analytics provider, or hosting provider is subject to those services' own processes. For a disputed or missing payment, consult your bank or payment app rather than this tool.
8. Security, limits, and changes
We use standard web delivery practices and keep the QR generation process in the browser. No website can promise that every device, network, extension, or third-party service is risk-free. The most important payment safety step is still to check the recipient and amount in the payer's UPI app before authorizing a transfer. Receiving money never requires you to reveal your UPI PIN on this site.
We may update this policy if the site's features, service providers, or data practices change. The date at the top shows the latest version published here. If a material change affects analytics, we will describe it on this page. You can return to this page at any time through the footer.
If you want to learn how the generator works as a product, read the About page. If you are ready to create a payment QR, return to the generator. Keep a copy of the recipient details you intended to use so you can compare them with what your UPI app displays when you test the code.