Reva is a local rewards network for local businesses. To make that work we have to remember a little about you — like that you've scanned at Café Luna three times this month. We don't collect anything beyond what the product needs to function, and we never sell what we do collect.
1. Who runs Reva (data controller)
Reva is operated by the team behind revanetwork.net ("Reva", "we", "us"). For the purposes of the EU General Data Protection Regulation (GDPR), Reva is the data controller for the personal data described in this policy. If you need to reach a human about anything here — including any data request — write to contact@revanetwork.net. A founder reads every message.
The company that operates Reva: GORILA PRINT S.R.L., CUI 54248359, J2026016938001, Str. Rapsodiei nr. 1, ap. 35, Baia Mare, jud. Maramureș.
2. What we collect
If you're a customer scanning a QR
- A device identifier — a random ID generated the first time you open a loyalty card, stored as a cookie in your browser. It is not your name, your phone number, or your IP.
- Where a scan came from — when you scan for a stamp, we note the network address (IP), the city and rough area that network is in, its provider, and what your browser says about the phone: kind and, where given, model, screen size, language, time zone and whether it is on Wi-Fi or mobile data. We never ask for your exact location. We use these only to spot stamps taken without a visit, for example from a photo of the code. The business does not see them, and we erase them after 90 days.
- Your loyalty progress — how many stamps you have at each participating business, which rewards you've redeemed, and the timestamps of those events.
- Optional: email and display name — only if you tap "Save my card" to sync across devices. We use this to send you a magic login link, nothing else.
If you take part in the monthly leaderboard
- Your points — the points your confirmed stamps and bonuses earn (a first visit to a place, three places or three kinds of places in a month, a week streak, a reward used, a rating, a friend you invited), with the month and city they count for. They are worked out from your loyalty activity, never from what you bought.
- Your public profile, only if you join the board — a nickname and an avatar shown next to your points. The board never shows the places you visited, what you spent or when. You can leave at any time.
- Invitations — when a friend opens your invite link, we record which device invited which, so both of you can be credited when they get their first stamp.
If you enter a Reva giveaway on Instagram
- Your Instagram username — the one you type on the giveaway page, linked to your Reva account or to the device your cards are on.
- Your public comment on the giveaway post — username, comment text, the accounts you tagged and the time. We read the comments on Reva's own Instagram post through Instagram's official API, only to check the entry conditions.
- Story mentions of @reva.network — when you mention us in a story, Instagram notifies us with your username and the time; we use them to tick that step.
- Opening the post from the giveaway page — the time you tapped the link, which we treat as the like step.
- Checks against unfair entries — whether your stamp came in time, and whether two entries look like the same person (for example, an account and the phone its cards are on). Only Reva admins see these checks, and a person reviews them before any decision.
The page also looks at the browser name your phone sends (for example, that it is Instagram's built-in browser) to tell you where to open it. That is not stored.
If you turn on notifications
- A push subscription — an address issued by your browser so we can send you notifications, linked to your device or account, plus a record of which notifications we sent, so none is sent twice. You can turn notifications off at any time in your browser or phone settings.
If you're a business owner or admin
- Account info — email, hashed password, optional display name.
- Business info — name, category, logo, accent color, the rewards you set up.
- Aggregated analytics on your own customers — return rate, redemption stats, visit frequency.
Technical data
- Basic request data — IP address and request timestamps are processed transiently by our hosting provider to deliver the service and prevent abuse. We don't store IP addresses against your loyalty card.
- Usage statistics — we count page views and how fast pages load, with our hosting provider's analytics. It uses no cookies and does not recognise you from one visit to the next or across other sites.
- Error reports — when something fails on our servers, a technical report (what failed and on which page) goes to our error-monitoring provider, set up not to include personal details.
What we don't collect
- We don't collect your precise location. We never ask for GPS.
- We don't collect what you ordered, ate or drank. Where a business gives stamps by the value of the bill, the amount its staff enters is saved with that visit; nothing else from the till is.
- We don't share data between businesses. Café Luna can't see who scans at Oak Barber, ever.
- We don't use third-party advertising trackers. There's no Facebook pixel, no Google Ads pixel, no TikTok pixel.
Appointments. When you book at a place that takes appointments on Reva, we keep your name, phone number, email, the service, the time and whether you came. That place sees them so it can receive you, and we use them only to confirm, remind you of and manage that appointment.
Table reservations. When you reserve a table at a venue that takes reservations on Reva, we keep your name, phone number, email, the day and time, how many people are coming, the note or occasion you add, where you booked from (for example the venue's Instagram link), whether you said you're coming and whether you came. If you join a venue's waitlist for a full day, we keep your name, phone, email, the day, your group size and the hours that suit you, so we can email you if a table frees up. The venue sees these details so it can receive you; we use them only to confirm, remind you of and manage that reservation.
Your birthday (optional). In your wallet you can add the day and month of your birthday. We never ask for the year. If you add it, the venues where you have a card or a reservation can see that your birthday is near, so they can greet you or make you an offer. You can change or remove it from your wallet at any time.
3. Why we collect it — and the legal basis
Under GDPR every use of your data needs a lawful basis. Here are ours:
- To run the loyalty program you opted into — tracking stamps, delivering rewards. Legal basis: performance of a contract (GDPR Art. 6(1)(b)).
- Optional email & name for saving and recovering your card. Legal basis: your consent (Art. 6(1)(a)), which you can withdraw at any time.
- Leaderboard points and invitations — part of the loyalty program. Legal basis: performance of a contract (Art. 6(1)(b)). Showing your nickname on the public board is based on your consent (Art. 6(1)(a)) — you choose to join and can leave.
- Giveaways — checking the entry conditions, the draw and contacting winners, under the official rules you accept when you enter. Legal basis: performance of a contract (Art. 6(1)(b)).
- Push notifications. Legal basis: your consent (Art. 6(1)(a)), given in your browser.
- Appointments, table reservations and waitlists — booking, confirming, reminding you and letting the venue receive you. Legal basis: performance of a contract (Art. 6(1)(b)), the booking you ask for.
- Your birthday. Legal basis: your consent (Art. 6(1)(a)): you add it yourself and can remove it at any time.
- Security, fraud prevention, and anonymous aggregates for the business owner. Legal basis: our legitimate interest (Art. 6(1)(f)) in running a safe, functioning network — balanced so it never overrides your rights.
That's it. We don't profile you for advertising. The only score is the leaderboard points you can see yourself, and they decide nothing about you beyond your place on the board. We don't sell to data brokers. We don't train AI on your behavior.
4. Who can see what
- You — see everything that's yours, from the customer card screen and the rewards history.
- The business you scanned at — sees that you exist (as an anonymous device, or as the name you chose to attach), what you've earned at their location, when you last visited. Nothing about your visits to other businesses. For your reservations there, it also sees the booking details above, and, if you added your birthday, that it is near. Never your birthday year, which we do not have.
- Reva platform admins — a small internal team has access to operational logs to keep the platform secure. We don't look at individual cards casually; we look when something is wrong (abuse, bugs, fraud).
- Other customers — only your nickname, avatar and points, and only if you joined the leaderboard. If you win a giveaway, your Instagram username may be announced on Reva's Instagram account.
- Nobody else. Not advertisers, not data brokers, not your bank. We read from Instagram; we don't send your Reva data to it.
5. Sub-processors
We use a small number of trusted infrastructure providers to run Reva. Each only processes data on our instructions, and each is bound by a Data Processing Agreement (DPA) consistent with GDPR. We don't add a sub-processor that we wouldn't trust with our own data.
- Supabase — database, authentication, and storage. Holds your account data and loyalty records. SOC 2 Type II audited.
- Vercel — application hosting and delivery. Serves the Reva website and app, and transiently processes request data (including IP) to do so. SOC 2 Type II audited.
- Resend — transactional email delivery. Sends login links, email verification, and account notifications. Processes the recipient email address and message content only.
- GoDaddy — domain registration and DNS for revanetwork.net. Handles the domain name and DNS routing; it does not process customer loyalty data.
- Meta Platforms Ireland — Instagram. For giveaways we read comments and story mentions on Reva's own Instagram account through Meta's official API. That data comes from Instagram, where Meta handles it under its own privacy policy.
- Browser push services (Apple, Google, Mozilla) — deliver notifications to your device when you turn them on. They carry the encrypted message only.
- Google and Apple — only if you add your card to Google Wallet or Apple Wallet. The card's name, your progress and a card number are sent so the pass can be shown and kept up to date on your phone.
- Sentry — error monitoring. Receives technical reports of server errors so we can fix them; set up not to send personal details.
- Upstash — protection against abuse. Counts requests to stop automated misuse. What it holds are one-way fingerprints, not readable addresses, and they expire within minutes.
- Stripe — payments for business subscriptions. A business owner enters the card and billing details on Stripe's own page; Reva never sees or stores card numbers. Customers are not involved.
If we add or change a sub-processor in a way that affects your data, we will update this list and notify registered users as described in section 11.
6. Where your data is hosted
Reva is built for the European market and we keep data within the EU wherever possible — our database and email infrastructure are hosted in the European Union. Some providers (such as our hosting CDN) operate global edge networks; where any processing occurs outside the European Economic Area, it is covered by appropriate safeguards such as the EU Standard Contractual Clauses. We never sell or transfer your data to a third party for their own purposes.
7. How long we keep it
- Customer loyalty data — for as long as the program is active at that business. If the business closes, we delete the associated cards within 30 days.
- Account data — until you delete your account (or ask us to).
- Operational logs — kept for up to 30 days for debugging and fraud detection, then erased.
- Where a scan came from (network address, city, details of the phone) — kept for 90 days, then erased.
- Giveaway entries — kept for 6 months after the draw, for questions and disputes, then deleted. Winners' entries stay as the record of the prizes given.
- Leaderboard points — for as long as your card or account exists. Notification records — 12 months.
- Your birthday — until you remove it from your wallet, or until your account is deleted.
- Reservations and waitlist entries — kept as the venue's booking history while it uses Reva. You can ask us to delete yours at any time.
8. Your rights (GDPR)
Wherever you are, you have these rights with us. If you're in the EU/UK, they are guaranteed by law:
- Access — ask for a copy of everything we have on you.
- Rectification — fix anything that's wrong.
- Erasure ("right to be forgotten") — ask us to delete your account or a specific loyalty card. Email contact@revanetwork.net and we comply within 30 days (usually much faster). Some fully anonymized aggregates may remain — these can't be traced back to you.
- Restriction & objection — ask us to pause or stop a particular use of your data.
- Portability — get your data in a machine-readable format.
- Withdraw consent — anytime, no questions asked, for anything based on your consent.
To exercise any right, email contact@revanetwork.net with the right you're exercising in the subject line. We don't hide behind a form, and we don't charge for it.
Right to complain. If you believe we've mishandled your data, you can lodge a complaint with your local data protection authority. In Romania this is the National Supervisory Authority for Personal Data Processing (ANSPDCP). We'd appreciate the chance to fix it first — but it's your right either way.
9. Cookies
We keep on your device only what the service needs to work, plus one thing we ask you about first.
- Needed for Reva to work — keeping you signed in, the device ID your cards are tied to, and your language and light or dark choice. For a business's staff, also the link that lets them give stamps. No consent banner is required for these.
- Only if you say yes — when you arrive through a Reva ambassador's link, we ask whether we may remember that for 30 days, so the recommendation is credited to them if you sign up. If you say no, nothing is kept.
- Counting, not following — we count how many different devices opened each ambassador's link in a day. That is a number for the ambassador, not a record of what you do.
We use no advertising or cross-site tracking cookies.
10. Security
Account data and customer records are hosted on Supabase and Vercel — both SOC 2 Type II audited. We encrypt data in transit (TLS) and at rest. Passwords are hashed (bcrypt) and never stored in plain text. Access to production data is limited to a small admin team and logged. Reva does not process or store payment card numbers.
11. Children
Reva is not intended for children under 16. We don't knowingly collect data from them. If you're a parent and think your child has a Reva card, email us and we'll delete it on the spot.
12. Changes to this policy
If we change anything material, we'll email registered users at least 14 days before it takes effect, and pin a banner on the dashboard. We won't change retroactively to make things worse for you.