DevLens extensions: Privacy Policy
Effective: 2 November 2026 · Publisher: Aryan Garg
This policy covers the DevLens Chrome extensions: DevLens URL Params, DevLens Encoders, DevLens JSON & Data, DevLens Timestamp, DevLens Storage, DevLens Screenshot, DevLens Design QA, DevLens A11y Auditor, DevLens DevFlow.
The short version
DevLens extensions do not collect, transmit, sell or share any personal data. They have no accounts, no analytics, no advertising and no servers. The extensions make no network requests of their own. Everything you paste, capture, record or inspect is processed inside your browser and stays on your device.
What the extensions access, and why
Each extension uses only the Chrome permissions it needs for its single purpose. Access to websites is optional and is granted per site when you click “Allow on <site>”. You can remove it at any time on chrome://extensions.
| Extension | What is stored on your device |
|---|---|
| DevLens URL Params | Presets (parameter names and values the user saves) are kept in the extension’s local storage on the device. |
| DevLens Encoders | Stores only your theme choice, and briefly holds text you send from the right-click menu until the side panel picks it up. |
| DevLens JSON & Data | Stores only your theme choice, and briefly holds text you send from the right-click menu until the side panel picks it up. |
| DevLens Timestamp | Stores only your theme choice, and briefly holds text you send from the right-click menu until the side panel picks it up. |
| DevLens Storage | Storage values and cookies are read from the page only to display them in the panel. Override rules and presets the user creates are stored on the device. |
| DevLens Screenshot | Screenshots exist only in the side panel until the user copies or downloads them. The only thing saved is the last crop rectangle and the theme choice. |
| DevLens Design QA | The mockup image the user loads and its overlay settings (opacity, position, scale) are saved per page path on the device, together with any design tokens the user pastes. They are never uploaded. |
| DevLens A11y Auditor | Audit results are shown in the panel and are not saved. Only the theme choice is stored. |
| DevLens DevFlow | The network inspector reads requests through the DevTools API only while DevTools is open. Recorded flows (element descriptions, masked input lengths and URLs) are stored on the device until the user deletes them. |
Data is kept in your browser’s extension storage (chrome.storage or the extension’s own local storage). Some hand-offs use chrome.storage.session, which is cleared when the browser closes. Uninstalling an extension deletes everything it stored.
Third parties
None. DevLens doesn’t use third-party services, SDKs, analytics or CDNs. Open-source libraries that ship inside an extension (such as axe-core in DevLens A11y Auditor) run locally and send nothing anywhere.
Children
DevLens is a set of developer tools and isn’t directed at children under 13.
Changes
If this policy changes, the updated version will be posted at this address with a new effective date. Any change that started sending data off your device would be stated here before it shipped.
Contact
Questions about this policy: use the developer contact email shown on any DevLens Chrome Web Store listing, or the contact form on this site.
