FOODZAPP™ | PRIVACY POLICY

FOODZAPP™ UNIFIED PRIVACY POLICY & DATA PROTECTION FRAMEWORK

General Software-as-a-Service (SaaS) Consumer & Transactional Privacy Policy — Version 3.0 (UAE Law Compliant Edition)
Hosted & Published Online at www.foodzapp.ae/privacy
📌 BINDING LEGAL FRAMEWORK, SAAS STATUS & UAE PDPL COMPLIANCE PRIOR TO USAGE: This FoodZapp™ Unified Privacy Policy & Data Protection Framework ('Policy') governs all collection, storage, processing, and transfer of personal and operational data managed by Spryntz Technologies L.L.C. (Dubai, UAE) operating under the commercial brand name FoodZapp™ In accordance with Section 2.1 of the FoodZapp™ End-User Terms of Use, users grant explicit, affirmative opt-in consent to this Policy prior to software utilization through any explicit electronic consent action (such as checking an acceptance box, clicking 'I Agree' during checkout, scanning a Smart Table QR code, or confirming a WhatsApp order ticket) FoodZapp™ operates strictly as a Software-as-a-Service (SaaS) technology enabler and Data Processor, while subscribing Merchants act as Data Controllers under United Arab Emirates Federal Decree-Law No. 45 of 2021 on Personal Data Protection (PDPL)

SECTION 1: PREAMBLE, CORPORATE STRUCTURE & OPERATIONAL SCOPE

1.1 Licensing Entity & Platform Operator Details

This digital software framework and cloud platform are owned, maintained, and operated exclusively by SPRYNTZ TECHNOLOGIES L.L.C., a limited liability company registered under the laws of the Emirate of Dubai, United Arab Emirates, holding Commercial License No. 1121529, with its registered corporate office located at 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 Unified SaaS Services & Data Processing

This Policy applies to all end-user diners, restaurant clients, guests, and administrative users who interact with FoodZapp™ software modules, digital touchpoints, and online ordering channels In strict alignment with the core services established on the FoodZapp homepage and End-User Terms of Use, the scope of data processing encompasses[cite: 3]:

1.3 Operational Definitions

🛡️ KEY OPERATIONAL DEFINITION — STRICT DATA PROCESSOR STATUS & CONTROLLER OWNERSHIP: Subscribing Merchants maintain absolute ownership of customer databases and act as Data Controllers under UAE PDPL Spryntz Technologies L.L.C. acts strictly as a Data Processor FoodZapp™ covenants and guarantees that it shall NEVER sell, lease, monetize, share, or disclose Merchant customer data or contact registries to any third party, competitor, or marketing agency

SECTION 2: LEGAL BASIS & LAWFUL PROCESSING FRAMEWORK UNDER UAE PDPL

2.1 Statutory Legal Grounds for Processing

In accordance with Articles 4 and 5 of United Arab Emirates Federal Decree-Law No. 45 of 2021 on Personal Data Protection ('UAE PDPL'), FoodZapp™ processes personal data strictly under standardized, lawful grounds[cite: 3]:

2.2 Fundamental Data Protection Principles

All processing activities across our cloud infrastructure adhere strictly to core UAE PDPL principles: (a) Lawfulness, fairness, and transparency; (b) Purpose limitation strictly tied to SaaS enablement; (c) Data minimization to collect only data necessary for transaction completion; (d) Accuracy and prompt updating; and (e) Storage limitation and robust technical security

SECTION 3: CATEGORIES OF PERSONAL DATA PROCESSED

3.1 End-Consumer & Diner Transactional Data

We process end-consumer data captured through FoodZapp™ digital ordering channels strictly on behalf of the subscribing Merchant[cite: 3]:

3.2 Merchant Corporate & Operational Data

We collect and process commercial data from subscribing Merchants to establish, maintain, and bill B2B subscription accounts[cite: 3]:

🤖 PROBABILISTIC AI & CONVERSATIONAL CHAT DATA PROCESSING DISCLAIMER: Natural language processing engines and conversational AI models operate on probabilistic data models Voice note recordings, transcriptions, and text inputs processed via WhatsApp Business API workflows are analyzed strictly to construct order summary tickets and optimize automated kitchen routing Spryntz Technologies L.L.C. disclaims liability for inadvertent data misinterpretations resulting from background noise or dialect variations, while ensuring all chat data is encrypted and retained strictly per statutory operational limits Pursuant to Article 18 of the UAE PDPL, users retain the right to request human verification or manual review of any order summary ticket generated via automated conversational AI models prior to kitchen dispatch

