Privacy Policy

The short version

Data accessed from your Google Account

When you authorize Google reporting access, the app requests read-only access to:

• AdMob reporting data (admob.readonly) — estimated earnings, impressions, eCPM and related reporting metrics.
• AdSense payment data (adsense.readonly) — unpaid balance and payment history.
• YouTube Analytics monetary reports (yt-analytics-monetary.readonly) and YouTube channel metadata (youtube.readonly) — revenue trends, top videos and country splits. These scopes are optional and only requested if you choose to connect YouTube.

All access is read-only. The app cannot modify your ads, campaigns, videos, payments or any other part of your Google account.

AdsMoney uses YouTube API Services. By connecting YouTube you also agree to the YouTube Terms of Service, and YouTube's handling of your data is governed by the Google Privacy Policy. You can review and revoke AdsMoney's access to your Google and YouTube data at any time at myaccount.google.com/permissions.

How that data is used

• Reports are fetched from Google's APIs directly by your device and rendered on screen.
• Nothing is uploaded to any AdsMoney server, because none exists. There is no report database or cross-device sync operated by us. Limited product-usage events that contain no Google user data or report figures are sent separately to Firebase Analytics as described below.

App analytics

AdsMoney uses Google Firebase Analytics to understand whether the app is working and where its onboarding and subscription flows can be improved. Firebase assigns a random app-instance identifier and automatically measures basic lifecycle information such as first open, sessions and app interaction. It may also process app and device information, a coarse location derived from a masked IP address, and StoreKit subscription events such as product identifier, product name and price.

AdsMoney additionally records a small fixed set of events: onboarding completion; Google authorization success, cancellation or broad failure category; report load success, empty result or broad failure category; first successful live report; paywall source; purchase and restore outcome; and opening Apple's offer-code sheet. Debug builds do not send analytics. A report backed by bundled sample data is labelled only as sample; none of its sample figures or labels is sent.

These events never include your name, email address, Google user ID, publisher or account ID, app/ad-unit/channel/video ID, OAuth token, report date range, raw API response or error message, earnings, revenue, balance, payment amount, impressions, or any other figure from your Google reports. AdsMoney does not set a Firebase user ID and does not link analytics to your Google authorization.

AdsMoney uses the Firebase Analytics Core package, which has no IDFA collection capability. Collection of Apple's IDFV, automatic screen reporting and advertising-personalisation signals is disabled. Analytics is used only for product measurement, not for tracking you across other companies' apps or websites and not for personalised advertising. See Privacy and Security in Firebase and Google's Privacy Policy.

For App Store privacy disclosure purposes, these analytics data types correspond to Product Interaction, Device ID, Coarse Location and Purchases. None of them is linked to your Google identity and none is used for tracking. Product Interaction, Device ID and Coarse Location are additionally processed for third-party advertising by the ad SDK described under Advertising.

What is stored on your device

So that you are not asked to authorize Google reporting access every time you open the app, and so Home Screen widgets can show a figure before their next refresh completes, some data is kept on the device between sessions:

• Your Google authorization session — the OAuth access and refresh tokens issued when you authorize reporting access, held in the iOS Keychain. They are shared with the AdsMoney widget extension through a private app group so widgets can refresh on their own, and they are never transmitted anywhere except to Google's own token endpoint.
• Widget snapshots — the most recent figures each widget displayed (earnings totals, a short daily series, unpaid balance and recent payouts), cached in the same private app group container so a widget can render while its next update is still loading.
• Recently viewed reports — a short-lived in-memory cache for the current session, so switching date ranges does not re-request the same report.
• Preferences — selected account ID, reporting time zone, appearance and accent theme, and your subscription status as last verified with Apple.

All of it lives inside the app's own sandbox on your device. Deleting the app removes it.

Who we share, transfer or disclose Google user data with

For complete transparency, these are the only outside parties involved in running AdsMoney at all, and exactly what each one receives:

Specifically, and without exception, Google user data obtained through AdsMoney is never:

• sold, rented or licensed to anyone;
• transferred to data brokers, information resellers or any other information-transfer service;
• used for serving advertisements, including personalised, targeted or retargeted advertising;
• used to determine credit-worthiness or for lending purposes;
• used to develop, improve or train generalised artificial-intelligence or machine-learning models;
• read by a human being. The only exceptions are the narrow ones the Google API Services User Data Policy permits — with your explicit prior consent for a specific action you asked for, where necessary for security purposes such as investigating abuse, or where required to comply with applicable law. None has ever occurred, because the data never leaves your device.

How we protect Google user data

Because AdsMoney runs no server, the strongest protection is structural: there is no central copy of your data to breach, no employee who could query it, and no backup of it anywhere but your own device. On top of that:

