Repository navigation
name google calendar and contacts in the privacy policy - #100
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The privacy policy's Google Workspace section now names Google Calendar and Google Contacts beside Gmail, Drive, Docs, Sheets and Slides. It also covers calendars, events and contacts among the data accessed, and inviting guests and answering invitations among the actions taken on the person's behalf. This is for the Calendar and Contacts scopes the Google connection asks for in #99: Google's verification reads the published page, so it has to match the scopes before the demo video is recorded. Nothing else changes, and the effective date is already today's.
Open workspace in Conductor