Privacy policy: the Diazoma browser extension

Last updated 9 October 2026. This page covers the Diazoma extension for Chrome and Edge. The wall that a website embeds itself is covered in Security and privacy.

In short

• Pictures, titles and page contents are read in your browser. They are not sent to Diazoma.
• The extension sends three kinds of requests to diazoma.app: a daily download of the recipe list, anonymous usage counts (you can switch them off), and a recipe request when you click "Request a recipe".
• The usage counts never contain page addresses, item addresses or any identifier of you.
• Nothing is sold, shared with third parties or used for advertising.

What the extension stores on your device

In the browser's extension storage, on your device only:

• your settings: whether usage counts are on, the sites you switched off (their origin, for example https://example.org), the custom list addresses you added, and your input profile;
• the recipe lists it downloaded, and the time and result of the last check;
• the queue of usage counts that are waiting to be sent (empty when you switch them off).

The wall also keeps comfort settings, the watch-later queue and the resume position. Where they are kept depends on how the wall was opened:

• A wall in its own tab (a recipe, Level 0): in the local storage of the extension's own page. Only the extension can read it, and uninstalling the extension removes it.
• A wall over the page (Level 1 and 2): in the local storage of the website you are on, under keys that start with diazoma:, exactly as when that site embeds the wall itself. The site can read it. It holds your comfort settings, the items you queued from that site, and your place in its list, and it stays in your browser until you clear that site's data.

Uninstalling the extension removes what it keeps for itself, but not what a wall over a page left in a site's own storage; clear the site's data in the browser to remove that.

What the extension sends

Like any web server, diazoma.app sees the IP address your browser connects from. For usage counts it keeps only a keyed hash of the network part of the address (the first three bytes of an IPv4 address, the first six of an IPv6 address), to limit how much one source can add, and does not store the address. For recipe requests it keeps a keyed hash of the address, to limit abuse.

When you open a wall, your browser asks the site itself (for example commons.wikimedia.org) for its pages, lists and pictures, as a visit would. Diazoma does not sit in between and does not receive that traffic.

Turning usage counts off

Open the extension's settings (right-click the toolbar button and choose Options) and switch off "Send anonymous usage counts". The switch works at once: anything waiting to be sent is deleted and nothing more is sent.

What the extension does not do

• It does not read pages until you click the toolbar button (Level 1 and 2), or open a wall for a recipe site.
• It does not collect your browsing history, account details, cookies or form contents.
• It does not bypass logins or paywalls, and it does not build a wall for a site whose manifest says policy: "deny".
• It does not load or run code from the internet. Recipe lists are data, checked against a signature from a key built into the extension before they are used.

Permissions

See Permissions in the extension documentation for what each one is used for.

Changes

If this policy changes, the date at the top changes, and a change to what is sent will come with a new version of the extension.

Contact

Questions about this policy: [email protected].