Policy for Youtube

Last Updated: 29 October 2026

EndPoint Clients
Website: https://www.endpointclients.com/
Privacy Contact: info@endpointclients.com

1. Introduction

EndPoint Clients ("EndPoint Clients," "EPC," "we," "us," or "our") is a Pakistan-registered business providing UI/UX Design, Software Development, and AI Automated Solutions.

This Privacy Policy describes how we handle information when operating our internal YouTube content automation workflow using Make.com and, where authorized, YouTube API Services and Google's OAuth 2.0 authorization system (the "Integration"). The Integration is intended to help authorized EndPoint Clients personnel prepare, schedule, upload, and manage videos for YouTube channels owned or authorized for management by EndPoint Clients.

This Integration is an internal business workflow, not a publicly offered software-as-a-service platform. It does not provide external customer registration, subscriptions, or access to unrelated users' YouTube channels.

Our Integration uses YouTube API Services. Use of YouTube through the Integration is subject to applicable YouTube terms and policies. Please also review the YouTube Terms of Service and Google Privacy Policy.

This document concerns the YouTube Integration. Our general website privacy practices, including website inquiries and marketing technologies, are addressed separately in our main website Privacy Policy.

2. Scope and Purpose

We use the Integration to support internal publishing activities, which may include:

Preparing company-created video content and accompanying metadata.
Identifying the authorized YouTube channel selected for a publishing task.
Uploading approved videos through supported YouTube API functionality.
Managing scheduled workflow execution and, where configured and supported, YouTube publication scheduling.
Recording upload status, video identifiers, and operational errors needed to maintain the workflow.
Managing or updating video information only where the workflow has been configured and authorized to do so.

Available capabilities depend on the permissions granted by the Google account holder, YouTube's requirements, and the functions actually enabled in the Make.com scenario.

We do not use this Integration to collect viewers' private information, access unrelated Google services, or carry out undisclosed actions on YouTube accounts.

3. Information We Access and Process

We limit our access to information necessary for the authorized Integration.

3.1 Google Authorization and Connection Information

To authorize YouTube functionality, the Integration may process:

The Google account authorization response and granted OAuth permissions (scopes).
Access tokens and, where issued, refresh tokens.
Token validity, expiration, and connection status.
Account or channel identifiers needed to direct an authorized API request to the appropriate YouTube channel.

We do not ask authorized personnel to provide their Google or YouTube passwords to EndPoint Clients or through an unofficial login form. Google handles the applicable account authentication and consent process.

3.2 YouTube Channel and Video Information

Depending on the granted permissions and API calls used, we may access or receive:

YouTube channel identifier and associated channel title or other limited channel information necessary to confirm the selected destination.
Video identifiers and links for uploaded content.
Video titles, descriptions, tags, category or language details, where used in the workflow.
Video privacy status, scheduled publication time, and upload or processing status.
YouTube API responses and errors relevant to publishing or troubleshooting.

We do not claim to collect channel analytics, subscribers' personal information, comments, or video performance statistics unless the Integration is subsequently configured with an authorized function that requires those data. Such a material change would require an updated disclosure and any necessary additional authorization.

3.3 Company-Created Content and Publishing Instructions

The Integration may process content supplied or approved by EndPoint Clients, including:

Original video files and other media prepared for upload.
Titles, descriptions, tags, and other publishing metadata.
Selected channel, posting schedule, and permitted visibility settings.
Internal approval or publishing instructions.
Upload results, timestamps, and workflow execution outcomes.

Video content may incidentally contain identifiable individuals. EndPoint Clients is responsible for ensuring the appropriate rights, permissions, and disclosures for content that it uploads.

3.4 Make.com Technical Data

As the workflow automation platform, Make.com may process the data passed to or from the configured scenario, such as media files or file references, metadata, API responses, connection details, timestamps, and execution errors. Depending on settings, execution history can also include data processed by individual workflow steps.

We use such information to operate and troubleshoot the Integration. We do not assume that Make.com stores this information in our AWS RDS database or that every Make.com data-retention setting is identical; those details depend on the actual Make.com configuration and contractual terms.

4. How We Use Information

We use the information described above to:

Authorize access: Connect a permitted Google account to the required YouTube functionality.
Identify the destination: Confirm the authorized YouTube channel for each publishing activity.
Publish approved material: Upload company-approved videos and metadata to YouTube, subject to the selected settings and granted permissions.
Coordinate scheduling: Run approved Make.com scenarios and use YouTube scheduling features where supported and configured.
Manage operations: Confirm whether an upload or publication request succeeded and investigate errors.
Maintain security and compliance: Protect authorization credentials and comply with applicable legal obligations and YouTube API Services requirements.

We do not sell YouTube API data or Google authorization credentials. We do not use YouTube API data for advertising audience creation, profiling, targeted advertisements, data brokerage, or training general-purpose AI models. EPC's general website advertising activities are separate from the information acquired through this Integration.

We use information received through Google APIs in accordance with the applicable Google API Services User Data Policy, including its Limited Use requirements where applicable.

