Privacy Policy — Drupal Visual Debugger

Last updated: 2026-08-17

Drupal Visual Debugger is a Chrome extension that overlays debug output Drupal itself already writes into a page's HTML — Twig theme-debug information (which template rendered an element, its theme hook, suggestions, and file path) and, when enabled, render-cache information (cache hit/miss, tags, contexts, keys, max-age) — through an on-page overlay and a fly-out inspector panel.

What this extension does with page content

To build the overlay and inspector panel, the extension reads the HTML comments Drupal's own debug settings write into the page (Twig theme-debug and, separately, render-cache debug output), along with the structure and position of the corresponding page elements. This processing happens entirely inside your browser tab. Nothing read from the page is sent to any server, to the developer, or to any third party — there is no analytics, tracking, or remote logging of any kind.

What this extension stores, and where

The extension stores two small pieces of state, both entirely on your own device, using Chrome's built-in storage APIs:

• Panel display preferences (the inspector panel's width, and whether it's shown expanded or collapsed) — saved via chrome.storage.local so your preference persists across page loads. This is cleared if you remove the extension or clear its storage.
• Per-tab on/off state — which browser tabs currently have the debugger turned on, and for which site — saved via chrome.storage.session. This is used only to keep the debugger active as you navigate within the same site, and is cleared automatically when you close the tab, navigate to a different site, or restart your browser.

Neither of these is transmitted anywhere. No personally identifiable information, health information, financial or payment information, authentication credentials, personal communications, or location data is collected, at any point.

Permissions this extension uses

• activeTab — lets the extension act on the specific tab you click its toolbar icon on, rather than requesting standing access to your browsing.
• scripting — used to inject the extension's own bundled CSS/JavaScript (the overlay and inspector panel) into the page when you turn the debugger on, and to remove it again when you turn it off. Everything injected ships inside the extension package itself — nothing is fetched or executed from anywhere else.
• storage — backs the two local-only uses described above.
• Host permission, requested per-site — rather than requesting access to every website up front, the extension asks for permission to a specific site's origin only at the moment you click its toolbar icon there. It does not hold standing access to sites you haven't explicitly activated it on.

Third parties

This extension does not share, sell, or transmit any data to third parties, because it does not transmit data anywhere in the first place. There are no third-party analytics or advertising SDKs of any kind.

Children's privacy

This extension is a developer tool for inspecting Drupal websites and is not directed at children. It does not knowingly collect any data from anyone, including children.

Open source

This extension's source, and the drupal-visual-debugger library it bundles, are both open source (GPL-2.0-or-later) and available at github.com/mabho/drupal-visual-debugger-extension.

Changes to this policy

If this policy changes, the updated version will be posted at this same URL with a revised "Last updated" date above.

Contact

Questions about this policy or the extension's data practices can be sent to marcos.buarque@uol.com.br, or raised as an issue on the GitHub repository.