Trust & data handling
What gets logged, and what doesn't
A plain-language summary of the data-handling stance across FORGE and the secure file-drop — no legalese, just what actually happens.
FORGE — threat-intel lookups
FORGE never logs the indicators you look up. Full detail lives on FORGE's own privacy page, but the short version:
- The IP, hash, domain, or URL you paste into any lookup is never recorded.
- Analytics are aggregate and cookieless — page/tool name, country, referrer host, device class. No per-visitor identifier.
- Rate-limit counters hold numbers only (e.g. "how many lookups today"), never the values looked up.
Secure file-drop — hardened handoff
The authenticated file-share is being hardened against misuse as bulk storage or a malware-distribution surface. That hardening adds accountability metadata — not content inspection:
- Logged: filename, file size, a SHA-256 hash of the file, uploader and recipient emails, timestamps, expiry, download count, and — per download attempt — IP address, geo, and device, so a share's actual usage is visible.
- Never logged: the file's contents. The SHA-256 hash lets a file be identified or cross-checked without ever storing or inspecting what's inside it.
- Why: a private handoff tool still needs to answer "did the recipient actually get this?" and "who downloaded what, from where?" — that's accountability, not surveillance, and it stops well short of reading anything.
Found a security issue? See security.txt for how to report it responsibly.