Last updated: September 24, 2026

Forge Access is a personal-use assistant integration operated by its owner. It can manage an authorized YouTube channel and, if separately authorized, read the owner's Gmail. It is not a public sign-up service. This policy describes how these integrations use data.

Information accessed and used

With the owner's YouTube authorization, Forge Access accesses channel identifiers and information, video titles and descriptions, thumbnail images, video privacy settings, upload and processing status, and available channel or video statistics. It processes video files, thumbnails, and metadata supplied or approved by the owner to carry out requested YouTube tasks.

With the owner's separate Gmail authorization, Forge Access can search messages and read message metadata and bodies to carry out requested mail-related tasks. Its Gmail permission is gmail.readonly. It cannot send, delete, or change messages through that permission. It does not read Gmail until the owner connects the account and requests related work.

Google issues OAuth access and refresh tokens for the selected services. Google's sign-in screen currently displays the OAuth app name Forge Assistant for this integration. Forge Access does not receive the owner's Google password. The current YouTube permission is youtube.force-ssl. YouTube and Gmail tokens are stored separately. The breadth of either Google permission does not mean every permitted operation is used.

Storage and processing

Authorization credentials are stored in access-restricted files on owner-controlled systems. Working video files, thumbnail images, message content selected for a task, metadata, task records, and verification results can be stored in the owner's workspace, shared storage, conversation history, or backups.

The assistant workflow can process selected task content, including video metadata, media, or Gmail message content, through the owner's configured AI service providers to carry out the owner's requests. Accordingly, processing is not exclusively local. Authorization secrets are kept separate from task content and are not intentionally included in assistant prompts.

Requested YouTube uploads and metadata changes are sent to Google/YouTube. Gmail messages are retrieved through Google's Gmail API when needed for authorized tasks. Google's API services are subject to the Google Privacy Policy; YouTube use is also subject to the YouTube Terms of Service.

Retention and control

Authorization remains stored until replaced, revoked, or removed. Working artifacts and records may remain until the owner deletes them; no single automatic deletion period is currently enforced across working files, assistant history, and backups. Provider-side data handling is also governed by the configured providers' terms and settings.

The owner can revoke Forge Access through Google Account third-party connections. Revoking access stops future authorized API access, but does not by itself delete previously uploaded YouTube videos or existing local files, histories, or backups. Those records must be managed separately by the owner.

Contact

For questions or requests concerning Forge Access data, contact its operator at 2kaac@daein.org.