Login, full name, and session tokens for the courier profile.
Order details: customer name, phone, address, products, notes, and payment status.
Optional photos attached during cancellation or incident workflows.
Starting with version 1.0.24 (26), GPS coordinates and available accuracy and speed are collected and sent to the server only while the app is open, with consent and location permission. Sending stops when the app closes or enters the background. Earlier versions may send background GPS with permission and a persistent service notification.
Order contents, total amount, payment method, and payment status are processed as operational order/purchase history. When available, the new-customer form can optionally submit legal name, tax/personal IDs, contract details, bank, account number, bank code, and tax/registration codes; the app does not ask for a bank card number.
For notifications and secure sessions, the app, server, and Firebase process an FCM registration token, Firebase Installation ID, an app-generated installation/device ID, app version/Firebase user agent, platform, language, notification status, and IP/technical request data visible to the server.
Why location is needed
To show nearby orders and route-related actions correctly.
To confirm delivery and perform GPS radius checks.
To keep courier coordinates updated for dispatchers and internal monitoring.
Sharing and security
Data is not sold for advertising.
Data is used only for order fulfillment, internal monitoring, payment checks, or legal requirements.
Server access is limited to authenticated couriers, authorized administrators, and responsible operators; visibility of push previews on the device depends on Android lock-screen settings.
App data is sent to the official production server shown on this page over HTTPS and is encrypted in transit; the Android release blocks cleartext HTTP traffic.
Google Firebase/FCM may process the token, installation ID, and operational notification payload. For a new-order push, the payload is limited to order ID/number, status, generic title/body, channel, and tap routing; customer/partner name, phone number, and delivery address are not sent. Other authorized service notifications may include their title/body and attachment or target metadata. OpenStreetMap/Nominatim may process a map request, IP address, and requested coordinates for maps and address lookup.
When the courier chooses an external route, route coordinates are passed to Google Maps or Yandex Maps. If online payment is enabled, the selected payment provider may process an order identifier/reference and amount to prepare or verify payment.
How data is used
Operational data is sent to the backend server used by Daily Go Kuryer. The app is designed for internal logistics and delivery operations and does not collect data for advertising targeting.
What may be stored on the device
To keep the session active and support notifications and service sync, the device may store an API token, selected language, notification status, and some local app settings.
User controls
Notifications can be enabled or disabled in the app settings.
Location permission can be managed at any time from device settings.
If GPS is disabled, nearby orders, map features, and some confirmation flows may be limited.
Retention
Profile, session, device, and push-registration data is kept while the account or device is active or while needed to operate and secure the service. Logging out or unregistering a device removes or disables the current token.
Orders, products, amount/payment status, audit records, cancellation photos, and location history are kept only while needed for active delivery, dispute handling, fraud/security, accounting, or legal obligations.
Retention is determined by the data type and applicable purpose above; no single automatic period applies to every category. When the applicable need ends, an authorized administrator deletes or de-identifies the data through the current operational process.
Account and data deletion request
Daily Go Kuryer accounts are created by an organization administrator, not through public self-registration. First send the request to your organization administrator or contact support using the phone/Telegram links on this page.
Use the subject “Daily Go Kuryer account and data deletion” and provide the login/full name and organization. Do not send a password, API token, or customer data. After identity and authority are verified, an authorized administrator processes the request manually.
Account access is disabled, active session and push tokens are revoked or disabled, and account-associated courier profile, device/push identifiers, and courier location data not required for a specific retention reason above are deleted or de-identified from active and recoverable server records. Access to order/audit records retained for a legal or other need listed above is restricted; those records are deleted or de-identified when that need ends.