Privacy Policy
Summary. TokenMaxxer uses no developer server for usage checks or accounts. The API keys, login tokens and session cookies you add, and the usage data the app fetches, are stored only on your device. On iPhone and Mac, credentials sync only between devices on your own Apple ID through end-to-end encrypted iCloud Keychain. The developer never receives or keeps them. To check usage, your device talks directly to the AI services you chose. The app has no ads or tracking. To understand active users and purchases, it sends app-usage statistics and purchase events without your name or email to Google Analytics (Firebase); credentials and usage data are never part of them. Feedback & bug report in Settings opens an email in your own mail app, pre-filled with app and device info; it reaches the developer only if you send it, and it never includes credentials or account names.
Minjun Kim ("the developer") operates the TokenMaxxer app ("the app") and this website, and handles your information as described below, in line with the Korean Personal Information Protection Act and other applicable laws.
01Information processed and how
The app processes the following information only on your device. The developer does not collect or receive it.
| Category | Items | When |
|---|---|---|
| Credentials | API keys, OAuth access and refresh tokens, web-login session cookies and tokens, provider-specific settings (e.g. region, organization ID) | When you add an account or finish a provider login |
| Account display data | Account label, sign-in method, enabled state | When you enter or change them |
| Usage data | Usage percentages, reset times, credits, balance and cost, plus the account email, plan and organization name a provider includes in its response | When the app fetches usage from a provider |
| Widget summary | Provider name, account label (which can be the login email if you left the label empty), usage percentage, reset time, error summary; never credentials | After each refresh, to show widgets and Live Activities |
| App settings | Auto-refresh interval, app icon choice | When you change a setting |
Separately, the app sends the following usage statistics to Google Analytics (Firebase). They never include your name, email, credentials or usage data.
| Category | Items | When |
|---|---|---|
| App instance ID | A random identifier created for each app installation | On first launch |
| App interactions | First open, app launches and session length, screens viewed, app updates | While you use the app |
| Purchase history | Subscription or lifetime product ID, price, currency, purchase time | When you pay inside the app |
| Device and app info | Device model, OS version, app version, language, and country/region inferred from the IP address (the IP address itself is not stored) | Whenever the above is sent |
Separately, tapping Settings > Feedback & bug report opens an email in your device's mail app, pre-filled with the information below. The app itself sends nothing; it reaches the developer's address (mnjn00.biz@gmail.com) only when you review and send the email.
| Category | Items | When |
|---|---|---|
| Report | What you write in the email and any files you attach, such as photos or videos | When you send the email |
| Sender | Your email address and the name set in your mail app | When you send the email |
| App and device info | App version, OS version, device model, app language | Pre-filled in the email body |
| Diagnostics | Number of accounts, IDs of the providers you added, IDs and error types of providers whose last refresh failed, whether demo mode is on (never account names, emails, credentials or usage) | Pre-filled in the email body |
The app has no sign-up and does not collect your name, phone number, precise location, contacts, photos or advertising identifier. It never asks for access to your photo library.
02Purpose
The information is used only to fetch the usage, limits and balance of the AI service accounts you added and show them in the app, home and lock screen widgets, and Live Activities. It is never used for anything else or combined with other data. The usage statistics in section 01 are used only to understand active users, feature use and purchases in order to run and improve the app, never for advertising or tracking across other apps and websites. Feedback and bug report emails are used only to find and fix problems, improve the app and reply to you.
03Storage and retention
- iOS and macOS: credentials are encrypted in the Keychain and, if you have iCloud Keychain turned on, synced between your iPhone and Mac on the same Apple ID with Apple's end-to-end encryption. App settings such as sort order, color theme, display mode and refresh interval (never credentials) sync through iCloud key-value storage. The developer cannot access this iCloud data.
- Android: credentials are stored in an app-private file encrypted with an Android Keystore key. App data is excluded from device backups.
- Fetched usage is kept in memory while the app runs; the widget summary keeps only the latest snapshot in the app's private shared container.
- Data is kept until you delete the account in the app or delete the app.
- The usage statistics in section 01 are stored in Google Analytics; event-level data is deleted two months after collection. Aggregated reports that cannot identify anyone (such as daily user counts) may remain.
- Feedback and bug report emails are kept in the developer's email account (Google Gmail) and deleted one year after receipt, or earlier on request.
04Deletion
Deleting an account in the app immediately removes its credentials and usage records from device storage, and iCloud Keychain removes them from your other devices on the same Apple ID. Deleting the app lets the operating system remove the app's data. iOS Keychain items can remain on the device after the app is deleted, so delete your accounts inside the app first if you want them fully removed.
05Communication with AI service providers
The developer does not share your information with third parties. The app does, however, send requests that carry an account's credentials directly to the servers of the AI services you added (for example OpenAI, Anthropic, Google, GitHub, Cursor, OpenRouter; "providers"). This happens between your device and the provider at your request and never passes through the developer.
- What a provider receives: the credentials for that provider account and the usual connection data of a request (IP address, device and app information).
- When: when you refresh, save an account, or when auto-refresh or background refresh runs (iOS Background App Refresh; on Android, a 15-minute job while a widget is in use).
- Provider servers may be located outside Korea, such as in the United States. Each provider handles what it receives under its own privacy policy.
OAuth sign-in happens on the provider's own login page. Web login runs in a separate temporary browser session per account; when it finishes, only that provider domain's cookies or token are stored for that account.
06Processors and international transfer
The developer entrusts analysis of app usage statistics to Google LLC, which transfers the usage statistics in section 01 abroad.
- Recipient (processor): Google LLC (Google Analytics for Firebase), contact: Google privacy inquiries
- Destination: the United States and other countries where Google operates data centers
- Items: the usage statistics in section 01 (app instance ID, app interactions, purchase history, device and app info)
- When and how: from time to time while you use the app, over an encrypted network connection (HTTPS)
- Purpose and retention: usage analytics; two months after collection
Feedback and bug report emails are received in the developer's email account (Google Gmail), which transfers the report information in section 01 abroad.
- Recipient (processor): Google LLC (Gmail, which hosts the developer's feedback inbox), contact: Google privacy inquiries
- Destination: the United States and other countries with Google data centers
- Items: the feedback and bug report information in section 01
- When and how: when you send a feedback email, through your own email service
- Purpose and retention: finding and fixing problems and replying to you; one year after receipt (deleted earlier on request)
The usage-statistics transfer is needed to operate the app; if you do not want it, you can stop using and delete the app. A feedback email is transferred only when you send it yourself, so nothing is transferred if you do not send one. This website is served on Cloudflare, Inc. infrastructure, and Cloudflare may process connection records such as IP addresses to deliver and secure the pages. The website uses no cookies and no analytics.
07Automatic collection
The app contains no advertising, crash reporting or tracking SDKs and does not use advertising identifiers (IDFA or Android advertising ID). It uses the Google Analytics for Firebase SDK for usage statistics, which stores an app instance ID on your device; the ID is removed when you delete the app and a new one is created if you reinstall. Cookies handled in the web-login screen exist only for provider sign-in as described in section 05 and are never sent to the developer.
08Information you share yourself
The "flex" share card and brag text are created on your device only when you tap share, and go to the app you pick. They contain provider names, an account label (omitted if it looks like an email), usage percentages and account counts, never credentials or emails. Device-code copy and text copy write to the clipboard only when you tap them.
09Security measures
- Encrypted storage in the operating system's secure storage (iOS and macOS Keychain, Android Keystore); cross-device sync uses only end-to-end encrypted iCloud Keychain
- Credentials and web-login sessions are separated per account
- HTTPS for provider communication, except local or private addresses you configure yourself (such as a self-hosted model server)
- No credentials in widget summaries, share cards or logs
10Your rights
Because account and usage data stay on your device, you can view, edit, delete or disable your accounts directly in the app. The developer does not hold this data and therefore cannot view or delete it for you, but questions are welcome at the contact below. You may also exercise your rights through a legal representative.
The developer keeps feedback and bug report emails, so you can ask to see or delete yours by writing to the contact below with the date you sent it and the address you sent it from.
11Children
The app is not directed to children under 14 and does not knowingly process their personal information.
12Privacy officer
Minjun Kim (developer) · mnjn00.biz@gmail.com
13Remedies
For reports or advice about privacy infringement in Korea you can contact the Personal Information Dispute Mediation Committee (1833-6972, kopico.go.kr), the KISA Privacy Infringement Report Center (118, privacy.kisa.or.kr), the Supreme Prosecutors' Office (1301, spo.go.kr) or the Korean National Police Agency (182, ecrm.police.go.kr).
14Changes
Changes are posted on this page with a new effective date. Changes that matter for your rights are announced at least 7 days in advance. If the Korean and English versions differ, the Korean version prevails.
Change history: 2026-10-14 added feedback and bug reports (sections 01, 02, 03, 06, 10). 2026-10-15 feedback and bug reports now go by email (sections 01, 02, 03, 06, 10).