RTMP LiveOps

Privacy Policy

RTMP LiveOps is internal operations software used by RTMP and the contractors who crew its live events. This page explains what Google user data LiveOps requests, why it is requested, how it is used and stored, and how to disconnect it.

What Google data we request

Nothing is connected by default. LiveOps has two separate Google Calendar connections, and they request different permissions.

A contractor connecting their own calendar grants one scope:

• https://www.googleapis.com/auth/calendar.events — lets LiveOps add, update, and cancel events it creates for that contractor's show assignments.

An RTMP staff member connecting a shared organization calendar grants two read-only scopes:

• https://www.googleapis.com/auth/calendar.calendarlist.readonly — lets LiveOps list the calendars on that account so a staff member can choose which one to import from.
• https://www.googleapis.com/auth/calendar.events.readonly — lets LiveOps read events on the chosen calendar, so bookings recorded there can be turned into draft show records in LiveOps.

Both connections also use openid and email to identify which Google account was connected. The staff organization-calendar connection additionally uses profile.

Why we request it

RTMP staff schedule live events and assign contractors to crew roles. When a contractor connects their calendar, LiveOps can place their show assignments on the calendar they already use. Staff can separately import a shared organization calendar to create draft show records for review.

What LiveOps writes to a contractor's calendar

LiveOps writes only to the primary calendar of the Google account the contractor connected; contractors do not currently choose a different destination calendar. It creates, updates, or cancels only assignment events that LiveOps created. It does not otherwise read, alter, or delete events on that calendar.

Where the data is stored

LiveOps stores connected-account identity, encrypted Google OAuth tokens, and identifiers and status needed to keep LiveOps-created assignment events in sync. Staff organization-calendar data is associated with that organization connection. LiveOps does not import a contractor's personal calendar or store unrelated contractor calendar events. If an assignment-event cancellation must be retried, LiveOps may temporarily retain the minimal connection and event identifiers and status needed for that recovery.

We never sell or share this data

Google user data obtained through LiveOps is never sold, and it is never shared with third parties. It is not used for advertising, and it is not used to train any model.

How to disconnect

A contractor can disconnect Google Calendar at any time using the disconnect control on their portal profile. Disconnecting removes LiveOps' stored access and refresh tokens and connection identity, and LiveOps asks Google to revoke its access. Google's response is not guaranteed, so a contractor may also revoke access directly from the Google Account permissions page.

Events LiveOps already added may remain on the calendar after disconnecting and can be deleted by the contractor in Google Calendar. To request deletion of any retained connection or cancellation-recovery records, write to the address below.

Contact

Questions about this privacy policy, or requests about Google user data LiveOps holds, can be sent to contact@rtmproductions.live.