How the local application handles data
Privacy Notice
Shorts Network Control is an owner-operated local application for the operator's YouTube channels. It uses the YouTube Data API v3 and YouTube Analytics API to connect selected channels, find editorial leads, upload individually approved videos, verify uploads, and display channel and video performance. The public information pages on this site do not host the dashboard or provide a Google sign-in flow.
Google's handling of information is described in the Google Privacy Policy. Use of YouTube is also subject to the YouTube Terms of Service.
Data accessed and why
| Data | Use and storage |
|---|---|
| Channel identity and statistics | Channel ID, name, upload count, view count, and subscriber count confirm the selected YouTube channel and show its status. These records are stored in local SQLite. |
| OAuth authorization | The app requests youtube.upload, youtube.readonly, and yt-analytics.readonly. It stores each refresh token and granted scopes in local SQLite, with the token encrypted using Fernet. The encryption key and OAuth client secret are kept in a private local configuration file. Short-lived access tokens are used for requests and are not stored in SQLite. |
| Public search leads | Public YouTube video metadata such as ID, URL, title, source channel, publication time, description excerpt, and view count may be retained for editorial discovery. A search result is never treated as permission to reuse footage. |
| Uploads and performance | The selected video file and approved title, description, category, language, audience, visibility, and optional schedule are sent to YouTube only after per-clip review and explicit upload authorization. Video IDs and URLs, upload status, channel/video statistics, authorized analytics snapshots, and reports are stored locally. |
| Production records | Source masters, generated clips, rights evidence, quality-review notes, consent records, schedules, jobs, errors, and logs support editing, audit, and recovery on the operator's computer. |
Sharing and third-party services
The app sends authorized API requests and approved uploads to Google and YouTube. A locally running Chopify Studio service may receive local master-file paths for video processing; the configured adapter accepts only a loopback address and does not send OAuth tokens or channel analytics to Chopify. The local dashboard loads the Inter font from Google Fonts, so opening the dashboard contacts Google for the font stylesheet and file.
The app has no advertising, data-sale, or separate web-analytics feature. These informational pages contain no forms, scripts, tracking code, or remote fonts and do not themselves set cookies. A website host may process ordinary connection logs when serving the pages.
Local storage and security
By default, the application database is data/network.sqlite3; media, logs, and reports are stored under the local data directory. Configuration can change those paths, and local processing projects or backups may hold copies. OAuth refresh tokens are encrypted, but the entire database and media library are not encrypted. The API is bound to local loopback and protects actions with an admin bearer token. The dashboard keeps that token in browser session storage and clears it when the operator locks the dashboard.
Retention, deletion, and revocation
There is no automatic retention schedule. The operator can disconnect a channel in the dashboard. That action pauses the channel, asks Google to revoke its OAuth grant, and removes its stored grant, analytics snapshots, channel statistics, API-discovered lead metadata, and upload response IDs and URLs. Original local media and rights evidence remain, and non-API upload tombstones remain to prevent accidental duplicate uploads. If Google revocation fails, the channel remains paused and the encrypted grant is retained only so revocation can be retried. Revocation may also affect other grants from the same Google account and project.
The operator can separately withdraw consent for one clip upload. Reports, logs, local processing copies, and backups require separate review and deletion. The software does not yet enforce deletion deadlines automatically across those copies. For a deletion request, contact mohamed.elgharef@gmail.com; relevant stored YouTube API data must be removed as soon as possible and within seven calendar days after revocation or a deletion request under the YouTube Developer Policies.
Access can also be revoked in Google Account security settings. Removing local records does not revoke an active Google grant unless the grant is separately revoked. Deleting local records or revoking access does not remove videos held by YouTube; use YouTube Studio to manage those videos.
Contact and audience
The current authorized user is the operator of the local installation. The application does not provide public account registration. For questions about this notice, access, or deletion, email mohamed.elgharef@gmail.com. The local dashboard separately records versioned acceptance of its own privacy notice and requires renewed acceptance when that local notice changes.