Privacy policy

Effective 28 August 2026

Short version: Doomwall collects nothing. There are no accounts, no servers, no analytics, and no network requests. Everything it knows lives in your browser and leaves only if you export it yourself.

What the extension stores

All data is kept in Chrome's local extension storage (chrome.storage.local) on your device:

• Your rules: the domains, paths, exceptions and time windows you add.
• Settings: blocking on/off, pause length, daily bypass limit, and the current pause timer.
• Usage counts: how many times a blocked site was attempted, how many times you bypassed, and minutes spent on a site after bypassing, per site and per day.

This data is never transmitted anywhere. It is deleted when you remove the extension.

Browsing history

The Activity page can suggest sites to block by reading your Chrome history for the most-visited hosts of the last 30 days. This happens only while that page is open, is computed in memory, and is not stored or sent anywhere.

What the extension does on websites

Doomwall does not inject scripts into, read, or modify any web page. Its only action on a site is redirecting your own navigation to a domain you have listed to the extension's blocked page.

AI agents (WebMCP)

Doomwall exposes its own controls as WebMCP tools on its own pages, so a browser agent you use can manage your rules. This is a local interface; Doomwall itself does not talk to any AI service.

Third parties

None. No data is shared or sold, because none is collected.

Changes

If this policy changes, the new version will be posted at this address with an updated date.

Contact

[email protected] · github.com/akgupta89/doomwall