Restaurant App
Privacy Policy
🍽️

Bahiran Restaurant App
Privacy Policy

How we collect, use, and protect your business and personal information as a restaurant partner on the Bahiran Delivery platform.

📅 Effective: April 6, 2026
🏢 Bahiran Delivery / Gebeta Tech
🌍 Ethiopia
01

Introduction

This Privacy Policy applies to the Bahiran Restaurant App — the progressive web application used by restaurant partners to manage incoming orders, update their menu, control their open/closed status, track earnings, and interact with customers and drivers via the Bahiran Delivery platform.

As a restaurant, you are both a business entity and an account holder on our platform. We collect business-level and account-level data to operate the partnership. This policy explains what data we collect, how it is used, and how it is protected.

🏪 Restaurant accounts require admin approval before going live on the platform. Your location coordinates are used to match your restaurant to nearby customers and drivers.

02

Data We Collect

We collect the following data from restaurant accounts:

🏢
Business Identity
Restaurant name, phone number, email address (optional), logo image, physical address, and business description.
📍
Location
GPS coordinates of your restaurant location (2dsphere geo-indexed). Used for nearby search and delivery routing.
🍕
Menu Data
All menu items including names, descriptions, prices, categories, availability status, photos, and packaging fee flags.
📋
Order Activity
All orders received, their status, items, pricing, and order timestamps. Full order history.
💰
Earnings & Wallet
Wallet balance (ETB), total earnings, packaging fee configuration, and withdrawal history.
Ratings
Customer ratings received, cumulative rating sum, total number of ratings, and average score.
🕐
Operating Hours
Configured opening and closing times, current open/closed status, and accepting-orders flag.
📱
Device & Session
Device platform, device ID fingerprint, and FCM push tokens registered per logged-in device.
🍳
Cuisine Tags
Cuisine category labels (e.g., Ethiopian, Italian, Fast Food) used to categorize your restaurant for customers.
🔐
Authentication
Hashed password (bcrypt), JWT tokens, phone verification status, approval status, and ban status.
03

How We Use Your Data

PurposeData UsedLegal Basis
Displaying your restaurant to nearby customersName, location, cuisine, menu, logo, hours, ratingsContract performance
Receiving and managing ordersMenu items, prices, order history, availability statusContract performance
Coordinating driver pickupRestaurant address, location coordinatesContract performance
Earnings tracking and wallet managementOrder totals, fees, wallet balanceContract performance
Withdrawal processing via ChapaWallet balance, bank/mobile payment infoContract performance
Restaurant approval and vettingIdentity, address, phone verificationLegal obligation / Legitimate interest
Showing customer-facing ratingsRating average and countLegitimate interest
Push notifications (new orders)FCM tokens, device platformConsent / Legitimate interest
Fraud prevention and policy enforcementAccount data, behavior, ban statusLegitimate interest
04

Location Data

Your restaurant's GPS coordinates are stored in MongoDB with a 2dsphere geo-index, enabling:

Your location is static (set during registration) and is not continuously tracked like driver locations. You may update your location by contacting support.

05

Menu & Pricing Data

Your full menu — including item names, descriptions, prices, categories, photos, availability, and packaging fee settings — is stored and displayed publicly to customers browsing the Bahiran User App. This is the nature of a marketplace listing:

06

Earnings, Wallet & Withdrawals

Revenue generated from orders flows into your in-app wallet (ETB balance). When you request a withdrawal:

07

Push Notifications

We use Firebase Cloud Messaging (FCM) to notify restaurants of:

The Restaurant App supports multiple devices per account. Each device's push token is registered separately. Tokens are removed on logout.

08

Third-Party Services

ServicePurposeData Shared
Chapa TransferRevenue payout to restaurantWallet balance, bank/mobile details
Firebase (Google)Push notificationsDevice push tokens
CloudinaryLogo and menu item photo storageRestaurant and food images
AfroMessageSMS OTP verificationPhone number, OTP
Google MapsMap display for location and routingRestaurant coordinates
Redis (RedisLabs)Order queue caching, session managementSession tokens (encrypted)

We do not sell restaurant data to third parties for marketing purposes.

09

Restaurant Approval & Account Status

New restaurant accounts must be reviewed and approved by Bahiran administrators before going live. During this process:

10

Data Retention

11

Your Rights

👁️
Access
Request a copy of your restaurant account data and order history
✏️
Correction
Update your business name, menu, hours, location, or contact info in-app
🗑️
Deletion
Request account and data deletion (subject to financial record retention requirements)
📤
Portability
Request your menu and order data in a machine-readable format
🔕
Notifications
Disable push notifications from your device settings
🚫
Object
Object to processing based on legitimate interests by contacting us
12

Security

13

Changes to This Policy

We may update this Privacy Policy when our data practices change. Material changes affecting restaurant partners will be communicated via in-app notification and SMS at least 7 days in advance. Continued use of the Restaurant App after the effective date constitutes acceptance.

14

Contact Us

Questions about restaurant data?

Reach the Bahiran Delivery privacy team at Gebeta Tech.

✉️ bahiran@gebetatech.com