Food Delivery — User app, restaurant app, driver app, and Laravel admin backend
A food delivery platform necessarily moves personal data around: an address so the food arrives, a driver location so you can watch it approach, a payment so the order is paid. This policy sets out exactly which data goes to whom, and for how long.
Food Delivery is software that an organization installs and runs on its own infrastructure. The business operating a given installation decides what data is entered into it and is the data controller for that installation. This page documents what the application itself collects and processes by design; it is the reference policy for the software, and an operator may publish additional terms on top of it. As the developer, I have no access to any production database unless an operator explicitly grants it for maintenance.
| Data | Why |
|---|---|
| Account data | Name, phone number, email, profile photo, and a hashed password — for every role (customer, restaurant, driver). |
| Delivery address & pinned coordinates | So the restaurant and driver can find you, and so delivery distance and fee can be calculated. |
| Driver location | Live coordinates while a delivery is active, for customer tracking and dispatch. Collected only when the driver is online and on a job. |
| Order data | Items, notes, price, status history, and timestamps — shared with the assigned restaurant and driver. |
| Payment status | Midtrans order ID, amount, method, and status. Card and account numbers never reach the platform. |
| Ratings and reviews | Your rating and comment about a restaurant or driver, shown with your display name. |
| Push token | A per-device Firebase token used to deliver order notifications. |
| Device & technical data | Device model, OS version, app version, and IP address — for troubleshooting and fraud prevention. |
Customer app: location is used to suggest nearby restaurants and to pin your delivery address. You can enter an address manually instead of granting the permission.
Driver app: location is transmitted while the driver is on shift and carrying an active order, so the customer and dispatcher can see the delivery progress. It stops when the driver goes offline or the order is completed. The route history of a completed delivery is retained for dispatch dispute resolution and payout verification.
Location is never used to build advertising profiles or shared with data brokers.
| Service | What it does |
|---|---|
| Google Firebase Privacy policy ↗ | Authentication, cloud database, and file storage. Data is stored on Google servers in the project owned by the operator. |
| Firebase Cloud Messaging Privacy policy ↗ | Delivers push notifications. Uses a per-device push token that is regenerated when the app is reinstalled. |
| Google Maps Platform Privacy policy ↗ | Displays maps, geocodes addresses, and draws delivery routes. Google receives the coordinates being displayed or geocoded. |
| Midtrans (PT Midtrans) Privacy policy ↗ | Processes payments (QRIS, virtual account, e-wallet, card). Card and banking details are entered on Midtrans’ own page — this application never sees or stores them. |
| Pusher Privacy policy ↗ | Real-time channels for order and status updates. Message payloads pass through Pusher’s infrastructure. |
Order and payment records are kept for as long as the operator’s accounting and dispute-resolution needs require. Live location points are retained with the order they belong to; no continuous location trail exists outside an active delivery.
You can request account deletion from the operator through the app or by contacting their support. Financial records tied to completed orders may be retained in anonymised form to satisfy bookkeeping obligations.
The application applies standard protections: passwords are stored as one-way hashes (never in plain text), access is limited by role, and all traffic between client and server is expected to run over HTTPS/TLS.
No system is perfectly secure. Server hardening, backups, and access management for a live installation are the responsibility of the organization operating it.
The apps are not directed at children under 13, and ordering requires a verified phone number and a payment method.
You have the right to ask for access to, correction of, or deletion of your personal data, and to object to certain processing.
Because your data lives in the installation run by the organization you deal with, address those requests to that organization first — they hold the data and can act on it. If you cannot reach them, or you believe the application itself is at fault, contact the developer at mhdlutfidev@gmail.com and I will assist technically.
If this policy changes, the “Last updated” date at the top of this page will be revised. Material changes will be reflected in the application release notes.
Questions, complaints, or privacy requests about this application:
I aim to respond within 7 business days.