Status and execution
This is a proposed addendum for review, not an executed agreement. It becomes binding only when the parties expressly approve it through an agreed contracting process. Deburise Solutions is the Menuji service provider; the addendum must also identify the restaurant customer, complete party particulars, the underlying order, processing locations, suppliers, security schedule and any required transfer terms. Contact [email protected] to discuss an agreed version.
Scope and roles
The proposed arrangement covers personal information a restaurant instructs Menuji to process to provide the enabled restaurant workspace. The restaurant determines the purposes of its guest and staff workflows; Menuji acts on documented instructions for that service. Menuji's own account administration, subscription billing, fraud prevention and legal duties may involve a separate role described in the privacy notice.
Processing description
Subject to the agreed enabled features, processing can include collection, storage, retrieval, display, transmission, export, correction and restricted deletion. Data subjects can include restaurant owners, authorised staff, guests, reservation contacts and delivery recipients. Data can include business contact details, permissions, order references, reservation information, delivery details, invoices, transaction references, receipt evidence and audit records. The agreed schedule must narrow this description to the customer's actual use.
Instructions and purpose limits
The approved order, enabled configuration and authorised support requests should define documented instructions. Processing must remain limited to delivering those instructions and any independent legal obligation. If an instruction appears unlawful or unsupported, the parties should pause that activity and resolve it. This draft does not authorise selling restaurant guest lists, unrelated advertising or training an AI model on private restaurant records.
Restaurant responsibilities
The restaurant should provide appropriate notices, obtain necessary permissions, maintain accurate data, limit staff access and use only supported lawful workflows. It should communicate restrictions that affect processing and avoid supplying excessive or unsupported sensitive information. Restaurant-selected messaging and payment services remain subject to their own agreements and instructions.
Confidentiality and access
An agreed addendum should require personnel access to be limited to authorised operational need and subject to appropriate confidentiality obligations. Support access, privilege changes and incident investigation should be controlled and reviewable. The precise procedures and evidence must be recorded in the final security schedule rather than assumed from this summary.
Security schedule
Before execution, document the actual controls for authentication, tenant isolation, secrets, transport protection, access review, logging, change management, incident response, retention and recovery. Identify responsibility for hosting and configuration. Do not state a certification, encryption boundary, backup schedule or recovery objective unless the deployed evidence supports it.
Suppliers and transfers
Attach the actual subprocessor list, service purpose, location and approval or notice process. Distinguish suppliers engaged by Menuji from integrations independently selected by the restaurant. Assess cross-border restrictions and adopt any required transfer instrument before the transfer. This draft does not itself provide a GDPR transfer mechanism, standard contractual clauses or verified India-only processing.
Requests from individuals and authorities
The parties should coordinate proportionate assistance for relevant access, correction, deletion, consent-withdrawal and complaint requests. Identity checks and restaurant authority must be verified without unnecessarily collecting more information. Legally binding authority requests require appropriate review, limited disclosure and customer notice where permitted. The final agreement should define contacts, assistance and applicable deadlines.
Incidents and cooperation
An executed addendum should define notification triggers, secure contacts, information to be shared as it becomes available, evidence preservation and cooperation with the restaurant. It must support applicable statutory reporting timelines without substituting an invented universal deadline. The parties should agree responsibility for guest communications and regulator contact where their legal roles require it.
Return, deletion and retention
Agree supported export formats, offboarding assistance, access cutoff and deletion or return procedures before termination. Identify retention exceptions for financial records, legal holds, security logs and immutable audit history, together with any backup expiry process. A complete removal commitment requires technical capability and a verified schedule; this draft makes no promise of immediate erasure.
Verification and document priority
The final addendum should define proportionate information or audit rights, confidentiality, frequency, costs if any, remediation handling and precedence over conflicting general terms for the relevant processing. Regulatory rights cannot be removed by contract. Material changes to suppliers, locations or processing scope should follow the agreed review process. No executed audit entitlement or commercial commitment is created by this discussion draft.