privacy
CSINT is a static archive built to collect as little as possible. This page explains in plain language what stays in your browser, which requests pass through Worker surfaces, and what is never collected.
note 01
Resource notes, evidence logs, report drafts, Event Desk workspaces, your theme/accent choice, and the latest update you have seen live in your browser's localStorage. They are never sent to a server, no other user can see them, and clearing browser data deletes them. Use the download buttons in each tool if you want a backup.
note 02
The site itself is static and has no server collecting form data. Three tools relay requests through Cloudflare Workers: the chat assistant (your question is forwarded to the model), the Web Archive Desk (the URL you look up is forwarded to archive services), and the Event Desk Pro Workspace (a separate Worker holding magic-link sessions and packets you explicitly save). Do not paste personal or sensitive data into these surfaces.
note 03
The standard Event Verification, Incident Lab, Inquiry Room, Evidence Builder, and Report Builder run entirely in your browser: claims, evidence, and report text never leave your device. Only packets you explicitly save to the Event Workspace are stored server-side.
note 04
The standard static site has no tracking cookies and no analytics scripts. If you use Event Desk Pro, email address and plan data may be processed for magic-link sessions, workspace membership, billing/subscription flow, and security records. These fields are used for access, invoices, and auditability, not profiling.
note 05
The site is served as static files from GitHub Pages. Hosting and CDN layers (GitHub, Cloudflare) may keep their own standard access logs, which we do not control or access. When you open an external link from the archive, that site's own privacy policy applies.
note 06
Think twice before typing sensitive data about real people even into local tools; storing and sharing exported files is your responsibility. See the Ethics and OPSEC pages for research boundaries.
note 07
If you spot a privacy risk, data leak, or vulnerability, use the security reporting channel on the Support page or email TurkishHoodie010@protonmail.com. Simple issues such as broken links can go to the Telegram channel.
