Riffology: Iconic Rock Albums Podcast
YouTube Data Privacy Policy
Riffology: Iconic Rock Albums Podcast uses YouTube API Services to bring view counts from its own YouTube channel into its private podcast statistics. Only the podcast's team connects a YouTube account. Listeners and website visitors are never asked to sign in with Google, and no YouTube data about them is collected.
Who we are
This website and its podcast analytics are run by Riffology using PodKit, self-hosted podcast software. In this policy, "we" means the team behind Riffology: Iconic Rock Albums Podcast.
YouTube API Services
When the channel owner connects YouTube, we use YouTube API Services under the YouTube Terms of Service. Google's handling of your information is described in the Google Privacy Policy.
What we access
Signing in with Google grants two read-only permissions:
youtube.readonly: the channel's ID and name, and the list of its uploaded videos (video ID, title, publish date and length).yt-analytics.readonly: daily view counts for each video, split by device type (mobile, computer, tablet, TV, games console), and each video's views by country.
We do not access or store email addresses, comments, subscriber lists, watch history, personal information about viewers, or anything outside these two permissions. We cannot upload, edit or delete anything on the channel.
How we use it
- We match videos to podcast episodes and count each YouTube view alongside the episode's podcast downloads, so the team can see an episode's total audience in one place.
- View counts are refreshed every 6 hours.
- YouTube data is used only for these statistics. It is not used for advertising, not sold, and not used to train AI models.
Who can see it
- The statistics are visible only to the podcast team's signed-in PodKit users.
- The team may connect its own AI assistant to PodKit (through the Model Context Protocol) to ask questions about the podcast's statistics. The assistant receives the same view counts, only in answer to the team's own requests.
- We do not share YouTube data with anyone else. We do not let third parties serve content or advertisements using it.
Storage and security
- The data is stored on our own server in the podcast's PodKit database, and is sent only over encrypted HTTPS connections.
- The Google access token is stored encrypted. Changing settings or viewing the data requires a PodKit administrator or team account.
- PodKit re-confirms with Google at least every 24 hours that it is still allowed to access the channel, and refreshes the video details at the same time.
Keeping and deleting data
- We keep YouTube data only while the channel remains connected.
- Disconnecting in PodKit revokes our Google access and immediately deletes all stored YouTube data: the video list and every imported view count.
- You can also revoke access at any time from your Google Account's third-party connections page (also reachable through Google security settings). Once PodKit sees that access is gone, it deletes the stored YouTube data within 25 days.
- Server backups made while the channel was connected may contain copies of this data until those backups are deleted.
Google API Services User Data Policy
Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
Contact
For questions or complaints about this policy or our use of YouTube data, email info@riffology.co. We'll reply as soon as we can.
Changes
If we change how we use YouTube data, we'll update this page and the date at the top.