CreatorScopeBETA
Trust & transparency

Privacy Policy

How the CreatorScope website handles information today, and what our planned YouTube integration will require.

Current status — November 17, 2026. This website is an informational product preview. It does not currently connect to YouTube accounts, request OAuth access, accept video uploads or collect YouTube API data. We will revise this policy before any authorized YouTube functionality launches.

1. About CreatorScope

CreatorScope is an independent software project based in Vietnam, accessible at creatorscope.site. The product is being developed for video publishing preparation, multi-channel organization and user-authorized YouTube workflows.

2. Information processed by this website

The public website is a set of informational pages. It does not offer user accounts, forms collecting personal information, ad tracking or Google OAuth sign-in. As with most hosted websites, the hosting provider may process basic technical request information, such as IP addresses, timestamps, browser information and security logs needed to deliver and protect pages. Any such handling is subject to the provider's policies and the actual hosting configuration after deployment.

Our website may request fonts from Google Fonts, which can involve a request to Google-operated font delivery servers. We do not use marketing cookies or behavioral advertising scripts in this website build.

3. Planned YouTube API functionality

CreatorScope plans to use YouTube API Services. When an authorization-based feature is released, users will be asked to connect through Google's OAuth 2.0 flow and to approve only the scopes used by active features. We will not ask for or store Google account passwords.

Depending on features enabled and the permissions granted, the future service may access authorized channel identifiers and names, video metadata (including title, description, tags and video IDs), upload or scheduling status, thumbnails, playlist information and related operational records. We may process a video file supplied by a user in order to upload it to the destination channel they select.

The planned purposes are to prepare and publish user-approved content, manage authorized channel workflows, monitor job outcomes, prevent duplicate uploads and give users control over their own operations. Data will not be made accessible to unrelated channel owners. Specific third-party processors and retention periods will be documented when the operational service is deployed.

4. User instructions and publishing consent

Before an authorized publishing action, the planned application will identify the selected channel, content and intended visibility and timing. Channel owners or permitted managers will authorize actions in accordance with the app's permissions and approval workflow. We will not use permissions to publish to unrelated channels.

5. Retention and deletion

No YouTube API data is currently stored by this public website. For the planned connected service, API-derived data will be refreshed or deleted as required by the YouTube API Services Developer Policies. When a user revokes access or requests deletion, we will remove relevant Authorized Data as soon as possible and within the applicable policy deadline. This does not remove data that remains on YouTube; users must manage YouTube-hosted videos through YouTube or an appropriately authorized application.

6. Revoking Google access

After OAuth functionality launches, users will be able to disconnect their accounts through the application. They can also revoke access directly from their Google Account permissions. For Google's own privacy practices, see the Google Privacy Policy.

7. Sharing, transfers and security

The website does not sell visitor data. We do not operate an advertising network. The operational service is planned to use encrypted transport, appropriate access controls and secured OAuth token handling. These are planned controls and will be described in greater detail once implemented and tested.

8. Contact and requests

For privacy questions, access requests or deletion inquiries, contact us at [email protected]. The public website does not currently connect YouTube accounts or store YouTube API data. Before connected services launch, we will document in-app disconnection and data deletion procedures.

9. Changes

This policy will be revised when the product or its data practices change. Material changes to Google/YouTube data usage will require updated user disclosures and consent where applicable.


Last revised: November 17, 2026. This policy is an accurate description of the current public preview, not a representation that the future operational product has passed a YouTube API compliance audit.