1. Scope and responsible organization
This Privacy Policy explains the current data practices of Essen Digital Studio ("Essen," "we," "us," or "our") for Essen Studio Tools and the requirements that will govern its first internal application, Essen Channel Analytics (the "Application"), if OAuth-enabled analytics functionality is activated.
The Application is a private analytics and editorial decision-support tool for YouTube channels operated by or expressly authorized to Essen Digital Studio. This public website does not itself provide sign-in, set analytics or advertising cookies, or collect YouTube account data.
2. YouTube and Google data we access
The Application uses YouTube API Services, including the YouTube Data API v3, YouTube Analytics API, and YouTube Reporting API. The exact data available depends on the Google account, channel, scopes shown on the Google consent screen, and permissions the user grants.
| Data category | Examples | Why it is needed |
|---|---|---|
| Google and channel identifiers | Authorized account reference, channel ID, channel title, and ownership or content-owner context | To connect the correct authorized channel and label its reports |
| Channel and video metadata | Video IDs, titles, descriptions, publish dates, thumbnails, playlists, visibility or status fields made available by the APIs | To organize analysis and relate performance to published content |
| Performance and analytics data | Views, watch time, average view duration, audience-retention data, traffic-source and geography breakdowns, and impression or click-through metrics when available | To analyze video performance, thumbnails, audience behaviour, and channel trends |
| Reporting data | Bulk reports generated through the YouTube Reporting API for the authorized channel or content owner | To support repeatable historical and operational analysis |
| Captions or transcript material | Caption-track information or transcript text only when made available to the Application through an authorized source | To compare script or transcript structure with audience-retention signals |
| OAuth credentials | Access tokens, refresh tokens, granted scopes, token status, and related authorization metadata | To maintain and verify authorized API access without requesting a Google password |
The Application must not request, collect, or store a user's Google or YouTube password. It is not intended to access private messages, payment-card data, precise location, contacts, Gmail, or unrelated Google-account data.
3. How we use the data
Authorized data is intended to be used only to:
- measure channel, video, and thumbnail performance;
- analyze watch time and audience-retention patterns;
- compare transcripts or editorial structure with performance signals;
- generate internal reports and answer authorized analytical queries;
- support an internal plan–do–check–act content-production workflow;
- maintain authorization, troubleshoot the Application, and meet legal or platform-policy obligations.
We do not intend to sell authorized data, use it for advertising, build unrelated user profiles, conduct surveillance, make credit or employment decisions, or publish or modify YouTube content. Any future material change in purpose must be disclosed, reflected in the requested OAuth scopes, and presented for renewed consent where required.
4. Google OAuth authorization
If OAuth-enabled functionality is activated, the Application will use Google OAuth 2.0. Google—not Essen—will collect the user's Google credentials and display the application identity, requested scopes, and consent choices. The Application will receive authorization tokens only after the user grants access. This public website does not initiate the OAuth flow or receive tokens.
Users may decline any request. If a required scope is declined, the related Application feature must remain unavailable and the Application must not attempt the corresponding API call. Essen will request only scopes needed for disclosed functionality and must revoke and delete tokens that are no longer needed.
Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
5. Data storage and security
Public website
This website is a static site hosted on Cloudflare Pages and delivered through Cloudflare's global network. It does not require an account, run application analytics, set first-party tracking cookies, or receive or store Google OAuth tokens or YouTube Authorized Data. Cloudflare may process standard network and security logs as the website infrastructure provider.
Application systems
As of the date above, Essen has not connected a production application backend or datastore to this website. Accordingly, Essen does not currently store OAuth access tokens, refresh tokens, or YouTube Authorized Data through the Application. There is therefore no current application storage provider, physical storage region, or production Authorized Data store to identify.
OAuth client secrets, tokens, and Authorized Data will never be embedded in or deployed with this public static website. Before a separate backend is permitted to receive any such data, Essen will select and document its provider and region, update this policy, and implement and test access controls, encryption in transit, encryption at rest for OAuth tokens, secret management, least-privilege access, appropriate logging, token revocation, retention, and deletion controls. These are launch conditions, not claims about a backend that does not yet exist.
No internet transmission or storage system can be guaranteed completely secure. If Essen identifies a security incident affecting Authorized Data, it will follow applicable legal and platform notification requirements.
6. Claude, Codex, and other AI processing
Essen does not currently transmit Google OAuth tokens, YouTube Authorized Data, channel analytics, captions, or transcripts from the Application to Anthropic's Claude, OpenAI's Codex, or any other AI provider. No production AI-processing integration is connected to the public website or to an Application backend.
If Essen later offers an optional AI-assisted analysis feature, this policy will be updated before that feature is activated to identify the provider and product mode, the data categories sent, applicable processing or storage locations, retention and training settings, contractual safeguards, and the user control that initiates the transfer. Any transfer must be limited to data needed for the user's requested analysis and must not be used by Essen for advertising or unrelated model training.
8. Retention, refresh, and deletion
The current public website has no application database and retains no Google OAuth tokens or YouTube Authorized Data. Before any backend is allowed to retain such data, Essen must implement and enforce the following:
- store Authorized Data only while needed for the specific purpose approved by an active user;
- refresh or delete stored API data within the time limits applicable under the YouTube API Services Developer Policies, including the general 30-day refresh-or-delete rule where it applies;
- periodically confirm that authorization remains valid;
- after authorization is revoked or can no longer be verified, revoke applicable tokens and delete the related Authorized Data as soon as possible and within seven calendar days;
- after a valid user deletion request, delete data held by the Application as soon as possible and within seven calendar days; and
- make clear that deleting Application data does not delete content or data held by YouTube.
Access and deletion requests are accepted by email at [email protected]. The requester should identify the relevant Google account or YouTube channel without sending a password, OAuth token, or other secret. Essen will verify the requester's authority, acknowledge the request, and confirm the result. Because the current website holds no Authorized Data, a current request will normally be answered by confirming that no such Application data is held. If a future backend holds applicable Authorized Data, Essen will delete it as soon as possible and within seven calendar days after a valid request or loss of valid authorization.
9. Your choices and controls
You may revoke the Application's Google access at any time from Google Account third-party access settings. Revocation stops future access through the revoked authorization but does not itself delete data held by YouTube.
You may also request access to or deletion of data held by the Application by emailing [email protected]. Deletion from the Application does not delete your channel, videos, analytics source data, or other content stored by YouTube.
10. External services and policies
The Application uses YouTube API Services. By using the Application, users also agree to be bound by the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.
Essen Studio Tools and Essen Channel Analytics are products of Essen Digital Studio and are not products of, endorsed by, or affiliated with Google LLC or YouTube.
11. Changes to this policy
We will update this page when data practices, requested scopes, service providers, or legal requirements change. If a change materially expands how Authorized Data is accessed or used, the Application must provide additional notice and request renewed agreement or OAuth consent where required.
12. Contact
Questions, privacy complaints, access requests, and deletion requests may be sent to Essen Digital Studio at [email protected].