Koolodoor
Legal page

Privacy Policy

Last updated: August 2, 2026. This policy explains how Koolodoor collects, uses, stores, and protects personal data for discovery, in-app ordering, delivery, fleet duty, push notifications, and cash-on-delivery finances.

Discovery, orders & COD Fleet duty location on duty only No personal data sale In-app data download & deletion

1) Scope

This Privacy Policy applies to Koolodoor apps, websites, and related services used by guests, customers, restaurant staff (partners), and delivery riders. Guests can browse listings and build a cart without signing in. Signed-in users may place orders, manage a profile, operate restaurant tools when linked to a business, join fleet duty as a rider, and view earnings or wallet activity where applicable.

2) Data We Collect

Account and profile data

  • Name, phone number, email address, username
  • Public profile details you choose to publish (for example display name, username, public contact fields you add, and profile photo)
  • Restaurant affiliation shown on your public profile when you have an active membership: the name and public handle of the linked restaurant group and/or business (store), visible to other signed-in users who view your profile—not to anonymous visitors without an account
  • Account creation date (“joined”), shown on your public profile (for example as “Joined …” on the Info tab) to other signed-in users who view your profile—not to anonymous visitors without an account
  • Business address for restaurant profiles (physical address where you operate or deliver, when you provide it)
  • Photos and videos you upload (for example profile images, business or venue photos, and menu or item imagery)
  • Other content you submit in the service (for example restaurant “about” sections, menu item names, and descriptions)
  • Account identifiers and user IDs (for example your Firebase Authentication user ID and other stable IDs we use to operate profiles and permissions)
  • Authentication and session metadata

Orders and delivery

  • Order contents (items, modifiers, notes), fulfillment type (pickup or delivery), and order status history
  • Delivery addresses you save or select, including street details and precise coordinates (latitude and longitude) required to route and complete delivery
  • Contact phone number used for order fulfillment. Customers must verify their phone before placing an order; this number is shared with the restaurant and rider only as needed to fulfill the order
  • Cash-on-delivery (COD) payment method selection and order totals (no card numbers are collected in the app)

Rider and fleet duty

  • Rider profile fields such as legal name, country, vehicle type, and operational status
  • Government-issued identity information collected during rider onboarding when required (for example government ID reference), used to verify eligibility and comply with operational requirements
  • Precise device location only while you are on fleet duty, including when the app is in the background, so we can match nearby delivery offers and show live delivery progress. Location tracking stops when you leave fleet duty or log out. We do not track riders when they are off duty

Push notifications and device data

  • Firebase Cloud Messaging (FCM) device tokens and notification preferences, used to deliver order updates, kitchen alerts, delivery offers, and account-related messages you opt into
  • We do not show a notification permission dialog at cold app launch. Permission is requested in context (for example when you open Live orders, enable notifications in Settings, or prepare to join fleet duty)
  • Device type, OS version, language, and app version
  • Limited service and security information needed to run the app (for example authentication-related events and safeguards against abuse), associated with your account when you are signed in

Financial and wallet data

  • COD wallet balances, earnings summaries, remittance records, and ledger entries related to completed orders
  • Partner and rider settlement references (amounts owed, collected, or remitted under our cash-on-delivery model)
  • Practice (Demo) orders are excluded from real financial settlement; related UI may show sample activity only

Location, maps, and printing

  • Approximate or precise location when you enable location services for discovery, maps, address entry, or checkout—depending on the permission you grant
  • When you use maps, search, or geocoding features, your device may send location or query data to third-party map providers (for example Google) under their terms and your device settings
  • On iOS, if a restaurant configures a Wi‑Fi thermal printer, the app may connect to the printer IP address you enter on the local network when you print a ticket or receipt

Support and communication

  • Messages sent to support
  • Feedback reports and issue details

