Privacy Policy

Playfood and Playfood Driver apps (kz.playfood.driver) — Effective May 14, 2026

Summary. We collect location data (including background location — even when the app is closed or not in use), name, phone, document photos and device information. This data is used only to operate the Playfood food-delivery / taxi service (order dispatching, navigation, payouts, safety). We do NOT sell data to third parties and we do NOT use it for advertising.

1. Who we are

Data controller: TOO «Playfood», a legal entity registered in the Republic of Kazakhstan, Almaty.

Email: support@playfood.kz
Phone: +7 (700) 085-63-63
Data deletion request: playfood.kz/privacy/data-deletion

2. Data we collect

Category	Specifically	Source
Location	Precise (GPS) and approximate (network) coordinates, speed, heading, accuracy	Device sensors, while the courier is on an active shift
Personal	Full name, phone number, date of birth, IIN (Kazakhstan tax ID)	Sign-up / profile
Documents and photos	Driver licence photo, selfie, vehicle photo, medical certificate, shift photo-checks	Camera / Photo Picker
Contacts (Driver only)	Local lookup of contact name when the customer's phone matches an entry on the device. Data NEVER leaves the device	On-device only
Order data	Trip / delivery history, ratings, earnings, tips	Server-side history
Technical	Device model, Android/iOS version, FCM token, IP address, crash logs	Automatically on launch
Payment	Card details for earnings payouts (stored at PCI-DSS-compliant provider)	Via PCI-DSS provider

3. Background location (ACCESS_BACKGROUND_LOCATION)

IMPORTANT. The Playfood Driver app collects location data (GPS), including even when the app is closed or not in use. This permission is requested separately, with a dedicated in-app prominent disclosure dialog shown BEFORE the Android system permission dialog.

3.1. Why we need background location

Order dispatching. The server picks the closest available driver based on real-time GPS.
ETA. Customers see how many minutes until the driver arrives.
Customer transparency. The driver appears live on the customer-facing map, refreshed every 5–10 seconds.
Pricing. Distance and duration are computed from the actual GPS track, not approximations.
Safety. If anything happens to the driver, the dispatcher sees the last known location.

3.2. When collection starts and stops

Collection starts only when the driver taps "Go on shift" inside the app.
Collection fully stops when the driver taps "End shift", logs out, or uninstalls the app.
While collecting, a permanent Android notification "Tracking active" is always visible — you always know GPS is running.
You can revoke the permission at any time: Android Settings → Apps → Playfood Driver → Permissions → Location → Allow only while using / Deny.

3.3. Who we share location with

Playfood servers (HTTPS/TLS 1.2+).
Partner-company dispatcher who registered your shift.
The customer who placed your active order — only while the order is in progress. Once delivered, location is no longer shown to that customer.

We do NOT share location with ad networks, data brokers, insurance companies, or any third party for marketing.

4. Permissions and why we request them

Android permission	Purpose
ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION	Driver GPS during shift
ACCESS_BACKGROUND_LOCATION	Tracking when screen is locked or driver uses a navigation app (see §3)
FOREGROUND_SERVICE / FOREGROUND_SERVICE_LOCATION	Persistent "Tracking active" notification during the shift
POST_NOTIFICATIONS	Push notifications about new orders
USE_FULL_SCREEN_INTENT	Full-screen incoming-order alert on the lock screen (similar to a phone call)
SYSTEM_ALERT_WINDOW	Floating "return to Playfood" bubble while you use a navigation app
CAMERA	Shift photo-checks and document upload
READ_CONTACTS	On-device lookup of customer name in driver's address book. Data NEVER leaves the device
RECEIVE_BOOT_COMPLETED / WAKE_LOCK	Resume work after a phone reboot
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS	Prevent Android from killing the foreground service

5. Third-party services (data processors)

Google Firebase Cloud Messaging — push delivery. Sends FCM device token. Privacy.
Google Crashlytics — crash reports. Sends device model, stack trace, pseudonymous user ID.
MapLibre / OpenStreetMap — map rendering. Tile requests carry the device IP only; no personal data.
PCI-DSS L1 payment provider — stores and processes card details for earnings payouts.

6. Retention

GPS coordinates — 90 days, then aggregated into anonymous distance statistics.
Order history and finance — 5 years (Kazakhstan tax law).
Documents (driver licence, selfie) — for the duration of the contract + 1 year.
Crash logs — 30 days.
After account deletion, all non-mandatory data is removed within 30 days.

7. International data transfers

Playfood servers are physically located in the Republic of Kazakhstan. Third-party processors (Firebase, MapLibre) may handle data on EU/US servers. These providers comply with GDPR and/or EU SCCs.

8. Your rights

Request a copy of your data (GDPR Art. 15).
Correct inaccurate data (Art. 16).
Delete your account and associated data (Art. 17 — right to be forgotten): playfood.kz/privacy/data-deletion.
Revoke location consent at any time via Android settings.
File a complaint with the Kazakhstan personal-data authority.

9. Security

All data is transmitted over HTTPS/TLS 1.2+.
Passwords stored as Argon2id hashes.
Admin panel access requires 2FA + IP allow-list.
Access logs retained and audited.

10. Children

Playfood Driver is restricted to users 18 years and older (driver licence required). We do not knowingly collect data from minors.

11. Changes to this policy

Material changes will be announced in-app and by email. The effective date is shown at the top of this document.

12. Contact us

Email: support@playfood.kz
Subject line: "Privacy / GDPR"
Response time: up to 30 calendar days