Amao Dash

隐私政策Privacy Policy

一、关于本政策

本隐私政策说明 Amao Dash Android 应用(下称“本应用”)如何处理与您相关的信息。“我们”指 Amao Dash 开发者,即一名独立开发者。本应用用于帮助发布商在连接自己的 Google 账号后,查看自己 Google AdMob 账号的报表数据(例如收入,以及按应用、国家/地区、广告单元等维度的细分),并提供多语言界面设置和一个明确标注为“演示模式”的功能,该模式仅显示合成的示例数据。

您使用 Google 服务时,Google 自身的条款与政策同样适用,相关链接见文末“相关 Google 政策与工具”。

二、要点概览

  • 仅在您主动选择连接账号时,申请唯一一项 Google 权限范围:AdMob 只读(admob.readonly)。
  • 通过 HTTPS 向 Google API 直接请求报表数据,并在您的设备上解析与展示。
  • 在当前构建中,报表数据本身不会被本应用写入设备存储;本地仅保存少量偏好设置(如语言、主题、所选报表周期)。
  • 开发者目前不运营用于存放本应用用户数据的服务器或用户账号数据库。
  • 应用内可能通过 Google 广告服务展示广告;Google 可能按其政策收集和处理数据(见第六节)。
  • 我们不出售本政策所述的报表数据,也不将其用于广告定向。

三、Google 账号授权

  • 当您选择连接账号时,本应用通过 Google Play 服务提供的 Google Identity 授权流程发起 OAuth 请求,申请的权限范围只有一项:https://www.googleapis.com/auth/admob.readonly(AdMob 只读)。该范围为只读,应用无法借此修改您 AdMob 账号中的数据或设置。是否授权完全由您在 Google 的界面中决定,您也可以随时撤销。
  • 授权产生的访问令牌(access token)仅保存在应用进程内存中,用于调用 Google API。本应用不会主动将令牌保存到磁盘或写入日志。断开连接或会话结束后,应用会释放其内存中的令牌。
  • Google Play 服务及相关 Google 组件可能会在设备上保存其自身的账号、服务或同意(consent)状态。这类数据由 Google 管理与控制,不属于本应用直接管理的范围。
  • 您可以随时在 Google 账号的“具有账号访问权限的第三方应用”页面查看或移除本应用的访问权限(链接见文末)。

四、报表数据的处理方式

  • 完成授权后,应用携带您的访问令牌,通过 HTTPS 直接请求 Google 的 API(googleapis.com),获取您选择的 AdMob 报表数据,例如发布商层级的指标,以及按应用、国家/地区、广告单元等维度细分的收入、展示次数、点击次数等数据。
  • 这些请求由 Google 的 AdMob API 在 Google 一侧处理,报表数据本身也来源于您的 Google AdMob 账号。也就是说,Google(AdMob)会收到相应的 API 请求,并按其自身政策处理相关数据——本应用不改变这一点。
  • 返回的数据在您的设备上解析与展示。当前版本不会将报表数据发送到开发者运营的服务器;开发者目前也没有运营此类服务器或用户账号数据库。
  • 演示模式仅显示合成的示例数据,不使用您账号中的真实数据。

五、设备上的本地存储

本应用使用 Android 标准的本地存储(SharedPreferences)保存少量偏好设置,例如:

  • 界面语言与主题;
  • 上次选择的发布商账号与报表周期;
  • 上次数据刷新时间;
  • 演示模式的开启状态(如果您使用该功能)。

在当前构建中,报表数据本身及其包含的财务数字不会被本应用持久化到设备存储;重新打开应用时,数据会重新从 Google 获取。

此外,Google Play 服务、Google Mobile Ads 及 Google 用户消息平台(UMP)等组件可能会在设备上保存其自身的标识符、广告相关状态与同意记录,具体以 Google 的政策与说明为准(链接见文末)。

在应用中断开连接,会清除应用本地的授权状态;在 Google 账号设置中移除访问权限,即可撤销对应的 OAuth 授权。

六、广告与 Google 的数据处理

为支持应用的免费使用,应用内可能通过 Google Mobile Ads 展示广告,并按要求通过 Google 用户消息平台(UMP)展示同意或选择消息。视您的选择、所在地区与适用要求以及 Google 的政策而定,Google 及其合作伙伴可能会收集和处理设备标识符(如广告 ID)、网络与 IP 信息、应用互动数据、诊断数据,以及广告与同意相关的数据。在应用发起广告请求之前,应用向 Google/UMP 发出的请求本身也可能涉及对网络信息与同意状态的处理。

  • 在展示同意消息的场景下,完成该消息流程是应用发起广告请求的前提;您也可以随时通过 Google 广告设置或设备系统设置管理广告隐私选项。
  • 本应用自身目前未启用由开发者运营的行为分析服务,也未启用 Firebase Analytics 或崩溃报告服务;Google 广告相关 SDK 自身的数据收集已在上文及 Google 政策中另行说明。
  • Google 各 SDK 如何处理数据,以 Google 的政策与披露为准(链接见文末)。