SECTION 4: PURPOSE OF PROCESSING & OPERATIONAL MECHANICS

4.1 Order Transmission & Kitchen Dispatch Mechanics

Consumer order details, text/voice inputs, and delivery GPS coordinates are processed in real time to transmit order tickets directly to Merchant kitchen portals, receipt printers, and integrated 3PL delivery fleets or in-house driver dispatch tools

4.2 System Optimization & AI Processing

Conversational AI algorithms interpret incoming consumer voice and text messages to construct structured order receipts, streamline order entry, improve system accuracy, and prevent operational bottlenecks The confirmed digital order summary ticket generated in WhatsApp serves as the definitive transaction record

4.3 CRM Broadcasts & Marketing Controls

Meta-approved WhatsApp CRM tools and deep-linking social media ad integrations allow Merchants to communicate directly with their customers Operational outreach is conducted strictly for order completion or quality assurance Promotional CRM broadcasts are dispatched solely where diners have opted in, and every promotional message contains an automated 'STOP' command for instantaneous opt-out

Real-Time Assistance & Order Recovery Outreach: Where an End User encounters technical errors or stalls during an active ordering session, FoodZapp™ or the subscribing Merchant may send automated or manual operational messages (via WhatsApp, SMS, or in-app prompts or call) to assist in resolving the issue and completing the order

Location-Based Restaurant Discovery & Geofencing: Precise GPS coordinates and location data are processed to determine the End User's geographical proximity, filter active subscribing Merchants, and display relevant nearby restaurant storefronts, menus, and delivery radiuses

💳 PCI-DSS GATEWAY PROCESSING & ZERO CARD RETENTION GUARANTEE: Online credit and debit card transactions are processed securely through licensed, PCI-DSS compliant financial payment gateway institutions integrated with FoodZapp™ or the Merchant FOODZAPP™ NEVER STORES, SAVES, TOKENIZES, OR RETAINS END-USER CREDIT CARD OR DEBIT CARD NUMBERS, EXPIRATION DATES, CVV CODES, OR BANK ACCOUNT CREDENTIALS ON ITS SERVERS All financial credentials pass directly through encrypted gateway pipelines

SECTION 5: DATA SECURITY SAFEGUARDS & DATA BREACH PROTOCOLS

5.1 Technical & Organizational Security Standards

Spryntz Technologies L.L.C. enforces enterprise-grade technical and organizational security measures across all cloud server infrastructure[cite: 3]:

5.2 Data Breach Notification & Escalation Protocols (UAE PDPL Article 9)

FoodZapp™ maintains 24/7 automated intrusion detection systems In the event of a confirmed or reasonably suspected personal data breach affecting confidentiality, integrity, or availability[cite: 3]:

  1. Reporting to the UAE Data Office: FoodZapp™ (or the Data Controller) shall immediately report the security breach to the UAE Data Office pursuant to Article 9 of the UAE PDPL and its Executive Regulations
  2. Notification to Affected Data Subjects: Where a breach poses a high risk to personal privacy or data rights, affected individuals shall be notified without undue delay, detailing the breach nature, likely consequences, and remedial measures implemented
  3. Processor-to-Controller Escalation: Operating as a Data Processor, FoodZapp™ shall notify subscribing Merchants (Data Controllers) within twenty-four (24) hours of confirming any security incident affecting their customer records

SECTION 6: STATUTORY DATA SUBJECT RIGHTS UNDER UAE LAW

6.1 Statutory Rights Under UAE PDPL (Articles 12–18)

Pursuant to Articles 12 through 18 of UAE Federal Decree-Law No. 45 of 2021 on Personal Data Protection (PDPL), Diners and Users possess explicit statutory rights[cite: 3]:

6.2 Mechanism for Exercising Rights, DPO Designation & Administrative Complaints

Pursuant to Articles 10 and 11 of the UAE PDPL, Spryntz Technologies L.L.C. has formally designated a Data Protection Officer[cite: 3]:

SECTION 7: CROSS-BORDER DATA TRANSFERS & THIRD-PARTY PROCESSORS