5. Google OAuth and YouTube API Permissions

Where the Integration connects to YouTube API Services, authorization takes place through Google's OAuth 2.0 process. The person authorizing access can review the requested permissions and decide whether to grant them.

For example, the YouTube Data API supports the scope https://www.googleapis.com/auth/youtube.upload for uploading videos. Other YouTube scopes may be needed if an enabled Make.com module performs additional authorized channel or video operations. The Integration must request only the permissions actually necessary for its implemented functionality.

Google may issue an access token and, where offline access is authorized, a refresh token. These credentials allow the configured workflow to perform permitted operations without asking the account holder to sign in for every scheduled execution.

Authorization does not transfer ownership of any Google account, YouTube channel, or uploaded video to EndPoint Clients. The account holder may revoke access as described in Section 11.

6. Automated Uploads, Scheduling, and User Control

Authorized personnel remain responsible for selecting the channel, approving content, and deciding the visibility and timing of a publication.

Where the Integration supports video uploads, the user must be able to set or approve YouTube's required video title, description, and privacy status. YouTube supports public, private, and unlisted visibility settings. We will not intentionally change a video's existing visibility without the authorizing user's express instructions.

For an approved scheduled workflow, Make.com may execute the authorized upload or publishing instruction at the configured time without requiring a new sign-in for every execution. This does not authorize the Integration to post unrelated material or change previously selected settings without appropriate authorization.

Where YouTube supports additional publishing fields, such as a scheduled publication date or a self-declaration relating to content made for children or synthetic media, these are subject to the applicable API functions, account settings, and YouTube requirements. We do not claim that all such fields are enabled in our current automation.

EndPoint Clients remains responsible for the content it supplies, including applicable intellectual property rights, sponsorship disclosures, and compliance with YouTube's content policies.

YouTube may apply quota limits, account restrictions, verification requirements, or other technical restrictions to API operations.

7. Information Sharing and Third Parties

Information is processed only as needed for the Integration and its authorized purpose.

Google and YouTube: The Integration sends authorized requests and approved content to YouTube API Services. Google and YouTube handle information under their applicable privacy policies and terms.

Make.com: We use Make.com to run the configured automation, transmit data between workflow steps, and handle relevant execution results. The categories of information available to Make.com depend on the scenario and connection configuration. Make Privacy Notice.

Authorized EndPoint Clients personnel: Access may be granted to personnel who are responsible for preparing content, maintaining connections, approving publication, or troubleshooting the workflow. Access to YouTube-authorized data must be limited to the authorizing user and agents expressly approved by that user, as required by YouTube's policies.

Authorities: We may disclose information where legally required, subject to applicable restrictions and due process.

We do not disclose YouTube API data to unrelated advertisers, data brokers, or other unauthorized recipients. We will not add a new recipient or secondary purpose for Google user data without assessing the relevant policies, making appropriate disclosures, and obtaining any required authorization.

8. Data Security

We recognize that Google authorization credentials and YouTube API data require appropriate protection. Our security responsibilities include restricting access to authorized personnel, protecting credentials against disclosure, securing data transfers, and managing technical access to Make.com scenarios and connected accounts.

OAuth client secrets, access tokens, and refresh tokens must not be published in public website code, public repositories, or publicly accessible workflow documentation. Appropriate security controls must be applied to the services that hold the credentials.

Make.com may retain execution payloads in scenario history depending on the configuration. We review available scenario controls, including settings for limiting stored execution data, when managing sensitive connection or publishing information.

No internet-connected service can guarantee absolute security. If an incident occurs, we will assess and address it according to applicable legal and contractual obligations, including relevant Google and YouTube requirements.

9. Data Retention and Refresh Requirements

We distinguish YouTube API data from original content independently created and stored by EndPoint Clients and from the lead information collected on our corporate website.

OAuth tokens: May be retained only while needed for the authorized connection and in accordance with the consent granted, applicable law, and Google/YouTube requirements.
Most stored YouTube API data: Unless a specific exception applies, authorized or non-authorized API data must be deleted or refreshed within 30 calendar days in accordance with YouTube's Developer Policies.
Certain authorized YouTube statistics and analytics: May be retained for longer where permitted, but the continuing authorization and applicable resource status must be reverified at least every 30 days. This does not imply that our current upload workflow collects such statistics.
Company-created source media: Original videos prepared independently by EndPoint Clients may be maintained for legitimate content production purposes. This is distinct from audiovisual content obtained from YouTube; the Integration does not authorize downloading or storing copies of YouTube videos in violation of YouTube's rules.
Make.com execution history: May be retained according to the configured account, scenario settings, and Make.com's applicable terms, subject to the shorter deletion or refresh requirements that apply to YouTube API data.

Where authorization is withdrawn, deletion is requested, or access is no longer valid, applicable API information must be removed within the relevant YouTube policy deadlines described in Sections 10 and 11.

Our general corporate website's 24-month inquiry retention period does not apply to YouTube API data or OAuth tokens.

10. Requests to Access or Delete Data

An authorized account holder may request deletion of information associated with the Integration without needing an account on a separate EndPoint Clients software platform.

