DevTools

Legal

Privacy Policy

📅 Updated: January 2025 🌐 Devtools Web Studio 📦 Chrome MV3

🔍 Policy summary

  • The extension does not collect personal data
  • No own servers — everything runs locally in your browser
  • Preferences are stored in Chrome storage (sync or local)
  • DNS requests are made via dns.google (Google DNS over HTTPS)
  • The source code can be inspected directly in Chrome
  • No tracking cookies or tracking pixels
  • No analytics or telemetry collection

1. Data controller

Devtools Web Studio is a browser extension independently developed and maintained by Cláudio Pereira, a Portuguese web developer.

Cláudio Pereira

Website: https://claudiopereira.pt

Contact: Contact form

2. Data collected

Devtools Web Studio was built with a privacy-by-default philosophy: it collects the absolute minimum data and never shares it with third parties.

2.1 Data stored locally (in your browser)

The extension stores the following preferences and data in Chrome storage:

Data Content Where Purpose
UI preferences Theme, language, active tab, panels sync Retain your preferences between sessions
API Collections Requests, headers, body, environments sync Save and reuse API requests
Code snippets Reusable JavaScript defined by you sync / local Save and run snippets on pages
Design settings Grid, guides, defined breakpoints sync Retain design settings between sessions
Todo list Tasks created by you sync Task persistence
Colour history Recently selected colours sync Quick access to used colours
Image cache Temporary thumbnails (Media Explorer) local Media Explorer performance
None of this data is transmitted to our servers. Everything stays in your browser and is controlled by you.

2.2 Data we do NOT collect

The extension does not collect, process or have access to:

  • Browsing history
  • Passwords or form data
  • Personally identifiable data (name, email, etc.)
  • Geographic location
  • Device identifiers (fingerprinting)
  • Content of visited pages (not collected or stored)
  • Analytics or telemetry data

The extension injects scripts into pages for inspection purposes, but the inspection result is never transmitted outside the browser.

2.3 Temporarily processed data (in memory)

During extension use, the following data is processed in memory (RAM) and discarded when you close the tab or panel:

  • DOM content of the active page (for element inspection)
  • HTTP headers of network requests (for the Diagnostics tab)
  • Cookies on the active page (only visible in the Diagnostics tab)
  • Captured JavaScript errors (JS Errors — opt-in only)
  • Console messages (opt-in only)
  • API responses (only in API Tester, discarded after viewing)

3. Local storage

3.1 chrome.storage.sync

Preferences and settings are synced via Google Chrome Sync (chrome.storage.sync). This includes:

  • Selected theme and language
  • API collections and environments
  • Code snippets
  • Grid settings and alignment guides

3.2 chrome.storage.local

Data too large for sync is stored in chrome.storage.local:

  • Temporary image cache (Media Explorer)
  • Recent API request history
  • Todo list and notes
🔒
Sync is handled by Google Chrome's infrastructure. Devtools Web Studio has no access to synced data — it passes directly from Chrome to the user's Google account.

4. Third-party services

Devtools Web Studio interacts with the following external services, always explicitly and initiated by the user:

4.1 Google DNS over HTTPS (dns.google)

When you use DNS diagnostics, the extension makes requests to Google's DNS over HTTPS service (dns.google/resolve) to resolve DNS records. Each request includes:

  • The domain name you want to query
  • The DNS record type (A, AAAA, MX, TXT, etc.)
  • Does not include your IP — the extension uses ct=application/dns-json mode which does not log IPs
  • Subject to Google's privacy policy: https://policies.google.com/privacy

4.2 Google Chrome Sync

Preference sync uses Chrome's native chrome.storage.sync mechanism, managed by Google. We have no access to this data.

4.3 Chrome Web Store

The extension is distributed through the Chrome Web Store. Google collects anonymous usage data about installs and uninstalls, per their privacy policy.

No other external service is used. There are no analytics SDKs, trackers, marketing pixels, third-party CDNs or external API calls beyond those described above.

5. Extension permissions

The extension requests the following permissions in Chrome. Each permission is needed for a specific feature:

Permission What it is used for Data accessed
sidePanel Show the Web Studio side panel No data accessed
activeTab Read the active tab content for inspection URL and content of the active tab
scripting Inject inspection scripts into pages Active page DOM (processed locally)
storage Save preferences and collections in the browser Configuration data (never transmitted)
contextMenus Right-click context menu No data accessed
webRequest Monitor page network requests URLs and headers of network requests
declarativeNetRequest Implement CORS bypass declaratively Temporarily modifies response headers
debugger Access console and JS events in real time Console messages and JS errors (opt-in)
⚠️
The webRequest permission is used only for the Diagnostics tab and CORS bypass. The extension does not monitor or store network traffic.

6. Children

Devtools Web Studio is a tool for web development professionals and enthusiasts. It is not directed at children under 13.

We collect no data from any user, regardless of age. If you are aware of a minor using the extension, you may contact us, but there is no data to delete.

7. Your rights

Since the extension does not collect or process personal data, most GDPR rights do not directly apply. However, we recognise the following rights:

  • Access - You can view all stored data at chrome://extensions → Devtools Web Studio → Storage
  • Erasure - You can delete all data at Settings → Reset extension, or by uninstalling the extension
  • Portability - You can export your collections and preferences in JSON format in the Export/Import section
  • Objection - You can disable Chrome sync at any time in Chrome settings
  • Complaint - You can lodge a complaint with your country's data protection authority

To exercise any right or clarify doubts, contact us through the support form.

8. Data retention

Data stored in the browser remains until:

  • Uninstalling the extension (deletes all local and sync data)
  • Using the "Reset extension" option in Web Studio settings

There is no data on our servers — therefore there are no retention periods on our end.

9. Changes to this policy

This policy may be updated when:

  • New features are added that change data handling
  • There are changes in the third-party services used
  • Legal or regulatory updates are required

10. Contact

For questions about privacy or this policy, you can contact us through:

Devtools.pt - User support

💬 Contact form at devtools.pt

🌐 https://devtools.pt

📄 Web Studio support page

We respond to all privacy questions within 30 business days.