Tokenrunway — Privacy

Nothing. The app makes no requests to us, contains no analytics or crash-reporting SDKs, and has no sign-in of its own.

Only to the providers you add, to read your own usage, directly from your computer. Depending on the accounts you set up, that is Anthropic (api.anthropic.com), OpenAI (chatgpt.com and api.openai.com), Amazon Web Services (through the AWS CLI and the profile you pick), GitHub for Copilot (api.github.com), Cursor (cursor.com), Google for Gemini (cloudcode-pa.googleapis.com) and xAI for Grok (grok.com and api.x.ai). Each request carries only the login or key for that account. What those providers do with requests made to their own services is covered by their privacy policies, not this one.

Some of these are the endpoints the providers' own apps and CLIs use, not documented public APIs. Tokenrunway calls them only for your own account, at an unhurried rate, and identifies itself honestly.

For Cursor and Grok you can sign in inside Tokenrunway. That opens the provider's own sign-in page in a separate window, with its own private storage for each account and no access to the rest of the app. Your password goes only to the provider. When you're signed in, Tokenrunway keeps just the session cookie it needs to read your usage, in your credential store, and closes the window.

The app checks GitHub (api.github.com) about once a day for a newer release, so it can show what's new and offer to update. That request sends nothing about you. Updates are downloaded from GitHub only when you choose to install one, and are verified before they are installed. You can turn the check off in Settings.

If you connect a Rattleboard, alerts and an “AI runway” card are sent to that board: on this computer, or to the board's address on your local network. Only window names, percentages and times are sent, never prompts, costs or keys. Messages to a board on your network travel as plain HTTP, so anyone else on the same network could read them in transit.

When you ask your admin for more allowance, Tokenrunway writes the message and opens it in your own email, Slack or Teams. Nothing is sent until you send it there.

To show your stats, Tokenrunway reads the session logs that Claude Code, Codex and opencode already keep on your computer. It reads them locally to count tokens and to work out the kind of work (building, bug fixing, discovery and so on). From those logs it keeps only counts, model names, project folders, times and categories. Your prompts and the agents' replies are never stored, and never leave your computer.

To read your allowances, the app uses the Claude Code, Codex, GitHub CLI, Gemini CLI, Cursor and AWS logins you already have, where those tools keep them, without changing them. On a Mac, reading Claude Code's keychain entry asks your permission once.

Your accounts list, settings, usage history and stats are stored in the app's own data folder and never leave your computer. Keys you paste in, such as an API admin key or a Rattleboard key, and the session cookies from signing in inside Tokenrunway, are kept only in the operating system's credential store: the macOS Keychain, Windows Credential Manager, or the Linux Secret Service (GNOME Keyring or KWallet). Never in a file, never in a log. Logins from other tools (Claude Code, Codex, the GitHub and Gemini CLIs, Cursor) stay where those tools keep them; Tokenrunway reads them when it checks your usage and does not copy them. A login or key is sent only to the provider it belongs to.

To remove everything, remove your accounts in the app, then uninstall it and delete its data folder.

Tokenrunway is not affiliated with or endorsed by Anthropic, OpenAI, Amazon, xAI, Google, GitHub or Cursor.

This page is part of iokig.com, whose site-wide privacy policy applies. Questions go through support.