FOODZAPP™ END-USER TERMS OF USE (B2C DINER TERMS)
Hosted & Published Online at www.foodzapp.ae
SECTION 1: PREAMBLE, CORPORATE STRUCTURE & OPERATIONAL DEFINITIONS
1.1 Provider Details & Software Licensing Entity
This digital software framework is owned, maintained, and operated exclusively by SPRYNTZ TECHNOLOGIES L.L.C., a limited liability company registered in the Emirate of Dubai, United Arab Emirates, holding Commercial License No. 1121529, registered at Office 205, Rania Business Center, Al Barsha First, Dubai, UAE (hereinafter referred to as 'FoodZapp™', 'Spryntz', 'Platform Provider', 'We', 'Us', or 'Our').
1.2 Scope of End-User Interaction
These Terms apply to all consumers, diners, clients, guests, and end users (hereinafter referred to as 'End User', 'Client', 'Diner', or 'You') who access or interact with FoodZapp™ software tools, including but not limited to WhatsApp Business API conversational chat flows, Smart Table QR code ordering web interfaces, custom restaurant-branded web storefronts, phone order logging tools, pre-scheduled meal subscription interfaces, and digital checkout gateways.
1.3 Core Operational Definitions
- End User / Diner: The individual consumer accessing software interfaces to place food, beverage, meal plan, or dine-in orders.
- Merchant / Restaurant: The independent third-party food and beverage establishment, restaurant, cloud kitchen, or cafeteria subscribing to FoodZapp™ SaaS tools to receive orders directly from End Users.
- FoodZapp™ SaaS Platform: The cloud software architecture, web storefronts, WhatsApp Business API ordering engines, natural language processing tools, POS portals, and table QR code software modules operated by Spryntz Technologies L.L.C.
- Delivery Logistics Fleet: Independent third-party logistics courier fleets (3PL) integrated with FoodZapp or delivery drivers directly employed and dispatched by the Merchant.
SECTION 2: ELECTRONIC CONSENT, AGE CONSENT & SOFTWARE LICENSE TERMS
2.1 Mechanics of Electronic Consent & Order Placement
The End User explicitly acknowledges that digital food ordering software operates on instantaneous access mechanics. The End User confirms full, unreserved legal acceptance of these Terms prior to software utilization through any of the following explicit electronic consent actions:
- Checking the consent checkbox or clicking 'I Agree' during digital checkout or WhatsApp setup;
- Scanning a FoodZapp™ Smart Table QR code situated at a Merchant's physical dining premises and confirming order placement on the web interface;
- Initiating, replying to, or confirming an order on a conversational chat workflow on WhatsApp directed to a Merchant's FoodZapp™ ordering channel;
- Browsing menu items and confirming an order on a custom web storefront hosted by FoodZapp™;
- Providing order details verbally over the phone to a Merchant for manual logging into the FoodZapp™ portal and confirming the order summary link or proceeding with checkout;
- Submitting a cart, authorizing a payment, or providing contact/location details for order dispatch or meal subscription.
By utilizing FoodZapp™ software interfaces, the End User explicitly agrees to the continuous collection of order session telemetry and acknowledges that FoodZapp™ or the Merchant may initiate proactive communication if the ordering process is interrupted or stuck.
By utilizing FoodZapp™ software interfaces, the End User explicitly agrees to the collection and processing of location data to display nearby Merchants, calculate delivery feasibility, and facilitate physical order dispatch.
2.2 Age-Related Consent & Legal Capacity
By accessing FoodZapp™ software interfaces, the End User explicitly warrants and represents that they are at least eighteen (18) years of age (or the legal age of majority in their jurisdiction) and possess full legal capacity and legal authority to enter into binding legal agreements under United Arab Emirates laws.
2.3 Limited Software License Grant
Subject to full compliance with these Terms, FoodZapp™ grants the End User a personal, revocable, non-exclusive, non-transferable, limited license to access and use its software interfaces solely for personal, non-commercial food browsing, order placement, and direct transaction settlement with Merchants.
2.4 Strict Usage Restrictions & Account Security
The End User covenants that they shall not, directly or indirectly: (a) Use automated web bots, scrapers, or data mining tools to extract menu items, pricing, or system code; (b) Decompile, reverse-engineer, or disrupt underlying WhatsApp API pipelines or cloud hosting infrastructure; (c) Inject malicious code or execute denial-of-service attacks; (d) Submit fraudulent orders, fictitious delivery addresses, or invalid payment credentials; or (e) Share account or WhatsApp session credentials with unauthorized third parties.
SECTION 3: INTERMEDIARY TECHNOLOGY STATUS & DIRECT CONSUMER-MERCHANT CONTRACT
3.1 Execution of Direct Merchant Contract
When an End User places an order through any FoodZapp™ interface, the legal contract for the purchase, preparation, packaging, temperature control, allergen safety, and fulfillment of food and beverage items is executed DIRECTLY AND EXCLUSIVELY between the End User and the respective Merchant. FoodZapp™ is not a party to this commercial transaction.
3.2 Merchant Statutory Responsibility under UAE Law
The Merchant maintains sole, exclusive legal liability under UAE Federal Law No. 15 of 2020 on Consumer Protection and municipal food safety codes for:
- Kitchen hygiene, sanitation, food safety, and compliance with UAE Municipal Standards;
- Veracity and accuracy of menu descriptions, ingredient disclosures, pricing, and allergen warnings;
- Order item fulfillment, culinary preparation, initial packaging integrity, and food temperature control prior to dispatch;
- Direct resolution and funding of customer refund demands, item replacements, dietary disputes, and missing item claims.
SECTION 4: INDIVIDUAL ORDERING MODULES & OPERATIONAL MECHANICS
4.1 WhatsApp Natural Language & AI Ordering Mechanics
Orders placed via WhatsApp text messages or voice notes are routed through automated chat workflows, natural language processing engines, and conversational AI tools.
4.2 Smart Table QR Ordering & Dine-In Checkout Mechanics
When scanning table QR codes at physical restaurant outlets, diners access digital menus enabling group cart creation and split-payment selection:
- Instant Auto-Acceptance & On-Premise Preparation: Table orders are auto-accepted immediately upon submission and prepared for on-premise dining. Once submitted, orders cannot be canceled post-submission.
- Individual Session Settlement: Each diner remains individually liable for settling all payment balances, shared bill allocations, and cart items ordered under their active digital table session.
- Merchant Floor Control & Network Connectivity: Physical seating verification, table allocation, food presentation, waiter service, and customer device connectivity (such as guest Wi-Fi or cellular signal at tables) remain the exclusive operational responsibility of the Merchant and fall outside FoodZapp’s technical control.
4.3 Pre-Scheduled Orders & Meal Plan Subscriptions
Where End Users utilize FoodZapp™ software tools to schedule advance meal deliveries or recurring weekly/monthly meal plan subscriptions:
- Advance Scheduling & Merchant Cut-Off Rules: The End User designates specific delivery calendar dates, recurring timeslots, and delivery addresses during initial subscription setup. Each subscribing Merchant maintains its own specific set of operational rules and cut-off deadlines for accepting plan modifications, pauses, calendar resets, or cancellations. The FoodZapp platform merely enforces these merchant-defined rules digitally.
- Merchant Fulfillment Commitment: The Merchant is solely responsible for preparing and dispatching meals according to the agreed calendar schedule.
- Non-Refundability Boundary: Pre-scheduled orders and active meal subscription cycles become strictly non-refundable once the Merchant initiates raw material procurement or kitchen preparation according to their rules. Unfulfilled meals caused by permanent restaurant kitchen closure will be credited via Merchant-specific coupons or refunded as authorized by the Merchant.
4.4 Phone & Verbal Order Capture Logging
Where Merchant personnel manually enter phone or verbal orders into the FoodZapp™ order management portal on behalf of a calling customer:
- Merchant Input Agency: The Merchant staff acts as an authorized input agent capturing the verbal requests of the End User directly into the FoodZapp™ portal.
- Order Summary Receipt Logging: Upon verbal order capture, the details are recorded within the Merchant's software portal, and a digital summary receipt or confirmation link may or may not be dispatched to the End User prior to kitchen preparation.
- Approval & Binding Acceptance: Proceeding with payment or accepting delivery after receiving and reviewing the digital order summary constitutes full legal acceptance of the captured order summary, pricing, and these Terms.
- Direct Merchant Calls Not Recorded: Calls made directly between the End User and the Merchant (whether for phone order placement, delivery status queries, or order issues) are direct telecommunication connections conducted outside FoodZapp's software interface. FoodZapp does NOT record, listen to, monitor, or archive direct phone calls between End Users and Merchants, and maintains zero recording or transcript records for such telephonic interactions. Mismatches between verbal calls and delivered food are evaluated directly between the client and the Merchant.
SECTION 5: DELIVERY DISPATCH, LOGISTICS FLEETS, TRANSIT ASSUMPTIONS & RIGHT VS. WRONG DELIVERY
5.1 Dual Fleet Dispatch Architecture
Order deliveries are fulfilled either by independent third-party logistics (3PL) delivery fleets integrated with FoodZapp (e.g., local courier companies) or by delivery drivers directly employed and dispatched by the Merchant. FoodZapp does not directly operate delivery vehicles or employ couriers.
5.2 Core Operational Assumptions in Food Transit
The End User agrees to the following fundamental operational assumptions governing food delivery:
- Transit Duration & ETA Approximations: Estimated Time of Arrival (ETA) quoted on digital interfaces is an automated approximation based on average preparation times and traffic data. ETA is NOT a guaranteed delivery deadline.
- Packaging & Steam Dynamics: Delivery food is packaged in thermal bags and disposable containers designed for temporary transit, which inherently alters texture, steam retention, and crispness.
- External Environmental Exposure: Extreme weather (extreme summer heat, dust storms, rain), traffic congestion, or security checkpoint delays naturally impact delivery speed and food temperature.
5.3 Operational Guidelines: Defining 'Right Delivery' vs. 'Wrong Delivery'
To establish transparent legal and operational benchmarks, order fulfillment is classified as follows (THESE DEFINITIONS SERVE AS OPERATIONAL BENCHMARKS FOR MERCHANT EVALUATION AND DO NOT CREATE DIRECT LEGAL LIABILITY FOR FOODZAPP):
A. What Constitutes a 'Right Delivery' (Conforming Order): An order is deemed legally fulfilled and non-refundable when all of the following condition guidelines are substantially satisfied:
- Ticket Match: Delivered items substantially match the primary dish names, requested major options, and quantities listed on the digital order confirmation summary ticket;
- Seal Integrity: Primary tamper-evident packaging or food container seals remain substantially intact upon arrival;
- Location & ETA: Delivery is completed to the address or GPS location designated by the End User within a reasonable operational window around the estimated ETA;
- Normal Transit Condition: Food exhibits normal, expected transit condition (accounting for inherent thermal loss, steam condensation, or minor textural changes natural to road transport).
B. What Constitutes a 'Wrong Delivery' (Non-Conforming Order): An order qualifies as a 'Wrong Delivery' eligible for remediation under any of the following explicit operational scenarios:
- Missing Items / Omissions: Entire dishes, drinks, or paid meal components listed on the digital order confirmation ticket are omitted from the delivery package;
- Incorrect Items / Dish Swap: The food delivered belongs to a completely different order or contains different primary dishes than ordered;
- Severe Physical Damage / Spillage: Food packaging suffered catastrophic crush damage, severe internal spillage, or total inversion during transit, rendering the food unconsumable;
- Major Allergen / Requirement Violation: Delivered food contains an explicit allergen that the End User specifically flagged in writing on the order ticket and the Merchant acknowledged prior to preparation;
- Extreme Unreasonable Delay: Delivery delay exceeds sixty (60) minutes past the upper ETA window solely due to driver gross fault, where food has spoiled or degraded beyond acceptable consumption standards.
5.4 End-User Rights & Operational Support Remediation Steps
Where an End User encounters a 'Wrong Delivery' as defined in Section 5.3(B), the End User possesses the right to request remediation through the following structured process:
- Primary Contact Protocol (Merchant First): Clients must first attempt to contact the Merchant directly using the phone number or contact details listed on the order confirmation. If the Merchant remains unresponsive after reasonable contact attempts, the client may escalate the issue to FoodZapp customer support via email at support@foodzapp.com.
- Immediate Notice (30-Minute Rule): The End User must notify the Merchant or submit a support ticket within thirty (30) minutes of physical delivery arrival. Claims submitted past 30 minutes will be rejected due to food safety and perishability constraints.
- Digital Summary & Photographic Verification: The End User must provide clear photographic evidence demonstrating: (a) delivered food containers and packaging seals; (b) the specific missing or damaged items; and (c) the digital order confirmation summary ticket. The digital summary ticket on the web, app, or WhatsApp serves as complete and sufficient evidence; a physical paper receipt may or may not be included.
- Structured Remediation Execution: Upon verification, remediation is executed according to the Hierarchy of Remediation set forth in Section 8.3 (Replacement Order, Merchant-Specific Store Credit Coupon, or Exceptional Card Reversal).
5.5 OPERATIONAL GUIDELINE ONLY & OPTIONAL COURTESY MEDIATION
THE END USER EXPLICITLY UNDERSTANDS AND AGREES THAT THE DELIVERY DEFINITIONS, OPERATIONAL GUIDELINES, AND SUPPORT REMEDIATION STEPS SET FORTH IN SECTIONS 5.3 AND 5.4 ARE INTERNAL SERVICE LEVEL BENCHMARKS DESIGNED FOR CUSTOMER SUPPORT MEDIATION. FoodZapp™ functions strictly as a Software-as-a-Service technology intermediary. Mediation by FoodZapp™ is strictly an optional, non-mandatory courtesy service. FoodZapp™ holds no legal obligation, mandatory duty, or debt liability to mediate disputes, guarantee outcomes, or fund refunds on behalf of subscribing Merchants. FoodZapp™ bears zero legal liability or financial obligation for rider actions, transit delays, damaged food, missing items, or delivery failures attributable to independent Merchants or 3PL carriers. The underlying financial and fulfillment obligations reside strictly and exclusively with the Merchant.
SECTION 6: FOOD SAFETY, INGREDIENTS, ALLERGENS & CONSUMER PROTECTION
6.1 Merchant Menu Authority & Allergen Disclosures
All menu descriptions, ingredient lists, price quotations, tax calculations, and allergen disclosures published across FoodZapp™ digital storefronts are configured and published independently by the Merchant. FoodZapp™ does not audit, inspect, or warrant menu accuracy or kitchen food safety standards.
6.2 End-User Duty regarding Severe Food Allergies & Religious Standards
END USERS WITH SEVERE FOOD ALLERGIES, MEDICAL DIETARY RESTRICTIONS, OR RELIGIOUS DIETARY REQUIREMENTS (SUCH AS STRICT HALAL PREPARATION) MUST CONTACT THE MERCHANT DIRECTLY VIA PHONE PRIOR TO ORDER SUBMISSION TO CONFIRM KITCHEN PREPARATION CONDITIONS. NEITHER FOODZAPP NOR THE MERCHANT GUARANTEES AN ALLERGEN-FREE ENVIRONMENT.
6.3 Statutory Health Liability Allocation
Subject to applicable mandatory UAE laws, FoodZapp™ provides its software platform as an intermediary technology enabler. To the fullest extent permitted by law, FoodZapp™ disclaims liability for health complications or foodborne issues arising from Merchant food preparation, provided that nothing in these Terms shall exclude or limit FoodZapp's liability for death, personal injury, fraud, or gross negligence directly caused by FoodZapp™ where such liability cannot be excluded under mandatory UAE statutory law.
SECTION 7: PAYMENT TERMS, CARD SECURITY & CASH ON DELIVERY (COD)
7.1 Payment Gateway Processing
When selecting online payment, the End User authorizes licensed payment gateway providers to debit the final order amount from their credit card, debit card, or digital wallet. Payment processing may be executed either through FoodZapp's registered payment gateway or directly through the Merchant's integrated payment gateway. Where payment is collected via FoodZapp's payment gateway, FoodZapp acts strictly as a technology facilitator collecting funds on behalf of and remitting them to the Merchant. In all cases, the primary commercial transaction remains directly between the End User and the Merchant.
7.2 Cash on Delivery (COD) & Doorstep POS Terms
Where Cash on Delivery (COD) or doorstep card reader payment is selected:
- The End User covenants to pay the exact cash balance or present a valid card to the delivery rider upon arrival;
- Failure to pay upon delivery constitutes a material breach, entitling the Merchant and FoodZapp™ to blacklist the End User and treat the order as a Customer-Caused Delivery Failure;
- Handling of cash and doorstep POS collection is managed directly by the delivery rider; FoodZapp™ retains zero physical cash custody.
7.3 Retail Menu Pricing, VAT & Consumer Usage Fees
All retail food prices quoted on digital storefronts are established by the Merchant and must be strictly inclusive of 5% UAE Value Added Tax (VAT) pursuant to UAE Federal Decree-Law No. 8 of 2017. Any applicable delivery charges or nominal software usage fees are itemized transparently on the final checkout confirmation screen.
SECTION 8: ORDER CANCELLATION FRAMEWORK, REFUND PROCEDURES & MEDIATION GUIDELINES
8.1 Instant Auto-Acceptance & Post-Placement Non-Cancellability Boundary
Because orders placed across FoodZapp™ software touchpoints are transmitted instantly to the Merchant's POS/kitchen terminal and auto-accepted immediately upon placement, it is operationally impossible for an End User to cancel an order once submitted. There is no automated cancellation button available within the software interface post-placement.
Direct Merchant Contact Requirement: Any request, concern, or modification after placing an order must be addressed on a case-by-case basis through direct communication between the client and the Merchant using the Merchant contact details listed on the order confirmation. The Merchant retains sole discretion to evaluate and determine if any operational adjustment can be accommodated prior to kitchen prep.
Post-Preparation Non-Cancellability: PURSUANT TO UAE CONSUMER PROTECTION STANDARDS GOVERNING PERISHABLE GOODS, ORDERS CANNOT BE CANCELED, MODIFIED, OR REFUNDED ONCE TRANSMITTED AND ACCEPTED BY THE MERCHANT KITCHEN. Because food and beverage items are prepared fresh to order using perishable raw ingredients, any post-placement cancellation attempt, refusal of delivery, or failure to accept delivery will result in a 100% charge of the total order value (including food costs and allocated delivery fees) to compensate the Merchant for kitchen waste and allocated courier resources.
8.2 Customer-Caused Delivery Failures & 100% Cost Retention
If a delivery cannot be completed upon courier arrival due to customer-side defaults, the order shall be classified as a Customer-Caused Delivery Failure. Customer-side defaults include:
- Unresponsiveness to courier phone calls or WhatsApp messages after reasonable contact attempts (minimum 10 minutes wait time and 3 call attempts);
- Providing an incorrect, incomplete, or unreachable physical address or GPS pin;
- Refusal to present valid government photo identification (Emirates ID or Passport) for age-restricted items under Section 2.2; or
- Unreasonable refusal to accept the food package at the designated delivery point.
In all such events, FoodZapp™ and the Merchant reserve the right to retain 100% of the total order value to cover perishable kitchen preparation expenses and third-party logistics costs incurred.
8.3 Step-by-Step Refund & Hierarchy of Remediation Workflow
Where a genuine order dispute occurs (such as a 'Wrong Delivery' under Section 5.3B or pre-kitchen adjustment approved by the Merchant), the claims process operates under the following structured workflow:
Step 1: Primary Contact Lodgment: The End User must first contact the Merchant directly using the contact details displayed on the digital order summary ticket within thirty (30) minutes of physical delivery. If the Merchant remains unresponsive after reasonable contact attempts, the End User may escalate the dispute to FoodZapp customer support via email at support@foodzapp.com.
Step 2: Evidence Submission: The End User provides clear photographic proof showing the delivered packaging, packaging seals, damaged/incorrect items, and the digital order summary ticket.
Step 3: Merchant Verification & Hierarchy of Remediation: The Merchant verifies the evidence against kitchen preparation records. Upon verification, remediation follows a strict 3-tier operational hierarchy:
| Remediation Level | Action & Scope | Resolution Timeline |
|---|---|---|
| Step 1: Primary Intent (Standard Replacement) |
Immediate kitchen re-preparation and dispatch of replacement items at zero extra cost. Transit time matches standard delivery timing, adhering strictly to the Rider Respect Policy. | Standard Delivery Transit Time |
| Step 2: Secondary Intent (Merchant Coupon / Credit) |
100% value of affected items issued as a Merchant-Specific Digital Coupon/Credit redeemable solely with that specific merchant. Valid for 12 months; non-transferable across other restaurants. | Instant Activation (Valid for 12 Months) |
| Step 3: Exceptional Intent (Card Gateway Reversal) |
Monetary reversal to customer payment card (rare scenario). Mandatory third-party payment gateway transaction fees or banking administrative charges may be debited from refund. | 5 to 14 Business Days (Bank Processing) |
8.4 REITERATION: OPTIONAL COURTESY MEDIATION ONLY
ALL CANCELLATION, REFUND, AND CLAIM STEPS OUTLINED IN THIS SECTION 8 CONSTITUTE OPERATIONAL MEDIATION GUIDELINES EXCLUSIVELY. Mediation by FoodZapp™ is strictly an optional, non-mandatory courtesy service. FoodZapp™ acts purely as an amicable technical mediator between the End User and the Merchant. FoodZapp™ assumes NO legal debt obligation, financial recourse liability, or refund payout guarantee under any circumstances. The Merchant remains exclusively responsible as the seller of record for funding approved customer refunds, replacements, or credits.
SECTION 9: GENERAL AGGREGATOR & SOFTWARE TERMS (UAE PUBLIC DOMAIN STANDARDS)
9.1 Software Availability, Upgrades & Controlled Maintenance
FoodZapp™ software interfaces are provided on an 'AS-IS' and 'AS-AVAILABLE' basis. Spryntz Technologies L.L.C. conducts periodic software updates and scheduled system maintenance. End users hold FoodZapp™ harmless against temporary downtime, cloud latency, or order processing pauses.
9.2 Intellectual Property Rights & Non-Scraping Covenant
All proprietary software architecture, WhatsApp ordering workflows, smart table QR systems, digital storefront designs, logos, software source code, and AI ordering interfaces are the sole intellectual property of Spryntz Technologies L.L.C. Users shall not scrape, copy, or misuse platform IP.
9.3 Data Privacy & UAE PDPL Compliance
Personal data collected by FoodZapp™ is processed strictly in accordance with UAE Federal Decree-Law No. 45 of 2021 on Personal Data Protection (PDPL) and our Privacy Policy (accessible at www.foodzapp.ae/privacy). End Users retain full statutory rights to access, rectify, request erasure of their personal data, or object to direct marketing communications by contacting our Data Protection Officer at privacy@foodzapp.com.
SECTION 10: COMPREHENSIVE INDEMNIFICATION, LIABILITY CAP & GOVERNING LAW
10.1 Direct End-User Indemnification
The End User agrees to indemnify and hold harmless FoodZapp™ against any direct third-party claims, liabilities, or losses incurred by FoodZapp™ arising solely from the End User's intentional fraudulent conduct, unlawful usage of the software platform, or material breach of these Terms.
The End User covenants and agrees to indemnify, defend, and hold harmless Spryntz Technologies L.L.C. (operating as FoodZapp™) against any claims, damages, liabilities, health complications, transit losses, or legal costs arising out of:
- Software usage across WhatsApp, table QR codes, custom web storefronts, phone order channels, or meal plan subscription tools;
- Consumption of food, beverage, or meal plan items prepared and delivered by Merchants;
- Order inaccuracies arising from non-deterministic AI voice or text translations or user input errors;
- Food transit degradation, thermal loss, packaging spillage, wrong delivery disputes, or rider transit delays;
- Providing false delivery addresses, invalid payment credentials, or breaching these Terms.
10.2 Statutory Aggregate Liability Cap
To the maximum extent permitted under applicable UAE laws, FoodZapp's total aggregate liability arising out of software usage or these Terms shall be limited to the lower of AED 500 or the value of the disputed order. This liability cap shall not apply to liabilities arising from FoodZapp's gross negligence, willful misconduct, fraud, or any statutory liability that cannot be contractually limited under mandatory UAE law.
10.3 Force Majeure Protections
Neither FoodZapp™ nor the Merchant shall be held liable for failure or delay in fulfilling order commitments resulting from acts of God, severe weather, flooding, sandstorms, power outages, telecommunications line failures, cloud infrastructure crashes, or government restrictions, pursuant to Articles 273 and 249 of the UAE Civil Code.
10.4 Governing Law & Dispute Resolution Jurisdiction
These Terms shall be governed by and construed in accordance with the laws of the Emirate of Dubai and the applicable Federal Laws of the United United Arab Emirates. Any consumer dispute or claim arising out of these Terms shall be subject to the jurisdiction of the competent Onshore Courts of Dubai, without prejudice to the consumer's statutory right to submit complaints to the UAE Ministry of Economy or local consumer protection authorities.
SECTION 11: CONTACT DETAILS FOR DISPUTES & SUPPORT
11.1 Primary Contact Protocol (Merchant Details First)
Diners must first contact the Merchant directly using the phone number, WhatsApp link, or contact details displayed on the digital order confirmation ticket.
11.2 Secondary Escalation (FoodZapp Customer Support Email)
If the Merchant remains unresponsive after reasonable contact attempts, clients may contact FoodZapp customer support via email at support@foodzapp.com.
11.3 Legal & Privacy Inquiries
For data protection, privacy rights, or legal notices: privacy@foodzapp.com
11.4 Corporate Office Address
Spryntz Technologies L.L.C., Office 205, Rania Business Center, Al Barsha First, Dubai, UAE