Privacy Policy

Effective date: 31 August 2026

This policy describes how PLIP Intelligence Platform ("PLIP") accesses and uses Google and YouTube data when the authorised user connects a YouTube account to the private PLIP service.

Google and YouTube data accessed

PLIP requests the Google OAuth scope https://www.googleapis.com/auth/youtube.readonly. Through the YouTube Data API, PLIP may access:

How the data is used

The data is used only to operate PLIP's private YouTube monitoring workflow: reconciling the authorised user's subscriptions with the PLIP YouTube Monitoring Universe, identifying changes that require a user decision, and identifying newly published videos for possible treatment as PLIP Sources.

Storage

PLIP stores the minimum operational state needed for this workflow on the operator's controlled local PLIP environment. This may include YouTube channel and video identifiers, titles, subscription observations, monitoring decisions, exception records and OAuth credentials required for scheduled read-only access.

OAuth credentials are stored locally using operating-system-protected storage. They are not published on this website.

Sharing

PLIP does not sell Google user data and does not provide Google user data to advertisers. Google user data accessed by this integration is not shared with unrelated third parties.

Account control and revocation

The authorised user can revoke PLIP's Google account access at any time through Google Account security settings. Revocation prevents further authorised YouTube API access until permission is granted again.

Limited use

PLIP's use of information received from Google APIs is limited to the functionality described in this policy and is intended to comply with the Google API Services User Data Policy, including applicable Limited Use requirements.

Changes

This policy may be updated if the PLIP YouTube integration materially changes. The current version will remain available at this URL.

Contact

Questions about this private application can be directed to the support email shown on the application's Google OAuth consent screen.