DevTrace v1.0.0 Local-Only Processing Developer Tool

Privacy Policy

DevTrace is a developer network inspection and API/resource debugging extension. It is not positioned as a general-purpose data collection service.

Summary: DevTrace processes captured request data locally inside the browser environment. It does not include built-in analytics, telemetry, or an external upload pipeline.

Limited Use disclosure: DevTrace uses browser activity data only to provide its user-facing developer network inspection, API debugging, and resource analysis features, and its use of such data is intended to comply with the Chrome Web Store User Data Policy, including the Limited Use requirements.

1. What Data DevTrace Uses

DevTrace may access the following information during normal operation:

the URL entered by the user when starting capture
network request metadata captured during the active session
extension settings such as capture mode, blocked domains, and allowed domains
local download status used to avoid re-downloading previously completed resources

Depending on the page being inspected, captured request data may include request URLs, methods, response status codes, resource types, timestamps, and response size metadata.

2. Purpose of Use

DevTrace uses this data only to provide user-visible developer tooling features, including:

inspecting page requests in real time
debugging API requests and responses
analyzing resource loading behavior
exporting user-selected resources for development and troubleshooting workflows

3. Data Storage

DevTrace stores its working state in chrome.storage.local, including capture sessions, current capture state, extension settings, persisted download completion state by domain, and the last entered URL.

This data remains on the local browser profile unless the user clears it.

4. What DevTrace Does Not Do

does not send captured data to a remote server
does not embed third-party analytics or telemetry
does not create user accounts
does not share captured request data with the developer by default
does not sell captured data

5. Permissions Explanation

tabs and activeTab: navigate and inspect the active browser tab during an explicit capture workflow
webRequest and webNavigation: observe request and navigation activity for the user-selected target scope
storage: persist local settings, session state, and download markers
downloads: export JSON data and selected resources to the local device
optional host permissions: requested at runtime for the chosen capture scope instead of granted globally up front

6. Resource Export

When the user exports resources, files are written either directly into a user-selected folder when supported by the browser, or through the browser Downloads API as a fallback. Exported files are written only because of explicit user action.

7. User Control

stop capture at any time
clear captured request data
reset the current session
choose which resources to export
remove the extension to stop future data handling

8. Contact

If you have questions about this privacy policy or DevTrace's data practices, contact: vidar1031@gmail.com