2. Scope of This Policy

This privacy policy applies to information accessed, processed, or stored through Beacon YouTube Automation, including data made available through Google OAuth and YouTube APIs. This policy specifically addresses the Google and YouTube user data that may be made available to the application through authorized connections.

3. Information We May Access

Depending on the permissions explicitly granted by the user, the application may access information such as:

• YouTube account/channel identifiers
• Channel metadata
• Video identifiers
• Video titles
• Descriptions
• Thumbnails
• Publication/privacy status
• Playlists
• Video metadata
• Upload-related information
• Authorized channel/account information
• Comments
• Ratings
• Captions
• Content-management metadata
• Information required to upload or manage authorized YouTube content
• Other YouTube data within the OAuth permissions explicitly granted by the authorized user

The application does not seek to access data beyond the scopes a user authorizes.

4. How We Use Google/YouTube User Data

Authorized Google/YouTube data may be used for:

• Publishing approved video content
• Managing authorized content
• Retrieving channel/video metadata
• Operating automated publishing workflows
• Preventing duplicate uploads
• Maintaining publishing logs
• Troubleshooting workflow failures
• Managing approved metadata
• Managing comments/engagement when enabled and authorized
• Improving reliability of internal content operations
• Maintaining internal audit records relating to authorized workflow activity

Google user data is used only for legitimate application functionality and authorized business operations.

6. Data Storage

Limited operational data may be stored when necessary. Stored data may include identifiers, publishing records, status information, workflow logs, metadata, deduplication records, and other operational information necessary to run authorized workflows. Data is retained only for legitimate operational, security, troubleshooting, audit, or compliance purposes.

Beacon Media Group, Inc. does not claim that no data is ever stored, and does not make claims of permanent storage or instant deletion where that is not the implemented behavior.

7. Data Sharing

• Beacon Media Group, Inc. does not sell Google user data.
• Google user data is not sold to advertisers.
• Google user data is not used for advertising profiling.
• Data may be processed by infrastructure/service providers strictly where necessary to operate the automation.
• Service providers must only process information for legitimate application operations.

8. Human Access

Authorized Beacon Media Group, Inc. personnel may access operational data only where reasonably necessary for support, troubleshooting, security, workflow maintenance, compliance, and content operations.

9. Security

Beacon Media Group, Inc. uses administrative, technical, and organizational safeguards designed to protect information handled through Beacon YouTube Automation.

10. Revoking Google Access

A user can revoke OAuth access at any time through their Google Account settings. General steps include:

Revoking access will disconnect the application's authorization for the associated Google account.

11. Data Deletion Requests

Users may request deletion of applicable data associated with Beacon YouTube Automation by emailing support@beaconmediagroupinc.com.

Requesters may be asked to verify ownership/authorization before deletion where appropriate. Beacon Media Group, Inc. does not promise deletion of information that must legally be retained.

12. Data Retention

Data is retained only for as long as reasonably necessary for application operation, workflow integrity, troubleshooting, security, compliance, and recordkeeping obligations.

13. Children's Privacy

Beacon YouTube Automation is a business operations application and is not directed to children. It is not intended for use by individuals under the age of 13.

14. Policy Changes

This policy may be updated from time to time. When updated, the effective date at the top of this page will be revised accordingly.