RezaCards

Privacy Policy

Version 1.1 · Last updated 1 October 2026

This explains what we collect, why, who else sees it, and how to get rid of it. We have tried to write it so you can actually read it. If anything here is unclear, email us and we will explain it properly.

There is a shorter, friendlier summary at Your data. This page is the full version, and it is the one that governs.

The short version

  • You do not need an account to collect stamps. If you are a customer, the only thing we ask for is your first name, and you can skip it.
  • We do not track you. There is no Google Analytics, no advertising pixel, no third-party tracker anywhere in this product.
  • We do not sell your data, and we never will.
  • Your café can send you the occasional offer. You can switch that off from your own card, and it stops immediately.
  • Ask us to delete your data and we will, within 30 days.

Who we are

RezaCards is a digital loyalty card. It is operated by Ali Reza Rasooli, Auckland, New Zealand, at rezacards.com (the site is also reachable at utoorder.com, our previous address). In privacy law we are the “agency” or “data controller” responsible for the information described here.

Your café is responsible for its own decisions about how it uses its loyalty program, including what messages it sends you. We are responsible for the platform underneath it.

Email rasouli9ali@gmail.com. We answer within 30 days, and usually much sooner. Ali Reza Rasooli, Auckland, New Zealand. We will give you our full postal address on request.

If you are a customer, this is everything we hold

It is a short list on purpose. We do not ask for your email address, your phone number, a password, or your date of birth, because a loyalty card does not need them.

  • Your first name (optional)

    Why we have it
    So the café can greet you by name. You can leave it blank and still get a card.

  • Your stamp count and reward status

    Why we have it
    It is the loyalty card. Without it there is nothing to show you.

  • A record of each stamp, with the date and which staff member gave it

    Why we have it
    It is the till-side audit trail that makes stamps hard to fake, and it is how a mistaken stamp gets undone rather than deleted.

  • Your card's code (the number behind the QR)

    Why we have it
    It is what the barista's scanner reads. Anyone holding it can see your card, so treat it like the card itself.

  • Which wallet you saved the card to, and a push token if you saved it

    Why we have it
    So your card updates itself the instant you are stamped, instead of you refreshing a page.

  • Messages and offers a café has sent you, and whether you switched them off

    Why we have it
    So we can show the message, stop sending when you say stop, and prove afterwards what your setting was.

One thing worth being plain about: the record of your stamps includes the date and time of each one. Put together, that is a history of when you visited a particular café. We keep it because it is what makes the card work and what lets a café undo a mistaken stamp, but you should know it exists, and you can have it deleted.

If you run or work at a café, this is what we hold

  • Your name and email address

    Why we have it
    To create your account and let you sign in.

  • Your password, stored scrambled (hashed) and never in readable form

    Why we have it
    So you can sign in. Nobody here can read it, including us.

  • A record that you asked us to delete your café, with the one-time code stored scrambled

    Why we have it
    So our deletion tool can prove the request came from you before it runs. Kept while it is valid (30 days), then cleared; if we act on it, kept until the café's anonymous shell is removed, at least 30 days later. Changing your password cancels an unused one.

  • Your café's phone number and address, if you add them (optional)

    Why we have it
    They are printed on your customers' cards so people can find you. Leave them out and nothing breaks.

  • Your IP address, briefly, when you sign in or a card is created

    Why we have it
    To stop password guessing and bulk fake sign-ups. These records are deleted after about a day.

If you add your café’s phone number and address, they are printed on your customers’ cards and are visible to anyone holding one. That is the point of them, but do not put anything there you would not want published.

Who else sees it

We use a small number of companies to actually run the service. They only ever process data on our instructions, and none of them is allowed to use it for their own purposes.

  • Supabase

    What they do
    Runs our database and file storage
    What reaches them
    Everything described above
    Where
    Sydney, Australia

  • Vercel

    What they do
    Runs and serves the website
    What reaches them
    Every request to the site, including IP addresses and server logs
    Where
    Sydney, Australia

  • Resend

    What they do
    Sends account emails
    What reaches them
    A café account holder's email address, for password resets only. No customer data is ever sent here.
    Where
    United States

  • Apple

    What they do
    Delivers updates to a card saved in Apple Wallet
    What reaches them
    Your device's push token. Apple is told a card changed, never what changed.
    Where
    Apple's global network

  • Google

    What they do
    Delivers a card saved to Google Wallet, and keeps it updated
    What reaches them
    Your first name, your stamp count, your card's code, and the café's details
    Where
    Google's global network

We do not sell personal information, we do not share it for advertising, and we do not hand it to anyone else unless the law requires it.

Where your data is kept

Our database and our servers are in Sydney, Australia. So although we are a New Zealand operation, your information is stored in Australia.

We are telling you this because we have to, and because you should know. Under principle 12 of the Privacy Act 2020, we may only send personal information overseas where it will be properly protected. Australia has privacy law comparable to New Zealand’s, and our agreement with our hosting provider contractually requires them to protect your information to the same standard we do.

If you are in the UK or the European Union, Australia is not covered by a UK or EU adequacy decision, so that same agreement includes the standard contractual clauses those laws require for an international transfer.

Messages from your café, and how to stop them

A café can send you an occasional message or offer through your card. If you have saved the card to Apple Wallet or Google Wallet, that can appear on your phone’s lock screen.

