Effective date: 28 October 2026.
This policy describes the AdMob Revenue integration used by an AdMob account owner and their authorized dashboard administrators for internal app revenue reporting.
Google data accessed
With the account owner's consent, the integration requests the Google permission https://www.googleapis.com/auth/admob.readonly.
The integration reads AdMob account information, including publisher identifier, reporting currency and time zone; app identifiers and names; and Network or Mediation reports for the requested dates and apps. Report data can include estimated earnings, impressions, clicks, CTR, eCPM, ad requests, matched requests and other supported reporting metrics.
The AdMob integration does not request access to Gmail, Google Drive or Google account passwords. It does not read browser cookies to obtain access to AdMob.
Purpose and use
The integration uses Google data to display the account owner's requested reports, app filters, totals and charts in the private dashboard. AdMob earnings are estimates and are not a statement of final payable earnings.
This integration does not use AdMob report data for advertising targeting or to train AI models. Its reporting flow does not send AdMob report data to an AI service.
Storage and protection
Google OAuth credentials are stored on the account owner's Windows reporting server and protected with Windows DPAPI for the Windows account running the reporting service. The dashboard backend stores a separate bridge API key used to request reports over HTTPS. That bridge key is not a Google token and is not sent to the dashboard browser.
Reports may be cached temporarily in the reporting process's memory to reduce repeated requests. The AdMob reporting flow currently does not persist report rows to the dashboard database. Loaded reports can also remain in the administrator's browser memory while the page is open.
Operational logs and server backups may contain service metadata or configuration. Server administrators control access, retention and removal of these records. Configuration backups containing credentials must be protected as confidential information.
Data recipients
Google processes authorization and AdMob API requests. The account owner's Windows reporting server and dashboard backend process the requested reports, and authorized dashboard administrators can view them.
The integration does not sell AdMob data or make account reports publicly accessible. Public information pages do not contain account reports, publisher identifiers, API keys or OAuth tokens.
Revocation and deletion
The account owner can revoke the application's access in their Google Account connections. Revocation prevents future Google API access once existing access is no longer valid; it does not erase information already displayed or retained elsewhere.
To disconnect the dashboard or request removal of locally stored OAuth credentials, bridge keys, configuration backups or operational records, contact the service administrator at support@lusinterlogi.asia. The administrator must remove those items from the relevant servers and backups according to the account owner's instructions. The tool does not delete or change data in the AdMob account.
Changes and contact
Changes to this integration's data handling will be reflected in this policy. For privacy questions or support, contact support@lusinterlogi.asia.