YOUR INFORMATION
Privacy Policy
What English Shorts Factory accesses, why it needs access, and how to contact the operator about your data.
Effective date: October 13, 2026
1. About this policy
English Shorts Factory, also referred to as UCF, is an independently operated application for preparing, rendering, checking and publishing educational video content. This policy covers its Google and YouTube integrations, application records, production files and these public information pages.
The operator can be contacted at englishshortsfactory@gmail.com. The application uses YouTube API Services. Google and YouTube operate under their own Google Privacy Policy and YouTube Terms of Service. Use of the YouTube integration is subject to those terms.
2. Information received from Google and YouTube
Information accessed depends on the permissions granted and the features enabled for the connected channel. It can include:
- Authorization and channel identity: a Google account identifier, the selected YouTube channel identifier and title, granted scopes, authorization status, and access and refresh tokens used by the application.
- Video metadata: video identifiers, titles, publication times, privacy status, thumbnail URLs and aggregate view, like and comment counts. Thumbnail URLs are metadata; this does not imply downloading thumbnails.
- Channel performance: views and engaged views, watch time, average viewing duration and percentage, likes and comments as counts, subscriber gains and losses, traffic sources, reported search terms, and available thumbnail impression and click-through metrics.
- Report dimensions: reporting dates, channel and video identifiers, and dimensions returned by supported reports, such as country, subscribed status and live/on-demand status. These are reported dimensions and aggregates, not individual viewers' identities.
- Publishing information: the rendered video, title, description, tags, intended visibility and schedule, upload-session references, returned YouTube video identifiers, upload progress and publication status.
The supported Analytics features read aggregate performance and report data. They do not collect individual viewers' Google login credentials or the bodies of viewer comments. The operator's own Google or YouTube password is not requested or stored by UCF.
3. Why OAuth permissions are requested
Google OAuth is used to authorize a specific account and channel. Read access and Publishing authorization are separate application bindings.
| Permission | Use in English Shorts Factory |
|---|---|
openid | Verify the Google account identity associated with authorization. |
youtube.readonly | Identify the owned channel and read supported video and channel metadata. |
yt-analytics.readonly | Read the authorized channel's supported Analytics and Reporting data. |
youtube.upload | Upload educational videos to the authorized channel. |
youtube.force-ssl | Support video-status updates needed for visibility and scheduled publication. The scope grants broader YouTube-management permission than these particular operations. |
The names above abbreviate the Google API scope URLs. Granting a scope does not mean that every action allowed by that scope is performed. UCF checks the channel binding and current authorization before admitted operations.
4. How information is used
Channel and account identifiers bind operations to the authorized channel. OAuth credentials are used to authenticate API requests and, when needed, refresh access. Metadata and Analytics reports support performance summaries, evidence-based content selection and production decisions for that channel.
Publishing information is used to prepare an upload, track the attempt, set the intended publication schedule and reconcile the result. Automation is subject to the owner's enabled policy, applicable permissions, quality checks, quotas and budgets. Workflow and attempt records support accountability and protection against repeating an uncertain publishing effect.
Use of Google API data is limited to the authorized channel features described here. These public pages do not display private channel data, OAuth credentials, production records or Analytics reports.
5. Storage and protection
Application records are stored in an operator-controlled PostgreSQL deployment. Production media and Analytics objects are held in separate operator-controlled storage locations. Independent control records govern authorization withdrawal, deletion and recovery.
OAuth credentials are kept in OS-backed secret storage, using Windows Credential Manager in the current deployment. Application records hold scoped references and integrity fingerprints rather than embedding those credential bytes in the public website. Protected operator access, session controls, channel-scoped permissions, integrity checks and independent authority controls are used to limit access and admitted actions.
Recovery copies of application records, media, Analytics objects and control records are maintained locally and in an operator-controlled private Google Drive recovery folder. Credential tokens are excluded from the deployment recovery exports. This policy does not claim a universal encryption-at-rest configuration for every database or media file.
7. Retention and deletion
Retention follows the configured resource rules, publication state and operational recovery requirements. There is no single automatic retention period for all UCF data. Rendered MP4s can have deletion deadlines or explicit retention holds; Analytics data can exist in managed copies and recovery archives.
Deletion is an operator-controlled process. Supported mechanisms include withdrawing Analytics authority, purging managed Analytics copies, and deleting eligible rendered publication artifacts under their configured retention rules. Independent deletion and withdrawal records are used to prevent older recovery copies from silently reactivating data that those controls deny.
Disconnecting Google access does not by itself delete existing local records, every recovery copy, or videos already uploaded to YouTube. Cancelling a publication intent does not delete its finished MP4. Recovery archives and historical records require their applicable cleanup procedures.
To request deletion of information held by UCF, email englishshortsfactory@gmail.com and identify the relevant channel or account. The operator will verify the request and determine the applicable records, media, managed copies and recovery copies. Do not send passwords or tokens. No unimplemented automatic deletion deadline is promised by this policy.
8. Withdrawing Google access
You can review and revoke English Shorts Factory's access through your Google Account connections and permissions. Google controls the effect of that revocation on future API authorization.
The protected UCF interface also provides separate disconnection controls for its read connection and Publishing permission. Local withdrawal removes the corresponding application authority and queues applicable provider cleanup. If provider cleanup is pending, local withdrawal and provider-side revocation are distinct states.
Revocation prevents continued authorized access when enforced by Google; it is not a request to delete existing stored copies. For deletion, contact the operator using the process above. Manage or delete already uploaded videos through YouTube's own controls as appropriate.
10. Questions, requests and changes
For privacy questions, complaints, access requests or deletion requests, contact englishshortsfactory@gmail.com. Include enough channel or account information to locate the relevant records, but never include a password, client secret, access token or refresh token.
This policy may be updated to reflect changes to the application or its data practices. The effective date above identifies the version of the policy. English Shorts Factory is not affiliated with or endorsed by Google or YouTube.