BOOKINGDESK POLICIES

Privacy Notice.

How personal information is used when you visit BookingDesk, create an account or manage restaurant reservations.

Draft updated: 31 October 2026 · Effective date: [to be confirmed before accepting live payments]

1. Who is responsible for your information?

[Legal operator name — to be confirmed], trading as BookingDesk, is the data controller for account administration, service operations, support and our own business records. Contact ronshipio@gmail.com for privacy enquiries. The operator’s identity, establishment and address are awaiting confirmation above.

Each restaurant is the controller of the guest information it enters into BookingDesk. BookingDesk processes those records on the restaurant’s instructions to provide the service. Guests should first contact the restaurant about their booking or data rights; we can assist the restaurant with its request. [Operator to confirm the applicable data-processing agreement before live launch.]

2. Information collected and why

  • Account and sign-in information: email, user identifier, authentication information and, where supplied by your sign-in provider, profile information. Used to create accounts, sign you in, maintain access and prevent account misuse.
  • Venue information: restaurant name, address, phone number, opening hours and settings. Used to set up and operate your venue; this may be personal information for sole traders.
  • Guest and reservation records: names, phone numbers, optional email addresses, booking dates and times, party sizes, table assignments, statuses, booking histories, preferences, special requests and notes. Used to manage reservations and customer records for your restaurant.
  • Dietary and other sensitive notes: notes may reveal health or religious information. Do not enter unnecessary sensitive information. The restaurant must identify a valid UK GDPR Article 9 condition, such as explicit consent where appropriate, as well as an Article 6 basis; ordinary contract or legitimate interests alone is insufficient for special-category data.
  • Support correspondence: your email, messages and information you provide. Used to answer questions, handle complaints and assist with billing or privacy requests. Avoid sending passwords or unnecessary guest records.
  • Billing and access records: payment provider customer, transaction and subscription identifiers, selected plan, payment status and paid-period dates. Used to link purchases to your account and manage subscription or lifetime access. Paddle handles checkout payment details under its own privacy notice.
  • Technical and diagnostic information: service providers may process IP addresses, browser/device information, request details and error reports when delivering the service. Used for service delivery, troubleshooting and security. [Operator to confirm provider logging, collected fields and retention before launch.]

3. Legal bases

For our controller activities, we rely on performance of the account/service contract for account administration and delivering paid access; legitimate interests for proportionate troubleshooting, security and support; legal obligation where records must be kept or disclosures made; and consent where required for optional cookies or marketing. You may withdraw consent without affecting processing already carried out. We do not treat opening an account as consent to marketing.

Restaurants determine the lawful basis for their guest records and must provide their own guest privacy information. Processing on a restaurant’s behalf is limited to its instructions and applicable legal obligations.

4. Who receives information?

Bookings, customers, tables and restaurant settings are private to your business account; other restaurants using BookingDesk cannot access your records. Necessary access by service providers or the operator for service delivery and support is distinct from access by other restaurants.

  • Lovable Cloud and its infrastructure providers support hosting, authentication and storage. Any authorised support, diagnostics or analytics providers receive only information needed for their role. [Operator to confirm the current subprocessor list and any analytics/support services.]
  • Paddle, our Merchant of Record, receives information needed for product sales, subscriptions, payments, fraud prevention, tax compliance and invoicing. Paddle acts as a separate controller for its own payment processing: Paddle Privacy Policy.
  • Sign-in providers receive information needed for the sign-in method you choose. Google Fonts is loaded by the website and receives the connection information needed to deliver fonts.
  • Professional advisers, such as legal and accounting advisers, where necessary; authorities where legally required; and a business successor where lawful and subject to appropriate notice and safeguards.

5. International transfers

Providers may process personal data outside the UK or EEA. Where such a transfer is restricted, an applicable adequacy decision or appropriate safeguards are required, such as the UK International Data Transfer Agreement or UK Addendum to EU Standard Contractual Clauses, and EU Standard Contractual Clauses for EEA transfers as applicable. Contact ronshipio@gmail.com for transfer information.

[Operator to confirm provider locations, actual transfer arrangements and available safeguard copies before launch. No particular hosting country or executed transfer agreement is asserted by this draft.]

6. How long information is kept

Account and venue data are retained while needed to provide the service. Restaurants determine how long guest records are needed and can delete records using the existing controls. Support messages are kept only while needed to resolve enquiries and handle follow-up. Billing records may need longer retention for legal, tax or dispute purposes. Data should be deleted or anonymised when no longer needed, subject to applicable legal duties.

Cancellation of subscription renewal does not itself delete your account or guest records. Contact ronshipio@gmail.com for account deletion or retention questions. [Operator to confirm account-closure deletion times, support retention, statutory billing periods and backup/log expiry periods before launch.] No automatic deletion schedule is promised here.

7. Your UK GDPR rights

Subject to the conditions and exceptions in data protection law, you can request access, rectification, erasure, restriction of processing, data portability, and object to processing based on legitimate interests, including direct marketing. You may withdraw consent at any time. To exercise rights concerning your account, contact ronshipio@gmail.com. We may need proportionate information to verify your identity.

We will respond without undue delay and normally within one month. Where legally permitted for complex or numerous requests, the deadline may be extended by two further months, with an explanation within the first month. For restaurant guest records, contact the restaurant as controller.

You can complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint, or your relevant EEA supervisory authority. Contacting us first is welcome but not required.

8. Cookies and browser storage

Essential authentication/session information is stored in browser storage and, where applicable, cookies to keep you signed in and support secure account access. Clearing this information may sign you out. Your browser settings allow you to clear or block cookies and local storage; blocking essential storage can prevent sign-in from working.

No optional analytics or marketing cookie tools have been identified in the BookingDesk application code. Paddle checkout and sign-in services may use their own storage; consult their notices and controls. [Operator to confirm hosted-site and third-party cookie behaviour before launch.] Any future non-essential cookies requiring consent must remain disabled until consent is given, with a way to change preferences.

9. Security and your responsibilities

The operator is responsible for appropriate technical and organisational measures proportionate to the risks, including access controls and appropriate protection of personal information. BookingDesk’s account-scoped access controls separate restaurant records. Keep account credentials private, limit unnecessary personal information and report suspected unauthorised access to ronshipio@gmail.com.

No guarantee of absolute security, encryption specification, certification or security audit is made by this notice. [Operator to verify operational measures and incident-response arrangements before launch.]

10. Changes and contact

Changes will be posted here with an updated date. Material changes will be communicated where required by law. Privacy questions and complaints: ronshipio@gmail.com. The legal operator and service address must be confirmed in the details above.