# LLM observability for AI agents Trace model calls, tool steps, and retrievals with OpenTelemetry. Inspect token usage, cost, latency, and errors from your instrumentation. Connect your AI application with our SDKs or an existing OTLP exporter. [Start tracing free](https://telemetry.dev/signup) or [read the quickstart](https://telemetry.dev/docs/quickstart.md). The Free plan includes 30,000 ingestion units a month, one per span, log record, or metric data point. No credit card is necessary. ## What you get telemetry.dev shows traces and metrics for AI applications: - Instrumented model calls, tool steps, and retrievals in a trace hierarchy - Reported token usage, cost, latency, and errors - Search by name and filters for status, environment, framework, and session - Cost and latency breakdowns by model, provider, environment, and user - TypeScript and Python SDKs, plus standard OTLP/HTTP ingest. Trace detail depends on what your instrumentation emits. Cost is calculated per call when token usage and matching model pricing are available. Capture is on by default. You can disable recognized input and output fields per environment before storage. Redaction patterns do not catch all sensitive data. The FAQ below describes the limits of these controls. ## Start building Send your first trace, or go straight to the guide for the stack you already use: - [Quickstart](https://telemetry.dev/docs/quickstart.md): Send your first trace with TypeScript or Python in five minutes. - [Integrations](https://telemetry.dev/docs/integrations.md): Choose a setup guide for a provider, framework, coding agent, SDK, or OpenTelemetry. - [TypeScript SDK](https://telemetry.dev/docs/sdk/typescript.md): Record functions, model calls, tools, and agents from Node and edge runtimes. - [Python SDK](https://telemetry.dev/docs/sdk/python.md): Record sync and async Python code with decorators and context managers. - [OpenTelemetry](https://telemetry.dev/docs/sdk/opentelemetry.md): Keep your existing instrumentation and export standard OTLP/HTTP. - [OTLP ingest API](https://telemetry.dev/docs/reference/otlp.md): Send traces, logs, and metrics from any OpenTelemetry exporter or collector. ## Frequently asked questions ### What is telemetry.dev? telemetry.dev is an LLM observability platform for AI applications and agents, built on OpenTelemetry. A trace groups the instrumented model calls, tool steps, and retrievals in a request or agent run. Reported token usage, cost, latency, and errors help you debug failures and monitor spend. ### How do I start sending traces? Make a project API key, then configure a telemetry.dev integration or an OTLP/HTTP exporter. Run an instrumented request and open its trace in your project. The [integration directory](https://telemetry.dev/docs/integrations.md) links to setup instructions for each SDK, provider, and framework. ### Which frameworks and languages are supported? TypeScript and Python have first-party SDKs, with integrations for providers and frameworks such as OpenAI, Anthropic, and Vercel AI SDK. Other languages can send standard OTLP over HTTP. Trace detail depends on what your instrumentation emits, so each integration guide describes its coverage. ### How is cost calculated? telemetry.dev calculates cost at ingest from reported token usage and its model-pricing catalog. Cache-read and cache-write tokens use separate rates when available. Reasoning tokens are not charged separately. An explicit span cost takes precedence. Without matching model pricing or token usage, computed cost is unavailable. ### Is the free plan actually free? Yes. The Free plan costs $0 and requires no credit card. It includes 30,000 ingestion units per month, 14-day retention, one project, and two seats. Each normalized span, OTLP log record, or metric data point uses one ingestion unit. ### Can I keep prompts and completions out of storage? Yes, for recognized prompt, response, and tool-payload fields. Capture is on by default, and you can disable it per environment before storage. This does not stop transmission to ingest or remove arbitrary content from logs, errors, or custom attributes. Built-in and project-specific redaction patterns apply, but pattern matching cannot catch all sensitive data. To prevent transmission, remove sensitive content in your instrumentation before export. ## Trace your next AI request Choose an integration, add your project API key, and run an instrumented request. [Start tracing free](https://telemetry.dev/signup) or [talk to an engineer](https://telemetry.dev/forms/book-demo). ## Pages - [Documentation](https://telemetry.dev/docs/index.md): Quickstart, SDK references, platform guides, and the ingest reference. - [Pricing](https://telemetry.dev/pricing.md): Plans, limits, and quotas - [Integrations](https://telemetry.dev/docs/integrations.md): SDKs, frameworks, coding agents, and OTLP setup guides. - [Contact](https://telemetry.dev/contact.md) - [Site overview for AI agents](https://telemetry.dev/llms.txt). --- # Pricing — telemetry.dev Observability for AI and LLM apps. Prices are per organization, per month. Each plan includes traces, logs, metrics, token counts, and cost data. One normalized span, OTLP log record, or metric data point counts as one ingestion unit. A trace containing five spans uses five units. Logs derived from span events and metric updates applied to existing spans do not add units. 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. To resume ingestion, upgrade or wait for your allowance to reset. Usage resets at 00:00 UTC on the first day of each calendar month, independently of your billing date. 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. ## Free - Price: $0/month - Limits: 30,000 ingestion units/month, 14-day retention, 1 project, 2 seats - No credit card required ## Pro - Price: $25/month - Limits: 500,000 ingestion units/month (soft limit; ingestion continues above the included amount), 30-day retention, 5 projects, 5 seats ## Team - Price: $50/month - Limits: 2,000,000 ingestion units/month (soft limit; ingestion continues above the included amount), 90-day retention, unlimited projects, unlimited seats - Includes priority support Sign up: https://telemetry.dev/signup Pricing page: https://telemetry.dev/pricing Last updated: 2026-09-10 --- # Contact telemetry.dev We read every message. The fastest way to reach the team is email. ## Support - **Email:** [support@telemetry.dev](mailto:support@telemetry.dev) — product questions, integration help, billing, and security reports all reach the team here. - **Book a demo:** [telemetry.dev/forms/book-demo](https://telemetry.dev/forms/book-demo) — a walkthrough of tracing, cost tracking, and privacy controls for your stack. ## In the product Once signed in, organization owners and admins manage members, projects, and API keys from the organization settings. Per-project switches for prompt capture, retention, and redaction live in each project's settings page. ## About the company telemetry.dev builds observability for AI and LLM applications: every model call, tool step, and retrieval lands as an OpenTelemetry trace with tokens, cost, latency, and errors attached. First-party SDKs ship for TypeScript and Python, provider wrappers cover the official OpenAI, Anthropic, Gemini, Bedrock, LiteLLM, and OpenRouter SDKs, and standard OTLP/HTTP ingest accepts traces from anything else. --- # Data Processing Agreement This Data Processing Agreement ("DPA") sets out how telemetry.dev handles the personal data inside the telemetry you send us. It forms part of the [Terms](/infopages/terms) and takes effect when you accept them, so there is nothing to sign. If your organization needs a countersigned copy, write to [support@telemetry.dev](mailto:support@telemetry.dev). Where this DPA and the Terms disagree about personal data, this DPA wins. ## 1. Who is who You are the controller of the personal data in your telemetry. We are the processor, and we act only on your instructions. Where you are yourself a processor for someone else, we are the sub-processor and the same terms carry down the chain. "Customer Data" means the traces, spans, logs and metrics your applications send to our ingest endpoint, together with the account and project records that describe them. ## 2. What we process, and why **Purpose.** We receive telemetry from your AI applications, normalize it, redact it, store it, and show it back to you as traces, charts and searches. We also count ingestion units to bill you. Nothing else. **Duration.** We hold each telemetry record for your project's retention window: 7, 14, 30 or 90 days. Account records last as long as your account does. **Types of personal data.** Two kinds, from two different sources. _Account data_, which you give us directly: name, email address, profile image, the account identifier from GitHub or Google if you sign in that way, and the IP address and browser user-agent attached to each session. _Telemetry data_, which your applications send us: span and trace names, model and provider names, token counts, cost, latency and error details, plus — unless you turn capture off — the prompts, completions, tool call arguments and tool results your application produced. Spans also carry any `user_id`, `session_id` and `conversation_id` you set, and whatever else you put in span attributes and metadata. **Categories of data subjects.** The people in your organization who hold telemetry.dev accounts, and the end users of your applications whose prompts, identifiers or content appear in the telemetry you send. We cannot know in advance what your prompts hold. What lands in Customer Data is your decision, which is why the controls below exist. ## 3. The controls you hold Three settings limit what we ever store. All three run at ingest, before anything reaches disk. **Capture switches.** Every project has a per-environment switch for input capture and output capture. Turn capture off for an environment and we drop prompt, message, completion and tool-payload fields from every span in that environment before storage. You keep the timings, token counts, costs and error rates. **Custom redaction patterns.** Every project takes a list of regular expressions. We apply them to each string we store and replace what matches. Patterns compile through RE2, so a slow pattern cannot stall your ingestion. **Retention.** Every project holds data for 7, 14, 30 or 90 days. A background job prunes rows past the window, and the storage engine enforces the outer limit as a backstop. Shortening the window also clears data already stored. Whatever those settings say, we always redact: - **Credentials** — private key blocks, `Bearer` tokens, JWTs, OpenAI-style `sk-` keys, AWS access key IDs, Google API keys, GitHub tokens, Slack tokens, our own `td_live_` keys, passwords embedded in URLs, and `api_key`, `password`, `secret` or `token` assignments in text and JSON. - **Personal identifiers** — email addresses, US Social Security numbers, phone numbers, and card numbers that pass a Luhn check. - **Anything named like a secret** — an attribute called `authorization`, `cookie`, `password`, `secret`, `token`, `credential` or `api_key` is dropped, not stored. One limit worth stating plainly: redaction is pattern matching, and pattern matching is never complete. It will not catch a name written into a sentence or a customer record buried in a tool result. You stay responsible for what your applications send us and for having a lawful basis to send it. The service's source code is private. For questions about these controls, contact [support@telemetry.dev](mailto:support@telemetry.dev). ## 4. What we owe you **We follow your instructions.** Your documented instructions are the Terms, this DPA, and the settings you pick in the product. We process Customer Data for no other purpose. If we ever believe an instruction breaks data protection law, we will say so. **We do not train on your data.** We send Customer Data to no model provider, and we use it to train and improve no model. Reading your telemetry is something the product does for you, not something we do for ourselves. **We do not sell your data.** Under the CCPA we are a service provider, not a business and not a third party. We have never sold or shared personal information and do not intend to. **Our people are bound to confidence.** Access reaches only the staff who need it to run the service, and their duty of confidence outlives their time here. **We help you answer data subjects.** When someone asks you for access, correction, export or deletion, the product is usually the fastest route: telemetry is queryable by the `user_id` you set, retention can be shortened, and deleting a project deletes its telemetry. Where the product falls short we will help directly. If a request reaches us instead of you, we pass it on rather than answer it ourselves. **We help you meet Articles 32 to 36.** We will support your security assessments, your data protection impact assessments, and any prior consultation with a regulator, so far as the information is ours to give. **We tell you about breaches.** If we find a personal data breach affecting Customer Data, we will tell you without undue delay and include what we know: what happened, which data and roughly how many records, the likely consequences, and what we are doing about it. We will keep you posted as we learn more. ## 5. How we keep it safe - Traffic to telemetry.dev and ingest.telemetry.dev runs over TLS. - Ingest API keys are stored as SHA-256 hashes. We keep a 16-character prefix so you can tell keys apart; the key itself appears once, at creation, and we cannot recover it. Revoking a key stops the next request that uses it. - Passwords are stored hashed, never as plain text. - Every telemetry query is scoped to a project and checked against your organization membership and role, so one organization's queries cannot reach another's rows. - The analytics database has no public address. It answers only over the private network, and the ingest, dashboard and migration paths each hold separate credentials with different rights. - Ingest and the dashboard run as separate services, so trouble in one does not drag down the other. We hold no SOC 2 report and no ISO 27001 certificate today. We would rather tell you that than let a page of security language imply otherwise. ## 6. Sub-processors You give us general authorization to use the sub-processors named on our [sub-processor page](/infopages/subprocessors). Each is bound by terms no weaker than these, and we remain liable to you for what they do. We update that page before a new sub-processor starts handling Customer Data. Write to [support@telemetry.dev](mailto:support@telemetry.dev) if you would rather hear about it by email and we will add you to the notice list. Object on reasonable data protection grounds within 30 days and we will look for an alternative; if none exists, you may stop using the affected part of the service and cancel the rest of the term without penalty. ## 7. Where your data lives Our services and databases run in the United States, in Northern Virginia. Personal data you send from the EEA, the United Kingdom or Switzerland is transferred to the United States. For those transfers we rely on the European Commission's Standard Contractual Clauses, brought into this DPA by reference: Module Two where you are a controller, Module Three where you are a processor. The UK International Data Transfer Addendum covers United Kingdom data. For Swiss data the Clauses apply with the Federal Data Protection and Information Commissioner as supervisory authority. Section 2 supplies the details the Clauses ask for, and section 5 is the description of technical and organizational measures. ## 8. Audits We will give you what you need to show that we meet Article 28, and we answer reasonable security questionnaires. For questions about the processing controls, contact [support@telemetry.dev](mailto:support@telemetry.dev). Where that is not enough, you or an auditor you appoint may inspect our processing once a year, on reasonable notice, at your cost, under confidence, and at a time that does not disturb the service. A regulator may inspect on whatever terms the law gives it. ## 9. Getting your data back, and getting rid of it While your account is open you can read everything we hold through the dashboard and the HTTP API. Telemetry then clears itself when its retention window closes. Deleting a project deletes that project's telemetry; deleting an organization deletes the telemetry of every project inside it. Both take effect at once and neither can be undone. When your account closes we delete Customer Data from live systems. Copies sitting in infrastructure backups go as those backups age out. We keep only what the law requires us to keep, such as billing records, and nothing beyond that. ## 10. Changes We will update this DPA as the service changes, and the date at the top of the page shows when we last did. If a change cuts your rights in a material way, we will email account owners before it takes effect. Questions about any of this go to [support@telemetry.dev](mailto:support@telemetry.dev). --- # Privacy Policy 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](/infopages/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](https://polar.sh) 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. **Sign-up checks.** The sign-up page loads Cloudflare Turnstile, which runs an invisible check in your browser when you create an account with an email address and password, to tell people apart from automated sign-ups. You do not see it. Cloudflare processes signals such as your IP address, browser details and the site you are on, both to detect bots for us and to improve Turnstile, as described in its [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/). Our server receives the result of the check and related details such as when it ran. **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](/infopages/subprocessors) names every company involved and what each one does. In summary: our host runs the servers and databases, one service sends account email and checks email sign-ups for bots, 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](/infopages/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 [support@telemetry.dev](mailto:support@telemetry.dev) 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: [support@telemetry.dev](mailto:support@telemetry.dev). --- # Sub-processors Running telemetry.dev takes a handful of other companies. This page names every one of them that touches personal data, says what they do and where they hold it, and is the list our [DPA](/infopages/dpa) refers to. We keep it short on purpose. The fewer companies your telemetry passes through, the less there is to explain. ## Handling Customer Data One company stores your telemetry. | Sub-processor | What it does | Where | | ------------- | --------------------------------------------------------------------------------------------------------- | --------------------------------- | | Railway | Hosting for our services, and the Postgres and ClickHouse databases holding account records and telemetry | United States (Northern Virginia) | That is the whole list. Your prompts, completions and span attributes reach no other company. In particular, we send them to no model provider and use them to train no model. ## Handling account data These companies see the details of your telemetry.dev account. None of them sees your telemetry. | Sub-processor | What it does | Where | | ------------- | ------------------------------------------------------------------------ | --------------------------- | | Cloudflare | Sends account email — invitations, address verification, password resets | United States | | Cloudflare | Checks email sign-ups for automated abuse with Turnstile | Cloudflare's global network | | Polar | Runs checkout, subscriptions and invoicing as merchant of record | United States | | GitHub | Signs you in, when you choose GitHub | United States | | Google | Signs you in, when you choose Google | United States | Signing in through GitHub or Google returns us your name, email address and profile image. We ask for nothing else and receive nothing else. Cloudflare also runs Turnstile on the sign-up page. It processes browser signals on our behalf to block automated sign-ups, and separately, as its own controller, to improve Turnstile, under its [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/). ## Handling enquiries Not a sub-processor under the DPA, since none of this is Customer Data, but you should know about it anyway. | Service | What it does | Where | | ------- | ---------------------------------------------------------- | ------------- | | Discord | Carries "Book a call" form submissions to our team channel | United States | ## Changes to this list We update this page before a new sub-processor starts handling Customer Data. To hear about changes by email, write to [support@telemetry.dev](mailto:support@telemetry.dev) and we will add you to the notice list. Section 6 of the [DPA](/infopages/dpa) covers your right to object to a new sub-processor and what happens if we cannot find an alternative. --- # Terms of Service 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](/infopages/dpa), which governs the personal data inside the telemetry you send us, and the [Privacy Policy](/infopages/privacy). 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 [support@telemetry.dev](mailto:support@telemetry.dev) 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](https://polar.sh) 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 [support@telemetry.dev](mailto:support@telemetry.dev) 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](/infopages/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](/infopages/subprocessors) 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 [support@telemetry.dev](mailto:support@telemetry.dev) 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 [support@telemetry.dev](mailto:support@telemetry.dev). ## 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](https://status.telemetry.dev). If something is broken, [support@telemetry.dev](mailto:support@telemetry.dev) 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 [support@telemetry.dev](mailto:support@telemetry.dev) for anything at all — questions about these terms, billing, security reports, or a bug that is ruining your afternoon.