Privacy Policy

Scope

Filament Labs develops Codex Usage and Resets (CUAR). This policy covers the local CUAR plugin, its project website, and messages sent to Filament Labs about CUAR.

Data processed and purposes

CUAR runs on your machine. When invoked, it starts your local Codex App Server and performs one read-only account/rateLimits/read request. It processes Codex usage percentages, usage-window duration, Scheduled Reset times, Banked Reset counts and expirations, the report observation time, and the time zone used to display results. These facts support usage reporting, Linear Pace calculations, Projected Exhaustion, and comparisons that can indicate an unexpected reset.

Normalization, calculations, and time-zone conversion happen locally. CUAR does not operate a hosted usage service or send plugin telemetry to Filament Labs. It does not read Codex authentication files, inspect session logs, or persist reset-credit identifiers, account identifiers, or raw App Server responses.

Local storage, retention, and controls

CUAR keeps one sanitized local snapshot containing the observation time, Scheduled Reset time, whole used percentage, and Banked Reset count. It may also keep one derived reset observation containing its observation window, prior Scheduled Reset, and source classification. These records support comparisons across invocations. Records are replaced rather than accumulated.

On each successful report, CUAR discards records older than eight days. It does not run a background deletion timer. If you stop using CUAR, the file and any retained records can remain on your machine until you delete it. A later successful report prunes old records while leaving the ledger file in place. A report that cannot form a trustworthy comparison clears the comparison chain.

The default ledger location is ~/Library/Caches/CUAR/reset-ledger.json on macOS, $XDG_CACHE_HOME/cuar/reset-ledger.json or ~/.cache/cuar/reset-ledger.json on Linux, and %LOCALAPPDATA%\CUAR\Cache\reset-ledger.json on Windows. You can delete the file to clear these records. A later successful invocation creates a new baseline. CUAR never uploads this file to Filament Labs.

Raw responses are processed in memory rather than saved by CUAR. That process memory is released when the CLI exits. Facts returned to your conversation can remain in the conversation under the host's data controls.

Recipients and host services

The plugin does not transmit usage data to Filament Labs. Your local Codex App Server communicates with OpenAI to obtain your account's usage data. When the skill reports results in a conversation, OpenAI may process the normalized facts under your account settings and its privacy policy. OpenAI controls retention of its service data and conversations. Use the data controls available in your OpenAI account to manage that data.

CUAR can request approved host execution when a task sandbox blocks its required local state or network access. It cannot grant itself permissions or change your sandbox policy, authentication, or Codex configuration. You control whether the host permits the command.

Diagnostics

CUAR exposes sanitized error messages. Its doctor report provides compatibility and version information without usage percentages, reset timestamps, reset-credit details, account identifiers, email addresses, authentication paths, or tokens.

Website services and analytics

Cloudflare hosts and delivers this website. It receives network information, such as your IP address and requested URL, to serve and protect the site. The project pages also use Cloudflare Web Analytics to measure aggregate traffic and page performance. Analytics dimensions include visited pages, referring sites, country, browser, operating system, and device type. Performance measurements include page-load timing.

Cloudflare states that Web Analytics does not use cookies, local storage, or browser fingerprinting to track visitors. Its Web Analytics documentation states that unsampled beacon data is kept for seven days, followed by sampled data for longer-term reporting. The dashboard provides access to the previous six months. This reporting window is not a promise that all Cloudflare service data is deleted after six months. Cloudflare's privacy policy describes its retention practices and privacy rights.

You can use browser controls or a content blocker to prevent the analytics script from loading. This does not prevent Cloudflare from processing the requests needed to deliver the site. Filament Labs does not use advertising trackers or a website contact form.

The pages load fonts from Google Fonts. Your browser sends requests to Google to retrieve those fonts. Google receives the network information needed to answer those requests. Its processing and retention are governed by Google's privacy policy. You can block external font requests with browser controls; the pages can use fallback fonts.

Support messages and privacy requests

If you email Filament Labs, we receive your email address, any name you provide, and the contents and attachments you choose to send. We use this information to answer your request and investigate reported issues. Filament Labs and the email service providers that deliver and store the correspondence process these messages.

Support correspondence remains in the email system until manually deleted, including in response to a deletion request. This policy does not promise an automatic deletion deadline. You can request access, correction, or deletion of correspondence you sent by emailing info@filamentlabs.io. We may need enough information to locate the message and verify that the request is yours. The email provider's backup and deletion practices can affect when removed messages cease to exist in its systems.

Do not send passwords, tokens, authentication files, raw App Server responses, or account-specific usage data for support. Use sanitized diagnostics instead.

Contact and changes

Send privacy questions to info@filamentlabs.io. We publish policy changes on this page and update the date above.