Last modified: October 19, 2020
By using this API, you consent to be bound by these terms, the Google Fit Developer and User Data Policy, 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.
Third-Party Brand Features
These terms do not grant you any right, title, interest in or to another party's trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of any third party ("Third Party Brand Features"). If you would like to use any Third Party Brand Features, you are responsible for obtaining the necessary rights, licenses, or permissions.
Location
You are responsible for obtaining all licenses, permissions, and user consents needed to view, collect, store, or otherwise use location data in connection with Google Fit.
HIPAA Use Limitations
Google Fit is not intended to be a medical device. Unless otherwise specified in writing by Google, Google does not intend uses of Google Fit to create obligations under the Health Insurance Portability and Accountability Act, as amended (“HIPAA”). Google makes no representations that Google Fit satisfies HIPAA requirements. If you are or become a Covered Entity or Business Associate under HIPAA, you agree not to use Google Fit for any purpose or in any manner involving Protected Health Information (as defined by HIPAA) unless you receive prior written consent to such use from Google. You acknowledge that upon discovery of a violation of this provision, Google may terminate your use of Google Fit. You are solely responsible for any applicable compliance with HIPAA and agree to hold Google harmless for any uses contrary to this provision.
Content Management
You are responsible for the accuracy of the content you provide to Google Fit is reasonably accurate and that you have stored that content appropriately in Google Fit.
If your API Client accesses content from the com.google namespace of Google Fit and your API Client also collects content that could be appropriately stored on the com.google namespace, then you agree to the following:
- Your API Client will store on the com.google namespace all the content that your API Client collects and that may be appropriately stored in the com.google namespace.
- The content your API Client stores in the com.google namespace will be of at least the same level of granularity as the content accessed by your API Client. For example, if your API Client accesses step count from Google Fit on a per-day basis, then your API Client should also store step count on Google Fit on a per- day basis, rather than per week or per month.
- You are responsible for backing up your content. Google reserves the right to set limits on the length of time content may be accessible on Google Fit.