privacy

Where your data sits, and where it passes through.

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.

local-firstno accountsno tracking

note 01

What stays in your browser

Resource notes, evidence logs, report drafts, Event Desk workspaces, and your theme/accent choice 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

What passes through Worker surfaces

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

Event Desk, Incident Lab, and report tools

The standard Event Desk, 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 Desk Pro Workspace are stored server-side.

note 04

No unnecessary personal data

There are no accounts, no membership, no tracking cookies, and no analytics scripts. We never ask for an email address or identity. Worker surfaces exist only to relay a request; no profiling happens.

note 05

Limits of a static site

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

Safe research expectations

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

Security and data reports

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.