Privacy Policy

Information accessed

After authorization, the integration may access:

• YouTube channel identity, including channel ID, title and uploads playlist.
• Owned video metadata, including video IDs, titles, publication dates and visibility/status information.
• Non-revenue YouTube Analytics for the authenticated channel and a bounded selection of its videos, including views, watch time, average view duration, likes, comments and shares.
• Public comment and reply text, comment/thread/video identifiers and publication, update and retrieval times, through the YouTube Data API. Stored text is bounded; commenter profile names and commenter channel identifiers are not retained by this reader.

OAuth access uses only youtube.readonly and yt-analytics.readonly. Public comments use a separate restricted API key. This integration has no authority to upload, edit, delete, reply to or moderate YouTube content.

Purpose and processing

Data is used to provide and improve the visible, authorized monitoring features: organizing channel activity, showing bounded summaries and evidence, and reducing manual checking. Current YouTube observations and grouping use local deterministic rules. Semantic comment analysis is disabled. Google/YouTube data is not sent to cloud AI services or used to train AI models by this integration.

Google/YouTube API requests necessarily communicate with Google. Retrieved application data is otherwise processed locally; these public pages do not expose the private dashboard or its records.

Storage and retention

OAuth tokens and API keys are stored separately in Windows-protected local credential storage. API data is held in a local application cache; that cache is not encrypted by the application. Device and account security therefore remain important.

The integration uses a bounded 28-day refresh/expiry lifecycle, not a permanent API archive. Successful refreshes replace or renew current data; comments have their own expiry checks so a metadata refresh cannot extend a comment’s retention by itself. Expired cache data is cleared on access, at startup and during periodic checks while the application runs.

If the application or computer is off, it cannot physically remove files during that time. Expired data is cleared when the application next runs or accesses the cache, before that data is used.

OAuth tokens, API keys and the YouTube API cache—including its video associations—are excluded from the application’s portable backups. Limited outcome counts or feedback without API payloads may remain separately. This policy does not control copies independently made outside the application.

Sharing and Limited Use

Google user data is used only for the visible user-facing functionality described here and its improvement, consistent with the Google API Services User Data Policy, including its Limited Use requirements.

We do not sell Google/YouTube data, use it for advertising, transfer it to data brokers or use it for credit or lending decisions. We do not disclose it to third parties except with authorization necessary for the requested functionality, to address security or abuse, or where law requires it. Human access beyond the authorized user is limited to consented support or applicable security/legal needs. The current integration adds no cloud AI processing or external data archive.

Your controls

• Delete stored YouTube data clears the local integration cache and associations and pauses scanning. It keeps the Google authorization available and does not delete your original YouTube content or independent internal creative records.
• Disconnect YouTube clears local API data, disables scanning and attempts to revoke Google authorization. If revocation cannot reach Google, the application reports that state and retains a protected token solely for retry; you can revoke directly at Google.
• Remove access at Google Account permissions. Once the running application detects a revoked grant, it clears the corresponding local API data. Detection requires the application to run and contact Google.

Deletion controls operate on local integration data, not the underlying channel, videos or public comments. For questions or a deletion request, contact ceo@silhouettemonroe.com. You can also ask the authorized operator to use the local deletion control.

These pages and third-party services

These informational pages add no analytics, advertising pixels, account forms or tracking cookies. The website host may process ordinary connection data needed to serve the pages. Google and YouTube govern their own services and data handling: see the Google Privacy Policy and YouTube Terms of Service.

Material changes to this policy will be reflected here. New uses or broader Google permissions require the appropriate notice and authorization; this policy does not itself grant additional access.

Responsible entity and contact

Monroe Music & Entertainment LLC
ceo@silhouettemonroe.com