Reg en privaatheid
Privaatheidskennisgewing
Last updated 21 October 2026
Hierdie kennisgewing verduidelik hoe Giveamenu persoonlike data hanteer wanneer jy ons webwerf besoek, 'n restaurantrekening skep of administreer, ons kontak of 'n derdepartydiens koppel.
Wie is verantwoordelik
Giveamenu bedryf giveamenu.com en is verantwoordelik vir handelaarrekeninge, platformadministrasie, sekuriteit, diensverbetering, faktuuradministrasie, ondersteuning en sy eie bemarkingsaktiwiteit. Kontak ons by [email protected].
Vir bestellings, besprekings, restaurantkommunikasie en resensies wat by 'n restaurantwinkelfront ingedien word, besluit die restaurant gewoonlik hoekom die data gebruik word. Giveamenu verskaf die platform en verwerk daardie data vir die restaurant, behalwe waar ons dit moet gebruik vir platformsekuriteit, bedrogvoorkoming, wetlike nakoming of diensadministrasie.
Data wat ons hanteer
- Rekening- en besigheidsdata, insluitend name, kontakbesonderhede, aanmeldidentifiseerders, rolle, toestemmings, restaurantbesonderhede en ondersteuningsboodskappe.
- Restaurantinhoud, insluitend spyskaarte, pryse, beelde, promosies, plasings, ontwerpinstruksies en KI-gesteunde konsepte.
- Bedryfsdata, insluitend bestellings, besprekings, betalingsstatus, klantterugvoer, ouditgebeurtenisse en dienslogboeke.
- Toestel- en gebruikdata waar geaktiveer, insluitend toestemmingskeuses, bladsy- of kenmerkgebruik, benaderde tegniese diagnostiek en sekuriteitsgebeurtenisse.
- 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.
Hoekom ons data gebruik
Ons gebruik data om die diens te verskaf en te beveilig, gebruikers te staaf, restaurantwebwerwe te skep en aan te bied, handelaarinstruksies te verwerk, bestellings en besprekings te ondersteun, op ondersteuningsversoeke te reageer, rekords in stand te hou, misbruik te voorkom, aan wet te voldoen en die produk te verbeter. Afhangende van die aktiwiteit, is die basis uitvoering van 'n kontrak, stappe wat voor 'n kontrak versoek word, wetlike verpligtinge, wettige belange om 'n veilige diens te bedryf, of toestemming vir opsionele berging en bemarking.
Google-gebruikersdata
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.
Deel en internasionale verwerking
Ons deel data slegs waar nodig met die relevante restaurant, gemagtigde personeel, gasheer- en infrastruktuurverskaffers, betalings- en kommunikasieverskaffers wat vir die diens gekies is, KI-verskaffers wat gebruik word vir versoekte generering of onttrekking, professionele adviseurs en openbare owerhede waar wetlik vereis. Sommige verskaffers kan data in ander lande verwerk. Waar nodig, gebruik Giveamenu 'n toepaslike toereikendheidsmeganisme of kontraktuele voorsorgmaatreëls.
Retensie
Google Besigheidsprofiel-inhoud word vir nie meer as 30 kalenderdae in die kas gestoor nie. Opsionele winkelfrontgebruikgeleenthede word vir tot 400 dae behou sodat restaurante seisoenale prestasie kan vergelyk. Toestemmingsrekords word vir tot 400 dae behou sodat keuses gedemonstreer en geëer kan word. Ander rekords word slegs gehou vir so lank as wat nodig is vir die diens, die restaurantverhouding, sekuriteit, geskille, belasting, rekeningkunde en ander wetlike vereistes, en dan uitgevee of geanonimiseer.
Jou keuses en regte
Jy kan vra vir toegang, regstelling, skrapping, beperking, oordraagbaarheid, of beswaar teen sekere verwerking waar van toepassing. Jy kan opsionele koekietoestemming enige tyd onttrek deur Privaatheid en koekie-instellings te gebruik. Handelaars kan Google Besigheidsprofiel van winkelinstellings ontkoppel. Versoeke oor 'n bestelling, bespreking of restaurantkommunikasie moet gewoonlik eers na daardie restaurant gestuur word.
Kontak Giveamenu by [email protected]. Jy kan ook kla by die databeskermingsowerheid wat van toepassing is waar jy woon of werk, insluitend die Britse Inligtingskommissaris waar van toepassing.
Outomatiese gereedskap
Giveamenu gebruik KI om te help met spyskaartonttrekking, vertaling, beskrywings, beelde en webwerfkonsepte. Hierdie instrumente skep voorstelle vir hersiening. Giveamenu gebruik dit nie om uitsluitlik outomatiese besluite te neem met wetlike of soortgelyke beduidende gevolge oor restaurantkliënte nie.
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.