1. Operator and scope
My App Manager, provided by MK Idea Box, helps app developers review revenue and backend status. It does not require a separate My App Manager account. This policy covers connections, metrics, ads, subscriptions, backups and alerts.
2. Information stored on your device
- Authentication tokens, service API keys, Supabase management tokens and Apple signing private keys use the device's secure storage. Display names and email addresses, project addresses, app identifiers and other connection settings use local storage.
- Raw revenue retrieved from APIs; the daily ledger by date, original currency and provider; installations and other metrics; backend status and usage; alert history; and preferences are stored locally. The app does not sync this raw revenue or ledger online or upload it to an operator server.
- Subscription status and its confirmed expiration use secure storage. Ad counts and reward expiration are stored on your device. An ad reward does not change subscription status.
3. Requests to connected services
Your device directly requests data from the Google Play, Cloud Storage, AdMob, Apple App Store Connect, RevenueCat and Supabase services you connect. Requests include authentication tokens or signed requests, necessary app or project identifiers, and reporting periods. The Apple private key is used on the device to sign requests. The app also checks backend addresses you add. These services may process connection information such as your IP address.
Registered-user counts are read from the Supabase Auth API. Its response may contain some individual user information; the app uses the aggregate count and does not maintain a separate ledger or user list of those individual details. Currency rates are requested from Frankfurter using a base currency, without account keys or revenue amounts.
The app has no feature that uploads your connection keys or retrieved business revenue to a server operated by MK Idea Box. It fetches data directly from the service APIs you select. Ads and subscriptions process information separately as described below.
4. Google OAuth and Google user data
When you connect a Google account, the app requests openid and email to label the account, plus permissions needed for the features you select: Google Play Android Publisher, read-only Cloud Storage, AdMob read and reporting, or Firebase read access. The corresponding scope strings are androidpublisher, devstorage.read_only, admob.readonly, admob.report and firebase.readonly. Google may describe androidpublisher on the consent screen as permission to view and manage a Play developer account, but this app's implementation uses it only for read requests such as app, review and rating retrieval. Within the other displayed scopes, the app reads project lists, Play reports, AdMob reports and Firebase project status.
Google may classify some of these as sensitive or restricted scopes and require OAuth app verification. Approved refresh tokens are kept in device secure storage, and access tokens are used for necessary Google API requests. Google account and report data is used only for the user-facing connection and metrics features you request. It is not sold, used for ad targeting, or sent to or stored on an MK Idea Box server. You can revoke access at any time in your Google Account security settings.
5. Advertising and frequency
Free use may include Google AdMob ads. Its SDK may process advertising or app identifiers, IP address and approximate location inferred from it, ad interactions, and device or app diagnostics for ad delivery, measurement and fraud prevention. See Google's privacy policy and partner services information.
Depending on legally required consent, region, advertising settings and device choices, AdMob may serve personalized, non-personalized or limited ads. Personalized ads may use previously collected information, such as past app or web activity, to select ads. Non-personalized ads do not use past behavior for targeting, but may use context and coarse location, and may use permitted identifiers or storage for frequency capping and aggregate reporting.
On iOS, the app requests App Tracking Transparency (ATT) permission before accessing the advertising identifier (IDFA) for ad targeting or measurement across other companies' apps and websites. If you decline, the app does not track using the IDFA and basic features remain available. Non-personalized or limited ads may still appear. Manage ad and tracking choices through Google consent screens when shown and through device privacy settings.
The frequency of additional ads is decided on your device using recent revenue and app usage time. Revenue amounts and revenue tiers used for this decision are not sent to AdMob or the RevenueCat purchase SDK.
Ads are not displayed while a subscription or an ad-free reward is active. Existing ad records remain subject to the provider's policy.
6. Subscriptions and RevenueCat
The app's own subscription is billed through Apple App Store or Google Play. RevenueCat processes product retrieval, purchase-receipt validation, restoration, renewal and access to benefits. Instead of a separate member account, the app uses an anonymous App User ID generated by RevenueCat. RevenueCat processes that ID, products, transactions, purchase history, subscription status and expiration information. We can view subscription status and purchase statistics in the RevenueCat dashboard.
The RevenueCat account you connect to analyze your own apps is separate from My App Manager's purchase SDK. Connected account emails, analytics API keys and your business revenue are not added as purchase SDK customer attributes. The app does not receive full payment-card details. See RevenueCat's privacy policy, Apple's privacy policy and Google's policy.
7. Backups, backend checks, alerts and device permissions
- Subscriber settings backups may include credentials and are encrypted with a password you choose. You select the file's save or transfer location. A cloud drive you select may store it under that provider's policy. The app does not automatically send it to us.
- When backend monitoring is enabled, the app directly accesses the Supabase, Firebase or custom health URL and API that you register or connect, from your device, to check outages, paused services and usage. Results and alert history are stored on the device, and issues are shown as local device notifications. No MK Idea Box server performs or relays the monitoring. Notifications may show project names and status. Manage lock-screen visibility, notifications and background execution in device settings.
- On Android, the app may read installed app icons to display them in your app list. It does not provide this installed-app list to ad or subscription SDKs.
8. Retention, deletion and choices
Delete connected credentials in app settings and revoke provider access in the provider's own settings. Local ledgers and preferences remain on the device and can be removed using device controls such as clearing app data. Delete exported files separately from their saved locations. iOS Keychain items and OS backups may survive app removal; uninstalling alone does not guarantee deletion of every copy.
Uninstalling the app or removing a connected account does not cancel a store subscription. Cancel it separately in the store. Advertising and subscription records are retained under their providers' policies and applicable legal requirements. Contact the email below to request access, correction or deletion; we will explain what we can process and any relevant provider request route. Do not include API keys or private keys in support requests.
9. Children, international processing and changes
The app is a developer tool and is not intended for children under 14. Connected services and ad or subscription providers may use infrastructure outside your country. Material changes will be reflected on this page and in-app notices where appropriate.