Privacy Policy
Last updated 2026-09-22. Applies to the FilterForge.dev website and the Filter Forge browser extension.
Filter Forge does not have a server, a database, an account system, analytics, or advertising. There is no backend for either the website or the extension to send anything to, and neither collects, stores, or transmits any personal data. Both are open about what little they do access, listed below in full.
The website (filterforge.dev)
The site is a static page that runs entirely in your browser. Editing or importing a filter never leaves your
device: a pasted code stays in memory, and a filter handed off from the extension travels in the page's URL
fragment (the part after #), which browsers never send to a server. The site sets no cookies and
loads no analytics or tracking scripts of any kind.
The browser extension
The extension reads build guide pages to turn them into loot filter codes. Here is exactly what each permission it asks for is for:
| Permission | What it's for |
|---|---|
storage |
Saves your chosen strictness settings and a small local cache of item names, on your device only, so lookups don't repeat. Never sent anywhere. |
tabs |
Checks whether the active tab is a supported build page, so the panel knows whether to offer to read it. |
Host access to maxroll.gg, planners.maxroll.gg, and assets-ng.maxroll.gg
|
Maxroll's build data lives behind an endpoint that blocks cross-origin requests from a normal web page. This permission lets the extension read that build's own public data directly from your browser, the same data the Maxroll page itself already loaded. Nothing about you or your browsing is sent to Maxroll beyond the ordinary request for that build's data, and nothing is sent anywhere else. |
The extension only acts on pages you open on Maxroll, Mobalytics, D4Builds, or InfinityBuilds, and only when you click its button. It does not run in the background, and it does not read or modify anything outside of that build page and the loot filter panel.
Third-party data
Item and affix names come from public, community-maintained Diablo 4 data projects (DiabloTools/d4data and ThunderEagle/D4LootBench), bundled with the extension and the site. No account with those projects is required or created.
Changes
If this policy ever changes, the date at the top of this page will change with it.
Contact
Questions about this policy can be raised as an issue on the project's repository.