Local Processing Only Zero Remote Servers Zero Telemetry & Tracking User-Controlled Storage Open Source
1. Overview and Purpose
WireData is a local-first developer productivity extension designed to inspect, capture, and query structured JSON network data and tables from web applications you are authorized to inspect.
Capture never runs automatically. Data handling only begins when you click an explicit action (such as Start Capture or Scrape Table) on an active browser tab.
2. User Data Handled by WireData
Under Chrome Web Store policies, data processed from web requests or pages you inspect is categorized as user data. The following outlines exactly what WireData handles locally:
A. Website Content & API Responses
- JSON API Responses: Intercepted HTTP/HTTPS
fetchandXMLHttpRequestJSON response payloads from the inspected tab during active capture sessions. - DOM Table / Grid Data: Cell text extracted from HTML table or grid elements during one-time table scraping.
- Sensitive Information Note: Captured response payloads are stored unmodified to preserve schema provenance. They may contain personal or sensitive information returned by the web service being inspected. All processing and storage remain strictly on your local machine.
B. Web Browsing Activity & URLs
- Request & Page URLs: Request endpoint URLs and target page URLs are recorded during capture.
- Automatic URL Sanitization: Query parameters containing credential-shaped names (such as
token,auth,key,secret,password,apikey,access_token) and URL hash fragments are automatically redacted or stripped before storage.
C. Authentication & Request Credentials
- Request Authentication Headers: Headers such as
Authorization,Cookie, and custom session tokens are never stored. - Request Bodies: HTTP request bodies are not stored or transmitted. For GraphQL requests only, WireData may transiently read the locally-available request body to extract the
operationNamefield for dataset labelling purposes. The body itself is immediately discarded in memory and is never persisted, logged, or transmitted remotely.
3. Capture Modes and Lifecycle
| Capture Mode | Trigger | What Is Handled Locally | Stop Conditions |
|---|---|---|---|
| Side Panel Network Capture | Click "Start Capture" in Side Panel | JSON fetch/XHR responses, HTTP method, status, timing, sanitized URLs | Click "Stop Capture", close side panel, close tab, or cross-origin navigation |
| DevTools Deep Capture | Start Capture in DevTools panel | JSON network entries, GraphQL operation names, timing, sanitized URLs | Click Stop, close DevTools, or close tab |
| DOM Table Scrape | Click "Scrape Table" in Side Panel | Snapshot of visible HTML table/grid rows and sanitized page URL | One-time snapshot (instantaneous) |
4. Data Retention and Storage Architecture
WireData provides two local storage mechanisms plus ephemeral session state, all strictly confined to your device:
- Ephemeral Session State: Active capture flags and inspected tab identifiers are stored in
chrome.storage.session. This transient control state is automatically wiped when your browser closes or the extension unloads. - Browser-Local Workspace (Default): By default, captures, extracted datasets, and metadata are saved locally in browser
IndexedDBstorage under the extension origin. This allows the Side Panel, Workbench, and DevTools to seamlessly share the same local workspace. The data remains strictly on your device until you clear it via the Workbench, clear extension storage, or uninstall the extension. - User-Selected Local Folder (Optional): If you explicitly choose a workspace directory via the File System Access API, captured JSON files, schema definitions, and DuckDB snapshots are saved directly to that local folder on your disk. This data remains on your computer under your full filesystem control until you delete it.
5. Permissions and Least Privilege
WireData requests only the minimum permissions required for local operation:
activeTab— Temporarily accesses the single tab where you open the extension. WireData does not have persistent or background access to all websites.scripting— Injects the temporary MAIN-world JSON capture hook and DOM table extractor into the active tab upon your explicit request.sidePanel— Displays the companion capture and dataset controller UI.storage— Manages ephemeral session state and directory handle persistence in IndexedDB.tabs— Reads the URL and hostname of your active browser tab when the side panel opens, enabling domain-aware dataset grouping. WireData does not monitor your browsing history.optional_host_permissions(http://*/*,https://*/*) — Requested on-demand, per site, only when you explicitly click Start Capture or Scrape Table. Zero host permissions are granted on installation. Chrome displays a native prompt for each new domain before access begins.
6. Third-Party Code and WebAssembly
WireData bundles DuckDB-WASM (an in-browser analytical SQL database) directly inside the extension package. DuckDB runs completely client-side in a WebAssembly worker. WireData does not load code, scripts, or WebAssembly binaries from remote CDNs or external servers.
7. Data Sharing and Transfer
No data is ever transferred. WireData does not sell, trade, transmit, or share your data with any third party, analytics vendor, or cloud provider.
8. Chrome Web Store Limited Use Disclosure
WireData's use and transfer to any other app of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
9. Contact & Source Code
WireData is open source. You can inspect the complete source code, review audits, or submit questions at our GitHub repository: