Skip to content
MenüNow.
How it worksBenefitsPricingGet started DE Start now
How it worksBenefitsPricingGet started Deutsch Start now

Data Processing Agreement (DPA)

under Art. 28 GDPR · Version of 14 November 2026. The German version (AVV) is legally binding.

between the Customer (operator of the restaurant, hotel or resort, as stated at registration) – the “Controller” –

and Asick Ahamed Jabarulla, sole proprietorship trading as “MenüNow”, Asbeck Str 5, 21073 Hamburg, Germany, data protection contact: Asick Ahamed Jabarulla, info@menunow.de – the “Processor”.

§ 1 Subject matter, duration, roles

1.1 The Processor provides the Controller with the “MenüNow” software under the Terms of Service (the “Main Contract”). In doing so, it processes personal data on behalf of the Controller. This agreement governs the parties’ data protection rights and obligations under Art. 28 GDPR.

1.2 Processing on behalf of the Controller is described separately by function:

  • Annex A – Digital Menu (all plans including Free),
  • Annex B – Online Ordering (Trial and paid plans),
  • Annex C – Additional features (AI features, map and address services, statistics).

Each annex applies only to the extent the Controller actually uses or has activated that function.

1.3 Not processing on behalf is any processing whose purposes and means the Processor determines itself. For such processing MenüNow is an independent controller and its Privacy Policy applies. This includes in particular:

  • registration, account, contract management and billing of the Controller (owner and contact person data, subscription and payment data);
  • communication and support with the Controller;
  • server and security logs to defend against attacks and misuse, fix errors and keep the Platform stable;
  • measuring each business’s use of AI features for allowance and cost control (without guest data);
  • anonymised or aggregated analyses without personal reference;
  • the website menunow.de.

1.4 Guest payments via the Controller’s own Stripe account (Stripe Connect) are processed by Stripe under its own contract with the Controller and on its own responsibility; in this respect Stripe is not a sub-processor of the Processor (§ 6.5).

1.5 This agreement applies for the term of the Main Contract and beyond for as long as the Processor processes personal data on behalf of the Controller (§ 9).

1.6 In the event of conflict, this agreement takes precedence over the Main Contract in matters of data protection.

§ 2 Nature, purpose and scope of processing

2.1 Nature of processing: collecting, storing, organising, displaying, transmitting (e.g. to the kitchen display, driver view, email delivery), analysing, backing up and erasing data (Art. 4(2) GDPR).

2.2 The purpose, types of personal data and categories of data subjects are set out for each function in Annexes A to C.

2.3 Special categories: Free-text fields (e.g. order notes, questions to the AI assistant) may contain information on allergies or intolerances and thus health data (Art. 9 GDPR) if guests provide it voluntarily. The Platform does not specifically ask for such data.

2.4 Location of processing: The database and application run in data centres in Germany. Some sub-processors also process data in third countries; § 7 and Annex E apply.

§ 3 Instructions

3.1 The Processor processes the data only on documented instructions from the Controller, including with regard to transfers to third countries, unless required to do so by Union or Member State law; in such a case the Processor informs the Controller of that legal requirement before processing, unless that law prohibits this (Art. 28(3)(a) GDPR).

3.2 The instructions are set out in the Main Contract, this agreement and the settings the Controller makes in the Platform (e.g. activating Online Ordering or an AI feature). The Controller gives further instructions in text form. Instructions beyond the agreed scope of services may be charged separately if agreed in advance.

3.3 If the Processor considers that an instruction infringes data protection law, it informs the Controller without delay (Art. 28(3) second subparagraph GDPR) and may suspend execution until the instruction is confirmed or changed.

§ 4 Obligations of the Processor

4.1 Confidentiality: The Processor only uses persons who have committed themselves to confidentiality or are under a statutory obligation of confidentiality (Art. 28(3)(b) GDPR). Currently only the owner has access to production data.

4.2 Security: The Processor implements the technical and organisational measures under Art. 32 GDPR described in Annex D. It may develop them further provided the level of protection is not reduced; it documents material changes.

4.3 Assistance with data subject rights: The Processor assists the Controller with appropriate technical and organisational measures in responding to data subject requests (Art. 12–22 GDPR), in particular by providing access to, correcting, exporting and erasing the data of a specific person on request in text form within 14 days, where the Controller cannot do this itself in the Platform. If a data subject contacts the Processor directly, the Processor forwards the request to the Controller without delay and does not answer it itself unless instructed to do so.

