Terms of Service

Last updated: August 23, 2026

These Terms of Service (“Terms”) govern use of ArchitectureEncyclopedia Creator Upload Automation (the “API Client”), a privately operated Python application used by the owner of Architecture Encyclopedia to upload original videos to the owner’s YouTube channel.

The API Client is not offered as a public service to third-party users.

By using the API Client, the operator agrees to these Terms.

1. YouTube API Services

The API Client uses YouTube API Services, including the YouTube Data API v3, and Google OAuth 2.0 to perform authorized video-upload operations.

Use of the API Client is also subject to the applicable terms and policies of Google and YouTube, including:

By using this API Client, the operator agrees to be bound by the YouTube Terms of Service.

If there is a conflict between these Terms and mandatory requirements imposed by YouTube or Google for use of YouTube API Services, the applicable YouTube or Google requirements control with respect to the API Client’s use of those services.

2. Purpose of the API Client

ArchitectureEncyclopedia Creator Upload Automation is intended solely to streamline publication of videos created and controlled by the operator.

Its primary functions may include:

Authenticating the operator through Google OAuth 2.0.
Selecting a local video file for upload.
Supplying a video title and description.
Selecting a privacy status such as public, unlisted, or private.
Providing the applicable audience designation, including whether content is made for kids.
Uploading the selected video and metadata to the operator’s authorized YouTube channel.
Reporting upload status or errors returned by YouTube API Services.

The API Client is not intended to provide access to unrelated YouTube accounts or to act as a public mass-upload service.

3. Authorization

The operator must authorize access to the applicable Google/YouTube account through Google OAuth 2.0 before the API Client can perform authorized YouTube API operations.

The operator must only authorize an account that the operator is legally permitted to access and manage.

The API Client must not be used to obtain, request, collect, or store a user’s Google or YouTube account password.

Authorization may be revoked at any time as described in the Privacy Policy.

4. Operator Control

The operator retains final control over actions performed through the API Client.

Before uploading content, the operator is responsible for reviewing the selected:

Video file
Title
Description
Privacy status
Audience designation
Other upload metadata, if applicable

The API Client should not intentionally upload, modify, or delete YouTube content without an action initiated or approved by the operator.

5. Content Certification and Responsibility

By submitting a video for upload through the API Client, the operator certifies that the content complies with the YouTube Community Guidelines and the YouTube Terms of Service.

The operator is solely responsible for ensuring that uploaded content:

Is lawful.
Does not infringe copyright, trademark, privacy, publicity, or other rights of third parties.
Does not contain content that the operator lacks permission or legal authority to publish.
Complies with the YouTube Community Guidelines.
Complies with applicable YouTube policies concerning spam, deceptive practices, harmful content, child safety, and other restricted content.
Is accurately designated as made for kids or not made for kids when such designation is required.

The API Client does not grant the operator any rights to third-party material.

6. Prohibited Uses

The API Client must not be used to:

Circumvent YouTube restrictions, enforcement actions, upload limits, or access controls.
Artificially manipulate views, likes, comments, subscribers, watch time, or other engagement metrics.
Upload spam, malware, deceptive content, or other content prohibited by YouTube.
Access or manage a YouTube account without authorization.
Harvest or collect information about YouTube users without appropriate authorization and a legitimate permitted purpose.
Interfere with YouTube API Services or attempt to bypass applicable API quotas or security controls.
Use YouTube API Services in a manner that violates applicable law or YouTube/Google policies.

7. Privacy and Data Handling

Use of Google user data and YouTube API data is governed by the API Client’s:

The Privacy Policy explains, among other things:

What information the API Client may access.
How OAuth credentials and YouTube API data are used.
How data may be stored.
How authorization can be revoked.
How stored Authorized Data can be deleted.

The operator should review the Privacy Policy before authorizing the API Client.

8. Availability and Changes

The API Client is privately maintained and may be modified, suspended, or discontinued at any time.

Functionality may also change when necessary to remain compatible with:

YouTube API Services
Google OAuth requirements
YouTube Developer Policies
YouTube API Services Terms of Service
Required Minimum Functionality
Applicable laws or security requirements

No guarantee is made that the API Client will remain continuously available or compatible with future versions of YouTube API Services.

9. YouTube and Google Services

YouTube and Google are independent service providers.

Their services, availability, API behavior, account policies, content policies, quota limits, and enforcement decisions are controlled by Google and/or YouTube, not by ArchitectureEncyclopedia Creator Upload Automation.

Use of YouTube itself remains governed by YouTube’s own terms and policies.

10. Suspension or Termination of Use

Use of the API Client must stop if:

The operator no longer agrees to these Terms.
Required Google/YouTube authorization is revoked.
Continued use would violate applicable law.
Continued use would violate the YouTube Terms of Service, YouTube API Services Terms of Service, Developer Policies, or other applicable YouTube/Google requirements.

OAuth authorization may be revoked through the API Client where supported or through Google Account security settings.

11. Disclaimer

The API Client is provided for the operator’s private use on an “as is” and “as available” basis.

To the extent permitted by applicable law, no warranty is made that the API Client will be uninterrupted, error-free, or compatible with every change to YouTube API Services.

The operator remains responsible for reviewing upload metadata and verifying the result of each upload.

Nothing in these Terms limits any rights or obligations that cannot legally be limited.

12. Changes to These Terms

These Terms may be updated if:

The API Client’s functionality changes.
Its use of YouTube API Services changes.
Google or YouTube changes applicable policies or technical requirements.
Changes are needed for legal, privacy, or security reasons.

The “Last updated” date at the top of this page identifies the current version.

Continued use of the API Client after an update constitutes acceptance of the updated Terms where permitted by applicable law.

13. Contact

Questions regarding these Terms or the API Client may be directed to the operator of ArchitectureEncyclopedia Creator Upload Automation.

Contact: ashedpipe@gmail.com

Website: ArchitectureEncyclopedia Creator Upload Automation

Before publishing: Replace ashedpipe@gmail.com with an email address that you actively monitor.

14. Applicable YouTube and Google Policies

For reference:

ArchitectureEncyclopedia Creator Upload Automation is an independent application and is not endorsed by or affiliated with YouTube or Google.

Terms of Service — ArchitectureEncyclopedia Creator Upload Automation