YOUTUBE-UPLOADER-API · LIGHT POSTING
Privacy Policy
Last updated: 18 November 2026
This policy describes how the operator of Light Posting handles information for the private youtube-uploader-api workspace at lightposting.org. Contact the operator at instuser63@gmail.com.
1. Scope and current integration
The workspace runs on a remote server and currently uses Taisly for connected-channel publishing. The direct Google OAuth 2.0 / YouTube Data API connection is being configured. No direct Google consent or token collection flow is offered on these public pages. The Google-specific provisions below apply when that connection is enabled; the deployed connection flow must disclose its actual permissions and token storage before authorization.
2. Information processed
- Content and publication settings: uploaded video files, titles, descriptions, hashtags, selected channels, schedules, publication identifiers, status and error messages.
- Connected account information: channel or account identifiers, display names, usernames and connection status returned by the configured publishing service. Where statistics collection is enabled, the workspace also stores available video and account metrics.
- Operational information: administrator-supplied service settings and credentials, technical logs, and information sent in support requests.
- Website access: the web server processes IP addresses and request information to deliver and protect the site. Essential session and remember-me cookies are used for the private workspace. These public pages do not install advertising or analytics trackers.
3. Google permissions and OAuth tokens
The intended direct upload permission is https://www.googleapis.com/auth/youtube.upload. Its purpose is to send videos and upload metadata selected by the owner to YouTube. It is not permission to read Gmail, Google Drive files or a Google password. Additional Google permissions must be disclosed and separately authorized before use.
For the current Taisly connection, authorization and any Google tokens held by that service are managed by Taisly under its own applicable policies. We cannot describe those tokens as stored only on the user's device or exclusively by Light Posting. Direct OAuth token persistence in Light Posting has not yet been deployed; this policy and the connection screen will be updated with the actual server-side storage and retention arrangements before it collects direct OAuth tokens.
4. Purposes and sharing
Information is used to prepare content, operate authorized publishing schedules, display job status, provide enabled statistics, troubleshoot failures and respond to the owner. Video files and metadata are sent to the selected publishing service and destination platform. Hosting providers process stored data as part of operating the server.
Optional content-generation features may send prompts, references or media selected for those features to their configured AI or voice providers. Those features are separate from Google authorization. Google authorization tokens are not inputs to content-generation tools.
We do not sell Google user data or use it for advertising, surveillance or training general-purpose AI models. Any use or transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements. Authorized maintenance access is limited to operating and supporting the workspace.
5. Storage and security
Workspace records, uploaded media and job files are stored in the operator-controlled remote server's database and filesystem. Browser session cookies remain in the user's browser. HTTPS protects traffic to this website, and the private workspace requires authentication. We do not claim that all stored media or database records are encrypted at rest.
Records and files are kept while needed for the selected publishing workflow, publication history or troubleshooting, or until the operator removes them. There is currently no uniform automatic deletion interval for all workspace media. The operator handles deletion requests manually; do not submit passwords or authorization tokens by email.
6. Revoke access and delete data
You can review and revoke Google access at Google Account — third-party connections. For a Taisly connection, revoke the corresponding connected application and disconnect the account in Taisly or the workspace. Revoking access prevents future authorized operations, but does not automatically delete files or records already stored in the workspace.
To request deletion, email instuser63@gmail.com with the channel identifier and the data you want removed. Ownership may need to be verified. Requests are handled by the operator. Google / YouTube user data covered by a verified deletion request must be deleted as soon as possible and within the applicable YouTube policy limit of 30 days. If a different deadline applies under law or Google's policies, that requirement takes precedence.
Deleting local files or revoking app access does not remove a video already published on YouTube. Manage or delete published videos in YouTube Studio. Information held by Google or a connected third-party service is also subject to that service's own controls and policies.
7. Third-party policies and changes
YouTube API Services are subject to the Google Privacy Policy and the YouTube Terms of Service. This policy will be updated when the integration or data handling changes. Material changes affecting Google data use must be disclosed before requesting the corresponding authorization.
Privacy contact: instuser63@gmail.com.