4.4 Assistance with other obligations: Taking into account the nature of processing and the information available to it, the Processor assists the Controller with the obligations under Art. 32 to 36 GDPR (security, breach notification, data protection impact assessment, prior consultation).

4.5 Personal data breaches: The Processor notifies the Controller of a personal data breach without undue delay and no later than 48 hours after becoming aware of it, by email to the address stored in the account (Art. 33(2) GDPR). The notification contains, as far as known, the information under Art. 33(3) GDPR; missing information is provided in phases. The Processor takes immediate containment measures and documents the incident. Notifying the supervisory authority and informing guests are the Controller’s responsibility.

4.6 Records: The Processor maintains a record of processing activities under Art. 30(2) GDPR.

4.7 Purpose limitation: The Processor does not use data processed on behalf of the Controller for its own purposes, except for the security, error and anonymised analyses listed in § 1.3. Guest data is not used to train AI models, neither by the Processor nor by its AI sub-processors; the Processor only uses paid AI interfaces whose terms exclude training on customer data.

4.8 Contact: The contact for data protection matters is Asick Ahamed Jabarulla, info@menunow.de. No data protection officer has been appointed as there is no obligation to do so under Art. 37 GDPR and § 38 BDSG.

§ 5 Obligations of the Controller

5.1 The Controller is responsible for the lawfulness of processing, informing its guests (Art. 13 GDPR), obtaining any required consent (e.g. for marketing or health information) and safeguarding data subject rights.

5.2 The Controller only enters data in the Platform, or asks guests for data, that is necessary for the purpose. It does not use free-text fields to specifically collect special categories of personal data.

5.3 The Controller informs the Processor without delay if it discovers errors or irregularities in processing.

5.4 The Controller keeps data it must retain for legal reasons (e.g. order and sales data under tax law) in its own systems; the Platform is not an archiving system (§ 10.5 of the Terms).

§ 6 Sub-processors

6.1 The Controller gives general written authorisation for the engagement of other processors (Art. 28(2) GDPR). The sub-processors engaged when the contract is concluded are listed in Annex E and are deemed approved.

6.2 The Processor informs the Controller by email at least four weeks before engaging a new sub-processor or replacing an existing one and updates Annex E. The Controller may object in text form within this period for an important data protection reason. If the parties cannot agree, the Controller may terminate the Main Contract with effect from the date of engagement; fees paid in advance are refunded pro rata. In urgent cases (e.g. outage or security incident at a sub-processor) the period may be shortened; the Processor then informs the Controller without delay.

6.3 The Processor contractually binds each sub-processor to data protection obligations that substantially correspond to those of this agreement, in particular sufficient guarantees of appropriate technical and organisational measures (Art. 28(4) GDPR). The Processor is liable to the Controller for the sub-processor’s compliance.

6.4 Ancillary services without access to personal data processed on behalf of the Controller (e.g. telecommunications, external availability checks of the Platform without personal data, code hosting) are not sub-processing.

6.5 Services that the Controller itself agrees with third parties are not sub-processing, in particular payment processing via its own Stripe account (Stripe Connect). On the Controller’s instruction, the Processor transmits order data (ordered items, amounts, order number and – where available – the guest’s email address) to Stripe.

§ 7 Transfers to third countries

7.1 Personal data is only transferred to a country outside the EU/EEA if the requirements of Art. 44 et seq. GDPR are met, in particular on the basis of an adequacy decision (e.g. the EU-US Data Privacy Framework for certified recipients, Art. 45 GDPR) or appropriate safeguards (European Commission Standard Contractual Clauses, Art. 46(2)(c) GDPR).

7.2 The basis for each transfer is stated in Annex E. The Processor checks the Data Privacy Framework certification of US recipients at least once a year.

§ 8 Audits

8.1 The Processor makes available to the Controller all information necessary to demonstrate compliance with this agreement (Art. 28(3)(h) GDPR), in particular a current description of the measures in Annex D and – where available – certificates and audit reports of sub-processors.

8.2 In addition, the Controller may carry out audits, including inspections, itself or through an auditor bound to confidentiality who is not a competitor of the Processor. Inspections must be announced with reasonable notice (usually four weeks), take place during normal business hours and must not disrupt operations disproportionately. They take place no more than once per calendar year, unless there is a specific reason (e.g. a data breach) or a supervisory authority requires it. As the Processor does not operate its own data centres, data centres are audited by means of the sub-processors’ evidence. The Processor may charge reasonable compensation for its effort unless the audit reveals a material breach.

§ 9 Deletion and return

9.1 During the term: The Controller can delete menu content in the Platform itself. It may request deletion or export of order, guest and staff data in text form; the Processor completes this within 14 days.

