Privacy Policy

AdFlow Network Inspector Browser Extension

Last Updated: January 4, 2026

Overview

AdFlow Network Inspector ("we," "our," or "the extension") is a browser extension designed for developers, ad operations teams, and technical professionals to debug and analyze advertising technology (adtech) network requests. This privacy policy explains how we handle data when you use AdFlow Network Inspector.

Our Core Privacy Principle: Your data stays on your device by default. We do not collect, store, or transmit any of your browsing data to our servers unless you explicitly enable optional AI-powered features.

1. Data Collection and Usage

1.1 What Data the Extension Accesses

To provide debugging functionality, AdFlow Network Inspector intercepts and analyzes network requests made by websites you visit. This includes:

1.2 How Data is Stored

All captured data is stored locally in your browser using Chrome's built-in storage APIs. Specifically:

Important: We do not have access to your locally stored data. It never leaves your device unless you explicitly use AI features (see section 2 below).

1.3 Data We Do NOT Collect

2. AI-Powered Features (Optional)

AdFlow Network Inspector offers optional AI-powered analysis features to help explain network requests and detect issues. These features are opt-in and disabled by default.

2.1 Two Operation Modes

Direct Mode (Bring Your Own API Key)

Backend Mode (Our Proxy Server)

Data Sent to AI Services: When you use AI features, the following data from network requests may be sent to Anthropic's API:
  • Request URLs and domains
  • Decoded request/response payloads
  • HTTP headers (sanitized of sensitive tokens when possible)
  • Vendor and request type metadata
This data may contain advertising IDs, bid prices, or other ad-related information. Do not use AI features if you are analyzing requests containing sensitive or confidential data.

2.2 Disabling AI Features

You can disable AI features at any time by:

The extension will continue to function normally for request capture and analysis without AI features.

3. Permissions Explanation

AdFlow Network Inspector requires the following browser permissions to function. Here's why we need each one:

3.1 webRequest Permission

Allows the extension to intercept and inspect network requests made by web pages. This is the core functionality that enables debugging of adtech requests.

3.2 <all_urls> Host Permission

Required to capture network requests from any website you visit. Advertising requests can come from hundreds of different domains, so we need broad access to analyze them effectively.

3.3 storage Permission

Used to save your preferences, settings, and optionally your AI API key locally on your device.

3.4 tabs and webNavigation Permissions

Allows the extension to track which browser tab each request belongs to and reset capture when you navigate to a new page.

3.5 scripting Permission

Enables the element picker feature that lets you select ad slots on the page to see related network requests.

3.6 sidePanel Permission

Displays the extension's user interface in Chrome's side panel for easier debugging.

4. Data Sharing and Third Parties

4.1 Third-Party Services

AdFlow Network Inspector may interact with the following third-party services only when you explicitly enable AI features:

4.2 No Data Selling

We do not sell, rent, or trade your data to third parties. We do not monetize user data in any way.

4.3 No Analytics or Tracking

AdFlow Network Inspector does not include any analytics, tracking, or telemetry. We do not collect information about how you use the extension.

5. User Control and Data Deletion

5.1 Viewing Your Data

All data captured by the extension is visible directly in the extension's interface. You can review network requests, headers, and payloads at any time.

5.2 Deleting Your Data

You have complete control over your data:

5.3 Exporting Your Data

The extension allows you to export captured requests as JSON or PDF for your own records. This export is saved to your local device only.

6. Security

6.1 API Key Storage

If you choose to use Direct Mode with your own API key:

Security Note: While chrome.storage.local is more secure than regular browser storage, API keys stored this way are still accessible to the extension itself. For maximum security, consider using Backend Mode where you don't need to provide your own API key.

6.2 Secure Connections

All external communications (to Anthropic API or our backend) use HTTPS encrypted connections.

6.3 No Backend Data Retention

When using Backend Mode, our proxy server:

7. Children's Privacy

AdFlow Network Inspector is a developer tool not intended for use by children under 13. We do not knowingly collect information from children.

8. Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected by updating the "Last Updated" date at the top of this page. For material changes, we will notify users through the extension's interface or Chrome Web Store listing.

Continued use of the extension after policy changes constitutes acceptance of the updated policy.

9. Legal Basis for Data Processing (GDPR)

For users in the European Economic Area (EEA), our legal basis for processing data is:

You have the right to withdraw consent at any time by disabling AI features or uninstalling the extension.

10. Contact Information

If you have questions, concerns, or requests regarding this privacy policy or how we handle data, please contact us:

Data Protection Rights: If you believe we are not handling your data in accordance with this policy, you have the right to lodge a complaint with your local data protection authority.