Privacy
4u Check is built to need as little about guests as possible.
| Data | Kept? |
|---|---|
| Guest name, phone or account | Not collected. There are no guest accounts |
| Card number | Never seen by 4u Check. The payment provider handles the card |
| Email or phone for a receipt | Only when the guest asks for a receipt to be sent, and only to send it |
| Details for a full tax invoice (name, email, optional TRN and address) | Only when the guest asks for a tax invoice. Encrypted, and erased once the request is resolved or after 30 days |
| Private feedback | A 1 to 5 rating and an optional comment, seen only by the restaurant |
| Orders and payments | Kept as the restaurant’s financial records |
Requests to see or delete data
Section titled “Requests to see or delete data”The operations team handles privacy requests from the admin console. A request can export the data held about a receipt or payment, or delete personal details while keeping the financial record the restaurant must keep by law. Deletion runs as a scheduled job and records what it removed. A legal hold pauses deletion when a dispute or investigation needs the data.
Where the rules come from
Section titled “Where the rules come from”The UAE Personal Data Protection Law is in force, but its detailed regulations are not yet issued. Restaurants in DIFC and ADGM fall under their own data protection laws. Privacy notices and consent text are set per restaurant to fit where it operates.

