Privacy
Launchpad is a Liatrio-internal tool, and the people it reports on are Liatrio employees. This page says exactly what it sends, so the switch in Settings means something.
Signed in, events are linked to you
You sign in to Launchpad with your Liatrio Google account. While you are signed in, your usage events, errors and web session recordings are linked to you: your Launchpad user id, your work email and your name. Nothing else about your account is sent. Signed out, events are anonymous. The Usage events switch in Settings stops all of it.
| What is collected | Signed out | Signed in |
|---|---|---|
| Who the events belong to | A random id that is thrown away and replaced every day. | Your Launchpad user id, with your work email and name. Events from earlier in the same visit, before you signed in, join it. |
| Stored profile | None is created, except after an error — see below. | One profile, holding your email and name, which you can ask us to delete. |
| Session recordings (web) | Every input is masked before it leaves your browser. Page text is shown. | Every input is masked before it leaves your browser. Page text is shown. |
| Session recordings (macOS) | None. The app does not record sessions. | None. The app does not record sessions. |
What is actually sent
Usage events
A named, reviewed list — opening the app, viewing a screen, opening a tool from the catalog, running a search. Each carries the screen or tool name, the platform, and the app version. Nothing captures page text automatically. The one thing you type that is recorded is catalog search: while you are signed in, PostHog keeps the text you searched for, how many tools it found, and which result or suggestion you picked. Email addresses in that text are replaced before it is sent. The other analytics service only ever sees how long a search was and how many tools it found, never the text.
Never sent
Passwords, sign-in tokens, sign-in codes and session data are never sent, signed in or not. Anything in a web address that could carry one — in particular the one-time code a sign-in leaves there — is stripped before an event or a recording leaves your browser.
Errors and crashes
When Launchpad breaks, it sends the error, the stack trace and the app version, so the crash can be found and fixed. These follow the same switch as usage events: turning telemetry off stops them too.
One caveat, because it is the single place the table above does not hold. Our analytics provider always files an error report against a stored profile, even when you are signed out, and we cannot turn that off without losing error reporting altogether. The profile it creates is keyed to that day's random id and holds no name, email or device id — but an error is the one event that leaves a record where nothing else does. That record stays until it is deleted; the id it is filed under stops being yours when the day rolls over.
Session recordings, on the web only
A replay of the pages you visited, used to see where a flow goes wrong. Everything you type into a field is replaced before it is sent, signed in or not, and password fields always are. The text on the page itself is recorded as shown, so the replay can be read.
Measured by our host, on the website only
The website runs on Vercel, and they count page views and measure how quickly pages load. This is the one thing on this page that the telemetry switch does not turn off — there is no off-switch for it, and we would rather say so than let you assume otherwise.
What makes that defensible is that there is nothing in it tied to you. No cookie is set and nothing is stored in your browser. To count visitors without one, Vercel derives a one-way hash from your IP address and browser, mixed with a secret they replace every 24 hours — so tomorrow the same person is a new visitor that cannot be linked to today.
What it records: the page, where you arrived from, your country, and your browser, operating system and device type; the speed measurements add how long the page took to become usable. No name, no email, no account id, and no profile of any kind. Anything in a web address that could identify you — in particular the one-time code a sign-in leaves there — is stripped before the measurement is sent. It does not cover the macOS app.
Where it goes
Three places. PostHog, for product analytics, error tracking and the web session recordings; Honeycomb, for the engineering traces that show whether the service itself is healthy; and Vercel, who host the website, for the page-view and page-speed measurements described above. The first two are under Liatrio's control and answer to the switch below; the third is part of running the site. Launchpad does not sell data, does not run advertising, and sends nothing to an ad network.
Turning it off
Settings → Telemetry → Usage events, on the web and in the macOS app. One switch, and it covers everything Launchpad itself collects: events, errors and recordings, in both PostHog and Honeycomb. Turning it off applies immediately — a recording in progress stops there and then. The app works exactly the same with it off.
The exception is the page-view and page-speed measurement our host takes, described above. That switch does not reach it, because it is part of serving the website rather than something the app does. Nothing in it is tied to you, and it never applies to the macOS app.
Signing out drops the link to you at once: from then on, events are anonymous under a fresh random id. It does not unlink what was recorded while you were signed in.
Asking for your data, or its deletion
For anything recorded while you were signed in, ask in #launchpad and we will export or delete your profile and its events. Signed-out events are tied to nothing — the id rotates daily — so there is generally nothing to look up. The error profiles described above are the exception, and we cannot tell you which of them is yours, because nothing in them says.
Liatrio internal. Back to Launchpad