Skip to main content

Privacy

Your fonts never leave your device

This page explains what FontPivot does with your files and what it measures about visits. Short version: the fonts you open stay on your computer, while Google Analytics measures visits and broad tool usage.

Last updated

Your font files

When you open fonts in any FontPivot tool, including the font converter, the webfont generator, the font subsetter, the variable font instancer, the font viewer, and the font fallback generator, your browser reads the files directly from your device. Previewing, reading the font’s details, converting, subsetting, instancing, fixing vertical metrics, removing hinting, calculating fallback values, and building the web font kit (ZIP) all happen inside your browser tab, whether you open one file or a whole family.

Subsetting, instancing, and removing hinting use HarfBuzz, an open-source text engine. FontPivot sends the HarfBuzz program to your browser like any other part of the page, and it works on your fonts there.

  • Your font files are not sent to our server or to any other service.
  • The converted font and the ZIP are created on your device and saved through your browser’s download.
  • Your files are kept in the page’s memory only while you use them. Removing a file, leaving the page, or closing the tab clears it.

After your first visit, your browser keeps a copy of FontPivot’s own pages and code so the tools also work offline. That copy holds only the site’s files, never your fonts, and it is replaced when the site is updated. You can remove it by clearing this site’s data in your browser settings.

Settings saved in your browser

A few choices are kept in your browser’s local storage on this device, so you do not have to make them again. They are never uploaded.

  • The web font kit options, but only after you change them in the converter: the font-display value, local() sources, base64 embedding, the font folder name, and the fallback font settings. The converter and the font viewer both use them for the next kit. “Reset to defaults” in the converter clears them.
  • Light or dark mode, if you switch it with the button in the header.

Clearing this site’s data in your browser settings removes all of them.

Analytics

FontPivot loads Google Analytics when you visit the site to understand which pages people visit and whether the tools work for them. Google Analytics may set cookies to count visits and recognize a returning browser.

What is recorded

Every tool event is a short list of categories, such as “WOFF2” or “1–5 MB”, never anything you typed or anything read from your fonts.

  • Page views: which page you opened and the page that linked you here.
  • The tool and the formats: whether you used the converter (which also runs the webfont generator, the subsetter, and the variable font instancer) or the font viewer, the format of the font you opened, and the format you converted to.
  • Size and number of files: a file size range (under 100 KB, 100 KB–1 MB, 1–5 MB, or over 5 MB) and how many fonts you handled at once (1 to 9, or 10 or more).
  • How things went: whether a preview, reading the font’s details, or a conversion succeeded, failed, or was cancelled; if a file was refused, whether it was too large, in an unsupported format, or unreadable; a general error type; and whether the result was larger, the same, or smaller, in rough ranges.
  • Subsetting: whether you used the built-in character sets, your own characters or ranges, or both; which built-in sets you picked; whether you removed any OpenType features; and whether you split the font into smaller files by character range.
  • Variable fonts: whether you fixed an axis at one value, narrowed its range, or both.
  • Line spacing and hinting: whether you turned on the vertical metrics fix, and whether you kept or removed the font’s hinting.
  • The CSS in a web font kit: the font-display value; whether you turned on local() sources or base64 embedding or changed the font folder; and whether fallback font CSS was added with the detected settings, with settings you changed, turned off, or could not be made.
  • Code snippets: which kind of snippet you opened or copied (CSS, preload HTML, Next.js, Tailwind, or Astro), and whether you opened or copied it.
  • Downloads: whether you downloaded a single font, the web font kit, or a ZIP of converted fonts.

What is never recorded

  • File names.
  • Font names or any other details read from the font, such as its designer or license text.
  • The contents of your font files.
  • The text you type into the preview.
  • The characters you type or the Unicode ranges you enter for subsetting, the axis values you choose for a variable font, and the font folder name you enter.
  • The code in the snippets you copy.

What Google collects

Like any Google Analytics site, Google also receives standard technical information when the script runs, such as your browser and device type, screen size, and an approximate location derived from your IP address. The site tells Google that advertising storage and ad personalization are not allowed, and FontPivot does not show ads. Google explains its own handling in How Google uses information from sites or apps that use our services.

Hosting

Like every website, FontPivot’s pages are delivered by a hosting service. To send a page to you, that service necessarily receives basic request information, such as your IP address and browser type. Your font files are never part of these requests.

Our guides link to documentation and resources on other websites, such as MDN and web.dev. Those sites have their own privacy practices.

Changes to this page

If FontPivot starts handling data differently, this page will be updated first and the date at the top will change.