Sia Makerlab
홈회사소개서비스포트폴리오공지사항문의하기

© since 2025 Sia Makerlab. All rights reserved.

사업자등록번호: 649-11-03282 | 대표: 이장욱

통신판매업신고번호: 제2025-충북제천-0264호

AdMob Monitor Dashboard

개인정보처리방침

Sia Makerlab 제품 포트폴리오 통합 페이지에서 제공하는 개인정보처리방침입니다.

개인정보처리방침v1.1

Privacy Policy

Last Updated: May 25, 2026

Effective Date: May 25, 2026

Revision: 1.1

Revision History

VersionDateChanges
1.1May 25, 2026Added in-app advertising disclosures (AdMob Adaptive Banner, App Open, Native), Google UMP SDK EU consent flow, Advertising ID processing; refreshed feature/data inventory (8 metrics, 5 preset ranges, sparkline trends, 4-tab app detail, 3 widget sizes, 5 notification types, cache-first 1h sync, single-entry-point safe sign-out clearing all on-device data).
1.0May 22, 2026Initial release

1. Introduction

This Privacy Policy describes how Sia Makerlab ("we," "us," or "our") collects, uses, and shares information in connection with your use of the AdMob Monitor Dashboard mobile application (the "App").

By downloading, installing, or using the App, you agree to the collection and use of information in accordance with this Privacy Policy. If you do not agree with this Privacy Policy, please do not use the App.

The App is a read-only client for the Google AdMob API and is not affiliated with, endorsed by, or sponsored by Google LLC. Google AdMob is a trademark of Google LLC.

2. Information We Collect

2.1 Information You Provide

The App requires you to sign in to your Google account that has access to AdMob in order to read AdMob data. We do not collect or store your Google account credentials. Sign-in is handled by Android's Credential Manager and Google's OAuth 2.0 flow.

After sign-in, the App stores the resulting OAuth access token and refresh token on your device only. These tokens are:

  • Encrypted with Tink AEAD using a key bound to the Android Keystore
  • Stored via Jetpack DataStore in the App's private storage
  • Never transmitted to any server we operate
  • Used exclusively to call the Google AdMob API on your behalf

We do not collect:

  • Your Google account email or display name (used only at runtime by Credential Manager and not persisted by us beyond the OAuth tokens above)
  • Names, phone numbers, or physical addresses
  • Payment information

2.2 Information Collected Automatically

2.2.1 Local Device Storage

The App stores the following data locally on your device only:

DataStoredPurpose
OAuth tokensDevice only, encryptedAuthentication with Google AdMob API
AdMob account, app, ad unit, mediation metadataDevice only, Room databaseDisplay dashboard, per-app detail, and mediation tabs
AdMob report data (8 metrics over up to 30 days: earnings, impressions, clicks, CTR, requests, match rate, RPM, eCPM)Device only, Room databaseDisplay dashboard, sparkline trends, app detail, and widgets
Widget configurationsDevice only, Room databaseRender the three home screen widgets (1×1 today earnings, 2×1 day-over-day, 2×2 key metrics)
API call logs (request/response metadata used for in-app diagnostics)Device only, Room databaseDiagnose sync issues in the Advanced section
App settings (theme, dynamic color, sync interval, alarm thresholds, biometric unlock, hide-earnings toggle, last-sync timestamp)Device only, DataStorePersonalize the App
UMP consent state (EU/UK/Switzerland users)Device only, managed by Google UMP SDKRemember your ad-personalization choice across sessions

This data is stored exclusively on your device. We do not have access to this data and it is never transmitted to our servers. The App ships with allowBackup="false" so Android Auto Backup will not copy this data to Google Drive.

When you sign out of the App, a single SignOutUseCase cancels background sync, deletes the entire local database (accounts, apps, ad units, report metrics, mediation, ad source, adapter, mapping, campaign report, widget configurations, and API logs), resets the LAST_SYNC_AT timestamp, clears OAuth tokens and Credential Manager state, and re-renders the home screen widgets to an empty state. Device-level preferences such as theme and notification toggles are preserved.

2.2.2 Network Communication

The App communicates over HTTPS with:

  • Google Identity / OAuth servers — to complete the OAuth 2.0 sign-in flow and refresh expired tokens
  • admob.googleapis.com — to call the Google AdMob API with the admob.readonly and admob.report scopes
  • Google Mobile Ads / AdMob serving infrastructure — to request and display the in-app ads described in §2.3
  • Google Play UMP SDK endpoints (EU / UK / Switzerland users only) — to retrieve and record consent state

NetworkSecurityConfig disables cleartext traffic. The App does not communicate with any servers operated by Sia Makerlab.

2.2.3 OAuth Scopes Used

