Does Fontlens send any data anywhere?

No. Fontlens makes no network requests of any kind. There is no fetch, no XMLHttpRequest, no WebSocket and no remote script in the shipped package. There is no server to send anything to.

Can Fontlens see my browsing history or other tabs?

No, and not by policy but by structure. Fontlens requests no host permissions. It uses activeTab, which grants access to a single tab and only at the moment you click the toolbar icon. It has no mechanism to read history, other tabs, or any page you have not explicitly activated it on.

Where are my saved fonts stored?

In chrome.storage.local on your own machine. They are not synced to a Google account and not sent anywhere. Uninstalling Fontlens deletes them.

How can I verify that Fontlens collects nothing?

Open DevTools on any page, go to the Network tab, activate Fontlens and use it. No request from the extension will appear. You can also inspect the extension's own source: open chrome://extensions, enable Developer mode, and click the service worker or use the Sources panel to read every shipped file.

Privacy

Last updated 7 August 2026 · Applies to Fontlens version 1.0.0

Short answer

Fontlens collects nothing and sends nothing anywhere. It makes no network requests of any kind: no analytics, no error reporting, not even a version check. There is no account, no sync and no server. Everything happens inside your browser and stays there. The section on verifying this yourself explains how to confirm it rather than take our word for it.

What is collected

Nothing. Not anonymised, not aggregated, not "for product improvement". There is no data pipeline in this extension because there is no network code in it.

In the Chrome Web Store's data disclosure form, every category is left unticked, and all three certifications are declared: data is not sold to third parties, not used for purposes unrelated to the extension's single purpose, and not used to determine creditworthiness.

What is stored on your machine

One thing, and only if you use it: the optional saved font list.

When you click save on a font, Fontlens keeps the font name, size and weight in chrome.storage.local. That is local browser storage on your own device. It is deliberately not chrome.storage.sync, so it is never uploaded to your Google account or shared between your devices. Uninstalling Fontlens removes it.

The three permissions, and why each one exists

Permission	What it allows	Why it is needed
`activeTab`	Access to the single tab you are currently viewing, granted only at the moment you click the toolbar icon, and revoked when you navigate away.	Fontlens has to read the page to report its fonts and colours. This is the narrowest permission that allows it.
`scripting`	Injecting the inspector into that one tab on that one click.	Injecting on click rather than on every page load is what keeps the scope to one tab and avoids running on pages you never asked about.
`storage`	Reading and writing local browser storage.	The saved font list, so it survives closing the browser. Nothing else is written.

What is deliberately absent matters more than what is present. Fontlens requests no host permissions, the ones that read as "read and change all your data on all websites" when you install something. Without them, an extension has no way to reach a page you have not explicitly activated it on. This is why Fontlens structurally cannot see your browsing history, your other tabs, or any site you are not looking at right now. It is not a promise, it is the permission model.

No remote code

Fontlens ships every line of code it runs inside the extension package. There is no eval, no new Function, no importScripts, and no script tag pointing at anything outside the package. This was verified by scanning every shipped file before submission, and it is declared as such in the Chrome Web Store listing.

This matters because an extension that loads code from a server can change what it does after you install it, without an update and without review. Fontlens cannot.

How to verify all of this yourself

None of the above is worth much as a claim. It is worth something as a thing you can check in about a minute.

Watch the network. Open DevTools on any page, go to the Network tab, then activate Fontlens and use it. Hover, pin, open the page report, save a font. No request from the extension appears, because there are none to make.
Read the source. Go to chrome://extensions, turn on Developer mode, and open the extension's files from the Sources panel in DevTools. Every file that ships is readable. Search for fetch, XMLHttpRequest and WebSocket and you will find none.
Check the permissions. On the same chrome://extensions page, click Details on Fontlens. Site access will show that it runs on click rather than on all sites.

Third parties

There are none. Fontlens contains no analytics SDK, no advertising code, no crash reporter and no third-party library that phones home.

This website is a separate matter and is stated separately: it is a set of static HTML files served by Vercel. It sets no cookies, runs no analytics and embeds no third-party scripts, fonts or trackers. Vercel, as the host, processes standard server request logs, which is unavoidable for any hosted website.

Children

Fontlens is a developer and design tool and is not directed at children. Since it collects no data at all, it collects no data from anyone of any age.

Changes to this policy

If Fontlens ever collects anything, this page will say so before that version ships, and the change will be visible in the Chrome Web Store's data disclosure, which cannot be updated silently. The current answer is nothing, and there is no plan to change it.

Questions

The Chrome Web Store review thread on the Fontlens listing is the place to ask. Reviews get answered.