ByeWall 2.0

Your click. Your choice.

Updated September 7, 2026 · Version 2.0.0

What leaves your browser

When you open an archive, your selected page address is sent to that provider (Archive.today at archive.is, or the Internet Archive at web.archive.org). The provider receives normal web-request information, such as your IP address, and may use cookies or verification challenges. Its own privacy practices apply.

This website

This website is hosted by Cloudflare, which processes normal request information, including IP addresses, to deliver and protect the site. The site has no analytics scripts or tracking cookies. Article lookups from the extension go directly to your chosen archive provider.

What the extension keeps

No accounts, analytics, remote scripts, reading history database, or ByeWall server. Article addresses are processed locally and are not stored by the extension. Browser history and archive providers may retain pages you open. Copy actions write the selected link to your system clipboard.

Safer addresses

ByeWall removes recognized tracking parameters and page fragments, and blocks browser-internal, local, IP-based, custom-port, and recognized sensitive-token addresses. These checks cannot identify every private page. Only open public article links you intend to share with the chosen archive.

Permissions

activeTab reads the selected page address when you invoke ByeWall. contextMenus adds right-click actions. ByeWall does not request access to all websites or your full browsing history.

Public snapshots

Lookups do not automatically submit new captures. The separate “Continue to submission page” action shares the article address with Archive.today for potential public archiving. Do not submit private content.