WebDive analyzes the tab you explicitly record. Captured application data is processed and stored locally in the Chrome extension. WebDive has no developer-operated backend, analytics service, advertising system, or account system.
Data handled
When you press Start or select a reload recording action, WebDive handles data from the inspected browser tab that can include:
- Page and resource URLs, hosts, request types, response metadata, transfer sizes, and timing.
- JavaScript and CSS source text, executed or matched coverage ranges, and source-map information.
- Chrome performance trace events, sampled call frames, CPU timing, rendering events, and long-task correlations.
- User-entered recording names, throttling choices, normalized reports, and exported backup files.
This can include confidential website content or browsing activity. Do not record an application unless you are authorized to inspect its resources.
How data is used
Data is used only to provide WebDive’s user-facing journey analysis: building the resource table, computing coverage and performance findings, showing original-module attribution, preserving local history, and creating backups you request.
Retention, access, and deletion
Completed reports and per-file source details remain in extension-local IndexedDB until you delete a run, clear the extension’s stored data, delete the Chrome profile, or uninstall the extension. WebDive cannot remotely access or recover this history. You can delete individual runs from Run history and export backups for records you wish to retain.
Chrome permission
debugger
This permission is required to attach to the tab the user chooses to inspect and to invoke the Chrome DevTools Protocol domains that provide Network data, precise JavaScript and CSS coverage, source text, emulation, and performance tracing. WebDive attaches only after an explicit recording action and detaches during Stop or cleanup. It requests no broad host permission.
Chrome Web Store Limited Use disclosure
WebDive’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
- Allowed use: Chrome API data is used only to provide and improve the journey-analysis functionality visible to the user.
- Allowed transfer: WebDive does not transfer user data except a Chrome-initiated request to a source-map URL declared by the inspected application, or an export initiated by the user.
- Advertising: WebDive does not use or transfer user data for personalized, retargeted, or interest-based advertising.
- Human access: The developer does not receive or permit humans to read captured user data.
Changes and contact
Material policy changes will be reflected on this page and in the effective date. Questions can be submitted through the support channel listed on WebDive’s Chrome Web Store page.