Operator / API Client: Eastern Histories
YouTube channel: youtube.com/@EasternHistories
Privacy contact: amadeus.ovo@gmail.com

1. Scope

This Privacy Policy describes how the Eastern Histories internal tools and related API clients (together, the “API Client”) access, collect, store, use, share, and delete information when they use YouTube API Services.

The API Client is operated for the Eastern Histories YouTube channel. It is used to manage our own channel (branding, metadata, privacy settings, uploads, playlists, analytics, and production pipeline automation). It is not a public multi-user product that invites third-party end users to sign in with their Google accounts.

By using the API Client, you agree to this Privacy Policy and to the YouTube Terms of Service.

2. YouTube API Services

The API Client uses YouTube API Services (including the YouTube Data API and, when needed, YouTube Analytics / Reporting APIs). Use of those services is also subject to Google’s policies:

3. Information we access and collect

Depending on the features in use and the OAuth scopes granted, the API Client may access:

We do not request, collect, or store YouTube usernames/passwords. Users authenticate only through Google’s official OAuth flow.

4. How we use information

We use the information described above solely to:

We do not use Authorized Data to sell advertising profiles, train public models for unrelated products, surveil third parties, or build independently calculated metrics that replace official YouTube metrics.

5. Sharing

We do not sell personal information. We do not share Authorized Data with unaffiliated third parties for their own marketing.

Limited sharing may occur only as follows:

Authorized Data retrieved for a user/channel is not displayed to other end users. This API Client is for the channel operator and authorized agents working under confidentiality.

6. Storage, retention, and security

7. Cookies and similar technologies

This static privacy page does not set first-party advertising cookies and does not use third-party ad networks. Hosting infrastructure (Cloudflare) may process standard server/security logs and may use cookies or similar technologies for security, performance, or abuse prevention as described in Cloudflare’s documentation.

The API Client itself does not place advertising trackers. If a future user-facing feature embeds the YouTube player, Google/YouTube may collect data as described in the Google Privacy Policy and related YouTube terms.

We do not currently allow third parties to serve advertisements through the API Client.

8. Your choices: revoke access and delete data

You can control authorization in two ways:

  1. Google account permissions — revoke the API Client’s access at any time: https://security.google.com/settings/security/permissions (also reachable from Google Account → Security → Third-party access).
  2. Contact us — email amadeus.ovo@gmail.com to request deletion of data stored by the API Client related to your authorization.

When consent is revoked or a deletion request is received, we delete stored Authorized Data associated with that authorization as soon as practicable and within the timeframes required by the YouTube API Services Developer Policies (including token revocation and deletion windows).

Deleting data stored by the API Client does not delete data stored by YouTube itself. To change or delete data on YouTube, use YouTube / Google Account tools (or an authorized client that supports those operations).

9. Children’s privacy

The API Client is not directed to children. We do not knowingly collect personal information from children. Eastern Histories content and tooling are intended for general audiences and channel operations by adults.

10. International processing

Information may be processed on systems and infrastructure located outside your country of residence (including services operated by Google/YouTube and Cloudflare). Where required, we rely on appropriate safeguards and contractual/technical measures.

11. Changes to this policy

We may update this Privacy Policy to reflect product, legal, or policy changes. The “Last updated” date at the top will change when we do. Material changes that expand how Authorized Data is used will be reflected here before those practices begin; re-acceptance may be required where the YouTube API Developer Policies require it.

12. Contact

Questions or complaints about this Privacy Policy or the API Client’s privacy practices: