Effective date: 2026-09-20
Developer and privacy contact: Kun Chen, kunc345@gmail.com.
1. Scope and responsibilities
This policy covers EdgeQuota for Mac and its support and privacy website. It explains local processing, connections to outside services, purchases, and support requests. Features depend on your app version and enabled connections, including when using TestFlight.
EdgeQuota is independent of OpenAI, Anthropic, DeepSeek, and Apple. The developer does not operate a user-account service or a quota relay server. Using a connected provider is not entirely offline: that provider handles authentication and requests under its own terms and privacy policy.
2. Information processed on your Mac
Depending on the features you enable, EdgeQuota processes:
- Account information and usage readings supplied by a connection, including supported plan labels, quota windows, reset times, timestamps, and API balances. Account identifiers or derived account markers help keep readings from different accounts separate.
- Local coding-task metadata, including session identifiers or derived markers, task titles, project or folder names, model labels, activity state, and timing.
- Preferences, connection configuration, authorized file-access references, and local images you choose for customization. Provider renewal dates and plan labels you enter manually are display preferences, not billing controls.
- Verified StoreKit product and entitlement information, including the original trial purchase time and whether access has been revoked.
- Local diagnostic information when a connection or diagnostic feature needs it, such as errors, local paths, request-status records, and a panel image when diagnostic capture is used.
Local activity records may contain more information than EdgeQuota displays. The app extracts supported task and usage fields; it does not automatically upload your source code or conversation transcripts to the developer. Derived or hashed identifiers are not a promise that all associated local information is anonymous.
3. Provider connections and credentials
OpenAI Codex. The bundled Codex component communicates with OpenAI for sign-in, account information, and quota requests. EdgeQuota uses an app-managed Codex environment and system Keychain storage rather than automatically importing another Codex client's credentials. Optional local task detection is separate from that account connection.
Claude Code. The local Code integration receives supported status-line and lifecycle events. Its supported runtime-based quota mode invokes a compatible, separately installed official Claude Code runtime using the authorized local Code configuration and its signed-in account. The runtime handles authentication with Anthropic; EdgeQuota uses account information to derive a local account marker and avoid mixing readings. Connecting this mode does not sign the user out of Claude Code. Other connection-specific files remain on the Mac.
DeepSeek. The optional balance connection stores the API key in the Mac's Keychain, with Keychain synchronization disabled for that item. It sends the key in an HTTPS request to DeepSeek's official balance endpoint. This client does not use a cookie store or response cache and does not follow redirects. A normal API key can authorize other paid API operations outside EdgeQuota, so keep it private.
Providers receive authentication and request information, as well as ordinary network information such as the requesting IP address. EdgeQuota's quota queries do not submit coding prompts. These requests are not routed through a developer-operated server, but the providers may retain service or security records under their own policies.
4. Diagnostics and analytics
EdgeQuota does not include developer-added advertising or behavioral analytics SDKs. For the provider components it launches, it sets Codex analytics and feedback options off, and Claude telemetry, error-reporting, and feedback options off. This does not change settings for coding sessions you run independently, nor does it eliminate every provider-side service or security record.
Some connection checks use temporary local diagnostic files. Diagnostic capture can also create a local report or panel image. These are not automatically sent to the developer. Do not assume every diagnostic file is empty of private information or immediately deleted; review and redact anything you choose to share.
5. App Store purchases and TestFlight
Apple handles payment and transaction processing. EdgeQuota verifies StoreKit information to grant the optional seven-day trial or lifetime access and to restore purchases. It does not receive your full payment card number or Apple Account password.
The trial starts with its original verified transaction and does not restart on reinstall or restore. It does not convert automatically into a paid purchase. Trial expiry pauses paid monitoring features rather than erasing your saved settings or connections.
Apple may process store, testing, crash, and diagnostic information according to its services and your settings. The developer may receive tester feedback or diagnostic reports made available by Apple and use them to investigate problems. Apple-controlled records are not deleted by uninstalling EdgeQuota.
6. Support messages
When you email kunc345@gmail.com, the developer receives your email address, message, and any name or attachments you include. These are used to respond, investigate the reported issue, and handle related follow-up. Gmail processes delivery and storage of support email under Google's Privacy Policy.
Send only information needed to explain the issue. Please do not send passwords, complete API keys, identity documents, bank details, source code, conversation transcripts, or complete unredacted log archives.
7. This website and Cloudflare
The support and privacy website is hosted on Cloudflare Pages. Our pages do not add advertising, browser analytics scripts, account forms, or cookies.
Delivering the site still involves network processing. Cloudflare may process IP addresses, routing and request information, and operational or security records. Hosting dashboards may provide traffic statistics or logs. This is different from saying the website has no data processing. See Cloudflare's Privacy Policy for its service practices.
Email links open your chosen mail application. Other external links take you to services governed by their own policies.
8. Storage, retention, and your controls
Local preferences, usage records, bookmarks, and connection files can remain between launches. You can stop monitoring, disconnect integrations, and revoke local access through the relevant controls. Disconnecting EdgeQuota does not cancel provider subscriptions, delete provider accounts, or necessarily sign other clients out.
For DeepSeek, disconnecting stops synchronization and attempts to delete the stored key. If macOS prevents deletion, EdgeQuota reports that the key has not yet been removed; retry the removal. To invalidate the key at DeepSeek, revoke it in your provider account too.
Uninstalling should not be assumed to remove every Keychain item, local diagnostic, or provider-side record. Contact support for help locating EdgeQuota's local records.
Support messages and developer-accessible diagnostic reports are retained while needed to resolve the issue, handle related follow-up, or meet applicable legal obligations. Retention also depends on the nature of the record and any ongoing dispute or security issue. Apple, AI providers, Google, and Cloudflare control retention of records they handle under their own policies.
9. Sharing, service locations, and security
The services described above process information as necessary for the features you choose, store functions, hosting, and support. We do not sell support information or use it for targeted advertising. Information may also be disclosed when required by law or necessary to protect rights and security.
These services may process information outside your country. EdgeQuota does not promise that all related information stays on your Mac or within one country. Keychain storage, local access controls, and HTTPS help protect information, but no software or transmission method guarantees absolute security.
10. Questions, requests, and changes
You can contact Kun Chen at kunc345@gmail.com to ask about information handled by the developer, request access, correction, or deletion, or get help with local records. Requests are handled according to applicable law and any relevant limits; you may have additional rights in your jurisdiction. Such a request does not delete information controlled by Apple or an AI provider.
The app does not require a separate EdgeQuota account, so there is no developer-hosted EdgeQuota account to delete. Use the respective provider's controls for its account and data.
If our practices change, we will update this policy and its effective date. The English and Chinese pages describe the same practices; contact us if you notice a discrepancy.