Terms of Service
Last updated on
These terms cover your use of telemetry.dev: the website, the dashboard, the ingest endpoint at ingest.telemetry.dev, and the HTTP API. "We" and "us" mean telemetry.dev. "You" means the person or organization holding an account.
Using the service means you accept these terms. They include the DPA, which governs the personal data inside the telemetry you send us, and the Privacy Policy.
We change these terms as the service changes. The date above shows when we last did. If a change matters to you, we email account owners before it takes effect.
Your account
You need an account to send us telemetry. Sign up with an email address and password, or through GitHub or Google.
Keep your credentials safe, and your ingest API keys safer. A key that starts td_live_ can write telemetry to your project until you revoke it, so treat it as a secret: keep it out of client-side code, out of public repositories, and out of screenshots. You can revoke any key from the dashboard and the next request that uses it will fail.
You are responsible for what happens under your account, including what the people you invite do. Tell us at [email protected] if you think someone else is using it.
Plans and limits
We meter ingestion units. One unit is one normalized span, one OTLP log record, or one metric data point. Logs derived from span events and metric updates applied to existing spans do not add units. Usage resets at 00:00 UTC on the first day of each calendar month, independently of your billing date. Prices are per organization, per month. Every plan carries a monthly allowance, a retention window, and caps on projects and seats:
| Plan | Price | Ingestion units | Retention | Projects | Seats |
|---|---|---|---|---|---|
| Free | $0 | 30,000 / month | 14 days | 1 | 2 |
| Pro | $25 / month | 500,000 / month | 30 days | 5 | 5 |
| Team | $50 / month | 2,000,000 / month | 90 days | Unlimited | Unlimited |
What happens at the cap. Free includes 30,000 ingestion units per month, with 20% headroom. We reject an ingestion request if accepting it would bring your organization's monthly total above 36,000 units. Upgrade or wait for the monthly reset to resume ingestion. On Pro and Team, ingestion continues above the included amounts, with no automatic overage charges. If your usage consistently exceeds your allowance, we'll contact you to discuss a suitable plan.
Project and seat caps are enforced as you go. If you drop to a plan with a shorter retention window, projects already set to a longer one keep it — we will not quietly shorten how long your data lives — but you cannot raise retention past your plan's limit.
Payment
Polar handles our checkout, subscriptions and invoices as merchant of record. They take your payment details, not us, and they charge and remit sales tax and VAT where it is due.
Paid plans bill monthly in advance. Upgrades take effect and bill at once; downgrades take effect at the start of the next cycle. Cancel and you keep the paid plan until the end of the period you have already paid for, and we do not prorate the rest of the month.
If a payment is not successful, we try the payment again and send you an email. If the payment stays unsuccessful, we set the account to Free. The Free project, seat, and ingestion limits then apply. The retention rule above also applies. Existing projects keep their retention setting. You cannot increase the setting more than the Free limit.
Write to [email protected] if a charge looks wrong. We would rather refund something than argue about it.
Your data
Your telemetry is yours. We claim nothing over it. You give us only the permission we need to run the service for you: to receive, store, redact, index and display your data, and to count it for billing.
We do not sell it. We do not share it. We do not send it to any model provider, and we do not use it to train or improve models.
The DPA sets out how we handle personal data inside your telemetry, what we redact, what controls you hold, and who else is involved. The sub-processor list names every company that touches it — there is one, and it hosts our servers.
You decide what your applications send us. Do not send us data you have no right to send.
Using the service properly
Do not use telemetry.dev to break the law or to hurt people. More specifically, do not:
- send telemetry you have no lawful basis to collect or share;
- deliberately send payloads built to break our parsing or exhaust our storage;
- try to reach another organization's data, or probe for a way to;
- resell the service, or run it as your own product behind a different name;
- work around ingestion limits with extra accounts.
Security research is welcome. Test against your own projects and report what you find to [email protected] before telling anyone else.
If you break these rules we may suspend the account. We will tell you why and give you a chance to put it right, unless the problem is doing active damage, in which case we act first and explain immediately after.
The API and the SDKs
The HTTP API is part of the service and these terms cover it. It is documented at /openapi.json. We may rate-limit a client that threatens the service for everyone else, and we will warn you first where there is time to.
Our SDKs are published under the MIT license and you can use them on its terms. That license covers the SDK code, not the hosted service.
The hosted service's source code is private. These terms do not give you a license to run your own copy of the service. For questions about how we handle your data, contact [email protected].
Leaving
Cancel from the dashboard whenever you like. No call, no retention offer.
While the account is open, you can read everything we hold through the dashboard and the API. Do that before you go: deleting a project deletes its telemetry, deleting an organization deletes every project inside it, and neither can be undone. Telemetry also ages out of its retention window on its own.
When your account closes we delete your data from live systems. Copies in infrastructure backups go as those backups age out. We keep only what the law makes us keep, such as billing records.
We can close an account that breaks these terms, or one that has been dormant on the Free plan for a long stretch. Either way you get notice and a chance to export first, unless the law stops us from giving it.
What we promise, and what we do not
We work hard to keep the service up, and we do not promise it will be. There is no uptime commitment and no service level agreement. We publish service status at status.telemetry.dev. If something is broken, [email protected] reaches a human.
Support runs on email for everyone, and Team accounts go to the front of the queue.
The service is provided as it is. We give no warranty that it will fit a particular purpose or run without fault. We will not be liable for lost profits, lost data, or any indirect or consequential loss. Where we are liable, our total liability is capped at what you paid us in the twelve months before the claim.
That is the usual language, and here is the honest version underneath it: telemetry.dev is an observability tool, not a system of record. Keep anything you cannot lose somewhere else too.
Getting in touch
[email protected] for anything at all — questions about these terms, billing, security reports, or a bug that is ruining your afternoon.