Inspektr

Privacy Policy

Last updated: September 2, 2026

      Core Privacy Commitment: Inspektr is an all-in-one web developer toolkit. We collect, store, and transmit zero personal data. All analysis, styling extraction, element diagnostics, and inspection operations happen strictly in your local browser runtime.
    

1. About the Inspektr Developer Suite

Inspektr is an expanding multi-tool suite engineered for web developers, UI/UX engineers, and web designers. The platform provides localized developer tools directly in Chromium-based browsers, currently including:

Font Detector: Real-time typeface, weight, sizing, and line-height inspection on user-selected DOM elements.
Upcoming Developer Tools: Color picker & WCAG contrast analyzer, image and asset diagnostic inspector, CSS custom properties (--var) extractor, layout & spacing ruler, and related client-side developer utilities.

Multi-Tool Scalability & Continuous Privacy Policy

As new inspection modules and developer tools are introduced into Inspektr, they will always adhere to the same privacy-first architecture: all processing remains 100% on-device without remote tracking or server uploads.

2. Information Collection and Use

We do not collect any personally identifiable information (PII) or telemetry:

No Browsing History: Inspektr does not track or store the URLs or websites you visit.
No Content Harvesting: Inspektr only inspects DOM properties (such as CSS styles, fonts, or colors) of the element you interact with, purely in memory on your machine.
No Analytics or Trackers: No Google Analytics, Mixpanel, or third-party tracking scripts are bundled.
No Remote Backend: Inspektr operates without an external API backend or server database.

3. Local Device Memory & Zero Persistent Storage

Inspektr does not use persistent local storage APIs (such as chrome.storage or cookies). Active tool states and temporary page inspection data are held strictly in transient session memory within the browser while the inspected tab remains active. This data:

Never leaves your local computer.
Is never transmitted across any network.
Is completely purged as soon as the tab is closed, reloaded, or the tool is exited.

4. Manifest V3 Permissions Explained

In accordance with Chrome Web Store Least Privilege policies, Inspektr requests only the minimum permissions essential to operate its developer tools on-demand:

Permission	Purpose & Scope
activeTab	Grants transient access to the currently active page only when you explicitly open Inspektr. It allows the tool to read element styles locally while active, and automatically terminates once you leave or close the tab.
scripting	Permits on-demand injection of tool modules (such as the Font Detector or upcoming color/image inspectors) into the active tab upon user request, avoiding permanent background access to all websites.

Inspektr does not request broad host_permissions (such as <all_urls>) or background access to your browser activity.

5. Zero External Resources & Assets

Inspektr is 100% self-contained. The extension does not load external web fonts (such as Google Fonts), external CDNs, tracking scripts, or remote assets. All typography relies entirely on your device's native system fonts (system-ui), ensuring complete offline capability and zero network leakage.

6. Open Source & Transparency

Inspektr is open and transparent. The complete source code, manifest configuration, and release builds are available for inspection on our official GitHub repository:
https://github.com/laricoDGT/inspektr

7. Policy Updates

As we deploy additional developer tools within the Inspektr suite, this policy will be maintained and updated accordingly. Any changes will be reflected with an updated date at the top of this document.

8. Contact & Issues

For questions, security inquiries, or feature suggestions regarding Inspektr, please submit an issue on our GitHub repository:
https://github.com/laricoDGT/inspektr/issues