Episode 178 — Google, Third Party Apps, and Data Privacy: a calendar scheduling example

Data Privacy Detective

Calendar scheduling—it can be simplified with third-party apps that schedule meeting times without a lot of back and forth. But third-party apps that do such scheduling entail significant privacy risks and choices. Using Calendly as an example, we explore in Episode 178 what happens when we allow a third-party app to connect through our IT platform, in this case that of Google. Google provides ample information and details about allowing third-party apps to connect through a Google sign-in. https://support.google.com/accounts/answer/13533235?hl=en It warns about the risks and encourages users to check out the websites and privacy choices of the app provider before syncing it with Google. Consider Google’s advice about granting permission to third-party apps, including the need to review how the third party will collect, share, use, and have the ability to delete data held within Google. Using Calendly’s April 15, 2024 Privacy Notice as an example, we explore the extent to which a third party app can receive, share, use, and delete data that reaches beyond the core function of the app’s basic purpose. Learn how the current data environment is not one of privacy by design and how third-party apps represent the spread of personal data beyond what we may assume. The first 155 episodes of Data Privacy Detective can be found on the feed of the Frost Brown Todd Podcast. You can listen on Apple Podcasts (https://apple.co/3IrHUTg), Spotify (https://bit.ly/49XRU2k), or Soundcloud (https://bit.ly/3T8EWrw).