Tell me what you have, or pick a starter below. I will point you to the right CSINT page and the next safe step.
Event Desk Pro
Claim, evidence and review workspace
Examine a claim with its sources, organise the evidence and share the result as a reviewable case file.
Team workspace features are currently available through the controlled pilot.
Open work
Active work
Reading the workspace.
Investigation console
Open file
Reading the workspace.
Evidence impact
Impact review
When a bound public source changes, the engine opens a separate review record for every affected evidence row, claim, export and share. The decision always stays with a person.
Reading impact records.
Lens
Take a public claim to publication readiness: source, timing, right of reply and a correction record.
Order of work in this role
- Verify a public claim
- Record the original source and publication time
- Compare independent sources
- Keep a right-of-reply note
- Review publication risk
- Prepare an editor brief
- Keep a visible correction history
This order is a checklist. The application does not perform these steps for you; you record each one.
Evidence chain
From claim to output
Each stage opens the existing workspace where that work is done.
- Open the desk
Claim
Write the single sentence being checked and where it came from.
Sample caseA corporate sign-in page reported as suspicious.
- Record the source
Source
Record the original address, the publication time and who published it.
Sample caseA urlscan.io result and a certificate transparency record.
- Open the vault
Artifact
Put the screenshot, log or document into the encrypted vault.
Sample caseA page screenshot and the certificate record.
- Examine the relationships
Finding
Write what the evidence shows and connect the entities behind it.
Sample caseThe page layout matches the real service; the host sits on a different autonomous system.
- See the readiness
Confidence
State the strength of the assessment and what is still missing.
Sample caseMedium. Limitation: the original message headers are unavailable.
- Open the review list
Review
Hand the file to a second reader and close the objections that come back.
Sample caseWaiting for a second reviewer.
- Open saved work
Output
Export or hand off the evidence list and the short report.
Sample caseAn evidence list and a short report.
AssessmentThe available indicators are consistent with a phishing campaign. This is an assessment, not a verdict.
The rows below are a sample, not a real case record.
Output
What you can produce in this role
Source list
WorkingThe Markdown export of a saved packet carries the source of every evidence row.
Verification timeline
WorkingPacket detail lists the claim history with its recorded times.
Editor brief
LocalThe executive brief tool drafts in the browser and makes no lookups.
The readiness list on this page is kept in this browser only.
Correction note
PlannedA separate correction record format does not exist yet. Note it on the evidence row for now.
Status
Capability status
Statuses are written from the code as it stands today. Planned rows are never mixed in with working ones.
| Capability | Status | Data location | Action |
|---|---|---|---|
| Evidence packets | Live | Workspace, sign-in required | Open |
| Encrypted evidence vault | Live | End to end encrypted, key stays in the browser | Open |
| Link analysis | Live | Workspace, layout kept in this browser | Open |
| Report export (Markdown, JSON, PDF) | Live | Workspace | Open |
| Source change signals | Live | Workspace review list | Review |
| Threat watchlist | Pilot | Workspace and public sources | Review |
| Team review and encrypted discussion | Pilot | Encrypted workspace | Details |
| Advanced workbench tools | Local only | This browser only, no lookups | Open |
| Correction and mitigation note formats | Planned | Not active | Scope |
Workspace tools
Evidence vault, watchlist and saved work
The exposure report, executive brief, redaction review and deliverable library sit on their own page.
Plans and access
Access, plan and billing controls are collected here.
Core verification stays free. Pro opens by pilot invite; there is no public signup or payment flow yet.
Pilot scope: packet storage, Markdown/JSON/PDF export, audit log, team assignment/comments and human-reviewed Review Desk. Out of scope: live social feeds, person tracking, doxxing, public auto-publish and full invoice automation.
- Demo recordShows how the workspace looks with sample data.
- Review DeskWorker review queue and controlled source signals. Owner and editor only.
- Client review linksSend a client-safe review packet without exposing the workspace. Expiring, revocable links.
- Admin accessGrant pilot access or review workspace health.
- Terms and safety boundaryRetention, privacy and OSINT boundaries.
- Security modelWhat is protected, what the server sees, what is not covered.
Pilot access and plan
Check pilot status
When you're signed in, your plan appears here. If Stripe is live, checkout starts here; if it is off, Pro access opens by manual invite.
Checking session…
CSINT does not collect or store card details; checkout and billing management run through Stripe. If production Stripe is off, Pro access opens after use-case fit, safety boundaries and manual approval.
Safety boundary. Pro Workspace is not used for people tracking, location surveillance, social-media scraping or live conflict feeds. Advanced features run on whitelisted sources with human approval.