Privacy

What lint.one and its browser extension keep, and what they never see.

Last updated 25 September 2026

The files and text you open never leave your device.

They are read, parsed and shown by code running in your browser. No page and no part of the extension sends them anywhere, lint.one included.

The website

Every tool runs entirely in the page. There are no accounts, no analytics, no advertising and no third-party requests: the fonts and libraries are served by lint.one itself. You can check this in your browser's developer tools, where the Network panel shows nothing leaving while you work.

Your browser keeps a few things on your device so the pages behave the way you left them. None of them holds anything you opened:

  • Three cookies. lintuz_theme and lintuz_contrast remember the theme and contrast you picked. lintuz_from lasts two minutes, and only when a converted document couldn't be handed to the next tool directly, so that tool can name the format waiting on your clipboard.
  • Local storage holds your text size, split width and a few view settings.
  • IndexedDB holds a file you drop on the home page, or a document you convert for another tool, for the second it takes that tool to open, and it is deleted as the tool reads it.
  • An offline copy of the site's own pages, kept by the service worker, so lint.one works without a connection.

Counting requests for new formats

Visiting an address for a format lint.one doesn't read yet (lint.one/toml, say) shows a page where you can add yourself to the count of people who want it. Only if you do, the server stores the format, the time, and a one-way hash of your IP address mixed with that format and a server-side secret. The hash lets each person count once. It can't be turned back into an address, and nothing else about you is kept.

The browser extension

The lint.one extension opens what you choose (a selection, a link, a page, text you paste, a tab's sound) in the lint.one tool that reads it. When you do:

  • A link or page is read by the page you found it on, with that page's own cookies, exactly as clicking it would. A selection is read from the page when you ask.
  • The file then passes from that page to the extension to the lint.one tab, inside your browser. It is never put in a web address and never sent to any server, lint.one's included.
  • When you choose Listen to this tab, the lint.one Audio tab hears that tab's sound to draw its spectrum and plays it back to you. It is not recorded, saved or sent anywhere, and it stops when you stop listening or close either tab.
  • The extension stores two things in your browser: whether Open data pages automatically is on, and the theme you picked on lint.one, so its menu matches.
  • It collects no data, has no analytics, and runs no code from anywhere but its own package.

The extension runs on lint.one, where it hands over the file, and on a page only when you click it there. Hearing a tab is asked for the first time you choose Listen to this tab. Access to every site is asked for only if you turn on Open data pages automatically. It is used to recognise JSON, XML, YAML and CSV pages as you open them, and to read links to other sites that you choose to open. Turning the setting off gives that access back.

Hosting

lint.one is served by Cloudflare. Like any web host, Cloudflare handles the requests your browser makes for lint.one's own pages and files, and its privacy policy covers that. Those requests never contain what you open, since that never leaves your browser.

Changes and questions

If any of this changes, this page changes with it, and the date above moves. lint.one is open source, so everything here can be checked in the source code. Questions are welcome as GitHub issues.