Upcoming change to the Google Fit API's

[keptenkurk]

Announcement by Google they will update their Google Fit API's. To be investigated and changed before april 2021:

We are writing to let you know about the key improvements to Google Fit APIs as well as an updated Developer & User Data policy. These changes are part of our ongoing efforts to enhance the security and privacy of Google Fit data for users and developers.

We’re reaching out to you because our records indicate that you’ve used the Google Fit APIs.

What do I need to know?
We’ve updated Google Fit’s Developer & User Data policy, aligned with this policy, we’re making the following changes to the Fit APIs:

Separating scopes for read and write access
Adding separate scopes for heart rate
Adding separate scopes for sleep and a new sleep stage data type
Increasing clarity around sessions access versus data access
Strengthening the review system for apps using Google Fit, and updating the classification of all Google Fit API scopes for Write access to ‘sensitive’, and all scopes for Read access to ‘restricted.’
Timeline for these changes and their enforcement:
Starting October 19, 2020, you can begin making changes to your apps and services, based on the policy and API changes. Please note that for your existing apps/services, you have until policy enforcement begins to go through OAuth verification for current scopes, or for additional relevant scopes listed above (heart rate and sleep).
By April 27, 2021, the policy will become enforceable and all app changes must be completed and rolled out.
You will be contacted by our Trust and Safety team at least a month in advance of your review and, at that time, they will share more details on the enhanced verification process

This issue serves as a reminder.