Dreamcare Developers Pvt. Ltd.
Privacy Policy
This policy explains how Bandobast collects and uses data for police deployment planning, officer duty coordination, active-duty tracking, evidence review and account security.
Last updated: 29 June 2026
Who this policy covers
Bandobast is intended for authorised police, command, controller and administrative personnel. It is not a public consumer social app. Access is controlled by account role, district, station, zone or branch scope.
Data we collect
| Category | Examples | Why we use it |
|---|---|---|
| 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. |
Location, camera and notifications
Precise location is used during active duty to show approach, check-in, drift and live deployment status to authorised command users. Background location is used only for active duty workflows that require live tracking. The camera is used for check-in selfies and optional chat attachments. Notifications are used for duty, escalation, approval, chat and operational alerts.
How data is shared
Data is shown only to authorised users in the relevant operational command chain and district scope. We may process data using trusted hosting, database, storage, notification, crash reporting and security providers needed to run the service. We do not sell personal data.
Retention
| Record | Retention |
|---|---|
| Raw location samples | Normally 90 days |
| Notifications | Normally 1 year |
| Audit log | Normally 5 years |
| OTP request data | Removed shortly after use or expiry |
| Placement events and duty records | Kept as operational history |
| Chat messages | Kept with the conversation history |
Security
Access is authenticated, operational data is scope-restricted, and production traffic should use HTTPS. Logs avoid OTP codes, raw GPS coordinates, selfie URLs, chat bodies, phone numbers and tokens.
Account deletion and corrections
Account access and deletion requests must be handled through the responsible organisation or developer support because accounts are assigned for official operational use. See account deletion for request steps. Some audit, legal, security or operational records may be retained when required.
Contact
For privacy questions, contact arthadmin01@gmail.com. Mention the app package in.bandobast.app and the district or organisation that manages your account.