9.2 Online Ordering ends, account continues (end of the Trial, cancellation or downgrade of a paid plan, switching off order acceptance): processing under Annex B for new orders ends. Order and guest data already stored continues to be stored on the Controller’s instruction and remains visible to the Controller until it requests deletion or the account ends. There is currently no automatic deletion.

9.3 End of the Main Contract: On request, the Processor provides the Controller with the data in a structured, commonly used and machine-readable format until 30 days after the end of the contract (§ 10 of the Terms) and then deletes all personal data processed on behalf of the Controller, unless Union or Member State law requires storage (Art. 28(3)(g) GDPR). This includes uploaded photos and files in the storage service (Annex E). For sub-processors that only process data temporarily (e.g. email delivery, AI requests), deletion follows their retention periods as described in Annex E.

9.4 Backups: Data in encrypted backups is not deleted individually but is overwritten in the regular rotation cycle of at most 60 days (Annex D, no. 3.3). Until then it is only used for restoration after an incident; if a backup is restored, data already deleted is deleted again.

9.5 On request, the Processor confirms deletion in text form.

§ 10 Liability

Liability is governed by Art. 82 GDPR. Otherwise, the liability rules of the Main Contract apply to the extent that Art. 82 GDPR does not conflict with them.

§ 11 Final provisions

11.1 Amendments and additions to this agreement must be made in text form. § 16 of the Terms applies accordingly to amendments; changes to Annexes D and E are governed by § 4.2 and § 6 respectively.

11.2 This agreement is concluded in electronic form (Art. 28(9) GDPR) when the Controller accepts it at registration or in the settings. It can be accessed at any time at menunow.de/en/dpa (German: /avv) and printed or saved as a PDF.

11.3 German law applies. The place of jurisdiction is Hamburg, to the extent permitted by law.

11.4 Should any provision be invalid, the remainder of this agreement remains valid.

Annex A – Digital Menu

Applies to: all plans including Free.

Purpose: providing and displaying the Controller’s menu to guests via link and QR code; account management by the Controller’s staff.

Data and data subjects:

Data subjectsData
Guests viewing the menutechnical connection data (IP address, time, browser and device details) to deliver the page; QR scan events only with time and table, without IP address or device identifier; the chosen language and, where applicable, display setting in the guest’s browser (local storage, no advertising cookies)
The Controller’s staffname, email address, role, password (hash only), login times
Persons shown in content, if anye.g. persons in uploaded photos – only where the Controller uploads such content

Note on roles: MenüNow also processes server and security logs as an independent controller (§ 1.3).

Annex B – Online Ordering

Applies to: the Trial and paid plans, for as long as the Controller uses Online Ordering, and to the data stored afterwards (§ 9.2).

Purpose: receiving, forwarding and handling orders (dine-in, pick-up, delivery, room charge), notifying guests and staff, delivery dispatch, reservations, guest accounts, loyalty programme and reviews – in each case to the extent the Controller uses these functions.

Data subjectsData
Customers / guestsname, phone number, email address; ordered items, options, notes (possibly health information, § 2.3), amount, tip, time, status, cancellation reason; table or room number
Guests with deliverydelivery address and the coordinates derived from it
Hotel and resort guests (room charge)room, guest’s last name, arrival and departure dates to check authorisation
Guests with a reservationname, email, phone, date, time, number of guests, notes
Guests with a guest accountname, email, password (hash only), phone, addresses, loyalty points, reviews, marketing consent
Guests paying onlinepayment method, payment status, Stripe payment and refund references (no card data)
Staff, kitchen, driversas Annex A; for drivers also shift status, vehicle type and only the latest location during the shift (no location history) for delivery dispatch; during a delivery the customer can see the driver’s location

Recipients: the Controller’s staff via the admin, kitchen display and driver view; the guest by email (order confirmation, status); Stripe under § 6.5.

Annex C – Additional features

Applies only to the extent the Controller or its guests use the respective feature.

FeaturePurposeDataRecipient (Annex E)
Guest assistant “Ask the menu” (Pro, Hotel, Resort)answering guests’ questions about the menuthe guest’s question (free text, possibly health information), menu content; no name, no contact detailsGoogle (Gemini)
Menu import, descriptions, translation, photo enhancementcreating menu contentthe Controller’s menu content, photos and documents; normally no personal dataGoogle (Gemini); Anthropic (fallback for import only); DeepL (fallback for translation only)
Geocoding the delivery addresscalculating distance and delivery fee, delivery mapdelivery address without name, from the Processor’s serverOpenStreetMap Foundation (Nominatim)
Delivery map (dispatch, driver view, guest order tracking)map displayIP address and browser data of staff and guests when loading map tilesOpenStreetMap Foundation (map tiles)
Statisticsreports for the Controllerorder and QR scan data from Annexes A and B, aggregatednone

