Privacy

Typecask collects nothing about you, and the app has no way to send anything anywhere. This page covers the app and this website separately, because they’re different things with different behaviour.

The app

Typecask collects no personal data. There are no accounts, no sign-in, no analytics or crash reporting SDKs, and no advertising.

The app makes no network requests of its own. Every font is bundled with the app as an On-Demand Resource, which means installing one downloads it from Apple’s App Store servers the same way any other app content arrives. Apple sees that request; Typecask doesn’t, and there’s no server of ours in the path. Apple’s handling of it is covered by the Apple Privacy Policy.

What stays on your device. The app records which fonts you’ve installed and their versions, so it can offer Update when a later release carries a newer version. That record lives on your device. It isn’t sent anywhere and isn’t readable by us.

Fonts you install become system fonts. They appear in Settings › General › Fonts and in any app that can use installed fonts. You can remove them from Typecask or from Settings.

This website

Page views are counted, without cookies. typecask.app uses Cloudflare Web Analytics, which sets no cookies, stores no identifier in your browser, and doesn’t follow you to other sites. It records the page you looked at, the referrer, and your browser, device type and country, derived from the request. Cloudflare’s Web Analytics privacy documentation describes what it collects.

There are no other trackers. No advertising, no session recording, no third-party embeds. Fonts, styles and scripts are served from typecask.app itself, so loading a page makes no request to anyone else.

Server logs. Cloudflare, which hosts the site, processes requests and keeps short-lived logs as part of delivering it.

Children

Typecask is not directed at children and collects nothing from anyone, children included.

Changes

Any change to this policy will be published here with a new date at the top. The history of this page is public in the site’s source.

Contact

Questions about privacy go in GitHub Issues, or see Support for the other ways to reach us.