RTMP LiveOps

Privacy Policy

This page explains what Google user data RTMP LiveOps requests, why it is requested, how it is used and stored, and how a contractor can disconnect it at any time.

What Google data we request

When a contractor connects their Google account to LiveOps, we request:

• The list of calendars the contractor is subscribed to in Google Calendar.
• Read access to the events on those calendars.

Why we request it

LiveOps uses this information so a contractor's own personal availability can be shown alongside RTMP show schedules. This helps RTMP staff avoid scheduling a contractor against a conflict that already exists on their personal calendar.

Access is read-only

LiveOps only reads calendar and event data for this purpose. LiveOps never creates, edits, or deletes events in a contractor's Google Calendar.

Where the data is stored

Calendar data retrieved from Google is stored in LiveOps' own database, associated with that contractor's profile. The Google OAuth tokens used to access this data are stored encrypted at rest.

We never sell or share this data

Google user data obtained through LiveOps is never sold, and it is never shared with third parties.

How to disconnect

A contractor can disconnect Google Calendar at any time using the Google Calendar disconnect control on their portal profile. Disconnecting revokes LiveOps' access token with Google and deletes the calendar data LiveOps had stored for that contractor.

Contact

Questions about this privacy policy or how LiveOps handles Google user data can be sent to contact@rtmproductions.live.