Privacy notice

This notice explains how Giveamenu handles personal data when you visit our website, create or administer a restaurant account, contact us, or connect a third-party service.

Who is responsible

Giveamenu operates giveamenu.com and is responsible for merchant accounts, platform administration, security, service improvement, billing administration, support, and its own marketing activity. Contact us at [email protected].

For orders, reservations, restaurant communications, and reviews submitted to a restaurant storefront, the restaurant normally decides why the data is used. Giveamenu provides the platform and processes that data for the restaurant, except where we must use it for platform security, fraud prevention, legal compliance, or service administration.

Data we handle

• Account and business data, including names, contact details, login identifiers, roles, permissions, restaurant details, and support messages.
• Restaurant content, including menus, prices, images, promotions, posts, design instructions, and AI-assisted drafts.
• Operational data, including orders, reservations, payments status, customer feedback, audit events, and service logs.
• Device and usage data where enabled, including consent choices, page or feature use, approximate technical diagnostics, and security events.
• Google account information when you choose Google sign-in, Business Profile data when an authorised merchant connects a location, and reporting data when an authorised company operator connects Analytics, Search Console or Google Ads.

Why we use data

We use data to provide and secure the service, authenticate users, create and host restaurant websites, process merchant instructions, support ordering and reservations, respond to support requests, maintain records, prevent abuse, comply with law, and improve the product. Depending on the activity, the basis is performance of a contract, steps requested before a contract, legal obligations, legitimate interests in operating a secure service, or consent for optional storage and marketing.

Google user data

Google connections are optional and require an authorised user to start the connection and consent through Google. Signing in with Google does not by itself grant access to Business Profile, Analytics, Search Console or Ads. We request access in the context of the selected feature, not access to Gmail, Google Drive or a Google account password.

Google sign-in

When you choose Google sign-in, we use the Google account identifier, name and email address returned by Google to identify you, create or link your Giveamenu account and authenticate your session. These account details are retained with your Giveamenu account; you can request account deletion using the contact details below.

Google Business Profile for merchants

After a merchant grants access, Giveamenu can identify the connected Google account, list Business Profile accounts and locations the user is authorised to manage, and let the merchant select a restaurant location. For that location we may import reviews and eligible business information, and prepare menu updates, review replies, and promotion or news posts. A merchant must review and specifically confirm a preview before Giveamenu sends a change to Google.

Business Profile access and refresh tokens are stored encrypted and are not displayed to restaurant staff. Google-provided Business Profile content cached for performance is deleted within 30 calendar days. A merchant can disconnect Business Profile from store settings; this revokes the available token and removes cached Google content and local connection credentials.

Analytics, Search Console and Ads reporting

Giveamenu company operators can separately connect company-authorised Google properties and advertising accounts to the private company dashboard to understand website traffic, search visibility and marketing performance. These connections are for company reporting, not a grant of access to every restaurant or its customers.

• Google Analytics 4: the selected property identifier and aggregate daily sessions, active users and traffic-channel reports. We request read-only Analytics access.
• Google Search Console: the selected verified site and daily search clicks, impressions, click-through rate and average position, with search-query or page breakdowns where requested. We request read-only Search Console access.
• Google Ads: the selected customer identifier, optional manager identifier, currency and daily advertising cost, impressions, clicks and provider-attributed conversions. Google provides a broad Ads permission; our company reporting connector only reads fixed reports and does not create or change campaigns, budgets or ads.

We store the selected account identifiers, encrypted OAuth access and refresh tokens, authorisation and sync status, and report snapshots needed to display and refresh those reports. Connections are restricted to company staff with the relevant permissions and reports are not publicly displayed or exposed to unrelated stores. We do not request individual Analytics visitor profiles or Ads audience lists through these reporting connectors.

How Google data is protected and shared

We use Google API data only for the sign-in, Business Profile management or reporting feature for which access was authorised. Credentials are encrypted at rest, Google API requests use HTTPS, and application permissions restrict access. Google data is processed by our hosting and infrastructure providers to operate these features and may be accessed by authorised personnel for the feature, security, support or legal obligations. We do not sell Google user data, share it with advertising networks or data brokers, use it for surveillance or credit decisions, or send it to AI providers to train general-purpose models. The AI services described elsewhere in this notice do not receive Google API reporting data through these connectors.

Giveamenu’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google API Services User Data Policy.

Retention, disconnection and deletion of Google data

Company reporting credentials remain stored while a connection is active. Revoking a connection in the company dashboard removes its local credentials and currently published report and stops future scheduled reads. It does not itself revoke the Google-side authorisation or immediately delete historical sync records. Completed, failed or cancelled reporting runs are eligible for scheduled cleanup after 30 days; the latest published report remains until it is replaced or the connection is revoked. Business Profile cache retention is separately limited to 30 calendar days.

You can also remove Giveamenu’s access in your Google Account third-party connections settings. This stops future authorised access but does not automatically erase data already stored by Giveamenu. To request deletion of previously collected Google data, contact us using the privacy email below and identify the connection or account. We remove data that is no longer needed, subject to applicable legal and security recordkeeping; we do not promise that disconnecting deletes every historical record immediately. Manage Google Account connections.

Sharing and international processing

We share data only where needed with the relevant restaurant, authorised staff, hosting and infrastructure providers, payment and communications providers selected for the service, AI providers used for requested generation or extraction, professional advisers, and public authorities where legally required. Some providers may process data in other countries. Where required, Giveamenu uses an applicable adequacy mechanism or contractual safeguards.

Retention

Google Business Profile content is cached for no more than 30 calendar days. Optional storefront usage events are retained for up to 400 days so restaurants can compare seasonal performance. Consent records are retained for up to 400 days so that choices can be demonstrated and honoured. Other records are kept only for as long as needed for the service, the restaurant relationship, security, disputes, tax, accounting, and other legal requirements, then deleted or anonymised.

Your choices and rights

You may ask for access, correction, deletion, restriction, portability, or object to certain processing where applicable. You can withdraw optional cookie consent at any time using Privacy & cookie settings. Merchants can disconnect Google Business Profile from store settings. Requests concerning an order, reservation, or restaurant communication should normally be sent to that restaurant first.

Contact Giveamenu at [email protected]. You may also complain to the data protection authority that applies where you live or work, including the UK Information Commissioner where applicable.

Automated tools

Giveamenu uses AI to assist with menu extraction, translation, descriptions, images, and website drafts. These tools create proposals for review. Giveamenu does not use them to make solely automated decisions with legal or similarly significant effects about restaurant customers.

Optional Google Analytics

With analytics consent, Giveamenu uses Google Analytics 4 through Google Tag Manager for marketing, admin product use, and internal storefront performance. Google receives page/event information, pseudonymous browser identifiers, and device and connection information. We exclude form contents, account details, and order/payment identifiers. Advertising personalization is disabled. Optional Google requests stay off before consent, and you can withdraw using Privacy & cookie settings.

Google privacy policy