Test environment · fictional bookings · booking messages and payments are off

Privacy Policy

How information is used in the current Save A Seat pilot.

1. Who handles your information

The Save A Seat operator and privacy contact are to be confirmed above. This draft describes the current app and identifies matters that need resolution before wider use. The operator must confirm which privacy laws apply and approve a final policy before public launch.

2. Information collected

  • Accounts: email, saved booking name and phone, customer-entered suburb or postcode, notification preferences, in-app updates and their read status, sign-up and sign-in information, account roles and optional two-step authentication information.
  • Bookings: restaurant, date, time, party size, contact details, requests, responses, offered times, changes, cancellations and booking history.
  • Restaurant operations: account memberships, restaurant applications, staff actions and internal booking notes. Restaurants can also enter waiting guests or walk-ins, including a name, optional phone, party size, table and visit status.
  • Listings: business contact details, menus, prices, opening times, uploaded photos/files and descriptions.
  • Support: messages, replies and request status.
  • Technical information: providers may process network addresses, device/browser information, request logs, authentication events and security diagnostics needed to host and protect the service.

Supabase handles sign-in and password verification. Do not put passwords, card details, identity documents or unnecessary sensitive information into support messages, notes or uploads.

Your suburb or postcode is required when setting up or saving your booking profile and is used to suggest restaurants in your area. Matching uses approximate suburb/postcode centres, not GPS or a street address. Your saved area is private and is not included in booking contact details shown to restaurants. Search-history preferences remain separate.

3. Where information comes from

Most information comes from you when you create an account, request a table, upload content or ask for help. A restaurant may enter information to manage a booking, a waiting party or a walk-in. Account and service providers supply information needed for authentication and operation.

You can browse published listings without a Save A Seat account. An account and booking contact details are needed for a direct Save A Seat request. You can decline optional notification preferences. Missing essential information may prevent the requested service.

Optional search memory

Optional search memory is off by default. If you enable Remember my searches, Save A Seat keeps up to 20 recent searches and their last-used times with your account, across the app and website, to suggest matching restaurants. Your saved searches are not shown to restaurants or other customers. Clear search history removes the saved searches while keeping the setting on. Turning the setting off also removes them. Account deletion removes this search memory from the application database; provider logs and backups follow their separate arrangements described below.

4. Why information is used

Information is used to run accounts, connect diners with restaurants, manage requests and visits, keep listings current, handle support, prevent misuse, maintain records and understand how the service is used.

Menu search matches text and selected filters. Booking tools check opening times, notice, capacity and table availability. Restaurant or authorised management users make decisions on direct requests and restaurant applications. External providers operate their own booking processes.

5. Who can see it

Your booking name and phone are shared with the relevant restaurant when you send a direct request. Its authorised team can access the bookings or visits it manages. Save A Seat management can review operations, account access and support within its permissions. Customer accounts cannot browse other customers’ private bookings.

Published restaurant details, listed menu items and selected photos/menu files are available to visitors. Keep private information out of public listing content. An already-issued signed file link may remain usable until expiry even after a file is removed from display.

Information is also processed by service providers, including Supabase for database, authentication and file storage, and Netlify for website hosting and private-site access. Account-confirmation and recovery emails use the authentication service’s configured email delivery. [CONFIRM THE FINAL PROVIDER AND SUBPROCESSOR REGISTER]. Information may also be disclosed where legally required or needed to address a lawful security issue.

6. External booking providers

Now Book It, OpenTable and other restaurant booking websites have their own privacy policies. Clicking a booking link opens their service. Information you enter there is handled by that provider and the restaurant; their bookings are not currently copied or synced into Save A Seat.

Save A Seat records an aggregate count of external booking-link clicks. This is not a record of a completed external booking. The external website may receive ordinary browser/network information when opened.

7. Notifications and marketing

Save A Seat uses email for automatic booking notifications and does not send SMS notifications. Your phone number is shared with the relevant restaurant so it can contact you directly about your booking. Booking email sending is disabled in this pilot. Your email preference can be saved for later; it does not mean a message has been sent. Check My bookings for direct-booking updates. Account-confirmation and password-reset emails are separate from booking notifications.

The current pilot has no connected advertising-data sales or marketing campaign system. Before enabling a new messaging or marketing service, its provider, purposes, choices and any additional information handling need to be reviewed and disclosed.

8. Browser storage and discovery counts

The browser stores sign-in/session information, your chosen appearance and, if you use the browser-only demo, sample bookings and schedules. Other providers may use their own necessary cookies or storage for hosting and sign-in.

The app’s discovery counters count searches, restaurant views and external-link clicks by day. Those counters do not store search text or a visitor identifier. This does not mean that hosting or authentication logs contain no network or account information. [CONFIRM THE FINAL COOKIE AND PROVIDER-LOG INVENTORY].

9. Storage, access and overseas processing

We use account permissions and provider sign-in/storage controls to limit access. Restaurant uploads stay private until selected for an eligible published listing. People with staff access should use information only for authorised work.

Provider hosting, support or subprocessors may involve processing outside Australia. The final policy must identify likely recipient countries where practicable, after checking the actual projects, provider arrangements and access locations. [CONFIRM STORAGE REGIONS, OVERSEAS RECIPIENTS AND COUNTRIES BEFORE APPROVAL]. This draft does not promise that every copy stays in Australia.

10. Retention and deletion

The pilot does not yet have an automated retention timetable for all booking history, staff notes, visit records and operational logs. [CONFIRM RETENTION PERIODS, LEGAL REQUIREMENTS AND THE DELETION PROCESS]. These arrangements need to be implemented and checked before public launch.

For an eligible customer account, the deletion flow removes its sign-in/profile and associated support requests, cancels affected upcoming direct bookings shown in the confirmation, and clears booking contact fields. Some operational records and audit history can remain. Team or restaurant accounts require an access review first.

Deletion from Save A Seat does not delete a restaurant’s independent records, an external provider’s records, or browser-only demo data on another device. Any provider logs, caches or backups may have separate retention and deletion processes. [CONFIRM THOSE PROCESSES AND RESIDUAL IDENTIFIERS]. We do not promise instant removal of every copy.

11. Access, correction and complaints

You can update saved booking details and notification preferences in My account. For access to other information, correction, a deletion request or a privacy complaint, use the privacy contact above once confirmed. During the pilot, signed-in users can also use Help and support.

We may need to verify your identity using a proportionate process. The final process must explain how requests are assessed, when a response is due and the reasons and review options if a request is refused. [CONFIRM RESPONSIBLE PERSON AND RESPONSE PROCESS]. A non-account contact method must be available before public launch.

If a privacy concern remains unresolved, the Office of the Australian Information Commissioner explains the complaints it can consider and applicable steps and timeframes.

12. Changes to this policy

The approved policy will carry an effective date and version. Important changes to purposes, providers or choices will be explained where required. New data uses or permissions will not be treated as agreed merely because this draft has been made available.

Leave without saving?

You have unsaved changes. Keep editing to save them, or leave to discard them.