Independent design exercise · Fictional scenario · In development
The Loyalty Card on the Counter
What should a neighborhood café ask customers to share for a loyalty perk, and where does that information go after an order?
The setting
Café Lakay is a fictional neighborhood café. I’m using a proposed loyalty program to think through the information that might move between the café, its register and an online ordering service. This is not an assessment of a real business or its systems.
A small perk, a fair question
A loyalty card can be a friendly way to welcome regulars. But does a free coffee need a customer’s birthday, phone number or order history? I want to see what the café can offer with less information, and how it can be clear about what it does collect.
Following the information
I’m mapping the journey from joining the program to claiming a reward. Along the way, I’ll look at what information is truly needed, who can see it, how long it stays on file, and what customers deserve to know.
This is a fictional scenario, not a claim about a real café or the tools it uses.
What I’m building
- A simple map of how customer details could move between the café, its register and online orders.
- A short guide to what the program needs, what it does not and when the information should be deleted.
- A look at who can see the information, how it may be shared and what choices customers have.
- A sign up notice that explains the program in everyday language.
Scope and status
This is a fictional project I’m developing on my own. No real customer details, business systems or vendor claims are involved. I’ll add the map, review and sample notice when they are ready.