Privacy policy

My App Manager (내 앱 장부) · Last updated: 2026-09-14

Retrieved raw revenue data and the daily revenue ledger are stored only on this device, not online or on an MK Idea Box server. The app does send authentication requests directly to services you connect, while Google AdMob and RevenueCat separately process information needed for advertising and the My App Manager subscription.

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

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 user data (Google OAuth)

This section covers only the data the app obtains through Google APIs after you connect a Google account ("Google user data"): what it accesses, how it is used, and with whom it is shared.

4.1 Google user data the app accesses

4.2 How the app uses Google user data

Google user data is used only to provide the features you use in the app, on your device: listing your apps with their reviews and ratings; showing earnings, installs, ad revenue and impressions, and totals derived from them; checking your Firebase projects; and storing and restoring your encrypted settings backup. Google user data is not used for advertising, including deciding how often ads are shown, personalised or retargeted ads; it is not used to build user profiles, to train or improve artificial intelligence or machine learning models, or for any purpose unrelated to these features. No person at MK Idea Box reads your Google user data.

4.3 How Google user data is shared, transferred or disclosed

MK Idea Box does not share, sell, rent, transfer or disclose Google user data to any third party. Every request goes directly from your device to Google APIs, and Google user data is never sent to or stored on an MK Idea Box server — so MK Idea Box holds no Google user data that it could share. Google user data is not passed to the advertising SDK (Google AdMob) or the subscription SDK (RevenueCat) used in the app. The only way Google user data leaves your device is at your own direction: when you export a settings backup file and choose where to save or send it, or when you turn on cloud backup and the encrypted file is saved to your own Google Drive.

4.4 Storage, protection and deletion

Refresh tokens are kept in the device's secure storage (Android Keystore / iOS Keychain), and access tokens are used only for the requests above. Retrieved reports and the figures derived from them are stored only on your device. You can disconnect a Google account in the app's settings, remove local data by clearing the app's data or uninstalling it, and revoke the app's access at any time at Google Account > Third-party connections.

4.5 Limited Use

My App Manager's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

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 app usage time and recent revenue from RevenueCat and App Store Connect only. Revenue obtained through Google APIs (Google Play reports and AdMob) is never used for this decision. The revenue amounts and tiers used 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

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. Delete cloud backups by removing this app's hidden app data under "Manage apps" in Google Drive settings, or by revoking the app's access in your Google Account. 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.