You can switch this off at any time. Open your card, choose Manage this card, and untick the offers box. It takes effect immediately, including for any message that is already being sent. Switching it off does not affect your stamps, and you can switch it back on whenever you like.

Each café is separate: turning messages off for one café does not turn them off for another. Until you delete your card, we keep a record of when you changed this setting, so that if you ever tell us we got it wrong, we can check.

A café can only message its own customers, no more than once every 14 days, and cannot buy access to anyone else’s.

Cookies and browser storage

There is no cookie banner on this site, and that is not an oversight. We do not use analytics, advertising or tracking cookies of any kind, so there is nothing to ask your consent for. The only things we store are the ones the service cannot work without, plus a couple of conveniences that never leave your device.

  • ali_session

    What it does
    Keeps you signed in to your café account
    How long
    30 days
    Who gets it
    Café owners and staff

  • uto_setup_hidden

    What it does
    Remembers that you dismissed the dashboard setup checklist
    How long
    1 year
    Who gets it
    Café owners

  • ali_admin

    What it does
    Signs in the platform operator to the internal admin console
    How long
    12 hours
    Who gets it
    The operator of RezaCards only

  • rc.wallet-nudge (browser storage, not a cookie)

    What it does
    Remembers that we already offered to save this card to your wallet, so we stop asking
    How long
    Until you clear your browser data
    Who gets it
    Customers

  • Scanner preferences (browser storage, not a cookie)

    What it does
    Remembers a till device's scan mode and whether sounds are muted
    How long
    Until you clear your browser data
    Who gets it
    Café staff devices

If we ever add analytics, we will update this page and ask for consent first, where consent is required.

How long we keep things

Being straight with you: at the moment we do not automatically delete much. Your card and its stamp history stay until you or your café ask us to remove them. The one exception is the short-lived records we keep to block password guessing and bulk fake sign-ups, which include IP addresses and are deleted after about a day.

We are working on automatic clean-up of inactive cards. Until then, you can remove your own information at any moment by deleting your card from its page — or ask us, and we will do it.

What remains after you delete a card. Your name, your stamp history and the record of messages sent to you are removed immediately. We keep an anonymous shell of the card — its random code, the café, and its total stamp and reward counts — because that is the only way to switch the pass off in your wallet; it names no one. If your card was in Apple Wallet, we keep your phone’s push address for up to 30 days so that switch-off can reach it, then remove it. Our database provider keeps rolling backups for about a week, after which deleted data is gone from those too. Your café keeps anonymous totals — for example that it gave out a certain number of stamps in a month, and how many stamps each member of staff issued per day, kept only for as long as that person still has a RezaCards account — none of which can be traced back to you.

If you run a café and close your account. You ask from your account page with your password, which gives you a one-time code to email us; we act only on that code plus a confirmation from the address on your account. We delete your account, your café’s details and images, staff accounts that belong to no other café, and every card your customers hold with you, exactly as if each customer had deleted their own (see above); once those staff accounts go, the daily staff totals no longer name them. An unnamed shell of the café and of each card stays for up to 30 days so the passes in your customers’ wallets can be switched off, then it is removed for good, totals included. Your café’s trade name stays on that shell for those 30 days, so the “this card was deleted” screen your customers see still says which café it was.

Your rights

You can ask us to:

  • Show you what we hold. We will send you a copy.
  • Correct something wrong. A misspelled name, for instance.
  • Delete it. You can do this yourself, from your card, in two taps (Manage this card, then Delete this card). Your card, your stamp history and your name are removed from our database immediately, and the pass in your wallet stops working — it shows as expired the next time your phone checks for updates, usually within minutes. It cannot be undone.
  • Stop messages. Also yourself, from your card, immediately.

For a copy or a correction, email rasouli9ali@gmail.com. It costs nothing and we will reply within 30 days. There is more detail, including what we need from you to find your card, at Delete or request your data.

If you are in the UK or the EU, you also have the right to object to processing, to restrict it, and to receive your data in a portable format. Ask and we will provide it.

Keeping it safe

Everything travels over an encrypted connection, and our database is encrypted where it is stored. Passwords are hashed, which means even we cannot read them. Only the café you joined can see your card, and only staff that café has added can stamp it.

The code behind your card’s QR works like a key: anyone holding it can view that card. Treat a screenshot of it the way you would treat the card itself.

No system is perfect. If we ever have a breach that could seriously harm you, we will tell you and the Office of the Privacy Commissioner, as the law requires.

Children

RezaCards is meant for general use and is not aimed at children. We do not knowingly collect information from children under 13. If you believe a child has a card and you want it removed, email us and we will remove it, no questions asked.

Complaints

Please come to us first, at rasouli9ali@gmail.com — most things are a misunderstanding we can fix quickly.

If you are not satisfied, you can complain to the New Zealand Office of the Privacy Commissioner at privacy.org.nz. If you are in the UK or the EU, you can complain to your own country’s data protection authority instead.

Changes to this policy

If we change something that matters, we will update the version and date at the top of this page, and where the change is significant we will tell café owners directly. Carrying on using RezaCards after a change means you accept the updated policy.

Contact us

Email rasouli9ali@gmail.com. We answer within 30 days, and usually much sooner. Ali Reza Rasooli, Auckland, New Zealand. We will give you our full postal address on request.