QRever

Privacy Policy

We collect very little, on purpose.

This page is written to be read, not scrolled past. The short version: no IP addresses on scans, no tracking of your customers, no selling of anything to anyone.

Last updated: 12 June 2026

  1. 01

    What we collect, and why

    Account data. Your email address and a hashed password (or your Google identity if you sign in with Google). This exists so you can log in and own your codes. Free static codes need no account, so for those we collect nothing at all.

    Purchase records. Which product you bought, the amount, the currency, and the payment gateway’s order ID. We never see or store your card number, UPI PIN, or bank details — payments are processed entirely by Razorpay (India) or Dodo Payments (everywhere else).

    Your codes and pages. The destinations, labels, designs, and page content you create. This is your data; we host it.

    Scan analytics. When someone scans a paid code, we record the country, a coarse city, the device type (mobile, desktop, or tablet), the referrer, and a timestamp. That’s the complete list.

  2. 02

    What we never collect

    No IP addresses are stored for scans. Not hashed, not truncated, not “anonymized” — not stored. The country and city come from CDN edge headers and the IP is discarded.

    No precise location. City-level at most, and only coarsely.

    No fingerprinting. Device type comes from the user-agent string and nothing else.

    People who scan your codes are your customers, not our product. We do not build profiles of them, and we have nothing to sell about them.

  3. 03

    RSVP data on event pages

    If you publish an event page with RSVP enabled, guests submit a name and phone number. That data is visible only to you, the page owner. We collect no email and store no IP for RSVP submissions (an IP is used transiently for rate-limiting and then discarded).

  4. 04

    Who processes data on our behalf

    We use a small number of processors, each for one job:

    • Supabase — database, authentication, and file storage.
    • Razorpay — payment processing in India.
    • Dodo Payments — payment processing everywhere else.
    • Vercel — hosting and the edge network that serves redirects.
    • PostHog— product analytics on our own site (which features get used), not on your codes’ scanners.

    We do not sell data to anyone. We do not share data with advertisers. There are no advertisers.

  5. 05

    Cookies

    We use cookies for one thing: keeping you logged in (Supabase auth session cookies). There are no advertising cookies and no cross-site tracking cookies.

  6. 06

    Your rights

    Export. Every paid code has a one-click export — short ID, destination history, and full scan history. No request form, no waiting period.

    Deletion. You can delete any code permanently from your dashboard. To delete your entire account and all associated data, email us and we’ll complete it within 30 days.

    Correction and access. Email us for anything you can’t change from the dashboard.

  7. 07

    Data retention

    We keep your data for as long as your account exists, because your codes are sold as forever products. Purchase records are retained as long as required by tax law. When you delete a code or your account, the deletion is real — not a soft-hide.

  8. 08

    Changes to this policy

    If we change this policy in a way that matters, we’ll email account holders before the change takes effect. The latest version always lives at this URL, with the date below.

  9. 09

    Contact

    QRever is operated by Sanora Technologies. For anything privacy related: support@qrever.com.

See also: Terms of Service · The Promise