Jarvis Channel Connection Privacy Policy
Policy version: 2026-10-07.1. Prepared October 7, 2026. This policy describes the current YouTube connection software in the private Jarvis application provided by House of NIVREK. The feature uses YouTube API Services. Visiting these public information pages does not authorize YouTube access. The connection is available to the authorized Jarvis owner.
Access and purpose
With your Google authorization, the initial connection requests https://www.googleapis.com/auth/youtube.readonly to find your eligible channel, let you select it, verify the connection and display recent uploaded videos when you request them. The connector does not request Gmail access for this feature.
YouTube sign-in uses the configured automated retention cleanup. The setup requires a separate Google app/project from Jarvis Cloud Email so the two features have independent Google authorization and revocation boundaries.
Google API responses can include channel identifiers, titles and profile snippet metadata, the channel's uploads-playlist identifier, and video identifiers, titles, thumbnail URLs, publication dates, durations, visibility, embed availability and made-for-kids status. The signed-in view displays up to ten recent video cards. It checks video metadata before offering an embedded player; private, unavailable, non-embeddable and made-for-kids or unknown-status videos use a link to YouTube instead. Jarvis does not download audiovisual files.
Optional reviewed visibility changes require a separate Google authorization for the read permission together with https://www.googleapis.com/auth/youtube.force-ssl. This permission can authorize broader YouTube operations at Google; the current Jarvis control only reviews and changes an existing owned video's visibility. For that review Jarvis also processes the selected video's identifier, title and current status, and your requested visibility. It does not upload a new video, post comments or delete a video. Read-only authorization alone does not enable these changes.
Storage and service providers
YouTube responses pass through Jarvis server requests to your signed-in browser. The recent-video list is temporary view data. The connector does not save that list to durable conversation or memory storage, or intentionally persist it in browser storage. Closing the list, leaving or hiding the page, or ending the browser session clears that view.
Google access and refresh authorization is encrypted with AES-GCM in private Sites and Cloudflare cloud storage, using a separate server-side social-connection key. Authorization and the accepted privacy-policy version are bound to the Jarvis owner and connection record. Authorization is not included in browser responses or shared with Jarvis's AI models. Stored account records also include the owner and internal account identifiers, provider, selected channel identifier and title, connection state, permission state, revisions and timestamps.
Pending connection data, including possible channel choices and authorization, is encrypted while the owner completes account selection. A pending connection is usable for ten minutes. Its saved encrypted payload is cleared after successful selection or a failed callback. Expired, failed and completed YouTube connection-attempt records are deleted during cleanup, including cleanup triggered by connection requests.
If optional visibility changes are enabled, the exact review is encrypted while awaiting approval and is usable for five minutes. Its encrypted content is cleared when the attempt finishes or the review is canceled; expired review content is cleared during cleanup. Operational action records can retain status, identifiers, a content digest, timestamps, an error category when applicable and a provider receipt, without completed review content. YouTube action records are removed by cleanup at their 28-day age cutoff or earlier when the selected connection is deleted.
Google processes authorization and YouTube API requests. Sites and Cloudflare provide the private application hosting, processing and storage needed for this feature. Provider requests use HTTPS. The connector does not collect your Google password.
Browser data, limited use and AI
Your device loads video thumbnails directly from YouTube. Selecting Open player loads a YouTube privacy-enhanced player from youtube-nocookie.com; no player loads automatically. The player uses YouTube's native controls and may show advertisements or related videos. Google may receive your IP address, device/browser information, the originating website and playback activity, and may use cookies or other browser data according to its policies. Privacy-enhanced mode is not a promise of no data collection. Watch on YouTube opens YouTube's own website or app, where your Google sign-in may be needed. Closing the video list, hiding or leaving Jarvis, pausing it, or ending the session removes the embedded player. Jarvis does not save playback data or thumbnail files to conversation or memory storage.
The private feature uses your Jarvis sign-in session. A connection attempt also uses a Secure, HttpOnly, SameSite cookie for up to ten minutes to bind the Google callback to that browser; the callback clears that cookie. The connector does not store Google authorization in local or session browser storage. The public House of NIVREK website and Jarvis's other features may have separate session and website data practices.
Jarvis uses YouTube API data for the visible selected-channel feature. We do not sell it or use it for advertising, profiling or AI model training. The connector does not automatically send YouTube responses to AI services or add them to Jarvis memory. Separate AI features use content the owner supplies. Access to private data is restricted to the authorized owner and service processing needed to provide the feature.
Google's handling of data is described in the Google Privacy Policy. Applicable provider rules include the Google API Services User Data Policy and YouTube API Services Developer Policies.
Retention, disconnecting and deletion requests
Temporary recent-video views clear when you close the view, leave or hide the page, or end the browser session. A successful channel read checks Google authorization and refreshes the saved channel title and verification time. Once automated cleanup is configured, a connection expires after 28 days without a successful channel read. Cleanup deletes its saved authorization, channel metadata and related action records; reconnecting then requires a fresh Google authorization. Older YouTube action records also reach a 28-day cleanup cutoff even while the channel connection remains active. Daily maintenance and cleanup during connection requests enforce these cutoffs; this policy does not promise an exact execution time or immediate erasure from hosting backups or operational logs.
Choose Disconnect on a selected YouTube channel to request deletion of its Jarvis data. Jarvis immediately deletes that selected connection's stored authorization, channel identifier/title, related review content and receipts, and pending channel choices that belong to that selected channel. Separate channel records and unrelated pending sign-ins are not automatically deleted. When a use request proves the selected authorization has expired or been revoked, Jarvis also removes that selected connection's saved data. For other deletion requests or questions, use Contact House of NIVREK.
Disconnect also attempts Google-side revocation. Jarvis reports whether Google confirmed that request. Local deletion still occurs if Google revocation cannot be confirmed; you can finish removing access through your Google Account connections. Google revocation may invalidate other YouTube grants for the same Google account using that same Google app. This does not mean all Jarvis channel records or grants belonging to different Google accounts are deleted. The required separate YouTube Google project keeps the cloud-email grants independent.
Deleting Jarvis data or revoking app access does not delete your channel or videos from YouTube, or undo a completed visibility change. A request YouTube already accepted may still finish. To delete or manage your videos and channel at YouTube, use YouTube or YouTube Studio.
Contact and changes
For privacy questions, complaints or deletion requests, use Contact House of NIVREK. Keep passwords, authorization tokens and private account data out of the contact form. Material changes to YouTube data access or use will be disclosed before the changed use begins, with additional agreement and authorization when required.