ScopePurpose
https://www.googleapis.com/auth/admob.readonlyRead AdMob account, app, ad unit, and mediation metadata
https://www.googleapis.com/auth/admob.reportRead AdMob report data (earnings, impressions, clicks, CTR, requests, match rate, RPM, eCPM)

These are read-only scopes. The App cannot create, modify, or delete any AdMob configuration. A BuildConfig.ENABLE_WRITE_API flag exists in source code and is permanently set to false for release builds, blocking any write API path at compile time.

2.3 In-App Advertising

To support free distribution, the App displays Google AdMob advertisements in the following three placements:

PlacementFormatNotes
Bottom adaptive bannerBanner (anchored adaptive)A single shared instance that re-sizes for foldables and multi-window
App Open adFull-screenShown at most once every 15 minutes on cold/warm resume; foldable letterbox guard
Native adIn-list nativeInserted into the 5th and 10th positions of the Apps list

Ad delivery is handled by Google's Mobile Ads SDK (GMA). To deliver and measure ads, the GMA SDK and Google may process information such as:

  • Android Advertising ID — a user-resettable identifier provided by the operating system
  • Coarse device and ad-request signals (device type, screen size, locale, app/SDK version)
  • General location derived from IP address
  • Ad interaction events (impressions, clicks)

We do not directly receive or store this information. It is processed by Google in accordance with the Google Privacy Policy and the Google Ads / AdMob Data Disclosures.

2.3.1 EU / UK / Switzerland Consent (UMP)

For users in the European Economic Area, the United Kingdom, and Switzerland, the App integrates the Google User Messaging Platform (UMP) SDK to present a Google-certified consent message before personalized ads are loaded. Your choices are stored by the UMP SDK on your device and respected across sessions.

  • If you grant consent, the App may load personalized ads.
  • If you decline consent, the App falls back to non-personalized ads.
  • You can revisit your consent choice from the App's Settings → Privacy section at any time.

2.3.2 Children's Advertising

The App is intended for adult AdMob publishers (see §8) and is not tagged for child-directed treatment.

2.4 Permissions

The App requests the following Android permissions:

INTERNET

Required to communicate with the Google AdMob API and to load ads. The App does not connect to any other endpoint outside Google's infrastructure.

POST_NOTIFICATIONS (Android 13+)

Required to display the five notification types described in §3.1 (daily summary, earnings drop, match-rate drop, zero impressions, sync failure). This permission is requested only when you opt in to notifications.

ACCESS_NETWORK_STATE

Required so background sync (WorkManager) waits for an available connection before calling the AdMob API.

AD_ID (Android 13+)

Required to access the Android Advertising ID for ad personalization, subject to your device-level "Reset advertising ID" / "Delete advertising ID" choice and any consent you provide via the UMP form (§2.3.1).

2.5 Information We Do NOT Collect

We explicitly do not collect:

  • Personal information beyond the OAuth tokens and locally stored data described above
  • Precise location (GPS) data
  • Contacts, photos, files, or media
  • Browsing history
  • Analytics or telemetry of any kind operated by Sia Makerlab

The Android Advertising ID and ad-request signals described in §2.3 are processed by Google's Mobile Ads SDK, not by Sia Makerlab.

3. How We Use Information

3.1 Local Data Usage

Locally stored data is used solely to:

  • Authenticate with the Google AdMob API on your behalf
  • Display your AdMob metrics, sparkline trends, app detail, and Top Apps in the App
  • Render the three home screen widgets (Jetpack Glance) with the latest cached values
  • Send the five notification types you've enabled (daily summary, earnings drop, match-rate drop, zero impressions, sync failure)
  • Auto-sync your data every hour through WorkManager when you are signed in
  • Remember your preferences and settings

3.2 Third-Party Data Usage

The Google AdMob API governs how data fetched from your AdMob account is handled by Google. The App fetches and caches this data on your device only.

The Google Mobile Ads SDK and Google's ad serving infrastructure govern how ad-request signals (§2.3) are processed by Google.

4. Data Sharing and Disclosure

4.1 We Do Not Sell Your Data

We do not sell, trade, or rent your information to third parties. We do not have access to your AdMob data and do not directly receive ad-request signals.

4.2 Third-Party Services

The App integrates the following Google services:

ServicePurposePrivacy Policy
Google Identity / Credential ManagerOAuth 2.0 sign-inhttps://policies.google.com/privacy
Google AdMob APIRead AdMob account and report datahttps://policies.google.com/privacy
Google Mobile Ads SDK (AdMob)Serve in-app ads (Banner / App Open / Native)https://policies.google.com/privacy
Google User Messaging Platform (UMP) SDKCapture and store EU/UK/Switzerland ad-personalization consenthttps://policies.google.com/privacy

4.3 Legal Requirements

We may disclose information if required to do so by law or in response to valid requests by public authorities. As we do not collect or store data on our servers, we have nothing to disclose other than what is described in this policy.

