Font Detector

Chrome Extension by Patrick Bushe

Privacy Policy

Last updated: March 2026  ·  Version 1.0

The Short Version

Font Detector does not collect, transmit, or share any personal data. Everything the extension does stays entirely on your device. No accounts, no servers, no tracking.

Data Collected

Font Detector collects no personal data whatsoever. The extension does not collect:

What Is Stored Locally

Font Detector uses chrome.storage.local to save a small amount of data on your device only. This data never leaves your browser.

Key What it stores Why
pickerEnabled Boolean — whether the font picker is active Preserves picker state across popup open/close
lastInspectedFont Font metadata: family name, size, weight, style, line height, color hex Shows your last inspected font in the "Last Inspected" panel when you reopen the popup

The lastInspectedFont entry stores only computed CSS typography values (e.g., "Inter", 16px, 400, normal, #1a1d27). It does not store any page content, the URL of the page you were on, or any other context.

Data Transmission

Font Detector makes zero network requests. The extension has no backend, no API calls, and communicates with no external servers — including servers operated by the developer.

Permissions Explained

Font Detector requests only the permissions required for its core functionality:

Third-Party Services

Font Detector does not integrate with, report to, or share data with any third-party services. There are no embedded SDKs, ad networks, analytics platforms, or external APIs.

Children's Privacy

Font Detector does not collect any data from users of any age. The extension is fully compliant with COPPA and similar regulations by virtue of collecting no data at all.

Changes to This Policy

If this privacy policy is updated, the new version will be published at this URL with a revised "Last updated" date. Significant changes will also be noted in the Chrome Web Store listing update notes.

Contact

Questions about this privacy policy or the extension's data practices? Reach out directly:

Patrick Bushe  ·  Los Angeles, CA