Annex D – Technical and organisational measures (Art. 32 GDPR)

1. Confidentiality

1.1 Physical access control: The servers are located in Hetzner Online GmbH data centres in Germany (ISO/IEC 27001 certified) with access control, video surveillance and security staff. The Processor does not operate its own servers in offices.

1.2 System access control:

  • server access only encrypted via SSH with keys; root login disabled;
  • firewall with only necessary ports open; fail2ban against brute-force attacks;
  • automatic operating system security updates;
  • user passwords stored only as bcrypt hashes; login attempt limits; other sessions logged out after a password change;
  • two-factor authentication for administrative access where offered by the service;
  • credentials and keys kept in a password manager; no secrets in source code.

1.3 Data access control:

  • tenant separation: each business only sees its own data; server-side access checks on every request;
  • staff roles (e.g. admin, kitchen, driver) with different permissions;
  • access to production data only by the owner, only as far as needed for operation and support.

1.4 Data minimisation: QR scan statistics without IP address; payment data only as a reference, no card data; fonts and the map library are loaded from our own server.

2. Integrity

2.1 Transfer control: all connections exclusively encrypted (TLS/HTTPS), including connections to sub-processors; the database is not publicly accessible.

2.2 Input control: logging of logins and errors; orders with timestamp and status history; server logs kept for no more than 30 days.

3. Availability and resilience

3.1 Container-based operation with automatic restart; own monitoring of availability, errors, performance, disk space and security updates with alerting, plus an external availability check.

3.2 Automated deployment of new versions with tests and the option of immediate rollback.

3.3 Daily encrypted database backup, stored separately from the server (Cloudflare R2); retention of 14 daily and 8 weekly backups (at most 60 days); regular restore test.

4. Regular review

  • automatic checks of software dependencies for known vulnerabilities;
  • review of these measures at least once a year;
  • sub-processors only with a data processing agreement, selected according to their security standards;
  • process for reporting personal data breaches within the period under § 4.5.

Annex E – Sub-processors

Sub-processorServiceData concernedAnnexLocationThird-country basis
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germanyservers, database, own monitoring and logsall dataA, B, CGermany–
Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USAstorage and delivery of photos and logos (R2, media.menunow.de), encrypted database backups, DNSIP addresses when images are loaded; backups are encrypted and Cloudflare has no access to their contentA, BEU (R2 storage); worldwide (delivery via the Cloudflare network)EU-US Data Privacy Framework; Standard Contractual Clauses
Plus Five Five, Inc. (“Resend”), 2261 Market Street #5039, San Francisco, CA 94114, USAsending emails to guests and staffname, email address, email content, delivery statusA, BEU region; company in the USAStandard Contractual Clauses (for access from the USA)
Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (with Google LLC, USA)AI features (Gemini API)see Annex CCEU / USAEU-US Data Privacy Framework; Standard Contractual Clauses
Anthropic Ireland, Limited, Ireland (with Anthropic, PBC, USA)fallback AI provider for menu importmenu content; no guest dataCUSAStandard Contractual Clauses
DeepL SE, Maarweg 165, 50825 Cologne, Germanyfallback translation service for menusmenu texts only, no guest dataCEU–
OpenStreetMap Foundation, St John’s Innovation Centre, Cowley Road, Cambridge, CB4 0WS, United Kingdomgeocoding the delivery address (Nominatim), map tilesdelivery address without name; IP address of staff and guests when loading the mapCUnited Kingdomadequacy decision

For clarity, not sub-processors: Stripe (guest payments go through the Controller’s own Stripe account, § 6.5); services without access to personal data processed on the Controller’s behalf (e.g. external availability checks, code hosting); the service providers of the website menunow.de (Vercel, GoatCounter), which do not process guest data.

MenüNow.

Your own ordering and payment system for restaurants, cafés and resorts. Zero commission.

Product

  • How it works
  • Features
  • Digital menu with QR code
  • Pricing
  • Setup & onboarding
  • Start now

UAE

  • MenüNow UAE
  • QR menu Dubai
  • Talabat alternative
  • Hotels & resorts

Company

  • Contact

Legal

  • Imprint
  • Privacy policy
  • Terms of service
  • Data processing (DPA)
© 2026 MenüNow · All rights reserved Made in Germany · GDPR compliant