Privacy policy
AI Token Viewer 0.5.1.1 · Updated: 2026-09-24
Scope and contact
This policy covers the AI Token Viewer plugin and its product and support website, provided by PuPuPu. For data questions or deletion requests, email support@pupupu.net. Do not send credential files, API keys, cookies, or conversation contents.
Data and purpose
- Codex: The account email and plan are shown in settings to identify the account for each button and kept in process memory. Usage limits and credit balances are retrieved for the key display. Codex itself stores credentials under
.ai-token-viewer/accounts/in your home directory. The plugin does not read credential file contents or copy them into Stream Deck settings. - Cursor Teams: The target member email you enter is saved in the button's Stream Deck settings and sent to the official Cursor Teams Admin API to find that member. The Admin API key is read from an environment variable, not saved in Stream Deck settings.
- Claude Code: The bridge saves only 5-hour and 7-day usage percentages, reset times, update time, and schema version to a local JSON file. It does not save conversations, working directories, or transcript paths.
- Gemini CLI / Gemini API: The bridge saves only the reported token count, provider ID, and update time to local JSON. It does not save conversation content.
- Settings: The selected service, display preferences, consent state, and configured file paths are stored in Stream Deck button settings. Paths may contain your username. Exported Stream Deck profiles may include these settings.
- Diagnostics: The official Stream Deck SDK may create local logs. This plugin's update-failure messages do not include credentials or conversation contents.
Consent and connections
The settings panel presents this explanation and policy. The plugin does not retrieve real usage data until you explicitly check the data-use consent box. Demo data remains available without consent. Revoking consent stops future retrieval and clears the displayed data and in-memory cache. Sign-out and local deletion remain available after revocation.
The plugin has no analytics, advertising, or remote telemetry. It communicates with Stream Deck over loopback. Codex CLI contacts OpenAI for sign-in and usage limits. Cursor Teams requests send the configured member email and Admin API key to the official Cursor API. Claude and Gemini integrations read local hooks or previously obtained response JSON. The settings UI loads no remote scripts or fonts.
Retention and deletion
Usage snapshots and Codex account email/plan are kept only in process memory and disappear when the plugin exits. Stream Deck settings remain until you remove the button or profile. Delete exported profile copies separately. Deleting a button alone does not remove Codex credentials or bridge JSON files.
- Uncheck data-use consent in settings to stop new retrieval.
- Use Sign out of this button on every Codex button. You may then remove its unused account folder under
.ai-token-viewer/accounts/. Never send credential files to others. - Restore Claude's previous
statusLinefrom backup. Remove only the GeminiAfterModelhook namedai-token-viewer-usage. Remove unused bridge scripts and JSON files under.ai-token-viewer. - Remove the Stream Deck button, exported profiles, and plugin if no longer needed. Remove the Cursor Admin API key environment variable if unused.
For help with deletion, or to request deletion of information sent to the publisher in a support inquiry, email support@pupupu.net. The publisher cannot remotely delete files or Stream Deck settings on your device. Support email is used to reply to and process your request.
Website
The static product and support pages contain no publisher-added analytics, advertising, cookie-setting scripts, or external fonts. The web host may process standard access logs. The hosting provider and log-retention terms must be confirmed and added to this page when the site is deployed. Support messages reach the publisher through the email provider.