UsageDeck

Privacy Policy

Effective October 5, 2026

UsageDeck is an open-source desktop application distributed under the MIT License. This policy explains what information the application and this website handle.

Summary

UsageDeck has no UsageDeck account system or UsageDeck-operated backend. The project does not add analytics, advertising, behavioral tracking, or telemetry to the application or website. Application data is stored on your device. UsageDeck is not an offline-only application: provider usage, authentication, reset-credit requests, and public model-price refreshes communicate directly with third-party services. Optional Session Kickstart runs provider commands on your device.

Information stored on your device

Depending on the features and providers you use, UsageDeck may store locally:

  • application settings and provider display preferences;
  • usage, quota, reset-time, reset-credit inventory and expiry, token-history, and estimated-cost data;
  • diagnostic logs designed to redact credentials and sensitive values;
  • API keys you add, stored through your operating system's credential store where supported; and
  • cached pricing and update information, account-card identities, and records of successfully delivered reset-expiry reminders.

The UsageDeck project does not receive this locally stored information.

Third-party provider communication

To retrieve usage, quota, and reset-credit information, UsageDeck sends requests directly from your device to the providers you enable. Refreshes may run automatically while the application is open. UsageDeck may also renew supported provider logins and save renewed credentials to their original local source. Codex reset redemption sends a provider request after you confirm it. These requests may include provider authentication material, account identifiers, and technical request information required by that provider. The provider receives and processes those requests under its own privacy policy and terms. UsageDeck does not proxy these requests through a UsageDeck-operated service.

Model price catalogs

To estimate spend, UsageDeck downloads public model-price catalogs about once a day from GitHub (raw.githubusercontent.com), models.dev, and openrouter.ai, and caches them on your device so the application still works offline. These requests carry no credentials, account identifiers, or usage data, and they are made whether or not you have configured a corresponding provider. The operators of those sites may receive standard connection information such as your IP address and user agent, which they handle under their own privacy policies.

Local sign-in data and API keys

For supported providers, UsageDeck may read authentication data previously stored by the provider's CLI or desktop application. API keys entered in UsageDeck are stored locally and are used only to make the provider requests you initiate or enable. UsageDeck does not send provider credentials to the UsageDeck maintainers. Named API-key accounts have separate saved keys. When you choose Use ZCode API key for a Z.ai card, UsageDeck reads the local ZCode login and replaces that card’s saved key with the matching personal-plan key; subsequent quota and reset requests use that account.

Optional Session Kickstart

If you enable Session Kickstart, UsageDeck runs a provider CLI command or your custom command after a rolling usage window expires. Built-in commands send a small prompt to the provider to begin the next window. The provider receives that prompt and any required authentication under its own policies. These prompts use provider quota and may incur charges. The feature is disabled by default and can be turned off in the provider’s Customize screen.

Updates and downloads

UsageDeck checks GitHub Releases according to your update-check preference or when you request a check. When you choose to install an update, it downloads the update from GitHub. Linux package installations that cannot update in the app open the release page for a manual download. GitHub may receive standard connection information such as your IP address and user agent. GitHub handles that information under the GitHub General Privacy Statement. Update packages are cryptographically verified by UsageDeck.

Website

The UsageDeck website does not set project-operated analytics or advertising cookies and does not include project-operated tracking scripts. It is hosted using GitHub Pages, so GitHub may process standard hosting logs and connection information under its own privacy statement. Links to third-party websites are governed by those sites' policies.

Retention and your choices

Reset All Settings restores preferences while preserving provider sign-ins, API keys, and usage history. Removing a named API-key account deletes its saved key; deleting an app-saved key may leave an external config or environment key available. To remove local usage data, delete the application’s data directory and remove saved keys from the system credential store as needed. Uninstalling the application does not necessarily delete those records. You can stop a provider’s usage refreshes by disabling it in Customize and stop automated prompts by disabling Session Kickstart. Public price-catalog requests remain independent of provider selection. Data already received by a third party is subject to that party’s retention rules.

Children

UsageDeck is a developer utility and is not directed to children. The project does not knowingly collect children's personal information through a UsageDeck-operated service.

Changes to this policy

Material changes will be published on this page and committed to the public UsageDeck repository. The effective date above identifies the current version.

Contact

For general privacy questions, open a GitHub issue without including credentials or private account data. If your report contains sensitive security information, use GitHub private vulnerability reporting.

Open source

You can inspect how UsageDeck handles data in the public source repository. UsageDeck preserves its lineage and attribution to OpenQuota and OpenUsage.