Anonymous code hosting for double-blind review
Authors hand Hido a GitHub repository. Reviewers get a read-only link with no login, no cookies, and no tracking — four outlets (browse, raw, zip, git clone) from one anonymization pipeline.
Built to stay up through conference deadlines
Why not anonymous.4open.science?
- Pre-render, don't live-proxy. Anonymization runs once at ingest; reviewers hit Cloudflare R2 static objects. Our API going down does not take your link down.
- One pipeline for every outlet. Web, raw, zip, and clone share the same transform — no zip that forgets to mask.
- Least privilege. GitHub App, Contents: Read-only, only the repo you pick — not full
repo scope.
- Zero tracking on the reader origin.
hido.science has no cookies and no analytics (ICLR / ACL ARR constraints).
How it works
- Sign in, install the App on one repository.
- List the strings that identify you (names, orgs, emails, paths). Hido does not guess.
- Dry-run the replacement report, then publish. Copy the anonymous URL into your paper.
Open console
FAQ
What we deliberately do not do
- No visitor analytics on anonymous links.
- No auto-derived term lists (they over-mask and destroy reviewability).
- No in-browser demo / webview of your HTML (deanonymization risk).