Token Controller
Use cases Integrations Estimates Pricing
Sign in Start free
Menu
Use casesIntegrationsEstimatesPricingSign in

Legal · Last updated 11 November 2026

Data processing agreement

How we process the data your organization puts into Token Controller on its behalf, under Article 28 GDPR.

  1. Parties and scope
  2. What is processed
  3. Instructions
  4. Confidentiality
  5. Security
  6. Subprocessors
  7. Transfers outside the EU
  8. Requests from data subjects
  9. Further help
  10. Personal data breaches
  11. Deletion at the end
  12. Proof and audits
  13. Liability and law
  14. Annex 1: Technical and organizational measures
  15. Annex 2: Subprocessors

Parties and scope

This agreement is between the organization that uses Token Controller (the customer, controller) and Jan Beck, Graz, Austria (the processor). It is part of the terms and applies whenever the customer uses the hosted service, on Solo, on the Team plan or on a hosted Enterprise plan instance. By accepting the terms the customer concludes this agreement. A countersigned copy is available on request.

It meets Article 28 GDPR. Where it differs from the terms, this agreement wins on data protection.

What is processed

Subject and purposeProviding Token Controller: receiving and storing what the customer's agents send, reading messages and activities from it, matching them with bills and tickets, and reporting cost per person, ticket and project.
NatureCollecting, storing, organizing, matching, reporting, exporting and deleting.
DurationThe term of the contract, plus the deletion period in section 11. Received records are kept for 400 days at most, see section 8.
Data subjectsThe customer's members (employees, contractors), people named in synced tickets, and the customer's contacts.
Personal dataNames, email addresses, grants and tags of members; received records (what the customer's agents sent, as it arrived, without content text unless the customer keeps it); messages (agent harness, model, provider when known, agent name, start and end time, token counts by kind, cost from the price table, signals such as branch, repository, sign-in and ticket keys, summary, tags) and activities (a kind such as a tool run, the session, the time and signals); estimates, plans and shares, and the organization's own price table rows, as listed on the Security and privacy page; ticket keys, titles and states from synced trackers; sign-in and security logs (IP address, time); support messages.
Content textPrompts, responses, tool output and file contents. Removed on arrival unless the customer switches keeping it on in the organization's settings. When kept, it is stored only in the received records, shown on no screen, and deleted with them. It may then hold any personal data the customer's members gave their agents.
Special categoriesNone intended. The customer does not send data under Article 9 or 10 GDPR, and keeps content text switched off where it might hold such data.

Instructions

The processor processes the data only on the customer's documented instructions. These are the terms, this agreement and the settings the customer makes in the app. The processor tells the customer at once if it thinks an instruction breaks data protection law. It processes the data otherwise only where EU or Austrian law requires, and tells the customer first unless that law forbids it.

Confidentiality

Only the processor has access to the customer's data in production. Anyone who may get access in future is bound to confidentiality first, under § 6 DSG.

Security

The processor takes the technical and organizational measures in Annex 1 (Article 32 GDPR). The processor may change them when the change keeps the same level of protection or raises it.

Subprocessors

The customer agrees to the subprocessors in Annex 2. The processor tells the customer at least 30 days before adding or replacing one, inside the app and on this page. The customer may object for reasons of data protection. If the two cannot solve the objection, the customer may end the contract before the change, and gets back what it paid for the time after.

The processor binds every subprocessor by contract to the same data protection duties as in this agreement, and stays responsible for them.

Transfers outside the EU

Data leaves the EU or EEA only under Chapter V GDPR: an adequacy decision, including the EU-U.S. Data Privacy Framework, or the EU Standard Contractual Clauses.

Requests from data subjects

Org managers can see, export and correct data in the app; a correction is a new entry that reverses the old one. They can delete received records, one by one, up to a date or all at once, and remove a member, and the organization can be deleted as a whole. Where that is not enough, the processor helps the customer answer requests under Articles 15 to 22 GDPR. If a data subject writes to the processor directly, the processor passes the request to the customer.

Further help

The processor helps the customer with security, breach notifications, data protection impact assessments and prior consultation (Articles 32 to 36 GDPR), with the information available to it.

Personal data breaches

The processor tells the customer about a personal data breach without undue delay, and no later than 48 hours after learning of it. It gives what Article 33 (3) GDPR asks for as far as known, adds more as it learns it, and takes steps to limit the harm.

Deletion at the end

The customer can export its data at any time, as CSV or as a full raw export. After the contract ends, the processor deletes the customer's data within 30 days, and it is gone from backups within another 35 days, unless the law requires keeping it.

Proof and audits

The processor gives the customer the information needed to show that it keeps this agreement. The customer may audit once a year, or after a breach, with 30 days' notice, during business hours, at its own cost, itself or through an auditor bound to confidentiality. The customer may accept a written report instead.

Liability and law

Liability follows Article 82 GDPR and, beyond it, the terms. Austrian law applies. The competent court in Graz, Austria, decides all disputes.

Annex 1: Technical and organizational measures

Where the data lives

  • Microsoft Azure data centers in Austria East (Vienna), certified to ISO/IEC 27001. A backup copy is kept in a second EU region.
  • Support messages and feedback reports from the customer's members, and our record of the customer, are stored at Cloudflare in Cloudflare's EU jurisdiction, with a nightly copy and point-in-time restore for 30 days.
  • An Enterprise plan instance has its own service and its own database, in the region the customer chooses.

Encryption

  • All traffic uses TLS 1.2 or newer.
  • The database and backups are encrypted at rest (AES-256). What is stored at Cloudflare is encrypted at rest too.

Access

  • Only the processor has access to production, with multi-factor authentication and personal accounts. There are no shared accounts.
  • Every record belongs to one organization, and every request is limited to the signed-in member's organization.
  • Inside an organization, grants decide who sees what: a grant gives a person a capability on a filter (for example view on one project); an org manager has every capability on the whole organization.
  • API tokens can be revoked at any time.

Less data

  • Content text is off by default: the local tools do not send it, and every usage endpoint removes it on arrival unless the customer switches keeping it on.
  • Received records are deleted after 400 days, or earlier when an org manager deletes them.
  • Test systems use made-up sample data, never customer data.

Availability

  • Automatic backups with point-in-time restore, and a nightly copy in a second EU region. Restores are tested every quarter.
  • At Cloudflare: point-in-time restore for 30 days and a nightly copy, kept 35 days.
  • Monitoring of errors, uptime and background jobs, with alerts to the processor.

Changes and records

  • All code is in version control and passes automated tests before release. The product's code is open source.
  • Sign-ins and important account actions are logged for 30 days. The Enterprise plan adds an audit log.

Annex 2: Subprocessors

CompanyWhat it does for usWhere
Microsoft Ireland Operations Limited, Dublin, IrelandHosting of the service, database and backups (Microsoft Azure)EU: Austria East (Vienna); backup copy in a second EU region
Cloudflare, Inc., San Francisco, USAWebsites, 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 recordGlobal network; stored data in the EU (Cloudflare's EU jurisdiction); EU-U.S. Data Privacy Framework and Standard Contractual Clauses
Functional Software, Inc. (Sentry), San Francisco, USAError reports from the serviceEU data region (Frankfurt); EU-U.S. Data Privacy Framework and Standard Contractual Clauses

Stripe processes card payments as its own controller, outside this agreement. It receives no data from inside Token Controller.

Token Controller

Cost accounting and management control for AI agents. Made in Graz.

Use cases

  • Cost per client
  • Bill reconciliation
  • Project plans
  • Cost per person
  • Quotes from past work
  • Non-coding agents
  • Self-hosting

Integrations

  • Claude Code
  • Codex CLI
  • Cursor
  • Anthropic
  • OpenAI
  • Jira Cloud
  • All integrations

Docs

  • Overview
  • How it works
  • Self-hosting
  • API reference
  • Security

Company

  • About
  • Blog
  • Newsletter
  • Open source
  • Status
  • Contact
  • Imprint
  • Privacy
  • Terms
  • Data processing agreement
Service status · v1.0.0 © 2026 Jan Beck · Graz, Austria · Data hosted in the EU