Bangladesh Police · LIC Barishal
A lawful, auditable bridge for operator subscriber lookups
Authorized officers request subscriber location and identity information from mobile operators through Telegram. Every request is logged, reviewed, and tied to the requesting officer. Nothing is sent, and nothing is posted back, without a record of who asked and who checked it.
How it works
Four steps, every one of them logged
Officer submits a request
A formatted lookup command (LRL, LCL, MS-NID, NID-MS, IMEI-MS) is sent through Telegram by a registered officer.
Routed to the right gateway
The backend routes it to the correct operator's dedicated gateway phone and sends the SMS exactly as formatted, with no manual copying.
Operator replies, tagged by requester
Only trusted sender replies from configured operator numbers are processed and matched back to the original request.
Reviewed before posting
A human reviewer approves the reply draft before it's posted back to the requesting officer on Telegram.
Why officers trust it
Built for accountability, not just speed
link
Tamper-evident audit log
Every step (submission, dispatch, reply, review) is recorded in a hash-chained log. Nothing can be quietly edited after the fact.
badge
Registered officers only
Access is validated against the real Personnel Registry — phone and email have to match a genuine record before an account is ever created.
policy
Human review, every time
No operator reply reaches a requester without a reviewer approving it first — the system assists, it doesn't decide.
shield_lock
Layered access control
Officers, admins, and the super-admin each see only what their role needs — enforced by the server, not just hidden in the interface.