七、本应用当前不做的事

  • 不建立开发者侧的用户账号体系:您仅使用自己的 Google 账号登录,开发者不维护独立的用户数据库。
  • 不出售本政策所述的报表数据。
  • 不将您的 AdMob 报表数据用于广告定向,也不将其提供给广告商。
  • 不提供支付或订阅功能。

如果上述做法发生变化,我们会相应更新本政策。

八、安全措施

应用与 Google 之间的数据传输使用 HTTPS。访问令牌仅保留在进程内存中,本应用不会主动将其持久化或写入日志。开发者目前不运营保存您报表数据的联网存储系统。同时,任何存储与传输方式都无法保证绝对安全,建议您定期检查自己 Google 账号中的第三方访问权限。

九、未成年人

本应用是面向 AdMob 发布商的效率工具,并非专门面向儿童设计。如果您认为有未成年人在未经授权的情况下使用了发布商账号,请通过文末邮箱联系我们。

十、您的权利与选择

  • 断开连接:在应用中断开连接会清除应用本地的授权状态,此后应用不再请求您的数据。
  • 管理 Google 授权:在 Google 账号的“具有账号访问权限的第三方应用”中,可查看或移除本应用的访问权限。
  • 广告与同意选择:可通过 Google 广告设置或设备系统设置管理广告隐私选项。
  • 您的报表数据:报表数据始终保存在您的 Google(AdMob)账号中,其保留与删除由 Google 服务的规则管理;本应用无法删除您 Google 账号中的数据。卸载应用或清除应用数据,可移除本应用保存在设备上的偏好设置;Google 组件自身的状态请通过系统设置或 Google 账号页面管理。
  • 联系与请求:就本政策或您的信息如有问题或请求,请联系 lihywh@gmail.com。根据您所在的地区,您可能享有访问、更正、删除、撤回同意等权利。涉及您 Google 账号内数据的请求,我们会指引您使用 Google 提供的工具完成,因为相应数据保存在您的 Google 账号中。

十一、政策更新

本政策可能会更新。发生重大变化时,我们会以新的生效日期发布更新版本,并在可行时在应用内或本页面提示。页面顶部的生效日期即代表当前版本。

十二、联系方式

Amao Dash 开发者
邮箱:lihywh@gmail.com(该邮箱同时是 Google OAuth 授权同意页面上展示的支持邮箱)

相关 Google 政策与工具

1. About this policy

This Privacy Policy explains how the Amao Dash Android app ("the app") handles information related to you. "We" refers to the Amao Dash developer, an independent developer. The app helps publishers view reporting data from their own Google AdMob account after connecting that Google account — for example earnings and breakdowns by app, country/region, and ad unit — and offers multilingual interface settings plus a clearly labelled demo mode that shows synthetic sample data only.

When you use Google services, Google's own terms and policies also apply; see "Related Google policies and tools" at the end of this page.

2. At a glance

  • A single Google OAuth scope is requested — AdMob read-only (admob.readonly) — and only when you take action to connect.
  • Report data is requested directly from Google APIs over HTTPS, then parsed and displayed on your device.
  • In the current build, the app does not write report data itself to device storage; only small preferences are stored locally (for example language, theme, and the selected report period).
  • The developer currently operates no server and no user account database for this app's user data.
  • The app may show ads through Google's advertising services; Google may collect and process data under its policies (see section 6).
  • We do not sell the report data described in this policy, and we do not use it for advertising targeting.

3. Google account authorization

  • When you choose to connect, the app starts an OAuth flow through Google Identity services (provided via Google Play services) and requests exactly one scope: https://www.googleapis.com/auth/admob.readonly (AdMob, read-only). This scope is read-only, so the app cannot use it to change data or settings in your AdMob account. Whether to grant access is your decision, made in Google's interface, and you can revoke it at any time.
  • The access token issued by Google is kept in the app's process memory and used to call Google APIs. The app does not deliberately save the token to disk or write it to logs. When you disconnect or the session ends, the app releases its in-memory copy of the token.
  • Google Play services and related Google components may keep their own account, service, or consent state on your device. That data is managed and controlled by Google, not by this app.
  • You can review or remove the app's access at any time on the "Third-party apps with account access" page of your Google Account (link at the end of this page).

