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 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
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.

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 [email protected] and we will add you to the notice list.

Section 6 of the DPA covers your right to object to a new sub-processor and what happens if we cannot find an alternative.