Privacy
Usage Desk has no cloud account, analytics, or credential-upload service.
What the app reads
The app reads account identity, plan, quota windows, and earned resets returned by your installed Codex CLI. It also reads Chrome’s Local State profile labels and emails for the optional browser picker. It never extracts browser cookies, passwords, history, or access-token databases.
Where sign-ins live
Your current CLI account stays in its existing Codex home. Added accounts get separate folders under ~/Library/Application Support/ResetDesk/accounts/. Codex manages their credentials locally. Those credentials may be sensitive files; Usage Desk does not promise that they are held in Keychain.
Removing an account stops tracking it but retains its local authentication directory. That avoids logging you out unexpectedly.
What goes over the network
Codex communicates with OpenAI for browser sign-in, credential refresh, and usage reads. OpenAI’s policies apply. Usage Desk has no intermediary server, doesn’t run model turns, and doesn’t redeem resets.
This website
The page has no analytics, advertising, external fonts, or tracking cookies. If you change its appearance, that preference is stored in your browser’s localStorage. Product images are captures of the actual app and its native SwiftUI views. Account details are anonymized or use isolated sample accounts, as labelled. The website never signs you in.
A hosting provider may keep ordinary access logs under its own policy. Published GitHub downloads are subject to GitHub’s policies.
Contributing safely
Do not include real account emails, tokens, auth files, or sign-in URLs in public screenshots or reports. Use the project’s isolated demo mode for screenshots. Security-reporting instructions are in SECURITY.md in the source.