Paulo / Privacy
What we hold, and for how long
Short version: booking details only, kept for twelve months, never sold, and no card data touches this website.
What we collect
When you request a table, enquire about an event, order a voucher or apply for a job, we collect the details you type into that form: your name, contact details, and whatever you tell us about the booking. Nothing else is gathered from you on this site.
We do not run advertising trackers, we do not sell data, and there is no third-party analytics on these pages beyond aggregate visit counts that contain no personal information.
Why we hold it
- To confirm and manage your booking, and to contact you if something changes.
- To plan around allergies and access requirements you have told us about.
- To keep a record of private dining agreements and deposits.
- To consider job applications, and to keep them on file for six months.
How long
Booking records are kept for twelve months. Event agreements are kept for six years because they are financial records. Job applications are deleted after six months unless you ask us to keep them longer. Allergy notes are held against the booking only and are not built into a profile.
Who sees it
The restaurant team, and the booking system we use to run the diary. Payment for vouchers and deposits is taken by phone or in person through our card provider; the website never handles card details and none are stored here.
Cookies
This site sets no cookies of its own. Fonts are loaded from a third-party service, which will see your IP address as part of serving that request.
Your choices
You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Write to hello@paulorestaurant.com and we will respond within thirty days. If you are not satisfied with the answer, you can complain to your local data protection authority.
Changes
If this page changes materially, the date below changes with it. Last updated on publication of this demo.
This is placeholder text for a demo build. Before launch it must be reviewed against the jurisdiction the restaurant operates in and the actual booking and payment providers in use.