A stamp card stores a name, a mobile number, and visit history — nothing more
When a customer enrolls in a car wash's Waya loyalty card, the data collected at signup is a first name and a mobile number, plus whatever the card generates afterward — stamp or points counts, visit dates, and reward redemptions. There's no payment data stored on the card, no vehicle information beyond what the merchant might note manually, and no location tracking beyond the geofence trigger itself, which fires without Waya storing a continuous location history.
This is a plain-language explainer, not legal advice, but it's worth stating simply because customers occasionally ask what a car wash "knows" about them once they've scanned a QR code and joined. The honest answer is: enough to run a loyalty program, and not much more.
The one Waya-specific fact worth knowing: staff scan the data, Waya doesn't pull it automatically
Because Waya has no POS or till integration, no customer data flows automatically from a payment system into the loyalty card — a staff member scans the customer's card manually after each wash, and that scan is the only moment new visit data gets recorded. There's no background data collection happening between visits.
That also means a car wash owner controls exactly what gets asked at enrollment — Waya's standard form asks for a name and mobile number, and nothing beyond that is required to issue a card. If a merchant wants to know more about a customer (vehicle type, preferred service), that's a manual note on the merchant's side, not a Waya data field.
- Enrollment data: first name, mobile number — that's the whole form
- Visit data: recorded only when staff scan the card, never automatically
- No payment data stored on the loyalty card itself
- Geofence fires without Waya storing a continuous location history
The limitation, stated honestly: this isn't a compliance guarantee
This page describes what data Waya's loyalty card collects and how, in plain terms — it isn't a substitute for reading Saudi PDPL directly or consulting a lawyer if data handling is a specific concern for your business. A car wash operator responsible for broader customer-data practices beyond the loyalty card (CCTV, a separate CRM, staff records) should treat those systems on their own terms.
What Waya can state plainly: the loyalty card's own data footprint is small and purpose-limited — name, number, visit history — collected only at enrollment and at each staff scan, never pulled from an outside system.
A worked comparison: what different systems around a car wash might collect
The table below separates the loyalty card's data footprint from other systems a car wash might run, so it's clear what Waya is and isn't responsible for.
| System | Typical data collected | Automatic or manual |
|---|---|---|
| Waya loyalty card | Name, mobile number, visit/stamp history | Manual — staff scan required |
| Payment terminal / POS | Transaction amounts, card details (handled by the payment provider) | Automatic, but not connected to Waya |
| CCTV (if installed) | Video footage | Automatic, entirely separate from Waya |
What a customer sees and controls
A customer's own view of their data is the wallet pass itself — their stamp count, reward progress, and the messages the shop has sent them, all visible right on the card in their wallet app. There's no separate customer-facing dashboard or account to log into beyond what's already on the pass.
If a customer wants their card removed, they can delete it from their wallet directly, the same way they'd remove a boarding pass or a coupon — no request needs to go through the merchant for that action specifically, though a merchant should still know how to handle a direct data question if a customer asks one.
Where this fits into launching a program
None of this changes how you set up loyalty day to day — see the full car wash guide for the actual launch plan. This page exists to answer the data question plainly when it comes up, whether from a curious customer or your own due diligence before turning on a new program.
As with everything else on Waya: no SMS channel (data doesn't flow through a text-messaging provider), and the Android merchant app is in closed testing, so staff on Android manage the dashboard through the web version for now.
Answering a customer's data question in four steps
If a customer asks what a car wash "knows" about them, a short, honest answer covers it without needing a legal team on standby.
- Step 1: name the two data fields
Explain that enrollment only asks for a first name and mobile number.
- Step 2: explain how visit data gets recorded
Say plainly that a staff member scans the card by hand each visit — nothing is pulled automatically from a till.
- Step 3: point to the wallet pass itself
Tell the customer their stamp count and message history are visible right on the card in their own wallet app.
- Step 4: explain how to remove the card
A customer can delete the pass from their wallet at any time, the same way they'd remove any other pass.
Frequently asked questions
What customer data does a Waya car wash loyalty card collect?
A first name and mobile number at enrollment, plus stamp or points counts, visit dates, and reward redemptions generated as the customer uses the card. No payment data is stored on the loyalty card.
Does Waya automatically pull customer data from a car wash's till or POS?
No. Waya has no POS or till integration — a staff member scans the customer's card manually after each wash, and that scan is the only moment new visit data is recorded.
Is this page legal advice on Saudi PDPL compliance?
No — it's a plain-language explanation of what Waya's loyalty card stores and how. For compliance questions about your business's broader data practices, consult PDPL directly or a lawyer.
Can a customer remove their data from a car wash's loyalty program?
They can delete the card directly from their wallet app at any time, the same way they'd remove any other pass, since their stamp count and messages live on the card itself rather than in a separate account.