Privacy policy

Last updated: 25 October 2026

This policy covers both parts of GUDOGUY: the team's production tool at editor.gudoguy.com ("the editor") and the public quiz site at club.gudoguy.com ("the quiz site"), where viewers of the channel's live movie-quiz streams see the leaderboard and their achievements. Both use YouTube API Services; see also the Google Privacy Policy. The editor's part comes first; the quiz site's part is in its own section below.

What the editor accesses

When a channel owner connects a channel, the editor asks Google for these permissions only:

• openid and email - the email address of the Google account that connected the channel, shown to the team so they know who connected it;
• https://www.googleapis.com/auth/youtube.force-ssl - to manage the connected channel's own videos and playlists (title, description, tags, thumbnail, playlists, scheduled time, uploading a rendered episode), to run the channel's own live quiz streams and read their live chat, and to read the comments under the channel's own videos, including those held for review, and post the channel's reply in a thread when a team member writes and sends one. The editor never edits, deletes or moderates a comment.
• https://www.googleapis.com/auth/yt-analytics.readonly - to read the YouTube Analytics and Reporting statistics of the channel's own videos (read only).

What it reads and stores

• OAuth tokens of the connected channel, encrypted in the editor's database. They are used only to make the requests listed below.
• The channel's id, title and uploads playlist id, to check that the right channel was connected.
• For each video the team links to an episode: its id, title, privacy status, scheduled time, thumbnail address and the name and size of the uploaded file, so the team can see what is on YouTube now and whether the latest version of the episode is the one uploaded. These are refreshed whenever the team opens or sends the episode, and deleted when the video is unlinked or the channel is disconnected.
• Comments under the channel's own videos: the text, like and reply counts, dates, the commenter's display name and channel id, and - for a connected channel - whether a comment is held for review or likely spam. The team reads them to learn what viewers think of its episodes. A comment is refreshed while it stays on YouTube and deleted from the editor within 7 days after it is removed there; anything YouTube has not shown again for 30 days is deleted. Comments held for review or marked as spam are deleted when the channel is disconnected.
• The channel's list of uploads (video id, title, publish time, length), to tell which episode a comment belongs to. It is refreshed daily; a title YouTube has not shown again for 30 days is erased.
• Statistics of the channel's own videos from YouTube Analytics and YouTube Reporting: views, watch time, average view duration and percentage, likes, comments, shares, subscribers gained and lost, playlist additions, thumbnail impressions and click-through rate - per video and per day, and per video its audience retention, traffic sources, subscribed or not and device types; the same totals per day for the channel. Only aggregate numbers - nothing about individual viewers. The team reads them to learn how each episode did. They are read daily while the channel stays connected; when the editor cannot confirm the connection for 30 days, or the channel is disconnected, they are deleted.
• A journal of API requests: which request was made, by which team member, what was sent and what YouTube answered. Tokens are never written to it, of comments it keeps only their ids, and of report files only their address. Entries are kept for 90 days.

The editor lists the channel's recent uploads and its playlists when a team member opens the picker; those lists are shown, not stored. It does not access other channels or monetization data. Of comments it posts only the channel's own replies, each one written and sent by a team member, and it never edits or deletes a comment.

What it does with the data

Only what the team asks for in the editor: set the title, description, tags, category, audience and altered-content settings, thumbnail, playlists and scheduled time of the channel's videos, read viewers' comments on them and answer them from the channel, and read the statistics of those videos. When a team member asks the team's AI assistant (Claude, by Anthropic) about viewers' feedback or how an episode did, the assistant reads the comment texts with their dates and like counts - never the commenters' names or channel ids - and the statistics listed above; it may draft a reply, which goes to YouTube only after the team member approves that text. Data from Google is not sold, not used for advertising, not shared with third parties and not used to train AI models. The editor's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who can see it

Signed-in members of the team's workspace in the editor. The editor is hosted on the team's own server; data is transferred only between that server and Google over HTTPS.

Revoking access and deleting data

• The Disconnect button on the editor's YouTube page revokes the token at Google and deletes the stored tokens and the channel's statistics immediately.
• Access can also be revoked in your Google Account at myaccount.google.com/permissions; the editor then stops making requests and asks for a new connection.
• To have everything the editor stored about a channel deleted, including its journal entries, write to the contact below; it is done within 30 days.

The quiz site (club.gudoguy.com)

During the channel's live streams viewers guess films from stills by writing in the stream's live chat. The stream reads that public chat of the channel's own broadcast and counts each viewer's points; the quiz site shows the results.

• What it keeps about players: the YouTube channel id, display name and avatar address that YouTube shows next to their messages in the live chat, and per stream their points, correct answers, place, answer speed, best streak, the number of their messages that fell in a question's time window, and the stream awards and achievements they won. The quiz site does not store the texts of chat messages. This is shown publicly on the leaderboard and on the player's page - the same name and picture anyone watching the stream sees in its chat.
• Signing in with Google is optional and only lets a viewer find their own page. The quiz site asks Google for one read-only permission, https://www.googleapis.com/auth/youtube.readonly, and uses it for a single request: which YouTube channel the viewer signed in with (its id, name and avatar). The access token is used for that request only and is never stored; the site gets no refresh token, no email address and nothing else from the Google Account, and reads nothing else from YouTube.
• A signed-in viewer is remembered by a session cookie of the quiz site only; Sign out ends it.
• Data from Google is not sold, not used for advertising, not shared with third parties and not used to train AI models, and its use adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• The permission can be revoked at myaccount.google.com/permissions. To have a player's page and results deleted, write to the contact below from the channel's Google Account or mention the channel id; it is done within 30 days.

Changes

If this policy changes, the date at the top changes with it.