throughline

Privacy.

What the service stores about you, how a key travels, and who else is involved.

Who holds your data

Throughline is operated by Michael O'Rourke. Privacy questions and requests go to access@throughline.markets.

What the service stores

Throughline uses these records to verify access, count usage, manage plans and recover the service.

Account
An account ID, the sign-in provider's issuer and its identifier for you, whether the account is enabled, the plan and its allowances, and when the account was created. The account database has no email address or name column.
Signup
Where signup recording is installed, the sign-in provider's registration time, the signed event's identifier and when it was first observed. These records support account-to-paid conversion totals. Older accounts without a registration record remain unknown rather than receiving an invented signup date.
API keys
For each key: an ID, the name you gave it, when it was created and revoked, and a SHA-256 hash of the key. The key itself is not stored. Where activation recording is installed, also the time of the key's most recent successful news request.
Activation
Where installed, one record per account: whether its first key came from the account page or an approved connection, when the account and that key were created, the times of the first recorded and most recent successful news request, running counts of successful news requests, failed requests made with a valid key, and allowance stops, and whether the account has been recorded since it was created. For an account older than the recording, earlier requests were never counted and the first recorded time is not its first request. It is not a list of requests and holds no request content.
Usage
Counts of responses and bytes per account for the current window. No record of which articles or contracts you read.
Trial and plan dates
When a trial started and ends, and when paid Builder time ends.
Connections
For each program you approved: its name, the permissions you granted, a hash of its management credential, and when it was created, last used, first read news, expires and was revoked.
Pairing requests
The name and permissions a program asked for, hashes of the secrets it generated, the code shown to you, timestamps and the outcome.
Account change record
For changes such as creating or revoking a key or connection: whether the browser or a connection did it, the action, its target, the time, the result and the request ID. Kept for a limited number of rows and days; the installed numbers are not published yet. Entries past that age are removed when later account changes are recorded, not on a clock, so with no later activity an old entry can remain.
Billing
The payment provider's customer and subscription identifiers, subscription status, paid-through date, checkout attempts, identifiers of provider events already processed, and for each paid invoice its identifier, period, amount and currency. No card details and no email address.
Operator alert delivery
Where enabled, separate private records identify account milestones and billing events, whether a notice was sent, pending attempts and its delivery receipt. They are used to retry notices and avoid ordinary duplicate sends. They contain no API keys or request content.
Network address
Short-window request limits count by network address in memory only. Limits on starting pairings store a keyed hash of the address group (an IPv4 address, or an IPv6 /64) with a private random salt, not the address itself, until the counter expires and is swept.

How a key travels

Stored as a hash only. The service keeps a SHA-256 hash of each key and never the key. It cannot show you a key again.

Sent on every request. Your program sends the key itself as a bearer credential in the Authorization header of each request, over HTTPS. The request passes through the network edge (Cloudflare) to the API host (DigitalOcean), where the service hashes the key to look it up. So the key is seen in transit by the edge and by the service each time it is used, even though it is not stored.

Created two ways. A key made in the account page is generated by the service and shown once in that response. A key made by pairing is generated by the program on your own machine; pairing registers only hashes of the feed key and any management credential. Throughline creates a separate device code for checking approval and stores its hash. Approval returns details of the connection and key. The throughline command keeps the credentials in private files on your machine.

Other parties

Cloudflare
Network edge in front of api.throughline.markets. Every API and account request passes through it, including network address and headers.
DigitalOcean
Hosts the API server and the account database.
Vercel
Hosts this website. These pages are static, set no cookies of their own and load no analytics script. The home page loads one first-party script that copies the setup line when you press its button; it sends and keeps nothing.
Google Fonts
These pages load fonts from Google, so your browser makes a request to Google when it opens them.
Clerk, Google and GitHub
Sign-in is handled by Clerk using Google or GitHub. Your email address and profile are held by them under their own terms. The service receives a signed session token and checks it, including that the email is verified. The account page shows your email address in your browser from that session.
Stripe
Checkout and the billing portal are Stripe pages. Card details go to Stripe and never reach the service.
Telegram
When operator alerts are enabled, a private Telegram chat receives shortened opaque account references, hashed event references, account milestones, payment amounts and aggregate conversion counts. It receives no customer names, email addresses, API credentials, request bodies or payment-provider object identifiers. Telegram handles these notices under its own terms.

What each of these records about a request is under its own terms and is not described here. The feed itself is about news articles and markets and contains nothing about customers. Customer data is not sold.

Recovery copies, retention and requests

Encrypted recovery copies. Encrypted copies of the account database are made for recovery and kept off the server by the operator. Earlier copies are kept, so a row removed from the running database, including an expired change-record entry, can remain in a copy.

Retention. No fixed retention period is set for an account. Revoked key records and paid records are kept. Revoked connection records can be removed after 30 days. Keys revoked with a connection stay revoked.

Access and deletion. There is no self-service route. Write to access@throughline.markets to reach the operator. See also the terms and contact page.