SolveStreak

Privacy policy

Effective date: 25 October 2026

This notice describes the information handled by the SolveStreak website and the private publishing workflow used by the channel owner. SolveStreak is an owner-operated YouTube channel. The website has no sign-up, contact form, advertising, or audience analytics.

Information handled by the publishing workflow

When the channel owner authorizes the workflow, it uses Google OAuth and the official YouTube Data API for that owner’s channel. Depending on the operation, it may access or process:

• the authorized channel identifier and channel identity needed to confirm the correct account;
• the owner-approved video file, its SHA-256 content hash, title, description, episode identifier, and declared audience classification;
• YouTube video identifiers, existing-video matches, privacy and processing status, and any owner-approved release date used to verify or manage a release; and
• OAuth credentials that the owner grants to the workflow.

The read-only permission is used to identify the channel, find existing uploads, and read back video details. A separate upload permission is used to upload owner-approved videos. A distinct video-management permission would be required to schedule or cancel a release; that permission is not currently configured or granted. The workflow does not read viewer profiles, comments, or YouTube Analytics data.

How information is used

Information is used to validate an approved video, prevent duplicate uploads, upload it to the owner’s channel, and confirm its metadata, audience setting, visibility, processing state, and any authorized release schedule. It is not used for advertising, profiling viewers, or any unrelated purpose.

Where information is stored and shared

• Google and YouTube: receive OAuth requests and YouTube API calls. When an upload is authorized, YouTube receives the video file and its approved metadata.
• GitHub: hosts the owner’s private source repository and runs the cloud workflow. The private repository stores the approved media and catalog. GitHub Actions secrets hold OAuth credentials. A private issue ledger records episode identifiers, content hashes, workflow attempts, video identifiers, audience decisions, and verified release state. GitHub Actions logs and temporary reservation artifacts support operation and recovery; reservation artifacts are configured for 90-day retention.
• Cloudflare: hosts this static website and provides its DNS and HTTPS. Cloudflare may process a visitor’s IP address and ordinary request and security metadata to deliver and protect the pages. The website does not send OAuth credentials or private channel records to Cloudflare.

SolveStreak does not sell Google or YouTube data and does not disclose it for advertising. The providers above process information to deliver the services described in their own privacy terms.

Website visits

The pages use no advertising pixels, analytics scripts, tracking cookies, or visitor accounts. The hosting provider may process standard connection data, such as an IP address, requested page, browser information, and security events, as described in Cloudflare’s privacy notice.

Retention and security

OAuth credentials remain in GitHub Actions secrets while the owner needs them and should be removed when access is no longer required. Private repository media and the upload ledger are retained for channel operations and duplicate prevention until the owner removes them. Reservation artifacts are configured to expire after 90 days. GitHub controls workflow-log retention under the repository settings. YouTube controls retention of videos and related information in its services.

Credentials are kept out of public pages and workflow output. Access to the private repository and its secrets is governed by its GitHub access controls. No online service can promise absolute security.

Access, revocation, and deletion

The channel owner can revoke SolveStreak’s Google access in Google Account connections, remove the related GitHub Actions secrets, and delete corresponding private repository records. YouTube videos are managed or deleted through YouTube. Revoking access stops future API calls after the authorization is removed; it does not automatically remove copies already retained by Google, GitHub, or YouTube under their own systems.

Contact

For questions about this notice or the Google account connection, use the SolveStreak support contact displayed on the Google OAuth consent screen.

Changes

This notice will be updated if the workflow’s data access, storage, or sharing practices materially change. The date above will show the latest revision.