APPMONITOR iOS Updated November 11, 2026
Privacy Policy
Effective: November 4, 2026 · Last updated: November 11, 2026
This policy applies to information handled by AppMonitor and its promotional website. Sections covering specific features, such as purchases or free trials, apply when you use those features in a version that provides them. Check the app for feature availability.
1. Scope and principles
The operator of AppMonitor (“we”) sets out in this policy how information is handled in the iPhone app AppMonitor (“the app”) and its promotional website. The web dashboard is outside this policy’s scope.
The app helps you view store information and analytics reports for apps you are authorized to access. ASC and GA4 credentials and fetched reports are not centrally collected on AppMonitor’s servers. Your device communicates with Apple, Google, and their designated delivery endpoints to fetch data. In-app inquiries send the message and basic device information to a private support system. Pro free trials also send the information needed to check and manage trial status to a server.
2. Information we handle
- App Store Connect credentials
- The Key ID, Issuer ID, and API private key (.p8) you enter or select. The private key signs authentication tokens sent to Apple. We do not obtain your Apple Account password.
- Data fetched from App Store Connect
- Depending on permissions and availability, the app handles app names, identifiers, icons, version information, reports such as downloads, views, and estimated proceeds, breakdowns by country and device, and review titles, text, ratings, dates, and countries. Review text may contain personal information.
- Google / GA4 credentials
- The app handles authorization codes, access tokens, and refresh tokens issued through Google authentication. It requests read-only Google Analytics access (analytics.readonly) and permission to identify the connected Google account (openid). The app does not obtain your Google password and does not request email or profile permissions.
- Google account matching information
- The app obtains a stable account identifier (sub) from Google and converts it to a matching hash on the device. This links settings and saved reports to the correct connection when you reconnect the same account and prevents mixing data from different accounts. We treat this value as Google-derived identifying information, not anonymous information.
- GA4 data and settings
- The app handles account, property, and stream names and identifiers, app links, time zones, daily active users, sessions, engagement, selected event counts, and event names and display names you configure. This also includes landing-page (web) URLs, display names, CTA settings, and aggregate views, traffic sources, campaigns, and landing pages. This feature displays aggregate reports from properties you select; it does not use GA4 to track behavior within AppMonitor itself.
- Settings and fetch status
- The app handles your monitored-app selection, display conditions, fetch times, warnings, and fetch results. Card layouts, display and notification settings, notification history, saved keywords, and keyword observation history stay on the device. Fetch logs are also stored locally and limited to 30 days and up to 100 entries per source. Private keys and tokens are not recorded in fetch logs.
- Support inquiries and submission verification
- The app handles your selected category, message, inquiry ID, app version and build, OS version, device model, and language setting. Drafts stay on the device. Apple App Attest verification information, key-identifier hashes, public keys, counters, challenges, message hashes, and delivery status are used to prevent abuse and verify delivery. The server uses source IP addresses to limit submissions. Applicable APIs use a keyed hash of the IP address and registration time to prevent excessive App Attest key registration.
- Purchases and Pro access
- Product information and verified purchase information obtained through App Store StoreKit are used for purchasing, restoration, access checks, and handling refunds or expiry. Apple processes payments; the app does not obtain credit card information.
- Pro free-trial management
- When checking or starting a trial, the app sends Apple-signed app acquisition information and App Attest verification information to the trial-management server. A matching ID derived from a verified account identifier, along with trial start and end times, is stored to carry trials over and prevent duplicate starts. The matching ID is treated as identifying information and is not used for advertising or cross-service tracking.
3. Purposes of use
- To connect to external services you authorize and retrieve the relevant lists and reports.
- To display, compare, and aggregate metrics, browse reviews, and check fetch status.
- To maintain connections and restore saved data and fetch settings.
- To receive inquiries, investigate issues, handle rights requests, verify delivery, and prevent abuse.
- To verify Pro purchase access and manage trial status, trial starts, carryover, and duplicate-start prevention.
Credentials and analytics data are not used for advertising, sale, data brokerage, or training general-purpose AI models.
4. Storage and security
ASC private keys and Google refresh tokens are stored in the iOS Keychain with access restricted to this device while it is unlocked. Google access tokens are handled in memory. Google account matching values are stored with Keychain connection information and as owner information for locally saved reports. Connection identifiers such as Key ID and Issuer ID may also appear in fetched data stored on the device.
Fetched reports and fetch settings are stored in the app’s private device storage with file protection. App icons are cached locally and may be removed by the OS. Settings, history, and drafts are stored in UserDefaults or local files. Notifications use on-device local notifications. Communications use HTTPS.
The app does not currently provide iCloud / CloudKit sync. If sync is introduced, we will explain the data involved, transmission to Apple, and how to stop syncing and delete data in advance, and update this policy so you can choose whether to use it.
Saved ASC reports and fetch logs are excluded from device backups. GA4 saved files do not have the same exclusion and may be included in device backups depending on OS settings. App sync and OS backups are separate. The app does not delete the original .p8 file you imported. You are responsible for the original file in Files or elsewhere and any cloud storage containing it.
5. Communications with external services
- Apple
- The app sends signed, short-lived authentication tokens, app and report identifiers, and query conditions to the App Store Connect API. Keyword searches send search terms, country, and related parameters to Apple’s iTunes Search API; indicative positions and observation history are handled locally. The private key itself is not sent. Your actions may request ongoing generation of analytics reports. Reports and icons are fetched from endpoints designated by Apple.
- The app sends Google the OAuth client identifier, requested permissions, authorization code, and related information during authentication; refresh tokens during token renewal; and access tokens, target properties, streams, dates, event conditions, and related parameters when calling GA4 APIs.
- Support and free-trial management
- After validating in-app inquiry submissions, the message and app and device information are stored in a private support system. Trial-management servers and databases handle verification, matching IDs, and trial periods. ASC private keys, Google tokens, analytics reports, and review text are not automatically attached to inquiry or trial API requests. Information you include in a message is transmitted.
These recipients handle IP addresses, request information, and related communication data under their own terms and privacy policies. Processing may take place outside your country. See Apple’s Privacy Policy, Google’s Privacy Policy for details.
We disclose personal data received through inquiries or other channels to third parties only with your consent or where permitted by law. When processing is entrusted to service providers, we appropriately manage and supervise them within the scope necessary for the stated purposes.
6. Use of Google user data
Information obtained from Google is used only to display and analyze the GA4 data you select and to provide and maintain those features. It is not used for advertising, credit assessment, sale, or training general-purpose AI models. There is no mechanism for the operator to automatically receive or view fetched reports.
Use of information received from Google APIs, and transfer of that information to other apps, complies with the Google API Services User Data Policy, including its Limited Use requirements. Connecting Google is optional.
7. Data retention and deletion
Saved reports remain on the device until updated by fetching, adjusted to the relevant data range, or removed through the actions below. The period queried and the retention period on the device are different; we do not guarantee that all saved data is deleted after a fixed number of days.
- Disconnect ASC
- Disconnecting in the app’s ASC settings deletes ASC credentials from that device. Fetched reports, monitored and hidden-app settings, history, and card layouts are retained. Disconnecting and deleting saved data are separate actions. Cached icons and the original .p8 file in Files are separate. Apple-side API keys and ongoing report-generation settings remain; revoke them in App Store Connect if needed.
- Delete ASC saved data
- Confirming “Settings → App Store Connect → Delete ASC saved data” deletes fetched ASC data. Credentials, app display settings, card layouts, and GA4 data are retained.
- Disconnect Google
- “Disconnect” in GA4 settings deletes Google credentials from that device’s Keychain and memory. Fetched reports, fetch settings, and the account matching value retained as saved-report owner information remain on the device. Manage this saved data and OS backups as described under “Delete locally saved app data” below. To revoke Google-side access, also remove the connection in Google account connections. Revoking access alone does not delete locally saved reports.
- Delete locally saved app data
- A dedicated bulk-delete feature for GA4 reports is not currently provided. Use iOS “Delete App” to remove local app data; “Offload App” keeps data. Keychain items may remain after deleting the app, so disconnect each service first. Copies in OS backups must be managed and deleted separately in the OS.
Trial expiry or purchase expiry does not delete credentials, fetched data, or card layouts. Viewing saved GA4 data and permission to fetch new data or change settings are handled separately.
Server-side record retention
Retention periods follow each record’s purpose as listed below, and unnecessary personal data is deleted. Even where a period is specified, deletion is not always automatic; administrators perform it when needed. If records are exceptionally retained for legal obligations or ongoing disputes, we manage the reason and necessary period.
- Inquiry messages, emails, and attachments
- Emails and records in the private support system are generally retained for one year after the inquiry is resolved, then deleted. Requests for deletion or other action are also handled through the procedure below.
- Inquiry receipt and delivery records
- Inquiry IDs, content hashes, delivery status, and submission-verification information are retained to verify delivery and prevent duplicate delivery of the same inquiry. Separately from message and email retention, the minimum receipt and verification records needed to prevent resubmission are retained while the service is provided. Inquiry messages are not stored in the receipt database.
- Trial matching IDs and start / end times
- These are retained as usage history while the service is provided, to carry trials over and prevent duplicate starts. Original account identifiers and Apple-signed acquisition information are not stored in the database or message logs. Matching IDs are treated as identifying information and are not used for advertising or cross-service tracking.
- App Attest and short-term submission-verification records
- Public keys, counters, and related information are retained as needed to verify submissions from the legitimate app and prevent replay. Trial-request records and key-registration rate-limit records using IP hashes have a 24-hour retention standard, with expired records cleaned up. Short-lived challenges expire, but those referenced by receipt records are retained to prevent replay.
- Execution and access logs
- Logs are handled as necessary to investigate failures and prevent abuse. Infrastructure logs follow the provider’s retention settings and are not normally exported for long-term storage. Service processing logs do not record inquiry messages, private keys, authentication tokens, or original trial-account identifiers. Records separately retained for an investigation are deleted within one year after the investigation ends.
- Backups
- Backup copies expire under the infrastructure’s retention periods. Information deleted from normal use may not immediately disappear from all backups. If restoration is necessary, we apply confirmed deletion requests and manage the process to avoid returning deleted information to normal use.
How to request deletion
To request deletion of server-side inquiry or trial records, use “Settings → Feedback and support” in the app, or contact studio64y@gmail.com. For information received by email, write from the email address used for that correspondence. We check the request type, inquiry time, inquiry ID, and other clues, and use the minimum necessary additional information to verify your identity and locate the records. We do not ask for passwords, authentication tokens, or .p8 files.
Trial matching IDs are not linked to email addresses, so an email address alone may not identify the relevant record. If we cannot verify your identity or identify the records, or cannot fulfill all or part of a request for legal or other reasons, we explain why. We aim to respond within 30 days after verification is complete and explain the reason and expected timing if more time is needed. Statutory deadlines and requirements take priority.
Deleting trial records may prevent us from maintaining trial carryover or repeat-trial restrictions. Deleting the app alone does not delete server-side inquiries, trial records, or notification signups.
Disconnecting or deleting the app does not delete original reports or account data held by Apple or Google. The operator cannot remotely view, delete, or restore information stored only on your device.
8. This website and support inquiries
The website’s source does not include advertising SDKs, analytics tags, or a general inquiry submission form. The launch notification form handles information as described below. Hosting providers may process IP addresses, access times, browser information, and related data to deliver the site, authenticate access, and prevent abuse. External delivery and database services are used to host the website and store notification signups. Cookies and communication logs used for delivery, authentication, and abuse prevention follow each provider’s settings and privacy policy. This site does not set its own advertising or behavioral-tracking cookies. Service providers are appropriately managed and supervised, and processing stays within the purposes stated in this policy.
In “Settings → Feedback and support,” you can review your message and basic information before sending. Inquiry messages are stored in a private support system. The current form has no reply-email or attachment fields. If you need a reply or the app will not open, use studio64y@gmail.com. For email inquiries, we use your sender address, message, and any attachments you choose to provide to handle the inquiry. Do not include private keys, tokens, or passwords. See our support information for details.
The app contains no advertising, SDKs tracking behavior within AppMonitor, or custom automatic crash-report submission. Diagnostic information handled by the OS or distribution platform follows their own settings and explanations.
About launch notification signup
Launch notification signup has been available since November 1, 2026. This section sets out how information for that signup is handled.
With your consent, your email address, signup time, and the version of the notice you accepted are stored on a server to send notifications and manage signups. They are used only to announce the launch of AppMonitor, not for advertising or sale to third parties. Signing up does not incur a charge.
To reduce abusive signups, we derive an IP hash that changes every ten minutes and use it to limit submissions. The original IP address is not stored in the signup database. Expired rate-limit records are cleaned up during a subsequent signup. Infrastructure communication logs follow the infrastructure’s own terms.
Signup information is retained until the notification has been sent or an unsubscribe request has been handled; information no longer needed is deleted. To unsubscribe or correct your address, contact studio64y@gmail.com from the email address you registered. We respond after verifying the address and request.
This form registers a notification address and does not send a confirmation email at signup. Please check your email address carefully. Notification timing will be announced after the release is decided.
9. Disclosure, correction, and other requests
To request notice of purpose of use, disclosure, correction, addition, deletion, suspension of use, erasure, cessation of third-party provision, or disclosure of related records for personal data we hold, contact us below. We verify identity as necessary and respond in accordance with applicable law. If we cannot comply, we explain why. Manage information stored only on your device through the app and OS.
10. Changes to this policy
Changes to our handling of information and their effective dates will be announced on this page, in the app, or through another appropriate channel. Where law or external-service rules require consent for a new purpose or transmission, we obtain it before proceeding.
11. Contact
- Support and personal data requests
- In the app: Settings → Feedback and support. Email: studio64y@gmail.com.
This contact also accepts inquiries about operator information concerning retained personal data, security measures, and request procedures. We respond without delay in accordance with applicable law.