• Encrypted in transit. Every request to Google's APIs and token endpoints uses HTTPS with TLS 1.2 or higher, with certificate validation enforced by iOS. The app makes no plaintext HTTP request, and sends Google user data to no host other than Google's own API endpoints.
• Encrypted at rest. Your OAuth access and refresh tokens are held in the iOS Keychain, encrypted by the device's hardware-backed cryptographic engine. They are marked kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly: readable only after you have unlocked the device since it booted, never synchronised to iCloud Keychain, and never included in an iCloud, Finder or iTunes backup. Everything else the app keeps lives in its sandboxed container under iOS file-level encryption tied to your device passcode.
• Access control. The iOS sandbox prevents any other app from reading AdsMoney's storage. The container shared between the app and its Home Screen widget is a private app group readable only by AdsMoney.
• Least privilege. AdsMoney requests read-only scopes exclusively. It is technically incapable of modifying, creating or deleting anything in your Google account — no campaign, video, payment or setting.
• Secure authorisation. Google authorization uses the OAuth 2.0 authorization code flow with PKCE (S256 challenge) and a random state value verified on return, protecting the exchange against interception and cross-site request forgery. No client secret is embedded in the app, and credentials are never written to logs, analytics or crash reports.
• Prompt revocation. Disconnecting Google revokes the token with Google immediately and erases the stored authorization session from the Keychain, so the grant cannot be reused even if the device is later compromised.

Data retention and deletion

• Report data — earnings, impressions, payments and YouTube revenue — is held in memory for the current session and discarded when the app closes. Widget snapshots are overwritten on each refresh and cleared when you disconnect Google or switch accounts.
• Your Google authorization session is kept only until you disconnect Google or delete the app, so you are not asked to authorize reporting access every time you open it.
• Deleting app data takes one action: disconnect Google in the app. That revokes the grant with Google and erases the authorization session, cached widget snapshots and account selection from the device. Deleting the app removes anything that remains locally.
• App analytics is retained by Google according to the Firebase and Google Analytics retention settings and policies. Deleting the app stops future collection and removes its local app-instance data, but does not immediately remove events already processed into aggregate analytics reports. Because AdsMoney does not attach your name, email, Google account or a Firebase user ID, these events cannot be looked up using your Google identity.

Delete your data sets out the same steps on their own page, with a table of what each one removes and what it leaves behind.

Google API Services — Limited Use disclosure

AdsMoney's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google user data is used only to provide the earnings-viewing features you see in the app, is never sold, is never used for advertising targeting, is never used to develop, improve or train generalised AI or machine-learning models, and is never read by humans. AdsMoney does not transfer Google user data to any third party, and does not use or transfer it for any purpose unrelated to the earnings-viewing features described above.

Advertising

The free tier of AdsMoney shows ads supplied by Google AdMob in two places: below the summary card on the Overview screen, and above the list on the Payment history screen. An AdsMoney Pro subscription removes both. No other screen carries advertising, and the app shows no interstitial, rewarded or pop-up ad formats.

To serve these ads the Google Mobile Ads SDK processes technical and interaction data from this app — device and app information, a coarse location derived from your IP address, interaction with the ad itself, and a publisher first-party identifier that Google generates for this app. Google may use that data for ad selection, frequency capping, measurement and fraud prevention. See How Google uses information from sites or apps that use our services and first-party identifiers in AdMob.

What the ad SDK never receives: your Google account identity, OAuth token, publisher or account ID, app, ad-unit, channel or video identifiers, or any earnings, balance, payment or impression figure from your reports. Ad requests are built from device context alone. Your report data is not used to target ads, either to you or to anyone else.

No cross-app tracking. AdsMoney does not use Apple's App Tracking Transparency framework and never requests the IDFA. The publisher first-party identifier is scoped to this publisher's own apps and cannot be used to link your activity here to a third party's app or website. The app does not share data with a data broker.

Your controls. Before the first ad request, Google's User Messaging Platform determines your consent state, and that state decides whether ads are personalised. Where local law requires it — including the EEA and the UK — you are shown a consent form first, and you can reopen your choices any time from Settings → Privacy & data → Manage privacy choices. You can also opt out of first-party-ID personalisation through the controls inside any ad. Subscribing to AdsMoney Pro stops all ad requests.

Purchases

AdsMoney Pro subscriptions are processed entirely by Apple through your Apple ID. We never see your payment details. Firebase Analytics may automatically measure the subscription product identifier, name and price and associates that event only with its app-instance identifier.

Revoking access

• Disconnect Google in the app (Settings → Disconnect Google). This revokes the token with Google, clears the stored authorization session from the Keychain, and empties the widget cache and account selection from your device.
• Deleting the app removes everything listed under "What is stored on your device".
• You can additionally revoke AdsMoney's access at any time at myaccount.google.com/permissions.

Children

AdsMoney is intended for publishers managing Google advertising accounts and is not directed at children under 13.

Changes

If this policy changes, the updated version will be published at this address with a new "Last updated" date.

Contact

Questions about privacy: iambatoan@gmail.com