5. Data Retention

5.1 Local Data

Data stored locally on your device remains until you:

  • Sign out within the App — the SignOutUseCase cancels background sync and deletes the entire local database, OAuth tokens, last-sync timestamp, and Credential Manager state, then re-renders the widgets to an empty state
  • Clear the App's data through device settings
  • Uninstall the App

5.2 Token Revocation

You may revoke the App's access to your Google account at any time at https://myaccount.google.com/permissions. Revoking access invalidates the stored OAuth tokens.

5.3 Advertising ID

You can reset or delete your Android Advertising ID at any time via your device's Settings → Google → Ads. EU / UK / Switzerland users can additionally re-open the UMP consent form from the App's Settings → Privacy section.

6. Your Rights and Choices

6.1 For All Users

You have the right to:

  • Access: View your locally stored data within the App
  • Delete: Sign out, clear app data, or uninstall the App to remove all local data
  • Revoke OAuth: Revoke Google account access through your Google Account settings
  • Control ad personalization: Reset/delete your Android Advertising ID via device settings

6.2 For Users in the EEA, United Kingdom, and Switzerland

Under GDPR and applicable laws, you have additional rights including the right to access, rectification, erasure, restrict processing, data portability, object, and withdraw consent. You can revisit and change your ad-personalization consent at any time via the App's Settings → Privacy section (UMP form). To exercise these rights regarding data held by Google, please contact Google directly.

6.3 For California Residents (CCPA/CPRA)

California residents have the right to know, access, delete, and opt out of the sale or sharing of personal information. We do not sell personal information as defined by the CCPA/CPRA. Information processed by Google's Mobile Ads SDK for ad delivery is subject to Google's own disclosures.

7. Data Security

We implement the following security measures:

  • OAuth tokens are encrypted with Tink AEAD bound to the Android Keystore
  • All network communication uses HTTPS only (cleartext disabled via NetworkSecurityConfig)
  • The App does not run an Android Auto Backup (allowBackup="false", data-extraction rules block token/DB backup)
  • Write APIs are blocked at compile time via BuildConfig.ENABLE_WRITE_API=false
  • Optional biometric unlock and hide-earnings toggles are available in Settings → Security
  • No data is transmitted to servers operated by Sia Makerlab

8. Children's Privacy

The App is intended for adult publishers managing AdMob accounts and is not directed to children under the age of 13 (or 16 in the EEA). We do not knowingly collect information from children, and the App is not tagged for child-directed ad treatment.

9. International Data Transfers

Data fetched from the Google AdMob API, processed by the Google Mobile Ads SDK, or stored by the UMP SDK may be transferred to and processed in countries where Google operates. Please refer to Google's Privacy Policy for more information.

10. Third-Party Links and Services

The App may contain links to third-party websites or services (such as the Google AdMob Help Center). We are not responsible for the privacy practices of these third parties.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by updating the "Last Updated" date and displaying a notice within the App for material changes.

12. Disclaimer of Liability

12.1 Third-Party Services

We are not responsible for the data collection, use, or security practices of Google's AdMob API, Google Identity services, Google Mobile Ads SDK, or the UMP SDK.

12.2 Data Loss

We are not responsible for any loss of locally stored data on your device.

12.3 Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, WE SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES RESULTING FROM YOUR USE OF THE APP.

13. Governing Law

This Privacy Policy shall be governed by the laws of the Republic of Korea. For EU users, it shall be interpreted in accordance with applicable EU law including the GDPR.

14. Contact Us

Sia Makerlab

  • Email: sia@siamakerlab.com
  • Website: https://siamakerlab.com

For GDPR-related inquiries from EEA residents, please include "GDPR Request" in the subject line.


Summary of Data Practices

Data TypeCollectedStoredSharedPurpose
OAuth tokensYesDevice only, encryptedNoGoogle AdMob API authentication
AdMob report data (8 metrics, up to 30 days)Yes (from your AdMob account)Device onlyNoDisplay dashboard, sparklines, app detail, widgets
Widget configurations / API logsYesDevice onlyNoRender widgets, in-app diagnostics
App settingsYesDevice onlyNoPersonalization
Android Advertising IDProcessed by Google Mobile Ads SDKManaged by GoogleProcessed by Google for ad deliveryIn-app ad personalization (subject to UMP consent in EU/UK/CH)
UMP consent stateYes (EU/UK/CH users)Device only, managed by UMP SDKNoRemember ad-personalization choice
Personal info (name, email, phone, address)NoN/AN/AN/A
Precise locationNoN/AN/AN/A

This Privacy Policy is available in English. If translated versions are provided, the English version shall prevail in case of any discrepancy.

AdMob Monitor Dashboard 제품 페이지로 돌아가기