Effective November 2, 2026
Privacy Policy — PixelOne Social Automation
Pixel One operates PixelOne Social Automation (the “Tool”), a private desktop utility for publishing festival-related videos to channels authorized by their owners. This policy describes its use of Google and YouTube data. This policy is specific to the Tool and is separate from the privacy policies for Pixel One's consumer mobile applications.
1. YouTube API Services and authorization
The Tool uses YouTube API Services and Google's OAuth authorization flow. By authorizing the Tool, the authorized channel owner grants the specific permissions displayed on Google's consent screen. The Tool currently requests youtube.upload for uploading videos and youtube.readonly for reading channel identity and relevant video data. It does not request the user's Google password.
Google's handling of information is described in the Google Privacy Policy.
2. Data accessed and stored
- Authorization data: OAuth access and refresh tokens and the configured OAuth client details, stored locally on the authorized operator's device.
- YouTube channel information: channel name and channel ID, used to confirm the selected destination before uploading.
- Video information: video IDs, titles, descriptions, publication times, privacy states, upload results, and related API status information, used for scheduling, verification and duplicate-upload prevention.
- Operational data: local videos, festival content metadata, error records and publishing history required to operate the Tool.
3. Purposes and sharing
These data are used only to authorize permitted operations, select the authorized channel, upload and schedule videos, verify the results, and investigate operational failures. Video content and associated descriptions are transmitted to YouTube when an authorized upload is performed. The Tool does not sell Google or YouTube user data or share OAuth tokens with advertisers. The Tool does not use Google user data to target advertising.
4. Security and local storage
OAuth tokens and operational records are stored on the operator's Mac in files protected by local operating-system access controls. API communications use HTTPS. The operator is responsible for securing the device and its account. This Tool has no public user registration or hosted account database.
5. Retention, access revocation and deletion
Local credentials and publishing records are retained as needed for authorized channel operations, subject to YouTube API Services' data-retention rules. The authorized account owner may revoke access at any time through Google Account third-party connections. The operator must then stop using the authorization and delete the corresponding stored authorization data and related YouTube API user data within the applicable policy deadlines.
To request deletion of locally stored data or obtain assistance with revocation, contact admin@pixelone.work. Deleting the Tool's local data does not delete videos already hosted on YouTube; those videos must be managed through YouTube Studio or other authorized YouTube interfaces.
6. Changes and contact
This policy may be revised as the Tool changes. The effective date will be updated when material changes are made. For privacy inquiries, email admin@pixelone.work.