FoodApp Restaurant Manager — Privacy Policy

Last updated: 2026-05-27 · Applies to the Android app fi.foodapp.manager

Who this app is for

FoodApp Restaurant Manager is a business-to-business app installed on the in-restaurant tablet (typically a Sunmi V2/V3 device) by restaurant staff. It is not a consumer-facing app. Restaurants use it to receive and process incoming orders placed through the FoodApp ordering platform.

Data we access on the device

• Login credentials (restaurant name, admin username, password) — entered by staff and stored locally to skip re-login between shifts. Stored only on the device.
• API auth token issued by the FoodApp backend after login — stored locally on the device only.
• Order data (order ID, items, customer name/phone, delivery address, totals) — fetched from the FoodApp backend over HTTPS so the kitchen can prepare and print the order. Not stored beyond the active session except in operating-system caches.
• Pusher subscription on a private channel scoped to the restaurant — used to receive real-time new-order notifications.
• Bluetooth pairing with the kitchen's thermal printer (when configured by the restaurant) — required to print tickets. No data is sent over Bluetooth except the print payload.

Data the app does NOT collect

• No advertising identifier. We declared "App does not use advertising ID" in Play Console.
• No location tracking. The app does not request location at runtime.
• No analytics SDKs that track the staff user. The app uses Sentry only for crash reporting (anonymous device + version metadata).
• No financial features. Payments live in the customer-facing app, not here.
• No health data. The app has no health or fitness functionality.
• No SMS / call logs / contacts. The app does not access them.

Foreground service

The app uses Android's FOREGROUND_SERVICE_DATA_SYNC permission to keep its order pipeline alive on aggressive Sunmi power-savers and MobileGuard. The service:

• Keeps a WebSocket connection to Pusher to receive new-order events.
• Issues a periodic HTTPS poll to /api/admin/orders/check on the FoodApp backend as a safety net when Pusher is unreachable.
• Triggers a local alarm (ringtone + vibration) when a new order arrives.

The persistent notification "Listening for new orders" is visible to staff at all times while the service is active.

How data is transmitted

All communication between the app and the FoodApp backend uses HTTPS (TLS). The backend lives at foodappordering.com. Order data is end-to-end encrypted in transit. Pusher uses an authenticated WebSocket on a private channel that only the authorised restaurant can subscribe to.

Data retention

Login credentials remain on the device until the staff signs out or uninstalls the app. Order data is cached on the device only for the duration of the active session and is automatically cleared on logout. Server-side retention of order data is governed by the FoodApp backend's policy.

Updates to this policy

This privacy policy may be updated when the app's data practices change. Material changes will be communicated to restaurant accounts via email.

Contact

Questions or data requests: [email protected].