Forward this page to your compliance team. Everything below is implemented and demoable today — and where something is a roadmap item, it says so.
GPS must lock before a report can be submitted. Coordinates, accuracy, timestamp and slot name are burned into every photograph on the officer's device.
Each image is SHA-256 hashed on the device — the hash covers exactly the stamped file that is stored. Voice notes are stored the same way.
Every state transition (routed, assigned, visit, submitted, QC, delivered) appends a hash-linked entry to the case's audit chain. Only the workflow engine can write it — direct inserts are closed at the database level.
The one-click Auditor Pack re-computes the entire chain at export and states the result: report PDF + every evidence file + manifest with hashes, sealed in one archive.
Every case carries a consent artifact — who attested, when, through which channel (console, bulk, or API). No consent, no case.
Each organisation sets an evidence retention period. Expired evidence on closed cases is purged automatically on a daily job.
Templates and capture flows are built without Aadhaar fields, by design.
Application and database run in Mumbai (ap-south-1).
A documented, timestamped complaint trail for outsourced field activity — the RBI outsourcing expectation, built in.
Every action is attributed to an individual login. Field officers are database-isolated to their own tasks; applicants can QR-verify the officer at the door.
We list the roadmap because your procurement team will ask — and because a vendor who claims everything is done usually hasn’t been asked hard questions yet.
Run the pilot — every delivered report in it comes with the sealed, re-verified evidence archive.