Archify collects nothing.

Last updated: 20 August 2026

Data we collect

None. Archify runs entirely in your browser. There are no servers, no accounts, no analytics, and no telemetry. Page contents are never stored or transmitted. The per-tab analysis Archify builds lives in the tab and goes away with it. One narrow exception stays on your device: if you trace an interaction and the page then redirects, that in-progress trace is held for up to 10 seconds so it survives the jump, and it is cleared when the tab closes or the browser session ends.

The launch waitlist

The extension collects nothing — that is unchanged. This website offers one optional thing: a launch waitlist. If you choose to enter your email, we store it solely to send you a single message about Archify's availability. It lives in our own backend (hosted on Vercel, stored with Upstash, acting only as processors for us), is never sold, shared with advertisers, or added to a newsletter, and is deleted after launch or whenever you ask.

Permissions, and why each is needed

• Access to the sites you visit (host permission): Archify's analysis runs on the pages you open, so the inspector is ready the moment you hover. All analysis happens locally in your browser; page data is never sent anywhere.
• storage: to remember a few small settings on your device — whether the hover inspector is on, and whether you've already seen the first-run hint and the one-time review prompt. Stored on your device only, never transmitted.

Network activity

Archify makes a single same-origin request to the page's own URL, to read its hosting response headers. That is the extension's only network request — nothing is sent to Archify or any third party, and no remote code is loaded. This website (where you're reading this) links out to GitHub and Glasswatch; those open only when you click them.

Third parties

We share no data with advertisers, data brokers, or analytics services. The only data this website handles — the optional waitlist email described above — is stored by our infrastructure providers acting solely as processors on our behalf.

Contact

Questions: open an issue on GitHub.