Legal · Last updated 11 November 2026
Privacy policy
What personal data we process, why, where it is stored and for how long. Written for the EU General Data Protection Regulation (GDPR) and the Austrian Data Protection Act (DSG).
Who is responsible
Jan Beck, Graz, Austria, is the controller for the personal data described on this page. Write through the contact form or through support inside the app. No data protection officer is appointed, because the law does not require one for a business of this size and kind.
Two roles
We decide what happens with the data of people who visit our websites, sign up, pay or write to us. This page covers that data.
Your organization decides what happens with the data it puts into Token Controller: its members, what its agents send (received records, messages and activities), its estimates, plans and shares, its bills and tickets. Your organization is the controller and we process that data on its behalf under the data processing agreement. If you are a member and want to see, fix or delete that data, ask your organization's org manager first. We help them answer.
If your organization runs Token Controller on its own servers, no data reaches us at all. The same holds for the CLI when it is not connected to an instance.
Our websites
tokencontroller.com, docs.tokencontroller.com and status.tokencontroller.com are delivered by Cloudflare. To send you a page, Cloudflare processes your IP address, the address of the page, the time and what your browser tells about itself. Cloudflare uses this to deliver the page and to block attacks, and keeps it for a short time under its own rules. We keep no access logs of our own. Legal basis: our legitimate interest in a working, secure website (Art. 6 (1) (f) GDPR).
To count visits we use Cloudflare Web Analytics. A small script from Cloudflare reports the page you opened, the page you came from, your browser, device type and country, and how fast the page loaded. It sets no cookies, stores nothing in your browser and does not recognize you on a later visit or on other websites. We see only totals, such as page views per day. Legal basis: our legitimate interest in knowing which pages help people (Art. 6 (1) (f) GDPR).
Our websites have an assistant that answers questions about Token Controller from our docs. When you ask it something, your question and the page you asked it on go to our customer relations app and to Anthropic, which writes the answer. We keep the question and the answer for 90 days, to find gaps in the docs. The app uses your IP address only in memory, for a short time, to limit how many questions, messages and sign-ups one visitor can send through the assistant and the forms, and never stores it. Please do not type personal data into the assistant. Legal basis: our legitimate interest in answering visitors' questions (Art. 6 (1) (f) GDPR).
The websites set no cookies, store nothing in your browser for the assistant or the forms, and load no other tracking. Fonts and pictures come from our own domain. Links to LinkedIn and GitHub are plain links: those sites get data only when you click them.
Your account
When you sign up we store your name, your email address, your organization and your role. We need them to give you the service (Art. 6 (1) (b) GDPR).
You sign in with a link sent to your email address. Organizations on the Enterprise plan can sign in through their own identity provider instead. After sign-in the app sets one cookie that keeps you signed in. It is needed for the service to work, so it needs no consent (§ 165 (3) TKG 2021).
For security we log sign-ins and important account actions with the IP address and the time, and keep these logs for 30 days (Art. 6 (1) (f) GDPR).
We keep one record per customer organization. It brings together the plan, the members, their messages to us, their feedback reports and notes from calls, so whoever answers knows the history. Legal basis: our legitimate interest in looking after our customers (Art. 6 (1) (f) GDPR).
Usage data your organization sends
Agents, the Claude Code mod, the CLI, the GitHub Action and telemetry send usage data to the service. The service first stores what it received, as it arrived (a received record), and then reads messages and activities from it. A message is one model call: which person, agent and model, the provider when known, when, how many tokens of each kind, a short summary, tags such as a ticket or a team, and signals such as a branch, a repository name or how the agent was signed in. An activity is anything else an agent reports, such as a tool run or a count of commits, with its signals. The service adds the cost from the price table. The full list is on the Security and privacy page. Your organization may also connect bills from AI providers and tickets from Jira, Azure DevOps or GitHub Issues, and records estimates, plans and shares. Corrections to messages, tags and bills are new entries in an event log: nothing there is edited or deleted in place, and a reversal is itself recorded.
Content text is off by default. Content text is prompts, responses, tool output and file contents. Nothing we ship sends it unless your organization switches it on, and the service removes it on arrival unless your organization switched keeping it on in its settings. Some agents send it in their telemetry by default; it is removed all the same. Only an org manager can switch it on. Kept content text is stored only in the received records, is shown on no screen, and is deleted with them.
Received records are kept for 400 days and then deleted. Org managers can delete them earlier, one by one, up to a date or all at once; the messages and activities read from them stay.
We process this data for your organization, as its processor (Art. 28 GDPR). Who in your organization sees what follows the grants.
Payment
The Team plan is paid by card through Stripe. Stripe Payments Europe, Limited, Dublin, Ireland, processes the card and is responsible for that data under its own privacy policy. We receive the billing name and address, a VAT number if you give one, the card brand and the last four digits. We never see the full card number.
Legal basis: the contract (Art. 6 (1) (b) GDPR) and our duty to keep accounting records (Art. 6 (1) (c) GDPR, § 132 BAO).
Messages and email
When you write through the contact form, to support inside the app, by email, or by replying to an email from us, we store your message, your name and the address you want an answer at, to answer you (Art. 6 (1) (b) or (f) GDPR).
An AI assistant answers from our docs first: Anthropic's Claude reads the conversation and writes the answer, and every answer says it was written by an AI assistant. What the docs do not answer goes to Jan Beck, who answers in person. If an answer does not help, reply and Jan Beck answers. The assistant decides nothing about you. Notices that a message is waiting carry a link, never the message itself.
The service sends sign-in links, reminders to submit and notices about your account. While a new organization sets up, its org managers also get at most one short email for each first step it has not taken after a few days: first message, first submit, first bill and first cutoff. None comes after the first cutoff. These are part of the service. The newsletter goes out only if you subscribed and confirmed by email (Art. 6 (1) (a) GDPR). Every newsletter has a link to unsubscribe with one click.
Feedback reports
The feedback button in the app sends us a report: a bug, an idea or a question, what you write, and diagnostics. The diagnostics are the page you were on, without the part of its address after a question mark, the app version, your browser, the screen size, the last error messages the app showed and the IDs of the last requests. A screenshot comes along only if you turn it on, and you see it first and can blur any part of it. The full list is on the Security and privacy page.
We read the report with your name, email address and organization, to answer it and fix what it reports (Art. 6 (1) (b) GDPR). When it is answered or fixed, you get an email with a link to the app, never the answer itself. If your organization runs Token Controller on its own servers, reports go to its own org managers and never reach us.
Error reports
When the service fails, it sends a technical error report to Sentry, in Sentry's EU data region. We set it up to strip names, email addresses and IP addresses from these reports. Legal basis: our legitimate interest in a service that works (Art. 6 (1) (f) GDPR).
Who processes data for us
We use these companies. Each is bound by a data processing agreement.
| Company | What it does for us | Where |
|---|---|---|
| Microsoft Ireland Operations Limited, Dublin, Ireland | Hosting of the service, database and backups (Microsoft Azure) | EU: Austria East (Vienna); backup copy in a second EU region |
| Cloudflare, Inc., San Francisco, USA | Websites, DNS, network protection, sending and receiving email (sign-in links, reminders, support), and our customer relations app: storing support messages, the newsletter list, questions to the assistant on our websites, feedback reports and the customer record | Global network; stored data in the EU (Cloudflare's EU jurisdiction); EU-U.S. Data Privacy Framework and Standard Contractual Clauses |
| Anthropic, PBC, San Francisco, USA | Writing answers from our docs to support messages and to questions on our websites (Claude). It may not train models on them. | USA; EU Standard Contractual Clauses |
| Plus Five Five, Inc. (Resend), San Francisco, USA | Sending the newsletter | USA; EU-U.S. Data Privacy Framework and Standard Contractual Clauses |
| Functional Software, Inc. (Sentry), San Francisco, USA | Error reports from the service | EU data region (Frankfurt); EU-U.S. Data Privacy Framework and Standard Contractual Clauses |
Where a company is based outside the EU, transfers rest on the EU-U.S. Data Privacy Framework or on the EU Standard Contractual Clauses (Art. 45 and 46 GDPR). We do not sell personal data, and we share it with nobody else unless the law makes us.
Where data is stored
The hosted service, its database and its backups run in Microsoft Azure in Austria East (Vienna), with a backup copy in a second EU region.
Support messages, the newsletter list, questions to the assistant, feedback reports and the customer record are kept by our customer relations app, which runs at Cloudflare and stores them in Cloudflare's EU jurisdiction, with a nightly copy and point-in-time restore for 30 days. Data we delete is gone from these copies within another 35 days. Email sent to us waits at Cloudflare in the EU until this app has taken it, and is deleted there after 90 days at the latest.
Test systems use made-up sample data, never customer data.
An Enterprise plan instance runs in the region its organization chooses, under its own contract.
How long we keep data
| Data | Kept for |
|---|---|
| Account and organization data | As long as the account exists. After deletion, 30 days, then gone from backups within another 35 days. |
| Invoices and payment records | 7 years, as Austrian tax law requires (§ 132 BAO). |
| Messages to support, replies to our emails and the contact form | 2 years after the last message. The original email, with its attachments, 90 days; its text stays with the conversation. |
| Questions to the assistant on our websites, and its answers | 90 days. |
| Feedback reports | 2 years after the last change. A screenshot, 90 days. |
| Notes about a customer organization | As long as its account exists. |
| Received records your organization's agents send (with content text only if your organization keeps it) | 400 days, unless an org manager deletes them earlier. Then gone from backups within another 35 days. |
| Messages, activities, tags, bills, estimates and plans of your organization | As long as the organization exists. After it is deleted, 30 days, then gone from backups within another 35 days. |
| Security logs | 30 days. |
| Error reports | 90 days. |
| Newsletter subscription | Until you unsubscribe; unsubscribing deletes your address. |
| Newsletter sign-up not confirmed | 7 days. |
Your rights
You can ask us to show you the data we hold about you, to correct it, to delete it, to limit its use, or to hand it over in a common format. You can object to use based on our legitimate interest, and withdraw a consent at any time with effect for the future. Use the contact form or support inside the app. We answer within one month.
You can also complain to the Austrian Data Protection Authority (Datenschutzbehörde), Barichgasse 40–42, 1030 Vienna, dsb.gv.at, or to the authority where you live or work.
Other points
You need to give your name and email address to use the service. Everything else is optional.
We make no decisions about people by automated means. Rules in the service assign work to features, and the service computes estimates from the organization's own past data, with a classifier when the organization's instance is set up with one. None of this is a decision about a person, and no decision with legal or similarly significant effect on a person is made by automated means.
When this page changes, the date at the top changes. We tell customers about important changes inside the app.