Privacy Policy
How Project Black handles YouTube API Data.
This policy describes the limited handling of public data received through YouTube API Services by Project Black.
YouTube API Services and Google Privacy Policy
Project Black uses YouTube API Services. Use of information received from YouTube API Services is subject to the Google Privacy Policy.
API Data we use
For the bounded Trend Intelligence workflow, Project Black may receive public video, channel, playlist, search, metadata, and public statistical data made available by YouTube API Services. Project Black does not request OAuth-authorized user data in this workflow.
Purpose and commercial context
We use this data solely for internal short-form trend analytics and commercial affiliate creative optimization. We do not sell YouTube API Data, provide API access for resale, or redistribute third-party YouTube audiovisual content.
Storage, refresh, and deletion
Project Black’s policy is to retain only the minimum public API Data necessary for the stated workflow. Non-authorized YouTube API Data is refreshed or deleted within 30 days, consistent with applicable YouTube API Services requirements. We do not claim a current right to extended retention for Derived Metrics.
Only if the requested Analytics & Reporting amendment is approved may Project Black apply any approved additional retention treatment to permitted statistical or independently derived data, and only within the approved conditions.
Independently generated analytics
Project Black may calculate independent statistical signals from permitted public API Data, such as subscriber-relative outlier, channel-baseline outlier, velocity, acceleration, and second-day surge. These analytics are independently generated by Project Black; they are not metrics provided by YouTube. They do not establish Customer Truth, Product Fact, Offer Reality, product claims, CTA authority, or publication authority.
Sharing and security
We do not share, sell, or redistribute YouTube API Data except as required to operate the internal system or comply with applicable law. Access is restricted to authorized system operation. We use reasonable safeguards designed to protect information from unauthorized access, disclosure, alteration, or destruction.
Third-party audiovisual content
Project Black currently does not download, store, cache, or analyze third-party YouTube audiovisual content. Content Observation is subject to separate authority and is not represented by this policy as implemented or approved.
Contact
PB01 YouTube Publisher — OAuth-authorized publishing
This section applies separately to PB01 YouTube Publisher, Project Black Business 1's internal publishing workflow. The public-data Trend Intelligence workflow described above does not use OAuth-authorized user data. The Publisher uses authorized YouTube data only when the user explicitly grants OAuth access.
APIs, authorization and limited purposes
The Publisher uses YouTube Data API and OAuth 2.0. It requests https://www.googleapis.com/auth/youtube.upload to upload Human-approved videos and https://www.googleapis.com/auth/youtube.readonly to confirm the authorized channel and check uploaded video identifiers, privacy/publication status and processing status.
Authorized data and credentials are used only for channel verification, approved uploads, recording publication results within Project Black, preventing duplicate uploads, and safe failure reconciliation, retry control and operational audit. Human approval and the applicable publication controls remain required. Scheduling and automatic publication are subject to connection readiness; this policy does not claim that the complete YouTube automatic-publication path is currently operational.
Data used and stored
The workflow handles YouTube channel identity (channel ID and title), video IDs, upload/publication and processing status, granted scopes and relevant API response metadata. OAuth access tokens are used transiently for API calls; refresh tokens and OAuth client credentials are handled in Google Cloud Secret Manager. Credential values are not stored as plaintext in the general application database or shown in application pages, operational records or logs. Channel/video identity, status, scope information and non-secret operational receipts may be retained for the stated purposes. This workflow does not request Google profile information through profile or email scopes.
Sharing, security and retention
The Publisher does not sell Google/YouTube API Data, provide it to third parties for advertising, or use it outside the stated publishing and operational purposes. Upload media and necessary metadata are transmitted to Google's YouTube API; authorization requests go to Google's OAuth service. Credentials are held in Google's Secret Manager, and non-secret operational records are stored using Project Black's existing database and artifact infrastructure. Access is limited to authorized operation. The inspected publishing and authorization paths do not send OAuth tokens or authorized channel/video API responses to creative-generation providers.
Credentials and related data are retained only while necessary for authorized operation and the stated safeguards. When authorization is revoked, operation ends, or information is no longer necessary, unnecessary credentials and related stored data are to be deleted through controlled operations. No fixed automatic deletion interval is claimed. Removing Google's access permission does not by itself delete records already held by Project Black.
Your control, revocation and deletion requests
You can review or revoke the Publisher's access using Google Account third-party connections. Revocation prevents subsequent authorized access and may stop uploads and status checks. For questions or requests to delete unnecessary credentials and related stored data, contact the existing operator address: contact@aimaskedman.com. Requests are handled by the operator; this is not a claim of an automated deletion service. Revocation or deletion of Project Black records does not automatically remove videos already uploaded to YouTube.