APPLICATION PRIVACY
Nifty Fifty Hub Privacy Policy
How the private application uses Google and YouTube integration data.
Last updated: 20 October 2026. This notice applies to Nifty Fifty Hub's Google and YouTube integration, not to the separate public Puddcast website.
1. Who operates this application
Nifty Fifty Hub is currently developed and operated by Paul Sproston. For questions, privacy enquiries, access withdrawal or deletion requests, email info@paulyypudd.com. Only users with appropriate authorisation to access a connected channel should connect that channel.
2. Google permissions and information accessed
Nifty Fifty Hub uses YouTube API Services, including the YouTube Data API and YouTube Analytics API. When a user grants permission via Google's OAuth consent screen, the Hub requests https://www.googleapis.com/auth/youtube.readonly and https://www.googleapis.com/auth/yt-analytics.readonly.
The connected account's authorised channel information and associated metadata may include the channel name, identifier and handle, video identifiers, titles, publication details, video privacy status, durations and thumbnails. Available performance data may include views, likes, comments, viewing time, average viewing duration, subscriber changes, traffic-source and device information. The application also records connection status, authorisation time and the identifying name of the user authorising the connection when available.
The Hub does not request Gmail, Google Drive, or YouTube upload/edit/delete permissions, and does not ask users to provide their Google passwords to the application.
3. How this information is used
Information is used for permitted internal production reporting, recognising and matching relevant recordings to draw schedules, and analysing performance trends. It is not used to serve targeted advertisements or sold to advertisers. We do not publish channel-authorised analytics or OAuth tokens on this public information website.
4. Where data is stored and who can access it
Google OAuth access and refresh tokens are held in server-side application configuration for the private Hub. YouTube video details and analytics/report snapshots may be stored in a server-side reporting database to support the Hub's reporting features. The public website at paulyypudd.com does not store these OAuth tokens or serve the Hub's private data.
The private application is access-restricted; channel-related reporting is intended for authorised users and channel representatives only. Data is transmitted to Google/YouTube APIs when using the integration and may be processed by the infrastructure used to operate the private application. The application does not intentionally share the data with unrelated third-party advertising services.
5. Storage, retention and accuracy
The application caches channel/video details and statistics for reporting. The current application does not automatically erase all cached reporting data when a channel is disconnected, and a comprehensive automatic retention and deletion schedule has not yet been implemented. Cached statistics may therefore remain until they are separately removed. Please contact the operator to request deletion of stored channel-related information. Records should be refreshed or deleted as necessary to comply with applicable YouTube requirements.
6. Disconnecting, revoking access and requesting deletion
Authorised administrators can use the Hub's Disconnect YouTube control. In the current version, this clears the Hub's locally stored OAuth access and refresh tokens, preventing continued access through that local connection. It does not currently send Google's token-revocation request and it does not automatically delete previously cached YouTube reporting information.
You can revoke the application's Google permission independently in Google's security permissions settings ↗ (also accessible through Google Account connections ↗). To request deletion of Hub-held Google/YouTube data, contact info@paulyypudd.com with enough information to identify the connected channel and verify your authority. Removing data from the Hub does not delete the underlying videos or data held by YouTube itself.
7. Your choices and rights
You may ask about information held about you, request corrections or deletion where applicable, withdraw Google access, and raise a privacy concern using the contact address above. Requests involving a connected channel may require verification that you are authorised to act for that channel. Applicable UK data protection rights may also apply.
8. Third-party terms and changes
Our application uses YouTube API Services. By using YouTube API features, users are also subject to the YouTube Terms of Service ↗. Google's handling of information is explained in the Google Privacy Policy ↗. This notice will be updated when the application's data handling or retention/deletion controls change.