Privacy Policy
Last updated on
This policy covers the data we hold about you, the person using telemetry.dev: your account, your visits to the site, your billing details.
It does not cover the telemetry your applications send us. We hold that on your behalf, not for ourselves, and the DPA governs it — what we redact, how long we keep it, and what controls you hold. If you are here to find out what happens to your prompts and completions, read that instead.
What we collect, and why
Your account. Your name, email address, and profile image if your sign-in provider gives us one. We need these to identify you, show you to your teammates, and email you about the service. If you sign in with GitHub or Google we also store the account identifier they return and the tokens that keep you signed in. We ask them for nothing beyond name, email and image.
Your sessions. Each sign-in records an IP address, a browser user-agent, and an expiry. This keeps your account secure and lets us spot someone else using it.
How you found us. When you first land on the site we record where you came from — the source, medium and campaign from any link parameters, the referring site's hostname, and the page you landed on. It attaches to your account if you sign up. It tells us which of the things we write and build actually reach people. We do not build a profile from it, and we do not pass it on.
Which days you were active. One row per user per day. It tells us whether people come back, which is the only growth number worth watching.
Billing. Polar runs checkout as merchant of record. Your card details go to them and never touch our servers. We see your plan, your subscription status, and enough to send you to the right invoice.
When you write to us. If you book a call or email support, we keep what you sent so we can answer.
We collect nothing else. There is no advertising pixel on this site, no session recorder, and no third-party analytics — no Google Analytics, no PostHog, no Plausible, nothing. If you want to know how many people read a page, we cannot tell you very precisely, and we have decided we can live with that.
Cookies
The app can set five cookie types. The app owns these cookies. We do not share these cookies.
| Cookie | What it does | How long |
|---|---|---|
better-auth.session_token | Keeps your sign-in session active | 7 days with "Remember me" or the browser session without it |
better-auth.session_data | Keeps signed session data in the browser cache | 5 minutes with "Remember me" or the browser session without it |
better-auth.dont_remember | Records that you set "Remember me" to off | The browser session |
telemetry_first_touch | Records the source of your first visit before signup | 90 days |
sidebar_state | Keeps the open or closed sidebar state | 7 days |
On the production site, Better Auth adds __Secure- to its cookie names. It can divide a large session_data value into numbered cookie parts. The site has no advertising cookies. Thus, the site has no consent banner. The authentication cookies are necessary to sign in and use the app. You can block telemetry_first_touch and sidebar_state. This does not change the other site functions.
Who else sees it
The sub-processor page names every company involved and what each one does. In summary: our host runs the servers and databases, one service sends account email, one runs billing, and GitHub and Google sign you in if you ask them to.
We do not sell your personal information and we do not share it for advertising. We have never done either.
We hand data to a government or a court only when a valid legal order compels us. Where we are allowed to tell you first, we will.
Where it lives, and for how long
Our servers and databases run in the United States, in Northern Virginia. If you are writing from the EEA, the United Kingdom or Switzerland, your data crosses to the United States, and the DPA sets out the transfer safeguards we rely on.
Account data lasts as long as your account. Close it and we delete your data from live systems, and copies in infrastructure backups go as those backups age out. We keep only what the law requires, such as billing records.
Your rights
Wherever you live, you can ask us to show you what we hold, correct it, delete it, hand it over in a portable form, or stop a particular use. Much of it is in the dashboard already. For the rest, write to [email protected] and we will answer within a month.
You will not get a worse service for asking. There is no charge, and there is nothing to bargain over — we offer no discount in exchange for your data, so there is no incentive to lose.
If you are in the EEA or the UK, you can also complain to your data protection authority. We would rather you came to us first.
If you live in California
The CCPA asks us to spell out what we collect and what we do with it. Everything above applies to you, and here it is in the CCPA's own terms.
In the last twelve months we collected identifiers (name, email, account IDs), internet and device information (IP address, user-agent, referring site, pages visited), and commercial information (your plan and subscription status). We use them to run the service, to talk to you, to bill you, to keep the account secure, and to understand whether people come back.
We disclose them for business purposes to the service providers named on our sub-processor page. We do not sell or share personal information, and have not in the last twelve months. We do not use or disclose sensitive personal information beyond the business purposes you cannot opt out of, so there is nothing here for you to limit. We do not offer financial incentives for your data.
Under California's "Shine the Light" law you may ask what personal information we disclosed to third parties for their own direct marketing. The answer is none, and we do not intend to start.
Children
telemetry.dev is a tool for developers and is not for anyone under 16. We do not knowingly collect their data. Tell us if you think we have and we will delete it.
Changes
We update this policy as the service changes, and the date at the top shows when we last did. If a change matters to you, we email account owners before it takes effect.
Questions, requests, or a suspicion that something here is wrong: [email protected].