Apple App Store 的資料揭露規定
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Apple 規定，在 App Store 發布應用程式的開發人員，須揭露與該應用程式資料使用相關的特定資訊。Apple 宣布自 2020 年 12 月 8 日起，新應用程式和應用程式更新必須提供這類揭露聲明。本指南說明截至 7.68.0 版為止，Google Mobile Ads SDK 的資料收集做法，協助 Ad Manager 開發人員回答 App Store Connect 中的問題。
為提升 Ad Manager 成效，Google Mobile Ads SDK 可能會收集應用程式的特定資訊，包括：
- IP 位址，可能會用於預估裝置的大概位置。
- 與使用者無關的當機記錄，可能會用於診斷問題及改良 SDK。診斷資訊也可能用於廣告和分析。
- 與使用者相關的成效資料 (例如應用程式啟動時間、停止回應率或能源用量)，可能會用於評估使用者行為、瞭解現有產品功能的成效，以及規劃新功能。成效資料也可能用於顯示廣告，包括分享給顯示廣告的其他實體。
- 裝置 ID，例如裝置的廣告 ID 或其他應用程式/開發人員限定裝置 ID，可能用於第三方廣告和分析。
- 廣告資料 (例如使用者看過的廣告)，可能會用來支援分析和廣告功能。
- 其他使用者產品互動 (例如輕觸啟動應用程式)，以及互動資訊 (例如影片觀看次數)，可能會用於提升廣告成效。
如果您有任何選用的產品功能涉及額外資料 (例如進階報表資料)，或是參與的新產品功能測試涉及額外資料，請務必確認這些功能或測試是否需要揭露額外資料。
如果您使用的是舊版 Google Mobile Ads SDK，建議更新至最新版本，確保您應用程式的揭露資料正確無誤。
Google Mobile Ads SDK 會持續更新。本文將反映這些異動，請務必返回瀏覽，並視需要更新揭露聲明。
Apple 的隱私權資訊清單檔案
Google Mobile Ads SDK 11.2.0 以上版本，支援隱私權資訊清單聲明。您有責任檢查隱私權資訊清單，並確保應用程式的資料揭露資訊為最新狀態。如要進一步瞭解如何解讀隱私權報告，以及應用程式提交的相關規範，請參閱 Apple 說明文件及其執行政策更新。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-27 (世界標準時間)。
[null,null,["上次更新時間：2025-08-27 (世界標準時間)。"],[[["\u003cp\u003eStarting December 8, 2020, Apple requires developers to disclose data collection practices for apps on the App Store.\u003c/p\u003e\n"],["\u003cp\u003eThis guide outlines the data the Google Mobile Ads SDK may collect to help developers comply with Apple's requirements.\u003c/p\u003e\n"],["\u003cp\u003eCollected data may include IP address, crash logs, performance data, device IDs, advertising data, and user interactions.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers should check for additional disclosures if using optional features or participating in new product feature tests.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Mobile Ads SDK supports privacy manifest declarations from version 11.2.0 onwards.\u003c/p\u003e\n"]]],["Apple mandates developers disclose app data usage, effective December 8, 2020. The Google Mobile Ads SDK collects data like IP addresses for location estimation, crash logs for SDK improvement, user performance data for product development and ad targeting, device IDs for advertising and analytics, and user interactions for improved advertising. Developers must ensure their app data disclosures remain accurate and updated. SDK version 11.2.0+ supports privacy manifest declarations. Xcode 16 might show irrelevant `Upload Symbols Failed` warnings. The table indicates the third-party SDKs with a privacy manifest.\n"],null,["# Apple App Store's data disclosure requirements\n\nSelect platform: [iOS](/ad-manager/mobile-ads-sdk/ios/privacy/data-disclosure \"View this page for the iOS platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/privacy/data-disclosure \"View this page for the Unity platform docs.\")\n\n\u003cbr /\u003e\n\nApple requires that developers publishing apps on the App Store disclose\n[certain information](//developer.apple.com/app-store/app-privacy-details/)\nregarding their apps' data use. Apple has\n[announced](//developer.apple.com/news/?id=vlj9jty9) that these disclosures will\nbe required for new apps and app updates starting December 8, 2020. This guide\nexplains the\n\nGoogle Mobile Ads SDK\n\n's data collection practices as of\n7.68.0, to make it easier for Ad Manager\ndevelopers to answer the questions in App Store Connect.\n\nTo improve the performance of Ad Manager, the\n\nGoogle Mobile Ads SDK\n\nmay collect\ncertain information from apps, including:\n\n- IP address, which may be used to estimate the general location of a device.\n- Non-user related crash logs, which may be used to diagnose problems and improve the SDK. Diagnostic information may also be used for advertising and analytics purposes.\n- User-associated performance data such as app launch time, hang rate, or energy usage, which may be used to evaluate user behavior, understand the effectiveness of existing product features, and plan new features. Performance data may also be used for displaying ads, including sharing with other entities that display ads.\n- A Device ID, such as the device's advertising identifier or other app- or developer-bounded device identifiers, which may be used for the purpose of third-party advertising and analytics.\n- Advertising data, such as advertisements the user has seen, may be used to power analytics and advertising features.\n- Other user product interactions like app launch taps, and interaction information, like video views, may be used to improve advertising performance.\n\nIf you are using any optional product features that involve additional data\n(such as advance reporting) or participating in any tests of new product\nfeatures that involve additional data, be sure to check if those features or\ntests require additional data disclosures.\n\nIf you are using a prior version of the\n\nGoogle Mobile Ads SDK\n\n, consider\nupdating to the latest version to ensure your app's disclosures are accurate.\nThe\n\nGoogle Mobile Ads SDK\n\nwill continue to be updated over time. This\narticle will reflect these changes, so make sure to check back and update your\ndisclosures as necessary.\n\nApple's privacy manifest files\n------------------------------\n\n\nGoogle Mobile Ads SDK\n\nversion 11.2.0 and higher supports\nprivacy manifest declarations. You are responsible for checking the privacy\nmanifest and ensuring that your application's data disclosures are up to date.\nRefer to\n[Apple documentation](//developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)\nfor details on interpreting a privacy report and their [enforcement update](//developer.apple.com/news/?id=pvszzano) for app submission requirements."]]
