TWELVE PAST / PUBLISHER
Account and data handling

Privacy Policy

Last updated: October 25, 2026

Twelve Past Publisher is an independently operated, private tool for publishing music videos to an authorized YouTube channel. It is not a public platform and does not offer general account registration. This policy explains how Google/YouTube account information may be accessed, used, stored, and shared when the owner authorizes the application.

1. Information the application accesses

With the account owner's permission through Google OAuth, the application requests the following scopes:

The application may process and store OAuth credentials and tokens, the authorized channel name and ID, video IDs, upload session/status information, and relevant video metadata (such as title, description, chapters, and thumbnail references). It does not request permission to read Gmail, Contacts, or Drive.

2. How information is used

Google user data is used solely to provide and maintain the owner-authorized YouTube publishing workflow: confirm the correct channel, upload videos requested by the owner, monitor results, and prevent accidental duplicate uploads. The application is not used to serve targeted advertising, sell data, or profile users.

3. Storage and security

The authorization process is initiated on the operator's local computer. Credentials and publishing records may be stored on a privately managed server operated by the developer. Access to authorization files is restricted through operating-system and application controls. Secrets are not intentionally included in the public website or source-code repositories. No security measure can guarantee absolute protection.

Uploaded videos and their metadata are also processed and stored by YouTube under Google's own terms and privacy policies.

4. Sharing and disclosure

Google user data is not sold or shared with advertisers or data brokers. It is exchanged with Google's OAuth and YouTube API services as needed for the authorized workflow. Hosting and infrastructure providers may process limited technical information as service providers. Data may also be disclosed where required by law or reasonably necessary to protect the security of the service.

5. Retention, revocation, and deletion

Authorization data and operational metadata may be retained while the publishing integration is active or while needed for security and troubleshooting. Media-production files are subject to operational retention settings and may be removed after upload and verification. This website does not itself provide media storage or a backup service.

You can revoke authorization in your Google Account connections. Revocation prevents further authorized API access but does not automatically erase local operational records or remove videos already uploaded to YouTube. To request deletion of stored integration data, contact the operator using the support contact shown on the Google OAuth consent screen or through the operator website.

6. Google API Services User Data Policy

Use of information obtained through Google APIs is limited to the purposes described in this policy and complies with the Google API Services User Data Policy, including its applicable Limited Use requirements. Google user data is not used for advertising or sold to third parties.

7. Website visitors

This informational website does not intentionally set analytics or advertising cookies and does not run third-party tracking scripts. The web hosting provider may process standard network request information, such as IP addresses and browser details, for delivery, security, and abuse prevention.

8. Updates and questions

This policy may be updated when the application's functionality or data handling changes. The updated version and date will be published here. Questions about this policy or data deletion may be directed to the support contact on the application's Google consent screen, or through caltinsoy.com.