The short version
Making a QR code needs nothing from you but a UPI ID or account number, and the code is drawn in your browser. To build the matching pay link, what you type is sent to our server as you type, encrypted into the link, and not saved. Hosted pages are different: pay pages, invoices, payment requests and group collections are saved on our server so their links work, with a private edit link that only you hold. We never ask for your UPI PIN, bank password, card details or OTP, and we never see your payments.
What we collect, tool by tool
QR generator (UPI ID or bank account tab)
The QR is drawn in your browser from what you type: UPI ID (or account number and IFSC), and optionally a name, amount, note and quick amounts. As soon as you've typed a valid UPI ID, what you've entered is sent to our server, which encrypts it into a pay link and sends it back; this repeats each time you change a detail. The encrypted link also appears in your browser's address bar. We don't save these details. When someone opens the link, our server decrypts it to show the payment page, and again saves nothing. Anyone who has the link can see the details on that page.
Bulk QR codes, QR decoder, UPI ID checker, GST calculator, amount in words
These run entirely in your browser. Lists you upload, images you decode and IDs you check are not sent to us.
Bill splitter
Your UPI ID, name, each person's share and the note are sent to our server each time you change them, to create a sealed link for each person, and not saved.
Instalment planner, print page and readable links
The instalment planner (split-payment) sends your UPI ID, name, each part's amount and its note to our server each time you change them, to make a sealed link for each part, and doesn't save them. It keeps your plan in your browser (see below). An older split-payment link is decrypted on our server to fill in the form. The print page decrypts a sealed link on our server, or reads details given in its web address. Links from the bulk tool's links.csv, the pay-button generator and the UPI ID checker's buttons are readable: the UPI ID, amount, name and note are in the web address itself, so they appear in our hosting provider's logs and in the browser history of whoever opens them.
Hosted items: pay pages, invoices, payment requests and group collections
These are saved on our server so their links work. We store exactly what you enter, plus a few technical fields:
| Item | What we store |
|---|---|
| Pay page | Page type, title, bio, note, UPI ID, up to 4 quick amounts, address, timings, Google Maps link, WhatsApp number, up to 40 items with prices |
| Invoice | Invoice number, dates, your name or business, address, GSTIN and UPI ID; your client's name, contact and address; line items, tax mode, discount, notes, paid status, repeat setting |
| Payment request | Your name, UPI ID, amount, purpose, the payer's name and contact (if you add them), due date, paid status, repeat setting |
| Group collection | Title, organiser, UPI ID, amounts, due date, note, members' names and paid status |
| For every item | A random link code; created, updated and last-opened times; a view count; report count and review status; the time it was marked paid, if it was; the date its UPI ID was last changed, if it was; a one-way hash of your private edit link (we can't read the link itself); and a keyed, one-way hash of the creating connection's IP address, used to limit abuse |
Anyone with an item's public link can see what's on it. Anyone with its edit link can change it, including the UPI ID payments go to, or delete it. If the UPI ID of a live item is changed, its public page shows the date of the change. Keep your edit link private. We can't recover a lost edit link.
Reports. If someone reports a hosted page, we store the page, the reason, any details they write (up to 500 characters) and the time.
When you email us. We receive your email address, your message and anything you attach, and use them only to answer you. We don't keep them anywhere on this site: they sit in our mailbox.
Collected automatically. We keep a keyed, one-way (pseudonymised) hash of your IP address when you create a hosted item. We use it to limit how many hosted items one connection can create in an hour. Each time someone opens a hosted item's public link, we update its view count and last-opened time. We don't run analytics on the site, and we don't use advertising cookies.
Why we use it
We use personal data only to:
- generate the codes, links and pages you ask for,
- keep the service running and secure, including limiting abuse and acting on reports, and
- answer you when you contact us.
What we never collect
We never ask for and never receive your UPI PIN, bank password, card details or OTP. Nothing on this site should ever ask you for those; if a page appears to, it isn't us. Close it.
We don't see your transactions. Payments go directly from the payer's UPI app to the payee's bank. We have no visibility into whether, when or how much anyone paid.
What's stored in your browser
Some things are kept only on your device, in your browser's local storage:
| What | Why | If you clear it |
|---|---|---|
| "My items": the public and edit links of pages, invoices, requests and collections you made (up to 100) | So you can find and edit them again on this device | The list is lost. The items still exist; you'll need your saved edit links |
| Your invoice "from" details | So your next invoice starts filled in | You type them again |
| Your invoice number counter | So invoices are numbered in sequence | Numbering restarts; check your last number |
| Your instalment plan: UPI ID, name, note, parts, dates and which parts you ticked as paid | So your plan is still there when you come back | The plan is lost |
| Your theme choice | Light or dark display | It resets |
You can clear these at any time from your browser settings.
How long we keep it
| Data | Kept for |
|---|---|
| Pay link and bill-splitter details | Not stored |
| Hosted items (pages, invoices, requests, collections) | Until you delete them with your edit link, or until nobody has opened the public link for 12 months, when they're deleted automatically |
| Hashed IP addresses | As long as the item they belong to |
Who we share it with
ezyupi runs on hosting and database services, which handle the data described above for us.
We don't sell personal data or use it for advertising.
We may disclose information if the law requires it, for example to law enforcement investigating fraud.
How we protect it
Connections to ezyupi are encrypted (HTTPS). Sealed pay links (/pay?d=…) are encrypted and signed so they can't be read or altered; readable links, described above, are not. Edit links are long random codes, and we store only a one-way hash of each. No system is perfectly secure; we'll tell you promptly if something goes wrong.
If something goes wrong
If a breach affects your personal data, we'll tell you and the Data Protection Board of India, as the law requires, with what happened, what it means for you, and what we're doing about it.
Your rights
Under India's Digital Personal Data Protection Act, you can:
- ask for a summary of the personal data we hold about you and how it's used,
- ask us to correct, complete or update it,
- ask us to erase it where we no longer need it,
- withdraw consent you've given, as easily as you gave it,
- nominate someone to exercise these rights for you if you're unable to, and
- raise a grievance with us, and if you're not satisfied with our answer, complain to the Data Protection Board of India.
Because there are no accounts, we may need the item's link (or edit link) to find your data. Write to [email protected].
Children
ezyupi isn't intended for anyone under 18, and we don't knowingly collect their data. Where the law requires it, processing a child's data needs verifiable consent from a parent or guardian.
Changes
We'll update this page when this policy changes.