Policy requirements for Google Mobile Developer Services
Stay organized with collections
Save and categorize content based on your preferences.
By enabling Google Mobile Developer Services you enable the collection of
data about your traffic, including via
identifiers for
mobile devices (including Android Advertising ID and Advertising
Identifier for iOS), cookies and similar technologies.
You will not facilitate the merging of personally-identifiable information
with non-personally identifiable information collected through any Google
product or feature unless you have robust notice of, and the user's prior
affirmative (i.e., opt-in) consent to, that merger.
You are required to notify your visitors by disclosing the following
information in your privacy policy:
- The Google Mobile Developer Services you've implemented.
- How you and third-party vendors use first-party cookies or other
first-party identifiers, and third-party cookies (such as identifiers for
mobile devices (including Android Advertising ID and Advertising Identifier
for iOS), cookies and similar technologies) or other third-party
identifiers together.
- How visitors can opt-out of Google Mobile Developer Services you use,
including through applicable device settings, such as the device advertising
settings for mobile apps, or any other available means.
European Union User Consent Policy
You must also comply with the
European
Union User Consent Policy.
Personalized advertising
If you use Google Mobile Developer Services to collect sensitive information
about your visitors, as described in the
Google
AdWords sensitive category restrictions, you may not use Google Mobile
Developer Services to collect data for the purpose of personalized advertising, formerly known as
interest-based advertising.
Because laws across countries and territories vary, and because Google
Mobile Developer Services can be used in many ways, Google is unable to
provide the exact language you need to include in your privacy policy. Only
you understand the unique aspects and special considerations of your
business, and your privacy policy should account for this information that
only you can provide.
This policy was last updated 2015-09-01.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eEnabling Google Mobile Developer Services allows the collection of user traffic data, including mobile device identifiers, cookies, and similar technologies.\u003c/p\u003e\n"],["\u003cp\u003eYou must obtain explicit user consent before merging personally-identifiable information with non-personally identifiable information collected through Google products.\u003c/p\u003e\n"],["\u003cp\u003eYour privacy policy must disclose the implemented Google Mobile Developer Services, how first and third-party identifiers are used, and how users can opt-out.\u003c/p\u003e\n"],["\u003cp\u003eYou must comply with the European Union User Consent Policy and refrain from using Google Mobile Developer Services for personalized advertising if collecting sensitive user data.\u003c/p\u003e\n"],["\u003cp\u003eGoogle provides guidelines but emphasizes that your privacy policy should reflect the specific nuances of your business and legal obligations.\u003c/p\u003e\n"]]],[],null,["# Policy requirements for Google Mobile Developer Services\n\nBy enabling Google Mobile Developer Services you enable the collection of\ndata about your traffic, including via\n[identifiers for\nmobile devices](http://www.google.com/policies/technologies/ads/) (including Android Advertising ID and Advertising\nIdentifier for iOS), cookies and similar technologies.\n\nYou will not facilitate the merging of personally-identifiable information\nwith non-personally identifiable information collected through any Google\nproduct or feature unless you have robust notice of, and the user's prior\naffirmative (i.e., opt-in) consent to, that merger.\n\nYou are required to notify your visitors by disclosing the following\ninformation in your privacy policy:\n\n1. The Google Mobile Developer Services you've implemented.\n2. How you and third-party vendors use first-party cookies or other first-party identifiers, and third-party cookies (such as identifiers for mobile devices (including Android Advertising ID and Advertising Identifier for iOS), cookies and similar technologies) or other third-party identifiers together.\n3. How visitors can opt-out of Google Mobile Developer Services you use, including through applicable device settings, such as the device advertising settings for mobile apps, or any other available means.\n\nEuropean Union User Consent Policy\n----------------------------------\n\nYou must also comply with the\n[European\nUnion User Consent Policy](http://www.google.com/about/company/user-consent-policy.html).\n\nPersonalized advertising\n------------------------\n\nIf you use Google Mobile Developer Services to collect sensitive information\nabout your visitors, as described in the\n[Google\nAdWords sensitive category restrictions](https://support.google.com/adwordspolicy/answer/143465#sensitive), you may not use Google Mobile\nDeveloper Services to collect data for the purpose of personalized advertising, formerly known as\ninterest-based advertising.\n\nBecause laws across countries and territories vary, and because Google\nMobile Developer Services can be used in many ways, Google is unable to\nprovide the exact language you need to include in your privacy policy. Only\nyou understand the unique aspects and special considerations of your\nbusiness, and your privacy policy should account for this information that\nonly you can provide.\n\nThis policy was last updated 2015-09-01."]]
