Investigations involve sensitive material: case narratives, evidence files, and sometimes leads about real people. This page explains how that data moves through the platform, the controls around it and what happens when it is no longer needed. Our privacy policy covers your rights in full.
01How case data flows
- IntakeA case request, workspace user or API call supplies identifiers, context and evidence.
- AnalysisThe platform traces public blockchain data and checks intelligence sources, using public identifiers only.
- ReviewAn analyst reviews findings; off-chain leads need a recorded legal basis first.
- OutputApproved reports and exports are versioned and hashed.
- RetentionData is kept for the engagement, then deleted or returned.
02Who controls the data
When an organisation runs its own investigations in a workspace, it decides what goes in and why. It acts as the controller and we process the data on its instructions. When you contact us directly, request an assessment or a demo, we are the controller of that data.
03What we handle, and what we never handle
- Wallet addresses, transaction hashes, networks and case references
- Case narratives, evidence files and notes added by authorised users
- Account, organisation and contact details
- Roles, assignments, approvals and activity history
- Invoices and payment status (not card details)
- Private keys or seed phrases
- Wallet passwords, exchange logins or one-time codes
- Advertising or behavioural profiles
- Device fingerprints or location tracking
- Data from our free tools, which stays in your browser
04Controls on sensitive lookups
Blockchain records are public, but leads about people are not. Off-chain identity sources, such as e-mail, phone or username checks, only run when the analyst has recorded the legal basis for that lookup on the case. Without one, the source is not queried and the case shows why.
Lookup results are not added to a case automatically. An analyst chooses what to keep; results that are not saved are discarded after 72 hours.
05Evidence integrity
- Uploaded evidence files are fingerprinted with SHA-256 and logged to a custody chain when they arrive.
- Each custody entry is linked to the one before it, so a removed or altered entry breaks the chain and can be detected.
- Report versions are hashed when approved; an export package carries its own hash so the recipient can verify it.
- Transaction evidence records the network’s finality state, so a pending or failed transaction is not presented as settled.
06Access and security
| Control | What it does |
|---|---|
| Role-based access | Users see only the workspaces and cases they are assigned to, with permissions set by their role. |
| Review before release | Reports need approval before they can be issued. |
| Audit trail | Sign-ins, case changes, approvals and exports are recorded. |
| Encryption in transit | All traffic uses TLS. |
| Secure sessions | Session cookies are Secure, HttpOnly and SameSite=Lax, with strict session handling. |
| Credential handling | Passwords are stored as salted hashes; access links are stored as hashes and expire. |
| Abuse limits | Public forms are rate-limited by address and e-mail. |
07AI-assisted features
Some workspace features can draft report text with an AI model. They run only when a user starts them, send only the case content the draft needs, and every draft is reviewed by a person before it is used. Customer case content is not used to train AI models.
08Service providers
| Category | Data they receive |
|---|---|
| Hosting and infrastructure | All platform data, stored and processed on our behalf |
| E-mail delivery | Recipient address and message content |
| Payments (Razorpay, PayPal) | Billing and payment details you enter with them |
| AI model provider | Case content for a draft a user requests |
| Blockchain and intelligence sources | Public identifiers being traced or checked |
We do not sell data or share it with advertisers, data brokers or other exchanges. We disclose case data to others only when the customer directs us to, or when a valid legal order requires it; where allowed, we tell the customer first.
09Retention and deletion
| Data | Kept for |
|---|---|
| Workspace cases, evidence and reports | The life of the engagement, then deleted or returned as agreed |
| Off-chain lookup results not saved to a case | 72 hours |
| Server security logs | 30 days |
| Billing records | As required by tax and accounting law |
| Erasure requests | Completed within 30 days unless the law requires us to keep the data |
Workspace administrators can ask for an export of their cases and reports at any time. Public blockchain records cannot be deleted by anyone.
10If something goes wrong
If we discover a security incident affecting personal or case data, we contain it, investigate it and notify affected customers and the relevant authorities as the law requires, telling you what happened, what data was involved and what we are doing about it.
