CCT Smart
Always available
Passive read of public manifest data. Does not touch device state.
— Product · operational
Mobile forensics platform. Available today.
Acquires Android and iOS devices, extracts artifacts, generates court-admissible reports. Native to Section 65B of the Indian Evidence Act 1872 (for matters predating BSA 2023) and to Section 63(4)(c) of the Bharatiya Sakshya Adhiniyam 2023 (the post-2024 framework).
— Same depth
Across 40+ capabilities benchmarked, Chakra Intel is at parity or ahead on the forensic core that decides Indian cases. Here is the honest read of where it stands.
— Where we lead
India-engineered.
7
— Where we match
At parity.
6
— On our roadmap
On the way.
5
Full capability-by-capability benchmark on request. sales@cyberchakra.in.
— Pipeline · nine stages
Nine stages, every one named, every one signed at the byte. The diagram below mirrors what runs inside Chakra Intel on a live acquisition.
01
Workstation readiness
Write-blocker engaged. Network isolated. Baseline hash captured.
02
Seizure log
Chain of custody opened. Evidence identifier issued.
03
Acquisition
Engine selected at intake. Image captured byte-for-byte.
04
Integrity verification
SHA-256 + BLAKE3 re-computed and matched at every handover.
05
Parsing
Artifacts decoded across system and application schemas.
06
Review
Examiner annotates. Reviewer cross-checks before sign-off.
07
Certification
Section 63(4)(c) certificate generated and signed at the byte.
08
Bates numbering
Every page sequentially marked for court submission.
09
Custody seal
Record sealed with the Ed25519 sign-off chain. Closed.
— Acquisition · five engines
Each engine corresponds to a device state and an acquisition depth. The right one is chosen at intake, not by default.
Passive read of public device metadata. Manifest, SIM identifiers, telecom carrier, radio history. No mutation to device state.
Standard logical extraction over ADB. Requires AFU + USB debugging. Recovers app data, messages, photos, call logs.
Exploit-fit logical extraction with temp-root. Reads filesystem in privileged context. Session terminates cleanly. Persistent state unchanged.
Full memory image. Chipset and bootloader specific. Recovers deleted data, slack space, hardware-keystore-resident artifacts where exploit permits.
Account-side acquisition under lawful warrant. Drive backups, Gmail metadata, photo originals, location history. Overlays the device-side image.
— Investigation · eight modes
Named surfaces for the work after acquisition. Each mode is a distinct analytical lens, not a tab.
Visual case linking. Relationship maps across artifacts, accounts, and devices, each node sourced to a hashed evidence item.
Payment-trail analysis. UPI handle clustering, mule-account detection, and wallet tracing across the seized device's app history.
Chronological event ordering across messaging, calls, app activity, location history, and system logs. One picture of what happened when.
Location history mapping. Resolves device positions over time from GPS records, cell-tower handovers, and Wi-Fi fingerprints recovered from app data.
Contact and conversation analysis across messaging apps, calls, and email. Relationships as a graph. Thread density as edges.
Photo and video review. EXIF inspection, perceptual hashing, and source-derivation matching against the public web where lawful.
Per-application database forensics. WhatsApp Crypt14, Signal SQLCipher, UPI app history, and the long tail of social and finance app schemas.
Continuous chain-of-custody record. Every action stamped, signed, and Bates-numbered from intake to court submission.
— Coverage and integrity
— What gets parsed
— Mobile OS
Android 8 through 14. iOS 10 through 18.
— Parsers
180+ across system and application data.
— Messaging
Thirteen messaging apps. WhatsApp Crypt12, Crypt14, Crypt15. Signal SQLCipher.
— Decoders
Thirty+ app decoders for finance, social, navigation, and productivity surfaces.
— Court-survivable by construction
— Hash
SHA-256 + BLAKE3 dual-hash on every byte. Re-verified at every handover.
— Signing
Ed25519 signatures applied per sign-off. The signing chain is part of the report.
— RBAC
Six-role access control. Examiner → reviewer → supervisor sign-off chain closes before any report leaves the lab.
— Certification
Section 63(4)(c) certificate generated at acquisition. The certificate is born of the acquisition itself, signed and dated at the byte.
— The honest envelope
Acquisition is a strategy, not a button. The matrix below names what each engine needs and what is in scope for a typical device. Specific device state changes the picture.
Always available
Passive read of public manifest data. Does not touch device state.
AFU + USB debugging
Available when the device is unlocked and ADB is on. Reads app data.
Exploit fit or temp-root
Depends on chipset and patch level. Reads filesystem in privileged context.
Chipset + bootloader exploit
Full memory dump. Specific to device family. Honest about what is and is not in scope.
Lawful account access
Drive backups, message backups, account-side metadata. Under warrant.
Chakra Intel can unlock some phones. Whether a given device is in scope depends on chipset, Android version, and bootloader state. The envelope is named, not hidden.
— Deployment
Chakra Intel runs on the lab's hardware. No cloud dependency. No remote license server. No telemetry leaves the workstation. The deployment matches institutional environments where evidence and infrastructure both stay inside the perimeter.
Where a deployment needs cloud-backed processing, the storage and compute sit on Indian government-backed sovereign cloud. Evidence never leaves Indian soil.
— See the work
The journey sandbox includes a Section 63(4)(c) showcase case that runs from acquisition to a self-proving certificate. About six minutes.
Walk the-65b-case →— Trial
A verified contact at your institution receives a 5-day trial license after strict approval. Six steps to apply, about five minutes.
Start a trial →