Cookies

What we count, and why

We use Google Analytics, through the same Firebase project the app uses, to learn how many people visit, which pages they read, where they came from, and how many of them press a download button. That's how we find out whether the install guide and tutorials are doing their job.

• If you choose no cookies (the default), your visit is still counted, but anonymously: no cookie, no identifier, nothing that links this page to the next one or to your next visit.
• If you accept, Google Analytics sets its own cookies (_ga and _ga_…, kept up to two years) so a return visit counts as the same visitor rather than a new one.
• Either way, Google's advertising features and Google Signals are switched off. Nothing here is used to show you ads, on this site or anywhere else.

Your choice is remembered in your browser's own storage, not in a cookie. Change your choice.

What else reaches another company

• Google Fonts. The typefaces are loaded from Google's servers, which means Google sees your IP address when a page loads.

The tutorials are screenshots served from this site, not embedded videos, so watching them contacts nobody else.

Inside the app

The desktop app is not a website and has no cookies either. It does store your preferences — which tab you had open, how you like things sorted — on your own computer. That never leaves your machine and is not used to identify you.

Separately, the app sends anonymous usage counts and scrubbed crash reports — on by default, and one switch in Settings → About turns them off. They carry no cookie and no merchant, amount or name; the privacy policy (section 3.5) lists exactly what is in them. Your statements are never part of any of this, on the site or in the app.

If this changes

If anything else starts counting or tracking, this page will say so plainly before it goes live. A privacy promise that quietly goes stale is worse than never making one.