DEX Privacy charter / public edition

Document 01 · 2026

Chrome Extension

Privacy
Policy.

Effective August 27, 2026

A public record of what Dex accesses, where processing occurs, how long information remains, and the controls available to each user.

00 Preamble

Purpose

Dex manages Chrome downloads and inspects downloadable resources on the current web page.

This policy describes the data Dex accesses to provide those functions. Download, tab, page-resource, and settings data is processed locally in the browser and is not transmitted to the developer.

I Access

Data accessed

Information used by Dex features

Dex accesses only the information needed to display and control downloads, open its in-page surfaces, and identify resources the user may choose to download.

Chrome download information

Download URLs, file names and local file paths, file type, size, progress, timestamps, status, and error or danger state.

Used for download display and controls.

Tab context

The URL and title of the active or target browser tab.

Used to open and route Dex on the intended page.

Page resource information

Resource URLs, element titles or alternative text, media dimensions and duration, resource type, and observed transfer size.

Used by the current-page resource inspector.

Extension preferences

User-selected settings, panel size, and a bounded list of pending Chrome download identifiers.

Used to preserve the expected Dex experience.

Dex does not request or read browser cookies, form input, passwords, authentication tokens, personal communications, payment information, health information, or precise location. When a user explicitly copies a displayed URL, Dex writes that selected value to the clipboard but does not read clipboard contents.
II Process

Processing

Local by default, original host when required

Dex has no separate service that receives browsing, download, or settings data.

Inside Chrome

Chrome download events and user actions
Local Dex processing and display
Chrome extension storage when persistence is needed

Original resource host

A download or page resource needs a size check
Dex sends a HEAD or bounded Range request directly to that resource URL
Only response metadata or the requested byte range is used
The request goes to the resource's existing HTTP or HTTPS host. It is not redirected through a Dex backend or a separate third-party service.
III Retain

Storage and retention

Each data class follows its product lifecycle

Settings

  • Stored with chrome.storage.sync.
  • Remain until reset, removal, or uninstall.
  • Chrome may synchronize them according to the user's Chrome sync configuration.

Local extension state

  • Panel size and pending download identifiers use chrome.storage.local.
  • The pending list is bounded and entries are removed as they are resolved.
  • Local extension storage is removed when Dex is uninstalled.

Page inspection

  • Results are held in memory for the active page session.
  • The resource cache is bounded.
  • Inspection results are not uploaded by Dex.

Downloads

  • History and downloaded files are managed by Chrome and the operating system.
  • Users can remove history entries or files through Dex, Chrome, or the operating system.
IV Control

Commitments and controls

No advertising, sale, or unrelated use

A

Sharing and advertising

Dex does not sell, rent, share, or transfer user data to the developer, advertisers, data brokers, or other third parties. It does not use data for advertising, profiling, creditworthiness, or purposes unrelated to its stated functionality.

B

Security

Dex uses Chrome extension APIs and local extension storage. Release builds package all executable code locally and do not download or run remote code.

C

User controls and deletion

Users can reset Dex settings, clear Chrome download history, delete downloaded files, reload a page to discard session resource results, manage Chrome sync, or uninstall Dex to remove extension storage.

V Limited Use

Chrome Web Store Limited Use

Data is used only for Dex's user-facing purpose.

Dex's use and transfer of information received from Google APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Dex uses such information only to provide or improve its download-management and resource-inspection features.