Dreamcare Developers Pvt. Ltd.
Google Play Data Safety Summary
This page is a plain-language companion for the Google Play Data safety form for Bandobast. The form in Play Console should match this summary and the privacy policy.
Last updated: 29 June 2026
Collection and sharing
- Bandobast collects personal, operational, location, photo, message, device and diagnostic data needed for official deployment workflows.
- Data is not sold. It is used for app functionality, account security, operational communication, analytics, crash diagnostics and legal or audit obligations.
- Data may be processed by trusted infrastructure providers that host, store, secure, notify, monitor or diagnose the service.
- Data is visible only to authorised users according to command chain, district and scope rules.
Data categories
| Category | Collected | Purpose |
|---|---|---|
| Account and identity | Name, Sevarth ID or service identifier, rank, posting, role, district, station, zone or branch, phone number used for OTP sign-in. | Authenticate authorised personnel, show the correct command scope, assign duties, and keep an operational audit trail. |
| Duty and operational records | Bandobast assignments, posts, reporting status, check-ins, absences, drift events, leave requests, approvals, escalations, pull requests, chat messages and notifications. | Plan deployments, coordinate teams, review attendance, support after-action review, and notify the command chain. |
| Precise location | Foreground and background GPS during an active duty, arrival/check-in coordinates, route/replay samples and drift information. | Verify arrival, support live command visibility, detect geofence drift, and reconstruct active-duty events. |
| Photos and attachments | Check-in selfies and optional chat attachments uploaded by authorised users. | Confirm presence at duty posts and support operational communication. |
| Device, app and diagnostics | Push notification token, app version, device/platform signals, crash reports, performance data, request status and safe error details. | Deliver notifications, protect the service, diagnose failures, and improve reliability. |
Security practices
- Data is transmitted over secure connections in production.
- Access is limited by account role and operational district scope.
- The app supports account deletion requests through developer or organisation support.
- Operational logs avoid OTP codes, raw GPS coordinates, selfie URLs, chat bodies, phone numbers and tokens.
Play Console notes
In Play Console, disclose precise location, photos, messages, user IDs, phone number/contact information, app activity, app info and performance, diagnostics, and any other category that matches the final production build. If a feature is disabled before public release, the Play Console form should reflect the build that users actually receive.