Google Fit Developer Principles
As a developer of health and fitness applications and services, you often collect and manage sensitive user information like health and wellness data. Keep these key principles in mind:
- Protect users' privacy: Don't use any Fit user data for prohibited uses, like selling or using user data for advertising purposes.
- Be transparent: Accurately represent and explain to users what data you will collect, why you will collect it, and how you will use it.
- Respect users' wishes: Honor user requests to delete their data.
- Secure user data: Handle all user data securely and demonstrate you adhere to certain security practices.
- Request appropriate permissions: Don't request access to data that you don't need to provide the primary features of your application or service.
Google Fit API Services
The policy below, as well as the Google APIs Terms of Service, Google API Services User Data Policy, Google Fit Developer Terms and Conditions, Google Fit Developer Guide, and OAuth 2.0 Policies govern the use of and access to Google Fit APIs and associated Google Fit user data. You must also comply with all applicable laws and regulations. Additional policies made available by Google from time to time may apply. In the event of a conflict between this policy or any other terms with regard to accessing user data, this Developer and User Data Policy controls.
Please check back from time to time as these policies are occasionally updated. It is your responsibility to monitor and ensure your compliance with these conditions on a regular basis. If, at any time, you cannot meet these conditions (or if there is a significant risk that you will not be able to meet them), you must immediately stop using our services. We reserve the right to remove your account if you do not comply with this policy.
Appropriate Access to and Use of Google Fit APIs
Requests to access user data must be clear and understandable. Google Fit APIs may only be used in accordance with the applicable policies, terms and conditions, and for approved use cases as set forth in this Policy. This means you may only request access to permissions when your application or service meets one of the approved use cases.
Approved use cases for access to permissions are:
Applications or services designed with the primary purpose to benefit users' health and fitness via a user interface allowing users to directly journal, report, monitor, and/or analyze their physical activity, sleep, mental well-being, nutrition, health measurements, physical descriptions, and/or other health or wellness-related descriptions and measurements.
Applications or services designed with the primary purpose to benefit users' health and fitness via a user interface allowing users to sync their physical activity, sleep, mental well-being, nutrition, health measurements, physical descriptions, and/or other health or wellness-related descriptions and measurements.
Access to Google Fit APIs may not be used in violation of this Policy or other applicable Google terms and conditions or policies, including for the following purposes:
- Do not use Google Fit APIs to sell information to third parties, such as advertising platforms, data brokers, or any information resellers.
- Do not disclose information obtained through Google Fit APIs to third parties in violation of this Policy, including the Limited Uses of User Data section below.
- Do not use Google Fit APIs for applications, services, or features designed to collect or combine user data for human subjects research, medical research, or any other similar research overseen by an Institutional Review Board or Ethics Committee unless you receive prior written approval to such use from Google. Select a "Medical Research" use case during the scope access request process and you will receive additional information on how to proceed.
- Do not use Google Fit APIs for any purpose or in any manner involving Protected Health Information, as defined by the Health Insurance Portability and Accountability Act of 1996 and its implementing regulations (“HIPAA”) unless you receive prior written approval to such use from Google.
- Do not use Google Fit APIs with any product or service that may qualify as a medical device pursuant to Section 201(h) of the Federal Food Drug & Cosmetic Act if the user data will be used by the medical device to perform its regulated function.
The above is a non-exhaustive list of use cases for which Google Fit does not permit access to its APIs.
Minimum Scope Required for Access to Google Fit APIs
You may only request access to permissions that are critical to implementing your application or service's functionality. This means:
Don't request access to information that you don't need. Only request access to the narrowest permissions necessary to implement your product's features or services. If more than one permission could be used to implement a feature, you must request permissions with the least access to data or functionality. If your product does not require access to sensitive or restricted permissions, then you must not request access to these permissions. Lastly, don't use permissions that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes.
Transparent and Accurate Notice and Control
Applications and services must also request access to user data in context (via incremental auth when possible), so that users better understand what data will be provided, why you need the data, and how the data will be used. In addition to the requirements under applicable law, you must also adhere to the following requirements, which reflect our OAuth 2.0 and Google API Services User Data policies:
You must provide a disclosure of your data access, collection, use, and sharing. The disclosure:
- Must accurately represent the identity of the application or service that seeks access to user data;
- Must be within the application itself if application-based or in a separate dialog window if web-based;
- Must be displayed in the normal usage of the application if application-based or website if web-based and not require the user to navigate into a menu or settings;
- Must provide clear and accurate information explaining the types of data being accessed, requested, and/or collected;
- Must explain how the data will be used and/or shared: if you request data for one reason, but the data will also be utilized for a secondary purpose, you must notify users of both use cases;
- Cannot be included with other disclosures unrelated to personal and sensitive data collection.
Your disclosure must accompany and immediately precede a request for user consent. You must not begin collection prior to obtaining affirmative consent. The request for consent:
- Must present the consent dialog in a clear and unambiguous way;
- Must require affirmative user action (for example, tap to accept, tick a check-box, a verbal command, etc.) in order to accept;
- Must not interpret navigation away from the disclosure (including tapping away or pressing the back or home button) as consent; and,
- Must not utilize auto-dismissing or expiring messages.
Limited Uses of User Data
Upon accessing Google Fit APIs for an appropriate use, your use of the data obtained must comply with the below requirements. These requirements apply to sensitive and restricted permissions, the raw data obtained from Google Fit APIs, and data aggregated, anonymized, de-identified, or derived from the raw data.
- Limit your use of user data to providing or improving your appropriate use case or features that are visible and prominent in the requesting application's user interface.
- Only transfer user data to third parties:
- To provide or improve your appropriate use case or features that are clear from the requesting application's user interface;
- If necessary for security purposes (for example, investigating abuse);
- To comply with applicable laws; or,
- As part of a merger, acquisition or sale of assets of the developer after obtaining explicit prior consent from the user.
- Do not allow humans to read user data, unless:
- The user's explicit consent to read specific data (for example, helping a user re-access the product or a service after having lost their password) is obtained;
- It’s necessary for security purposes (for example, investigating abuse);
- To comply with applicable laws; or,
- The data (including derivations) is aggregated and anonymized and used for internal operations in accordance with applicable privacy and other jurisdictional legal requirements.
All other transfers, uses, or sale of user data is completely prohibited, including:
- Transferring or selling user data to third parties like advertising platforms, data brokers, or any information resellers.
- Transferring, selling, or using user data for serving ads, including personalized or interest-based advertising.
- Transferring, selling, or using user data to determine credit-worthiness or for lending purposes.
- Transferring, selling, or using the user data with any product or service that may qualify as a medical device pursuant to Section 201(h) of the Federal Food Drug & Cosmetic Act if the user data will be used by the medical device to perform its regulated function.
- Transferring, selling, or using user data for any purpose or in any manner involving Protected Health Information (as defined by HIPAA) unless you receive prior written approval to such use from Google.
Secure Data Handling
You must handle all user data securely. Take reasonable and appropriate steps to protect all applications or systems that make use of Google Fit API Services against unauthorized or unlawful access, use, destruction, loss, alteration, or disclosure.
Applications accessing restricted permissions must demonstrate that they adhere to certain security practices. Recommended security practices include implementing and maintaining an Information Security Management System such as outlined in ISO/IEC 27001 and ensuring your application or web service is robust and free from common security issues as set out by the OWASP Top 10.
Required security measures include:
- Using an industry accepted encryption standard to encrypt user data that is:
- Stored on portable devices or portable electronic media;
- Maintained outside of Google's or your systems;
- Transferred across any external network not solely managed by you; and,
- At rest on your systems.
- Transmitting data using secure modern protocols (for example, over HTTPS).
- Keeping user data and credentials, specifically tokens such as OAuth access and refresh tokens, encrypted at rest.
- Ensuring keys and key material are managed appropriately, such as stored in a hardware security module or equivalent-strength key management system.
Your application or service must also pass an annual security assessment and obtain a Letter of Assessment from a Google-designated third party if your product transfers data off the user's own device.
European Data Transfers
If you access, use, or process personal information made available by Google that directly or indirectly identifies an individual and that originated in the European Union, UK, or Switzerland (“EU Personal Information”), then you must:
- Comply with all applicable privacy, data security, and data protection laws, directives, regulations, and rules;
- Access, use, or process EU Personal Information only for purposes that are consistent with the consent obtained from the individual to whom the EU Personal Information relates;
- Implement appropriate organizational and technical measures to protect EU Personal Information against loss, misuse, and unauthorized or unlawful access, disclosure, alteration and destruction; and,
- Provide the same level of protection as is required by the Privacy Shield Principles.
You must monitor your compliance with these conditions on a regular basis. If, at any time, you cannot meet these conditions (or if there is a significant risk that you will not be able to meet them), you must immediately notify us by email to firstname.lastname@example.org, stop processing EU Personal Information or take reasonable and appropriate steps to restore an adequate level of protection.