Privacy Policy

This policy applies to the oldyak application.

oldyak is a publishing tool for creators of short-form video. It publishes finished episodes to the creator's own connected channels, and it is built for creators who want a repeatable way to release their work on a schedule.

This policy explains what Google user data the application accesses, how that data is used, where it is stored, and how it is shared.

1. Google user data we access

The application asks for authorization from the Google Account that owns the YouTube channel being published to. It requests the following OAuth scopes:

Scope	What it allows
`youtube.upload`	Publishing video files and their metadata (title, description, tags, thumbnail, privacy status, and the synthetic-media disclosure flag) to the authorizing account's own YouTube channel.
`youtube.readonly`	Reading basic information about the authorizing account's own channel — channel name, channel ID, subscriber count and video count — so the uploader can confirm that a publication succeeded.

The application does not request, and cannot access, any data belonging to any other Google or YouTube account. It does not read viewer data, comments, messages, watch history, or analytics beyond the channel-level counts listed above.

2. How we use Google user data

To publish video files that the creator has produced, to the creator's own channel.
To set the metadata for those publications, including the AI-generated content disclosure required by YouTube.
To read back basic channel information in order to verify that a publication was successful.

Google user data is used for no other purpose. The application performs no advertising, profiling, analytics or marketing of any kind.

3. How Google user data is stored

All data stays on the machine that runs the tool. Specifically:

OAuth tokens (access token and refresh token) are written to a local file with owner-only file permissions. They are used solely to authenticate API calls and are never transmitted anywhere except to Google's own API endpoints.
Publication records — a local list of which episodes have already been published, together with the returned YouTube video ID — are written to a local file on the same machine.

The application uses no cloud database, no remote server, and no third-party storage of any kind.

4. Sharing

We do not share, transfer, sell, rent or disclose Google user data to any third party.

We do not use Google user data for serving advertisements, and we do not allow humans to read it, except where required by law or where the creator is the data subject.

5. Data retention and deletion

Publication records are kept locally and can be deleted at any time by deleting the local file.
OAuth tokens are kept until the grant is revoked. Revoking access removes the token's validity immediately.
You can revoke this application's access at any time at myaccount.google.com/permissions. Once revoked, the stored token stops working and no further data can be accessed.
To request deletion of any locally stored data, contact us using the address below.

6. Limited Use disclosure

The application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

7. Security

Credential files are stored with owner-only permissions on a machine that is not publicly accessible. All communication with Google services takes place over HTTPS.

8. Children

This application is not directed at children and does not knowingly collect data from anyone under the age of 13.

9. Changes to this policy

If this policy changes, the revised version will be published on this page with an updated date at the bottom.

10. Contact

For any question about this policy, or to request access to or deletion of your data: 454840@qq.com