Privacy Policy

Gluoon Copilot uses YouTube API Services to upload finished videos from the editing workstations to the YouTube channels of the studio and its partners. By using this feature you agree to the YouTube Terms of Service and the Google Privacy Policy.

What happens to the Google data obtained through the API:

• The channel owner grants Copilot two permissions once: youtube.upload to upload videos and youtube.readonly to read the channel name and id. The studio server stores the OAuth access token together with the channel name, id and thumbnail.
• The token is used for two things only: uploading a video edited by the studio to that channel, and checking that the access is still valid. Copilot does not read comments, statistics or subscriber lists, and does not change channel settings.
• Every uploaded video is set to Private. The channel manager publishes it manually in YouTube Studio after filling in the title, description and thumbnail.
• Google data is not shared with third parties and is not used for advertising, profiling or model training. The only extra information attached to a video is the studio's own metadata: file name, project name and the editor's name.
• Tokens live in a database on the studio server that only administrators can reach. A token is deleted when the channel is disconnected in Copilot or when the owner asks for it.

Gluoon's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can revoke access at any time in two ways: the Disconnect button next to the channel in Copilot, or the Google security page security.google.com/settings/security/permissions. After that the stored token stops working and the channel record is removed.

The GVP publication calendar can keep the schedule of upcoming video releases in a Google Calendar of the studio. To do that the calendar owner grants the https://www.googleapis.com/auth/calendar permission once.

• What the system does: it creates, updates and deletes its own events for planned publications and shoots in the selected calendar, and reads them back to show the schedule inside GVP.
• Why this scope: the Google Calendar API offers no narrower scope for writing events — calendar.readonly cannot create events, and calendar.events alone still needs access to the calendar list to locate the right calendar in our flow.
• What the system does not do: it does not read or modify personal events other than the ones it created itself, does not look at attendee lists of other meetings, and never shares calendar content.
• The server stores the OAuth token, the calendar id and the ids of the events it created, so that it can update exactly its own records.

You can revoke the permission at myaccount.google.com/permissions — synchronisation then stops and the stored token is deleted.

Gluoon's use of Google Calendar data likewise adheres to the Google API Services User Data Policy, including the Limited Use requirements.