To request deletion:

Email info@endpointclients.com.
Use the subject line YouTube Data Deletion Request — EndPoint Clients.
Identify the relevant YouTube channel or Google connection and describe the information to be removed. Do not send your password or authentication token.
We may reasonably verify your authority over the relevant account or records.
We will process eligible requests in accordance with applicable law and YouTube API Services requirements.

For requests to delete stored YouTube user data under YouTube's Developer Policies, the relevant data must be deleted as soon as possible and within 7 calendar days after the applicable request, subject to any overriding legal requirements.

Deletion may cover retained authorization credentials, applicable YouTube channel or video data, pending workflow instructions, and stored API responses or other data subject to the request. Deletion and cleanup in connected service-provider systems must also be addressed where applicable.

Deleting information from the Integration does not automatically delete a video already published on YouTube. Videos already on YouTube must be managed through YouTube or an appropriately authorized application that supports deletion.

11. Revoking Google and YouTube Access

The Google account holder can review and revoke third-party access using Google's security settings:

Google Account — Third-party connections and access

Locate the application or connection associated with the Integration and remove its access. The visible application name may depend on whether the Google connection is established through Make.com or through a Google Cloud OAuth client configured for EndPoint Clients.

An authorized account holder may also contact info@endpointclients.com to request that the Integration be disconnected.

When a user revokes authorization directly through the Integration's available disconnect process, the applicable token must be revoked programmatically without delay and the authorized YouTube data obtained under that authorization must be deleted as soon as possible, and within 7 calendar days under YouTube's rules.

Where consent is revoked through Google's security settings, the Integration must stop using the revoked authorization, check authorization validity, and delete the associated API data as soon as possible, within the applicable 30-calendar-day outer limit in YouTube's policies.

Revocation prevents new authorized API activity under the affected connection but does not, by itself, remove videos previously published on YouTube. Other business records, if lawfully retained for independent purposes, are handled separately from YouTube API data.

12. International Processing

EndPoint Clients operates from Pakistan. Google, YouTube, and Make.com may process information through infrastructure located in other countries.

Where a relevant international transfer is subject to privacy law requirements, we will assess the applicable safeguards. Processing of Google and YouTube information must also comply with the relevant developer terms and service-provider arrangements.

13. Privacy Rights and Legal Bases

Depending on the processing activity and applicable law, relevant legal bases may include consent, legitimate interests, the performance of an applicable contract, or compliance with legal obligations.

Google OAuth authorization establishes the technical permission for the Integration to access specified Google or YouTube functionality; it does not replace any separate legal basis required by privacy law.

Subject to applicable law, individuals may have rights to access, correct, or delete personal information; object to or restrict certain processing; request eligible data portability; withdraw consent; and complain to an appropriate supervisory authority.

Requests may be sent to info@endpointclients.com. We may need to verify the requester's identity or authority before disclosing or deleting information.

14. Cookies, Advertising, and Other Website Activity

This Integration is an internal workflow; it is not a public application that serves advertisements or uses YouTube API data to create advertising audiences.

Our corporate website may use separate analytics or advertising tools as described in its general Privacy Policy. Such tools and website marketing purposes are separate from the Google and YouTube information obtained for this Integration.

This Integration does not require visitors to install a browser cookie to enable video uploading through Make.com. Google's and Make.com's own sign-in interfaces may independently use cookies or related technologies under their respective notices.

If the Integration later presents a separate user-facing site that stores or accesses cookies or permits third parties to serve content or advertisements, the disclosures and any legally required consent mechanisms will be updated before deployment.

15. Children's Privacy

The Integration is designed for authorized EndPoint Clients personnel and business use, not for children to sign up or connect their own channels.

This does not remove EndPoint Clients' responsibility to use the appropriate YouTube audience designation and follow applicable rules when uploading content that is made for children.

We do not intentionally collect children's personal information through a public registration feature for this Integration.

16. YouTube and Google Policies

The Integration uses YouTube API Services and must comply with the relevant platform requirements. Please review:

EndPoint Clients is an independent company and is not owned, sponsored, or endorsed by Google, YouTube, or Make.com.

This Privacy Policy is not a substitute for the Integration's applicable terms of use. If separate terms of use are provided for the Integration, they must incorporate the required acceptance of the YouTube Terms of Service.

17. Changes to This Privacy Policy

We may update this Privacy Policy when the Integration's functionality, permissions, providers, data practices, or applicable legal and platform requirements change.

If we introduce a new purpose or materially different use of Google or YouTube data, we will update the disclosures and obtain renewed authorization or consent where required before beginning that use.

We will update the "Last Updated" date when this Policy changes.

18. Contact Information

EndPoint Clients
New City Phase 2, F-Block, Street 6B, House # 1
Wah Cantt, Punjab 47040, Pakistan

Website: https://www.endpointclients.com/
Email: info@endpointclients.com

Privacy request subject: Privacy Request — EndPoint Clients
YouTube data deletion subject: YouTube Data Deletion Request — EndPoint Clients