Privacy Policy
Effective 19 November 2026
This Privacy Policy explains how Qruuk ("Qruuk", "we", "us") handles personal data. Qruuk is a platform that lets businesses run digital loyalty cards, passes and tickets. It is written to meet the EU General Data Protection Regulation (GDPR).
Qruuk is operated by SangTech OÜ, registry code 14814447, Estonia. Contact: privacy@qruuk.com.
1. Two roles: controller and processor
Qruuk processes personal data in two distinct roles, and it matters which applies to you:
- For businesses that use Qruuk (merchants and their staff) we are the data controller of the account and login data described below.
- For end customers (people who join a loyalty program or hold a pass), the business is the data controller and Qruuk acts only as a data processor on that business's instructions. Requests about that data are handled by the business; Qruuk gives businesses the tools to honour them (see §7).
2. What we collect
Business accounts
- Name, email, and password (stored only as a secure hash).
- Business name and description, and the programs, QR codes and cards you create.
- Activity needed to run and secure the service: sign-in events, audit logs, IP address and device/browser for security and rate limiting.
- How you found Qruuk: the website or campaign you came from (for example "facebook" or another site's name), and, if another business invited you, its invite code. Also the language you signed up in, so our emails to you are in it.
- Your business's own invite code, which businesses that signed up with it, and any free period on your plan (from Qruuk, or as an invite reward).
Visitors to qruuk.com
- We count visits: per day, the page someone arrived on and where they came from (a campaign name or another site's name). Nothing about the visitor is kept: no cookies, nothing stored on the device, no identifier, no IP address with the count.
- Your IP address is used for a moment to stop abuse of the counter (rate limiting) and is deleted within an hour.
- If you use the form "Will Qruuk fit your business?": the email address, the website and the description you typed, and the answer we write for you. We use them to send you one email with a link and to show you the answer, and we send nothing else unless you start an account. When you open the link, we read the front page of the website you gave once (respecting its robots.txt) and send your description and that page's text, never your email address, to an AI model to write the answer.
End customers (processed for the business)
- The contact details a customer gives to join — typically first name and email, and optionally phone.
- Their card activity: stamps, entries, tickets used, rewards earned and redeemed.
- Whether they gave separate marketing consent, and when.
- What they bought and how they paid: the item, amount and date, the way of paying (cash, bank transfer, Stebby or online), the payment provider's reference for an online payment, and any refund. Qruuk never receives or stores card numbers or bank login details.
- If they ask for an invoice: the company name, registry code, VAT number and address they give for it.
- If they buy a membership that renews: the payment provider's token for the card or bank link they agreed to save, with a label such as "Visa •••• 4242", so the next payment can be taken. Never the card number.
- Class bookings, whether they came (check-ins and no-shows), places on a waitlist, and memberships with their renewal dates.
- Credit kept on their card (for example change from a cash payment) and how it was used.
- Emails sent to them in the business's name (a follow-up, a booking reminder, a membership reminder): which one, and when.
- If they add a card to Apple Wallet: an identifier of the wallet on their phone and a push token, so the card in the wallet updates when it changes. Removing the card from the wallet removes them. (Google Wallet needs neither: updates go to the card's pass at Google.)
3. Why we use it, and the lawful basis
- To provide the service (run programs, issue and validate cards) — performance of a contract.
- To secure the service (fraud prevention, audit, rate limiting) — legitimate interests.
- Emails to business owners about using Qruuk (getting started tips, a weekly summary, notes when a plan limit or a free period is near) — legitimate interests in helping you use the service you signed up for. Every one has a link to stop them, and you can turn them off in Settings → Emails from Qruuk; sign-in, security and billing emails are separate and still sent.
- Answering the fit check on qruuk.com — steps you asked for before a possible contract.
- Knowing how businesses find Qruuk (visit counts, where a sign-up came from, invites) and giving invite rewards — legitimate interests in understanding what works and keeping the promise of the invite.
- Program-operation data for end customers — the business's lawful basis for running its program; storing a contact to run a card is not a basis to market to them.
- Marketing to end customers — only with their separate, explicit consent, which they can withdraw at any time.
4. Marketing and consent
Marketing consent is captured separately from joining a program and is off by default. A customer who opts in can unsubscribe at any time via the link in any marketing message; we record the withdrawal and stop including them. Withdrawing marketing consent does not affect the operation of their card, and they still receive transactional messages (for example the link to their own card).
5. Sub-processors
We use a small number of providers to run the service:
- Google Cloud (Google Cloud EMEA Ltd) — hosting and database, in the EU (europe-north1, Finland).
- Resend — email: sign-in codes, password resets, card links, emails sent in a business's name, and Qruuk's emails to business owners described in §3. Where marketing sync is switched on, customers who gave marketing consent (name and email) are also kept in an email audience at Resend, and removed when they withdraw consent.
- Stripe — payments: Qruuk subscriptions, and online payments for businesses that connect a Stripe account (the business's own account).
- EveryPay (EveryPay AS, LHV Group) — online payments for businesses that connect their own bank's EveryPay e-shop account; Qruuk stores that account's API credentials encrypted and receives payment references and states, never card or bank data.
- OpenRouter — the AI setup assistant and the sorting of feedback. It receives the business description a merchant types in at sign-up, the messages a merchant sends through Send feedback in the app, and, for the fit check on qruuk.com, the description a visitor typed and the text of the front page of the website they gave, with email addresses, phone numbers and card-like numbers removed first. No end-customer data is sent on purpose.
- Cloudflare — DNS, hosting of the qruuk.com website, and receiving email sent to our @qruuk.com addresses, which it forwards to our mailbox.
- Apple and Google — only when a customer adds a card to Apple Wallet or Google Wallet: the card's details (program, first name, stamps or visits, the card's QR) go to their wallet, and updates are sent through Apple's push service or Google's Wallet API.
A business may also connect its own tools — a till (Erply, Loyverse), automation platforms (Zapier, Make, n8n), add-ons from our marketplace, AI assistants or its own systems through our API and webhooks. Those receive data only because the business set them up, and are chosen by the business. Questions: privacy@qruuk.com.
6. How long we keep data
- Business account data — for as long as the account is open. Closing the account can be undone for 30 days; after that, personal data in it (the team's logins, clients' names, emails and phone numbers, logs and connected-app keys) is erased. The business's bookkeeping records (invoices, credit notes, payments, payouts and the seller's legal details) are kept for 7 years after the end of the year the account was closed, as accounting law requires, and then deleted. The same applies to the accounting records of our own invoices.
- End-customer data — kept while the business's program runs and the business instructs us to keep it; erased when the business erases the customer, or 30 days after the business closes its account. Sales and payments then keep their amounts but not the customer's name or contact details. An invoice is a bookkeeping record: it keeps the buyer details printed on it and is kept as above.
- Aggregate, non-identifying activity — statistics that no longer identify a person (including the qruuk.com visit counts) may be retained to operate and improve the service.
- Where a sign-up came from and invite codes — with the business account; erased with its personal data, 30 days after the account is closed.
- Rate-limiting counters (which include an IP address) — at most an hour.
- Fit check requests from qruuk.com — 7 days if the emailed link is never opened, otherwise 30 days.
- Security and audit logs — 12 months, then deleted.
- Event and delivery logs (records of stamps, sign-ups and webhook deliveries kept to run integrations) — 30 days.
- The log of emails sent in a business's name (follow-ups) — 13 months, and erased with the customer.
- Records of sales and payments — kept with the business's account for its bookkeeping. Erasing a customer removes their name and contact details from them; the amounts stay. An invoice already issued keeps the buyer details printed on it, as bookkeeping law requires.
7. Your rights
Under the GDPR you have the right to access, correct, erase, restrict, and port your data, and to object to certain processing. You can also complain to your data protection authority.
- Businesses: you can download all of your account's data as a file, and close your account, in Settings → Your data (see §6 for what is kept after closing). Contact privacy@qruuk.com for anything else.
- End customers: please contact the business whose program you joined — they are the controller. Qruuk provides them one-click tools to export or erase your data, and a self-service unsubscribe for marketing.
8. International transfers
We host data in the EU. Where a sub-processor processes data outside the EEA, we rely on an adequacy decision or Standard Contractual Clauses.
9. Security
Passwords are stored only as hashes, transport is encrypted (HTTPS), API access uses scoped keys, outbound webhooks are signed, and every merchant action on a card is logged. No system is perfectly secure, but we take reasonable technical and organisational measures to protect data.
When a business asks us for help, a Qruuk administrator can open a read-only view of that business's account: what it has set up (programs, prices, schedule), totals and recent sales, and the messages it has sent us. That view does not show the names or contact details of the business's customers. Each time it is opened it is recorded in the audit log, and administrators sign in with a second factor.
10. Cookies and storage on your device
Qruuk stores only what's strictly necessary for something you asked for. We use no advertising, analytics or third-party tracking cookies, and the qruuk.com visit counter stores nothing on your device. Because of that, no consent banner is legally required, but here is the full list:
- Signed in (cookie
auth_token): a secure, HttpOnly session cookie so you stay signed in. - Your cards on this phone (cookie
qruuk_cards): for customers, the codes of the cards this device holds, so scanning a business's code opens your card. It holds no name or email. - Your bookings on this phone (cookie
qruuk_bookings): for customers, the places booked on this device (ids only, no names), so a booking is recognised at the door and can be cancelled. - Language (cookie
qruuk_locale, and the same in local storage): the language you chose. - Cookie notice seen (cookie
qruuk_cookies_ok): so the notice isn't shown again. - Sign-up in progress (session storage, cleared when the tab closes): what you typed in the sign-up form (never the password) and the email waiting for its code, so going back doesn't lose them.
- Back button (session storage, cleared when the tab closes): where you were on a page, so going back returns you there.
- Counter settings (local storage, for businesses and staff): the Counter's last mode and card type, and whether you dismissed the "install the app" tip.
11. Changes
We may update this policy; we will change the effective date above and, for material changes, notify account owners by email.
12. Contact
Questions or requests: privacy@qruuk.com. The Estonian supervisory authority is the Data Protection Inspectorate (Andmekaitse Inspektsioon).