Help & FAQ
ClearQuota is intentionally small and local-first. Here is how its data and credential handling work.
Yes. ClearQuota stores only the Secret Manager identifier you configure, such as a secret name or full secret reference. Provider credential values are fetched only during a refresh, used to make the provider request, and are never persisted, logged, or returned to the browser.
ClearQuota preserves provider setup metadata and sanitized usage snapshots in a local SQLite database. That can include the provider name, its Secret Manager reference, usage amounts, quota limits, timestamps, and refresh results. It never contains provider API keys.
It runs on your computer and binds only to 127.0.0.1. There is no ClearQuota-hosted service receiving your dashboard data or usage history.
You configure a Google Secret Manager secret name or reference. On refresh, ClearQuota uses your local Google Application Default Credentials to resolve that exact secret and sends it directly to the provider API. Google sign-in is separate from the provider credential.
ClearQuota currently supports OpenAI organization usage and spend alerts, Apify monthly credit usage, and Resend monthly and daily email metrics.
Yes. ClearQuota data stays on your machine under your control. You can remove the local database when you no longer need the saved provider configuration and usage snapshots.
Need something else? Open an issue on GitHub.