Privacy notice

Who is responsible

G-SQUARE.AI LTD, trading through Dinner Picker, decides why and how account, restaurant relationship, directory and service-analytics information is used and acts as controller for that processing.

Information we use

  • Account and relationship details such as name, email, telephone number, saved address or postcode, region, role, restaurant and sign-in history.
  • Restaurant listing content, claims, verification evidence, public food-hygiene register details, opening hours, structured menu items, prices, external links and accuracy records.
  • Publicly mapped restaurant email addresses, telephone numbers and websites held in our private prospect workspace, together with their OpenStreetMap source and observation date.
  • Connected support messages, operational notes, approval decisions and audit records.
  • Marketing choices, objections and the minimum suppression record needed to respect a do-not-contact request.
  • Discovery activity such as searches, result impressions, profile and menu views, and clicks on telephone, website, directions, Just Eat, Deliveroo or other external actions. A search identifier connects the steps in one discovery journey.
  • A restaurant rating you choose to submit. The score is linked to your shopper account so you can change or remove it and so we can limit duplicate or abusive ratings. Restaurant pages show only the combined score and number of ratings, not who rated.
  • An address, location or postcode entered for nearby restaurant search. Exact search text is used to find results; behavioural events retain only an approximate location rounded to roughly one kilometre.
  • If you choose personalisation, a random first-party visitor identifier connects visits so we can learn your likely food and restaurant preferences, improve ranking and develop recommendations. If you sign in, this history is linked to your account so your preferences can work across your devices. We do not use covert device fingerprinting.
  • Approximate country from trusted network headers, security logs and basic technical information needed to operate the service.

Dinner Picker has no consumer basket, food-order or food-payment record and does not receive card numbers or security codes for food purchases.

Sources and purposes

Basic restaurant names, general cuisines and locations come from OpenStreetMap under the ODbL. Publicly mapped business contact details may also be imported into a private prospect record for restaurant research, onboarding and carefully reviewed business-to-business contact; they are not added to the public Basic listing. Managed content comes from authorised restaurant representatives, and service records come from account and support activity. A Basic listing is not presented as restaurant-confirmed.

PurposeReason
Create accounts, review claims, publish listings and provide support.Provide the requested service and manage the relationship.
Research and approach eligible restaurants about managing their listing.Documented legitimate interests where appropriate, subject to subscriber classification, channel-specific marketing rules, preference screening and the right to object.
Keep menus and links accurate, prevent abuse and secure the service.Legitimate interests in a reliable and secure directory; legal obligations where applicable.
Measure searches, results, menus and external-link activity.Improve Dinner Picker using minimised first-party service statistics and the controls described below.
Publish customer rating totals and prevent rating abuse.Provide the feature you choose to use and maintain a trustworthy service.
Remember discovery activity across visits and personalise results or recommendations.Your choice. This history is connected only after you select personalisation and you can withdraw that choice.
Send optional promotional communications.Consent where required or another documented lawful route; you can object at any time.

Restaurant prospect contact

A public business contact is not treated as consent, proof of restaurant ownership or automatic permission to send marketing. Before first contact, we review whether the route and subscriber type are suitable, identify Dinner Picker, explain the source and purpose where required, and provide a simple way to object. Telephone campaigns must be screened against the relevant preference registers and our own suppression list.

If a mapped contact identifies a person rather than only a business, we provide the required privacy information no later than our first communication and normally within one month of obtaining it. Websites remain research routes unless a separate contact route has passed review.

Analytics and restaurant reporting

Dinner Picker records a random session identifier, searches, visible results and interactions so we can understand whether discovery works. Activity while you are signed in is associated with your account. If you choose personalisation, we also store a random visitor identifier in your browser for up to 12 months and connect activity across visits. We then connect that preference history to your account, including activity from before sign-in, so it can support better ranking, saved preferences and future recommendations across your devices. It is not assembled from your hardware or browser characteristics.

Campaign source and campaign name are linked to activity only when personalisation is enabled. Analytics does not collect passwords, support messages, payment data, IP addresses, full user-agent strings or exact customer coordinates in the product event ledger.

Restaurant-facing reports are aggregated. Restaurants do not receive customer identities or an individual customer activity feed.

Sharing

We use providers for hosting, databases, security, application delivery and postcode or location lookup. The current restaurant service is free and does not require payment details. Clicking an external restaurant or delivery-provider link sends you to that separate operator under its own privacy terms. We do not send it a Dinner Picker food order or payment record and do not sell personal information.

Retention

  • Active account, listing and support records are kept while the relationship continues and normally for up to 24 months after closure.
  • Raw discovery events are retained for up to 24 months for analysis, comparison and model development, then deleted or aggregated. A visitor identifier stored in your browser expires after 12 months unless refreshed with your continued choice.
  • Unconverted prospect records are reviewed or removed within 12 months of the last meaningful contact.
  • Approval, security and any historical billing records may be kept longer where needed for audit, accounting or legal claims.
  • Minimal do-not-contact records remain while needed to honour the objection.

Your choices and rights

Depending on the circumstances, you can ask for access, correction, deletion, restriction or portability, or object to processing. You can withdraw consent where it is used. We may need to verify identity before acting.

Cookies and local storage

The service uses a necessary signed session cookie for account/admin access and browser storage for your chosen search location and interface preferences. Basic service measurement uses an identifier that ends when the page closes.

If you select “Yes, personalise it”, local storage holds your choice for six months and a random Dinner Picker visitor identifier for up to 12 months. This lets us connect your searches and views across visits. Select “Privacy choices” in the page footer at any time to turn personalisation off and remove that identifier from the browser.

Changes

Material changes will be dated here and communicated where appropriate. Full operator and contact details will be published before wider onboarding.