India’s first CDR analysis that runs in your hand.
For verified Law Enforcement Agency personnel only. Product access, demos and licences are not available to the general public.
The first mobile and web-view friendly CDR and tower dump analysis software built for Indian law enforcement. Import the operator file on the phone, get the full report set, and open the same case on a laptop through Web Access — one engine, identical numbers.
Import, analyse, export
CSV and Excel CDRs from Indian operators, parsed on the handset. Every report exports to Word.
Web Access, same engine
Open the same case in a browser with flow diagrams. The numbers are identical on both.
CDR data stays local
Call records are not uploaded. Only tower address and caller-name lookups go out, securely.
From laptop only, to the officer’s hand.
Every earlier report grouped a case by topic — contacts, towers, handsets, counterparties. These reports answer the question an officer actually asks: what happened, in what order, and what followed what.
Event Chain
The CDR read in time order — and what happened within minutes of what.
Abnormalities
Handset changes, long silences, burner swaps and night activity, now without a laptop.
Common Points
What two or more subjects share, with a rebuilt simultaneous switch-off.
Event Chain
Money events in order: credit → rapid debit, failed → retry, new device → transfer.
Money Trail
Where the money that came in went — forwarded, pooled or split — and what was kept.
One report engine
Mobile and Web Access run the same engine, so the numbers are identical on both.
The reports, one by one.
The CDR read in time order.
Trigger patterns come first — pairs of events close enough in time that the first may have prompted the second. Then the chronological chain of significant events only, each showing how soon it followed the last. A ↳ 12 min chip marks a linked pair.
New contacts that went on to recur, handset changes, silences over a day, first visit to a new area, long calls and night activity.
The app gives the sequence. You draw the conclusion.
No report ever says “caused”. Every line reads “within N min of ___, ___ happened”. Sequence and proximity are facts from the record; the inference stays with the investigating officer.
Wording that holds
Every line is phrased “within N min of ___, ___ happened”. Sequence and proximity are facts from the CDR; the finding is the officer's.
Thresholds printed
The thresholds each report used — 30 min, 60 min, more than a day, 24 hours, 75% — appear on the page. If counsel asks, the number is already there.
Merchants marked
Money Trail never counts shop or QR payments as forwarding. Merchants are tagged and shown for context only.
Locations stated plainly
Payment-app locations are app-reported, often network-derived, so no impossible-travel claim is made and an area counts only after three or more transactions.
Where each report lives.
Mobile and Web Access run the same report engine, so the numbers match on both.
The full CDR toolkit, on a handset.
Designed to make field-level CDR analysis faster, simpler and more practical for investigation teams — with a one-tap pre-analysis report as a Word document at the end of it.
Bring one CDR. We’ll show you the chain.
Open a single CDR, run Event Chain, and read the first trigger row aloud — “call from X, and within 21 min the phone went silent for 2 days.” Then share it to Word for the case file.
For authorised law-enforcement and investigation use only. Automated findings are for intelligence and lead generation, and require certification under Section 65B of the Indian Evidence Act, 1872 / Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 before legal use. Thresholds used by each report (30 min, 60 min, 24 hours, 75%) are printed on the report itself.
Product access and activation require verification of law-enforcement credentials.