Privacy Policy

1. Introduction

DMCloudArchitect Video Publisher ("the Application") is a private video publishing platform operated by DMCloudArchitect.

The Application is used to publish video content to:

• YouTube channels owned by DMCloudArchitect.
• Private organizational YouTube channels managed by DMCloudArchitect.
• Client YouTube channels where the channel owner has explicitly authorized DMCloudArchitect to publish content on their behalf using Google's OAuth 2.0 authorization process.

The Application is not offered as a public software platform and does not provide public account registration or self-service access.

---

2. Who We Are

DMCloudArchitect provides cloud architecture, infrastructure automation, content generation, and managed publishing services.

---

3. Information We Collect

Depending on the services provided, the Application may store or process the following information.

Google OAuth Information

• OAuth access token.
• OAuth refresh token.
• OAuth expiration and authorization status information.

YouTube Information

• Authorized YouTube channel identifier.
• YouTube channel name.
• Publishing permissions granted through Google OAuth.

Publishing Information

• Video title and description.
• Tags, category, language, and thumbnail.
• Visibility and scheduling settings.
• Published YouTube video identifier and URL.
• Upload, processing, and publishing status.
• Technical errors returned by the YouTube API.

Internal Workflow Information

• Publishing job identifier.
• Client, project, or campaign identifier.
• Approval and publication status.
• Planned and actual publication dates.
• Technical logs required for troubleshooting.

---

4. How We Use Information

Information is used only to provide and support the authorized video publishing service.

• Authenticate an authorized YouTube account.
• Upload approved videos.
• Apply approved titles, descriptions, tags, thumbnails, categories, visibility, and scheduling settings.
• Record publishing history and the resulting YouTube video identifier.
• Prevent duplicate uploads.
• Troubleshoot failed or incomplete uploads.
• Support approved DMCloudArchitect and client publishing workflows.

Google account information is not used for advertising, profiling, credit decisions, resale, or unrelated marketing.

---

5. Google OAuth Authorization

Every connected YouTube channel must be authorized by its owner or an authorized administrator through Google's OAuth 2.0 authorization process.

DMCloudArchitect never requests or stores Google account passwords. Google handles account authentication and returns authorization credentials that allow the Application to perform approved publishing actions.

The Application requests only the permissions required for the implemented publishing workflow.

---

6. Client Channels

DMCloudArchitect may publish videos on behalf of clients only after the client or an authorized channel representative has granted permission.

Authorization may be supported by:

• Google OAuth authorization.
• A written service agreement.
• Written approval from an authorized client representative.
• An approved content plan or publishing workflow.

Clients remain the owners and controllers of their YouTube channels and may revoke access at any time.

---

7. Data Sharing

DMCloudArchitect does not sell Google user data, OAuth credentials, YouTube channel information, or client publishing data.

Information is not shared with advertisers, data brokers, or unrelated third parties.

Information may be disclosed only when necessary to:

• Operate, host, secure, or support the publishing service.
• Provide services to the client that owns or controls the connected channel.
• Comply with applicable legal obligations.
• Protect the security, integrity, and operation of the Application.

Information associated with one client is not intentionally disclosed to another client.

---

8. Data Security

DMCloudArchitect uses reasonable administrative and technical safeguards to protect OAuth credentials, YouTube channel information, publishing records, and client content.

• Secure storage of OAuth credentials.
• Restricted administrative access.
• Encrypted network communications.
• Authentication and access controls.
• Publishing activity logging.
• Credential and authorization review.
• Separation of client publishing records and configurations.

No method of electronic transmission or storage is completely secure, but DMCloudArchitect takes reasonable measures to protect the information it processes.

---

9. Data Retention

OAuth credentials are retained only while an authorized publishing relationship remains active and access is required to provide the service.

Publishing records may be retained for:

• Operational history.
• Troubleshooting and support.
• Client reporting.
• Security and audit purposes.
• Contractual, accounting, or legal requirements.

Temporary or intermediate video files may be deleted after publication according to the applicable project or client retention process.

---

10. Revoking Access

The Google account owner or authorized channel administrator may revoke the Application's access at any time through the Google Account third-party access settings.

Once authorization is revoked, the Application can no longer make authorized YouTube API requests or publish additional content to the affected channel unless access is granted again.

---

11. Data Deletion

Clients and authorized users may request deletion of:

• Stored OAuth credentials.
• Connected YouTube channel information.
• Publishing history and workflow records.
• Temporary video and publishing files.
• Other information associated with the authorized publishing service.

Deletion requests may be submitted to:

[email protected]

Some records may be retained when required for legal, contractual, accounting, security, backup, or compliance purposes.

---

12. Google API Services User Data Policy

DMCloudArchitect Video Publisher's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including applicable Limited Use requirements.

Google user data is used only to provide or improve the user-facing publishing functionality requested and authorized by the connected account owner.

---

13. YouTube Terms and Policies

Use of DMCloudArchitect Video Publisher is also subject to applicable YouTube terms, API policies, community guidelines, copyright requirements, and other platform rules.

Clients are responsible for confirming that content submitted for publication complies with applicable laws, licenses, permissions, and YouTube requirements.

---

14. Changes to This Policy

This Privacy Policy may be updated when the Application's functionality, data practices, legal requirements, or Google and YouTube requirements change.

The effective date at the top of this page will be updated when material changes are made.

---

15. Contact