Privacy Policy

1. About Creative OS

Creative OS is private software used by its operator to manage content operations and analyze performance for channels and accounts that the operator owns or is explicitly authorized to access. It is not intended as a public social network, advertising platform or data broker.

2. Use of YouTube API Services

Creative OS uses YouTube API Services, including the YouTube Data API and YouTube Analytics API. When a YouTube channel is connected, access is authorized through Google OAuth.

The integration requests these read-only scopes:

Creative OS does not request or store a user's YouTube password and does not use these scopes to upload, edit or delete YouTube content.

3. Information accessed

Depending on what the YouTube APIs return for an authorized channel, Creative OS may access:

• channel identifiers, channel name/title and upload-playlist identifiers;
• video identifiers, titles, descriptions, publication timestamps and video status metadata;
• video statistics such as view, like and comment counts when available;
• authorized YouTube Analytics data such as views, watch-time and engagement metrics;
• technical metadata needed to operate the connection, such as OAuth status and granted scopes.

Creative OS does not use YouTube API Services to obtain YouTube login credentials or to monitor a user's private browsing history.

4. How the information is used

Authorized YouTube data is used only to:

• identify content and publications belonging to the authorized channel;
• retrieve and review performance metrics;
• maintain historical performance observations for internal analysis;
• operate, secure and troubleshoot the YouTube integration.

Creative OS does not sell YouTube API Data, does not use it for targeted advertising and does not intentionally disclose Authorized Data to unauthorized third parties.

5. Storage and credentials

The YouTube integration is designed so that OAuth secrets are kept separate from normal application data. The Google OAuth client secret and refresh token are stored in the operator's local operating-system credential store. Short-lived access tokens are kept in memory and are not intentionally persisted by Creative OS.

Application records such as publication metadata, authorized analytics data, statistical observations and synchronization metadata may be stored in the operator's private database for legitimate operation and historical analysis.

6. Retention and refresh of YouTube data

Creative OS handles stored YouTube API Data in accordance with the YouTube API Services Developer Policies. Authorized YouTube Analytics data and authorized statistical data may be retained while needed for the authorized purpose and while authorization remains valid. Other stored API metadata is refreshed or deleted as required by applicable YouTube API policies.

The application periodically accesses the APIs under the active authorization. If the authorization is revoked or can no longer be verified, the integration fails closed rather than silently continuing to collect data.

7. Revoking access and requesting deletion

A user can revoke Creative OS access to Google/YouTube data at any time from the Google Account permissions page.

A direct request to delete data associated with an authorization can be sent to privacy@vxns.studio. On a valid direct deletion request, stored user-related data will be removed as soon as reasonably possible and no later than seven calendar days. If authorization is revoked or can no longer be verified, stored data will be handled within the time limits required by the YouTube API Services Developer Policies.

Deleting information stored by Creative OS does not delete content or data stored by YouTube. YouTube content must be managed through YouTube or another authorized YouTube client.

8. Sharing and service providers

Creative OS does not sell Authorized Data. Data may be transmitted to Google/YouTube as necessary to use their APIs and may be processed by infrastructure strictly necessary to operate the software. Creative OS does not intentionally provide Authorized Data to unrelated third parties for their own marketing or advertising purposes.

9. Security

Creative OS uses HTTPS for network communication with Google APIs and separates OAuth secrets from ordinary application data. Access to the private application and its local data is limited to the authorized operator. Reasonable technical and organizational measures are used to protect stored information from unauthorized access, use or disclosure.

10. Cookies and this website

These public information pages do not intentionally use advertising cookies, tracking pixels or behavioral analytics. The Creative OS application itself is separate from this public website.

11. Google and YouTube policies

Use of YouTube-connected features is also subject to the YouTube Terms of Service and the Google Privacy Policy.

12. Changes to this policy

This policy may be updated if Creative OS changes how it accesses or uses YouTube API Data, or if applicable platform requirements change. The date at the top of this page indicates the latest revision.