Privacy Policy — DLBrowser

Last updated: July 13, 2026 · Published by Dekrypt Labs

This policy covers the DLBrowser browser extension and the hosted gateway at api.dekryptlabs.com. The open-source DLBrowser software you self-host is governed by its repository license; when self-hosted, your data never leaves your infrastructure.

1. Summary

DLBrowser does not collect, sell, or use your data for tracking, and embeds no analytics, telemetry, or advertising. To perform an action you request (fetch, extract, screenshot, crawl), the target URL and/or page content is sent to the DLBrowser server you configure. By default that is the hosted gateway at https://api.dekryptlabs.com, operated by Dekrypt Labs — so by default that data leaves your machine and is processed by the gateway. Point DLBrowser at a self-hosted server (including localhost) to keep everything on your own infrastructure. The extension's "scrape" mode is processed entirely within your browser.

2. Information accessed

Data	When	Purpose
Active tab content	Only when you explicitly trigger an action	To fulfil the fetch/extract/screenshot/crawl you requested
Current tab URL & title	When the popup opens	To show the target page in the UI
Your configuration	On startup	To remember your server URL (Chrome `storage` API)

3. Processing & transmission

Scrape mode: processed locally in your browser; nothing is transmitted.
Fetch/extract/screenshot/crawl: the URL and/or content is sent to the DLBrowser server you configure. Default = the hosted gateway (Dekrypt Labs). Set a self-hosted URL (e.g. http://localhost:8929) and data never leaves your machine.
No third-party sharing or tracking. No analytics, advertising, or data sales.

4. Data retention

The extension stores only your server-URL setting. It keeps no history of pages you access. The hosted gateway retains operational logs and usage metadata to run the service and meter credits; it does not sell your data. Aggregated, de-identified performance data (e.g. per-domain success rates) may be used to improve routing.

5. Permissions (extension)

Permission	Why
`activeTab`	Read the current page only when you trigger an action
`scripting`	Inject the extraction script on demand
`storage`	Persist your server-URL setting
`downloads`	Save extracted content/screenshots locally
`tabs`	Show the current tab's URL and title
broad host access	Fetch content from any page you choose; connects only to your configured server

6. Security

Traffic to the hosted gateway uses HTTPS. Self-hosted on your own machine, data stays local. We recommend HTTPS for any remote DLBrowser server.

7. Children's privacy

DLBrowser is not directed at children under 13, and we do not knowingly collect their information.

8. Changes

We will update this page and the date above if our practices change; material changes are noted on the Chrome Web Store listing.

9. Contact

Dekrypt Labs — privacy@dekryptlabs.com