Key takeaways
- If the customer booked with you, you are the one who answers, within a month; the software supplier gives you the tool.
- Bookings are anonymised: name, phone, email and notes go, while date, time and party size stay for the statistics.
- For consents you keep a minimal proof: date, privacy notice version and answer, with email and phone turned into a code that cannot be reversed.
- The email leaves the offers list at once, and the request leaves one log row with the date and the number of rows changed, with no customer data.
- Emails, chats, phone contacts and spreadsheets outside the software have to be cleaned up by hand.
Sooner or later it happens: a customer who booked through your website writes "delete my data". You have one month to answer. Pressing "delete" is easy. The hard part is knowing what to remove, what to keep, and how to prove months later that you did it.
I have just built this page in LocalProAI, the website and booking software for local businesses that I develop. Here are the choices, because anyone who keeps a list of customers has to ask the same questions, even on an Excel sheet.
Who has to answer
If the customer booked with you, your business processes their data: you are the controller. The software provider is a processor. It gives you the tool and helps if you ask, but the decision and the answer are yours. If the request reaches the provider by mistake, it has to pass it on to you without delay.
In LocalProAI only the account owner can erase data. Someone with a staff login sees the page but not the button: it is the owner's choice and it stays with them.
Finding everything, even with one contact detail
The customer writes from their email, but maybe they booked leaving only a phone number. On the page you enter the email, the phone or both, and before anything is deleted you see the list of bookings and consents found. Phone numbers are compared by their digits only, with or without +39, because the same person writes them in different ways.
The tricky case is consents left without an email. The booking form saves them together with the booking, a few milliseconds apart. So they are matched to that customer only if they come from the same IP address within 10 seconds of the booking, and never if they carry someone else's email: two customers on the same Wi-Fi share an IP. If another booking without an email came from the same IP in the same window, the software leaves those rows as they are. Better to leave one IP address behind than to delete someone else's proof.
Bookings: the name goes, the numbers stay
Bookings do not disappear, they are anonymised. The name becomes «Cliente cancellato» ("Deleted customer"), and phone, email, notes and IP are emptied. Date, time, party size and status stay. The month's figures still add up, and those rows no longer say who the customer was.
This is the point to check in any booking system. If deleting a customer also wipes their history, the year's numbers change. If the bookings stay with the name on them, you have not deleted the data.
Consents: keep a minimal proof
Here two needs pull in opposite directions. The customer asks you to delete everything. But if one day they dispute ever having said yes to offers, you need to show what they chose and when. The GDPR lets you keep what you need to defend legal claims (Article 17(3)(e)), and nothing more.
So the consent row keeps the date, the purpose, the privacy notice version and the answer, yes or no. Email and phone become a code computed with a secret key (an HMAC-SHA256), which cannot be turned back into the data. IP address, browser and referring page are deleted. If the customer disputes it, you compute the code again from their email and see whether it matches the stored one.
That row no longer counts as consent: the email leaves the marketing list at once, and sign-ups still waiting for confirmation are deleted. The minimal proof has an end too: it goes when the consent retention period runs out, 60 months by default.
One line records the request
After the erasure, one log line remains: who did it, when, and how many rows it touched. No customer data. It is there if someone asks you to prove that you answered. If the search finds nothing, you can still confirm: the request is logged with zero rows, which is still proof that you acted on it.
What the software cannot see
The page says it plainly: copies outside the panel are yours to delete. Booking notification emails, Telegram messages, the phone's contacts, the sheet on the counter. In backups the data goes when old backups are replaced, because nobody restores a whole backup to remove one person. Reviews on Google or TripAdvisor live on those platforms, and erasure is requested there.
A list to keep at hand
Whether you use LocalProAI, another system or a notebook, when the request arrives:
- Write down the date it arrived. The month to answer starts there.
- Look for the person everywhere. Booking system, email, chats, contacts, spreadsheets, by email and by phone.
- Remove name and contact details from bookings. The numbers for your statistics can stay.
- For consents, keep only the proof. Date, notice version, answer. No plain contact details.
- Take the person off marketing lists right away. Newsletter, WhatsApp groups, SMS lists.
- Answer the customer and note the answer. Date and what you did, without copying their data.
I wrote about proving consent for emails before: the article on email tracking pixels after the Garante's guidelines covers which choices to record so you can prove them.
This article is a practical read, not legal advice. For doubtful cases, ask your privacy consultant or DPO.