7.1 Third-Party Processor Architecture

To execute core SaaS operations, FoodZapp™ engages reputable third-party technology providers under strict data processing agreements[cite: 3]:

7.2 Cross-Border Safeguards (UAE PDPL Articles 22 & 23)

International data transfers across Meta API nodes or cloud server networks comply strictly with UAE PDPL cross-border transfer requirements under Articles 22 and 23, ensuring adequate protection through[cite: 3]:

  1. Adequacy Decisions (Article 22): Transfers to jurisdictions recognized by the UAE Data Office as providing an adequate level of data protection
  2. Standard Contractual Clauses (Article 23): Relying on Standard Contractual Clauses (SCCs) incorporating data protection standards approved by the UAE Data Office and strict non-disclosure obligations

SECTION 8: DATA RETENTION SCHEDULES & TAX ACCOUNTING

8.1 Statutory Retention Periods & AI Minimization Schedule (Article 6)

In compliance with the Storage Limitation and Data Minimization principles under Article 6 of the UAE PDPL, personal data is retained only for the duration necessary to fulfill processing purposes or statutory obligations[cite: 3]:

SECTION 9: COMPREHENSIVE INDEMNIFICATION, LIABILITY CAP & GOVERNING LAW

9.1 Statutory Liability Allocation & Data Processor Indemnity

The subscribing Merchant, acting as Data Controller, agrees to defend, indemnify, and hold harmless Spryntz Technologies L.L.C. against any third-party claims, consumer privacy disputes, Meta WhatsApp account suspensions, or regulatory fines resulting from unauthorized merchant marketing broadcasts or merchant-side data breaches

9.2 Statutory Aggregate Liability Cap & Consumer Severability

Contractual liability caps set forth in B2B SaaS Master Terms or End-User Terms apply solely to commercial business claims between contracting parties Nothing in this Policy shall restrict, limit, or exclude consumer statutory rights under UAE Federal Decree-Law No. 45 of 2021, nor shall it prejudice administrative enforcement penalties imposed by the UAE Data Office

⚖️ STATUTORY DATA RIGHTS, AGGREGATE LIABILITY CAP & GOVERNING LAW: To the maximum extent permitted by UAE law, Spryntz Technologies L.L.C. (FoodZapp™) shall maintain B2B data processing liability strictly capped at AED 5,000 or the total SaaS subscription fees paid in the three (3) months preceding any claim All data disputes shall be governed by the laws of the Emirate of Dubai and applicable UAE Federal Laws, subject to the administrative authority of the UAE Data Office or the exclusive jurisdiction of the competent Onshore Courts of Dubai or the Dubai International Financial Centre (DIFC) Courts

9.3 Governing Law & Dispute Resolution Jurisdiction

This Policy shall be governed by and construed in accordance with the laws of the Emirate of Dubai and applicable Federal Laws of the United Arab Emirates Any dispute arising out of or in connection with this Policy shall be subject to the administrative jurisdiction of the UAE Data Office, or the exclusive jurisdiction of the competent Onshore Courts of Dubai or the DIFC Courts

SECTION 10: UNIFIED SERVICES & PRIVACY PROTECTION MATRIX

The following matrix summarizes the alignment between FoodZapp™ base services and statutory privacy protections[cite: 3]:

FoodZapp™ Base Service Module Primary Data Categories Processed Statutory Data Protection Safeguard
WhatsApp AI Ordering Voice notes, text strings, phone number, order preferences Transient processing; 14-day voice note deletion; probabilistic AI disclaimer; Article 18 human review right
Smart Table QR Code Table number, order items, split payment selections No card storage; session-isolated cart data; Merchant floor liability
Branded Web Storefronts Diner contact details, delivery address, order history Merchant is Data Controller; FoodZapp non-monetization guarantee
Phone Order Logging Caller name, phone number, verbal order choices Merchant acts as input agent; digital receipt link dispatched to caller
Meal Subscriptions Recurring calendar dates, address, subscription plans Fixed delivery schedules; non-refundable post-preparation; 5-yr VAT log
Digital Checkout Gateways Tokenized payment gateway reference IDs Strict PCI-DSS gateway routing; Zero Card Retention on FoodZapp servers
3PL Fleet Integration GPS coordinates, delivery street address, recipient phone Data shared strictly for fulfillment; restricted to active delivery window