Structural
Clarity.
Data security is not a black box. We expose the mechanics of how your files are handled so you can verify, not just trust.
Edge-only proxy
Uploads pass through Cloudflare Pages Functions. The backend endpoint is never exposed to browsers.
Files never persist on our systems
Uploads land in a temporary directory, are processed, and are deleted in a finally block immediately after John the Ripper returns — successful or not. No backups, no cached copies, no logs of file contents.
Volatile memory processing
Hashes are extracted in process memory, written to a temp file only long enough for John the Ripper to read them, then deleted.
Cloudflare edge proxy
Your browser only ever talks to Cloudflare Pages Functions. The John the Ripper backend IP is a secret held at the edge — no direct client-to-backend path.
No account, no tracking
We do not require you to sign up, provide an email, or authenticate. Each recovery is anonymous and stateless. The only logs we keep are aggregated request counts for capacity planning.
What we actually do
A plain-English description of the pipeline. No marketing words.
-
1
Browser uploads the file to Cloudflare
A Pages Function accepts the multipart body, checks size and extension, and streams it onward to our backend over an authenticated channel.
-
2
Backend extracts the hash
The matching John the Ripper extractor (
office2john,zip2john, etc.) reads the file header and emits a hash string. The original file is deleted. -
3
John the Ripper runs against a wordlist
The hash is compared against rockyou or a smaller dictionary, chosen by hash format. If a match is found, the password is returned.
-
4
Temp files are deleted
Both the uploaded file and the extracted hash file are removed from disk before the response is returned.