Privacy

Built for users who care where their data goes.

TokenPeep is designed as a local-first Windows utility. It does not include TokenPeep telemetry, advertising trackers, product analytics, crash reporting, a TokenPeep account system, or a developer-controlled hosted backend.

What TokenPeep reads

TokenPeep reads your existing local Codex login state on your computer so it can request Codex usage metadata directly from ChatGPT/Codex. It reads the local Codex auth file only to extract the temporary access token and account ID needed for that request.

When the responsive activity indicator is enabled, TokenPeep may scan recent local Codex session files for usage metadata and token-count activity. Those files may contain Codex conversation data, but TokenPeep is designed only to extract sanitized usage metadata.

TokenPeep does not ask for an OpenAI API key, does not call OpenAI model-generation APIs, and does not generate completions. Checking usage through TokenPeep does not spend OpenAI API tokens.

What TokenPeep stores

TokenPeep stores local settings and sanitized last-known usage values, such as display preferences, refresh state, 5-hour and weekly percentages, reset times, alert settings, and safe status text.

What TokenPeep is designed not to store

• Access tokens or refresh tokens
• Auth headers or cookies
• Account IDs, user IDs, or email addresses
• Raw auth files, raw backend responses, or raw session files
• Prompts, conversation text, or private code

Network access

Fresh usage readings are requested directly from your computer to ChatGPT/OpenAI. TokenPeep does not send those readings to a TokenPeep server.

Independent utility

TokenPeep is an independent utility and is not affiliated with, endorsed by, or sponsored by OpenAI. Codex and OpenAI are trademarks of OpenAI.