Back to TAS Forge

Privacy policy

Clear boundaries for your YouTube data.

This policy explains how TAS Forge handles Google user data through its current private, read-only YouTube analytics integration and how additional permissions will be handled before planned channel-management features are enabled.

Effective August 29, 2026Last updated August 29, 2026
The short version

TAS Forge currently reads analytics for an authorized YouTube channel so its owner can ask questions about performance. The current connection cannot upload, edit, publish, or delete content. Planned management features are not active and will require additional Google consent and owner approval before use. TAS Forge does not sell Google user data or use it for advertising.

01

Scope

This Privacy Policy applies to the public TAS Forge website at tasforge.com and to TAS Forge Creator Console (the “Service”), including its private ChatGPT connection. The Service is being built for two owner-controlled channel profiles—Malito+ and The Quiet HUD. It is not a public analytics platform and does not offer public user accounts.

The public website provides information about the Service and this policy. It does not ask visitors to sign in with Google or collect YouTube analytics from website visitors.

02

Google data accessed

At this time, with the channel owner’s Google OAuth authorization, the Service uses the YouTube Data API, YouTube Analytics API, and YouTube Reporting API with read-only scopes. Depending on the requested action, it may access:

  • Channel identifiers, name, handle, profile details, and subscriber totals.
  • Owned video identifiers, titles, publication dates, thumbnails, and public engagement totals.
  • Views, watch time, average view duration, and audience-retention information.
  • Impressions, thumbnail click-through rate, traffic sources, and YouTube search terms.
  • Aggregated breakdowns such as geography, device, format, and subscriber status.
  • OAuth authorization tokens and the authorized channel identifier needed to maintain the connection.

The Service does not request the owner’s Google password. The current analytics connection does not use YouTube write, upload, edit, or delete scopes.

03

How data is used

Google user data accessed by the current connection is used only to:

  • Authenticate the authorized channel and keep the private connection available.
  • Retrieve the read-only metric or report requested by the channel owner.
  • Present and summarize channel performance through the owner’s connected ChatGPT workspace.
  • Diagnose and secure the connector, including confirming that it remains locked to the intended channel.
  • Keep each authorized channel’s credentials and data profile separated within TAS Forge.

TAS Forge does not sell Google user data, build advertising profiles from it, or permit human review except when necessary for security, legal compliance, or support requested by the owner.

04

Planned channel-management features

TAS Forge is planned to support controlled management for Malito+ and The Quiet HUD after the analytics foundation is stable. The first management workflow will start with videos the owner has already uploaded to YouTube as Private. It is expected to prepare or apply:

  • Titles and descriptions in English and the owner’s 11 configured localization languages.
  • SRT caption files, thumbnails, tags, category, audience settings, and playlists.
  • Validation results, visibility choices, and a requested publication schedule.

These features are not enabled by the current authorization. Before any management feature is activated, TAS Forge will update this policy as necessary, request only the additional Google scopes required for that feature, and present a new Google consent step. Changing visibility, scheduling, or publishing will require an explicit owner-approved action.

Automatic MP4 uploading is a later phase. It will not be enabled until the private-video workflow is proven reliable and any required YouTube API compliance review is completed. Deletion will not be bundled into routine publishing automation.

05

Storage and security

OAuth tokens, the channel lock, and connector configuration are stored on TAS-fort, a privately administered server. Access is restricted to the system owner and processes required to run the Service. The connector communicates with OpenAI’s control plane through an outbound secure tunnel; the private server is not exposed as a general public endpoint.

No system can guarantee absolute security. TAS Forge uses reasonable technical and administrative safeguards and limits access to the minimum required for the Service to operate.

06

Sharing and processing

Google user data may be processed by:

  • Google, to authenticate the owner and provide requested YouTube API data under Google’s terms and privacy policy.
  • OpenAI/ChatGPT, when the owner explicitly invokes a connected action, so ChatGPT can receive and respond using the requested result. OpenAI’s handling is governed by the owner’s ChatGPT plan, workspace settings, data controls, and applicable OpenAI policies.
  • Infrastructure providers, only as needed to operate, secure, or deliver the Service and public website.

TAS Forge does not disclose Google user data to data brokers, advertisers, or unrelated third parties.

07

Retention and deletion

Authorization tokens and channel configuration are retained while the owner keeps the Service connected. Requested analytics are retained only as needed to provide the Service, maintain any private history explicitly configured by the owner, troubleshoot issues, or meet legal obligations.

The owner can request deletion of locally stored Google user data by emailing support@tasforge.com. After verifying the request, TAS Forge will delete data under its control within a reasonable period, except where retention is legally required.

08

Your controls

The authorized channel owner can:

  • Disconnect TAS Forge Creator Console in ChatGPT.
  • Revoke Google access from the Google Account’s third-party connections page.
  • Ask TAS Forge to remove stored authorization and associated data.

09

Google API Services User Data Policy

TAS Forge’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

10

Changes and contact

This policy may be updated when the Service’s features or data practices change. The “Last updated” date above will identify the latest version. Material changes will be reflected here before the changed practice is used.

Questions, privacy requests, and deletion requests can be sent to support@tasforge.com.