OneSceneDeeper Publisher
Privacy policy
Effective 17 October 2026
This policy explains how our personal desktop publishing tool and this information website handle data. The application uses YouTube API Services.
1. Who operates the application
OneSceneDeeper Publisher is operated by Ayvaz for the owner’s YouTube channels. Questions about privacy, access or deletion can be sent to ayvazovak36@gmail.com. The application is not offered as a public service.
2. Google and YouTube data
With the owner’s permission, the application accesses channel identity, including the channel ID and name, and the metadata, visibility and processing status of known videos. It uploads owner-selected video files together with titles, descriptions and publishing settings.
The requested Google permissions are youtube.readonly for reading channel and video information and youtube.upload for uploading approved videos. Google handles sign-in. The application never asks for or stores the owner’s Google password.
3. Why this information is used
The tool uses this data to confirm the intended channel, prepare approved batches, avoid duplicate uploads, resume interrupted uploads and check whether an upload has completed. Google user data is not sold, used for advertising, or used by this application to build or train generalized AI or machine-learning models.
4. Storage and access
OAuth credentials, refresh tokens and resumable-upload session URLs are stored in the macOS Keychain on the owner’s Mac. Short-lived access tokens are held in process memory. A local database stores channel identifiers, planned metadata, file hashes, progress and uploaded video IDs. Finished video files remain in the local project and are transmitted to YouTube when the owner approves an upload.
The owner can use the tool through Codex. Non-secret tool results, such as channel names, publishing plans, video IDs and statuses, can appear in the Codex conversation and are processed by OpenAI under the owner’s account settings and OpenAI Privacy Policy. Access tokens and Google passwords are not included in these tool results.
5. Sharing and service providers
Approved video files and metadata are sent to Google/YouTube through the YouTube API. Their handling of this data is governed by the Google Privacy Policy. The information website is hosted using OpenAI Sites and Cloudflare infrastructure; these providers may process request information such as IP addresses, browser details and security logs to deliver and protect the site.
This website has no upload form, Google sign-in flow, advertising, embedded YouTube players or application analytics scripts. Hosting providers may use operational or security cookies. The website does not receive the desktop application’s OAuth tokens or local video library.
6. Retention, deletion and revocation
Local publishing records are kept while they are needed to manage the owner’s queue, verify uploads and avoid duplicates. The owner controls the files and database on the Mac and can request removal of local application data and saved credentials by contacting the address above. Removal is handled manually; it is not performed by visiting this website.
You can revoke the application’s Google access at any time through Google Account connections. Revocation prevents further authorized API access but does not automatically erase local records. To remove those as well, contact the operator. Previously uploaded videos remain on YouTube until managed or deleted through YouTube Studio.
7. Limited use and changes
Use and transfer of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. Material changes to this policy will be reflected on this page with an updated effective date.