4. How report data is handled

  • After you authorize, the app calls Google's APIs (googleapis.com) directly over HTTPS, using your access token, to retrieve the AdMob reporting data you request — for example publisher-level metrics, and earnings, impressions, and clicks broken down by app, country/region, or ad unit.
  • These requests are processed on Google's side by the AdMob API, and the report data itself originates in your Google AdMob account. In other words, Google (AdMob) does receive the API requests and handles the related data under its own policies — this app does not change that.
  • Returned data is parsed and displayed on your device. The current version does not send report data to any developer-operated server, and the developer currently operates no such server or user account database.
  • Demo mode shows synthetic sample data only and does not use real data from your account.

5. Local storage on your device

The app uses Android's standard local storage (SharedPreferences) to keep a small number of preferences, for example:

  • interface language and theme;
  • the publisher account and report period you last selected;
  • the time of your last data refresh;
  • whether demo mode is enabled (if you use that feature).

In the current build, the report data itself and the financial figures it contains are not persisted to device storage by the app; when you reopen the app, data is fetched again from Google.

In addition, components such as Google Play services, Google Mobile Ads, and Google's User Messaging Platform (UMP) may store their own identifiers, ad-related state, and consent records on your device; see Google's policies and disclosures (links at the end of this page).

Disconnecting in the app clears the app's local authorization state; removing access in your Google Account settings revokes the OAuth grant.

6. Ads and Google's data processing

To keep the app free to use, the app may show ads served through Google Mobile Ads and, where required, display a consent or choices message powered by Google's User Messaging Platform (UMP). Depending on your choices, your region and applicable requirements, and Google's policies, Google and its partners may collect and process device identifiers (such as the advertising ID), network and IP information, app interaction data, diagnostics, and ad- and consent-related data. Requests the app makes to Google/UMP can themselves involve processing of network information and consent state before an ad request is made.

  • Where a consent message is shown, completing that message flow is a precondition for the app to request ads. You can also manage ad privacy choices at any time through Google Ad Settings or your device's system settings.
  • The app itself currently enables no developer-operated behavioral analytics services and no Firebase Analytics or crash reporting services; data collection by Google's advertising SDKs themselves is disclosed separately above and in Google's policies.
  • How Google's SDKs handle data is governed by Google's policies and disclosures (links at the end of this page).

7. What the app does not currently do

  • It does not build a developer-side user account system: you sign in with your own Google account, and the developer keeps no separate user database.
  • It does not sell the report data described in this policy.
  • It does not use your AdMob report data for advertising targeting, and it does not provide that data to advertisers.
  • It does not offer payments or subscriptions.

If any of these practices change, we will update this policy accordingly.

8. Security

Data in transit between the app and Google uses HTTPS. The access token is kept in process memory and is not deliberately persisted or written to logs by the app. The developer currently operates no internet-connected storage system that holds your report data. No method of storage or transmission is completely secure, so we encourage you to review the third-party access granted in your Google Account from time to time.

9. Minors

The app is a productivity tool for AdMob publishers and is not specifically directed to children. If you believe a publisher account was used by a minor without authorization, please contact us at the email at the end of this page.

10. Your rights and choices

  • Disconnect: disconnecting in the app clears the app's local authorization state, after which the app no longer requests your data.
  • Manage Google authorization: view or remove the app's access under "Third-party apps with account access" in your Google Account.
  • Ads and consent choices: manage ad privacy options via Google Ad Settings or your device's system settings.
  • Your report data: report data stays in your Google (AdMob) account; its retention and deletion are governed by the rules of Google's services. This app cannot delete data inside your Google account. Uninstalling the app or clearing its data removes the preferences the app keeps on your device; for the state kept by Google's own components, use your system settings or Google Account pages.
  • Contact and requests: for questions or requests about this policy or your information, contact lihywh@gmail.com. Depending on where you are, you may have rights such as access, correction, deletion, or withdrawal of consent. Where a request concerns data inside your Google account, we will point you to Google's tools, because that data lives in your Google account.

11. Changes to this policy

We may update this policy. For material changes we will publish an updated version with a new effective date and, where feasible, flag the change in the app or on this page. The effective date at the top of this page identifies the current version.

12. Contact

Amao Dash developer
Email: lihywh@gmail.com (this is also the support email shown on the Google OAuth consent screen)

Related Google policies and tools