Privacy policy — TokenTriage

1. Who we are

INFEROPS LLC (“InferOps”, “we”, “us”) is a limited liability company formed in Washington, United States. We publish TokenTriage and operate this website at tokentriage.com. We are the controller of the personal data described below.

Questions, requests, or complaints: [email protected].

2. What this policy does not cover

The TokenTriage software you run yourself does not transmit anything to us. You run it on your own infrastructure, it talks to the model providers you configure, and the prompts, responses, logs, and cost records it produces stay on systems you control. The software you run yourself has no telemetry, no usage reporting, no activation check, and no update ping. We cannot see that traffic, and for a self-hosted deployment we have no mechanism that would let us.

So if you run TokenTriage on your own infrastructure and never visit this website, we hold no personal data about you at all. Everything below concerns visitors to the website.

The hosted service is the other case, and this policy is not the document that covers it. TokenTriage operated by us rather than by you necessarily involves processing that a self-hosted deployment keeps entirely on your side — account details, the traffic a workspace sends through the gateway, and the records that produce a bill. It is not open yet.

When it opens, that processing is described in the hosted service’s own privacy notice: a versioned document, accepted at signup alongside the hosted agreement, and the authority on the specifics. It does not replace this policy and this policy does not absorb it. The two cover different processing, they are revised on different schedules, and this one continues to govern your visits to this website — which is why the sentence above scopes itself to the software you run yourself rather than to “TokenTriage” generally.

3. What we collect, and why

Server logs

Our host processes the technical details every web request necessarily carries: IP address, browser user-agent, the URL requested, and a coarse location derived from the IP. These are used to serve the page, to keep the site available, and to identify abuse. Our legal basis is our legitimate interest in operating and securing the site.

Analytics — off unless you switch it on

We use product analytics to see which pages get read and which links get clicked. Two things are worth being precise about:

By default, no identifier is stored on your device at all. Analytics runs without writing a cookie or any other persistent storage, which means we cannot recognise you across page loads or between visits. We do not ask you to accept anything, and there is no prompt to dismiss — the private setting is simply the one you get. You can turn the identifier on yourself if you want to (see §6); nothing switches it on for you.
Session recording is switched off. We do not record your screen, your mouse movement, your keystrokes, or the contents of any form. We do not run advertising trackers, and there are no ad networks on this site.

Where analytics storage requires consent, our legal basis is that consent, which you may withdraw at any time (see §6).

Things you send us on purpose

Mailing list: If you submit the launch-updates form, we receive the email address you typed and your subscription status. We use it to send project updates and nothing else. Every message carries an unsubscribe link. Legal basis: consent.
Demo bookings: If you open the scheduler and book a time, we receive your name, email address, chosen slot and time zone, and anything you write in the booking form. We use it to hold and attend the meeting. Legal basis: taking steps at your request prior to entering into a contract.
Email: If you write to us, we hold your message and address for as long as needed to deal with it and to keep a record of the correspondence.

4. Who else sees it

We use a small number of service providers, and we publish the complete list — including what each one receives and where it processes data — on the subprocessors page. The browser-visible part of that list is reconciled against this site’s Content-Security-Policy by a build check, so a third-party script cannot be added to this website without being named there. That check is structurally blind to a provider our servers talk to rather than your browser — the hosted service’s infrastructure and mail providers among them — and the subprocessors page says which of its rows rest on the check and which are declared by hand.

As of this policy’s effective date, the recipients are Cloudflare, Inc. (which serves the site), and PostHog, Inc., Cal.com, Inc., Buttondown, LLC (each of which only receives data in the circumstances described above).

We do not sell your personal information, and we do not share it for cross-context behavioural advertising — as those terms are defined under California law. We have never done so. We may disclose data if we are legally required to, or to establish or defend a legal claim.

5. How long we keep it

Analytics events: 12 months, which is the retention period of the analytics plan we are on.
Mailing list: Until you unsubscribe, plus a record of the unsubscribe so we do not email you again.
Demo bookings: For the life of the booking and our record of the meeting.
Server logs: For the short operational period our host retains them.
Email correspondence: As long as the matter is live, and afterwards where we need a record of it.

6. Cookies and similar storage

A cookie is a small file a site stores on your device; local storage is the same idea with a different mechanism. This site uses both sparingly:

Your choices. Your light/dark theme preference, and your analytics setting if you have changed it from the default. These are stored only so the site can honour a choice you made — otherwise it would forget it on every page.
Analytics. Only if you turn it on yourself. Off is the default, and we never change it for you. Turning it on is what lets us tell one returning reader from ten new ones.
The scheduler. If you open the demo booking embed, the scheduler may set its own storage. It does not load at all unless you open it.

The control is in the site footer, on every page, and it works in both directions: turn analytics on if you are happy to be counted properly, and turn it off again whenever you like. Turning it off stops the identifier being stored, removes the one already there, and stops us being able to recognise you between page loads. You can also clear this site’s storage in your browser settings, which returns everything to the default.

7. Where your data goes

We are a United States company and our service providers process data in the United States. If you are in the European Economic Area, the United Kingdom, or Switzerland, this means your data is transferred outside your home jurisdiction. Where that transfer requires a safeguard, we rely on the Standard Contractual Clauses or an equivalent mechanism in our agreements with the providers named on the subprocessors page.

8. Your rights

Depending on where you live, you have some or all of the following rights over the personal data we hold about you:

Access — ask what we hold and get a copy.
Correction — have inaccurate data fixed.
Deletion — ask us to erase it.
Portability — receive it in a machine-readable form.
Objection and restriction — object to processing based on legitimate interests, or ask us to pause it.
Withdraw consent — at any time, without affecting processing already carried out.
Non-discrimination — we will not treat you differently for exercising any of these.

To exercise any of them, write to [email protected]. We may need to ask you for information to confirm who you are, and we will only use what you send for that purpose. You may use an authorised agent where your local law provides for one.

What happens next is written down. The data-requests page is the procedure we actually follow: how we check the request is yours without asking for identity documents we would then be holding, the one-month deadline we work to and when it starts, the order we do things in — and, because it is the part that decides whether an answer is any use to you, the things we cannot do. The largest of those is that we store no identifier for analytics by default, so for most readers we hold no key that would let us find their events at all.

If you are in the EEA or UK and you think we have handled your data badly, you may complain to your national supervisory authority. We would rather you told us first, but that is your right and not conditional on contacting us.

9. Children

This site is aimed at software engineers evaluating infrastructure. It is not directed at children, and we do not knowingly collect data from anyone under 16. If you believe a child has sent us personal data, write to us and we will delete it.

10. Security

How we protect what we hold — and the architectural reason there is so little of it — is set out on the security page. If you have found a vulnerability, that page tells you how to report it.

11. Changes

When this policy changes materially we will update the effective date at the top and describe what changed. Because all four of our trust documents share one effective date, a change to any of them re-dates the set — which makes a quiet edit to one of them visible.

The hosted service’s agreement and privacy notice are versioned separately, and deliberately so: you accept a named version of those at signup and we can tell you afterwards which one you accepted. This page carries no such record, because a website policy is not something anyone accepts — which is exactly why the hosted processing is documented there rather than here.

12. Contact

INFEROPS LLC, Washington, United States.
[email protected]