3) Why We Use Data

  • To create and manage user accounts
  • To show which restaurant group or store a user is linked to when they have staff membership, so other signed-in users can see that affiliation in context
  • To show when a user joined the platform on their public profile, so other signed-in users can see that information in context
  • To process in-app orders, route deliveries, and communicate order status to customers, restaurants, and riders
  • To operate fleet duty: assign delivery offers, track active deliveries, and stop location collection when a rider goes off duty
  • To calculate and display COD earnings, wallets, and remittance records
  • To deliver push notifications you have allowed
  • To provide core app features and improve performance
  • To secure the service and prevent fraud or abuse
  • To communicate about support, updates, and policy changes
  • To comply with legal obligations

4) Payments and Checkout

This version of Koolodoor supports in-app ordering with cash on delivery (COD) as the payment method for customer checkout. We do not process card payments or in-app purchases through a payment service provider in this release. Order totals, delivery fees, and service fees are shown before you confirm an order.

We do not include in-app advertising, ad measurement, or dedicated product analytics SDKs in the current app. If we introduce new data uses (for example card payments or ads), we will update this policy and the app before enabling them.

5) Background Location (Fleet Duty)

Riders who choose to go on fleet duty must grant Always location permission (and Precise Location on iOS) after an in-app explanation and acknowledgment, so the app can receive delivery offers and update live delivery progress while the app is in the background. On iOS, a blue status-bar indicator appears while location is active in the background.

Background location is used only during an active fleet duty session. Leaving fleet duty or logging out stops GPS collection immediately. We do not use silent audio or background audio modes to keep the app running. On iOS, background operation for fleet duty uses the declared location, remote-notification, fetch, and processing background modes (the latter two support scheduled fleet-duty task refresh only — not continuous tracking when off duty).

6) Sharing and Disclosure

We may share data only when needed to run the service:

  • Infrastructure providers (hosting, storage, authentication)
  • Map, search, and geocoding providers (for example Google) when those features are used
  • Push notification delivery (Firebase Cloud Messaging)
  • Support and communication tools
  • Restaurants and riders, limited to what is needed to fulfill an order (for example delivery address, contact phone, and order details)
  • Law enforcement when required by law

We do not sell your personal data.

7) Data Retention

We keep personal data only as long as needed for service operations, legal compliance, dispute resolution, and security. Retention windows vary by data type—for example:

  • Account and profile data: retained while your account is active and for a limited period after deletion where required by law
  • Order and delivery records: retained to support order history, support inquiries, and financial reconciliation
  • Fleet duty location updates: ephemeral operational data with short retention for live dispatch; not used for off-duty tracking
  • Financial ledger entries: retained as needed for COD settlement, remittance, and audit requirements
  • Push device tokens: retained while notifications remain enabled and refreshed when you sign in on a new device

8) User Controls and Rights

  • You may update profile fields from app Settings
  • You may download a copy of your data in the app: open Settings → Download Data, start an export, and return to that screen when your file is ready. A time-limited download link is provided in the app (not by email). You can also reach this flow before account deletion if the app prompts you to save your information first.
  • You may delete your account in the app: open Settings, choose delete account, confirm your identity when prompted, and complete the confirmation steps. This starts permanent removal of your account and associated personal data, subject to legal retention requirements.
  • You may control location and notification permissions in your device settings. Disabling Always location or notifications may limit fleet duty and order alerts.
  • For your security, sensitive actions such as account deletion and changing your sign-in email require you to have signed in recently (within about the last 10 minutes). If your session is older, the app will ask you to sign in again before continuing.
  • Depending on your region, you may have additional rights to access, correct, object, or restrict processing. Contact us at contact@koolodoor.com for other privacy requests.

9) Children’s Privacy

Koolodoor is intended for users aged 13 and older. We do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us personal data, contact us at contact@koolodoor.com and we will take appropriate steps to delete it.

10) Security

We use technical and organizational safeguards such as access control, transport encryption, and monitoring. No system is 100% secure, but we continuously improve controls.

12) Policy Updates

We may update this policy over time. Material changes will be communicated in-app or through official channels. The date at the top indicates the latest revision.