Privacy notice
Draft for operator review - 6 September 2026. Published preparation draft; not yet adopted as the final application policy. Identity and contact details are confirmed. The outstanding deletion/retention implementation must be completed before this can serve as the final notice.
Controller and contact
Controller: Manuel Pascal Burghartz, Untergasse 12a, 56645 Nickenich, Rheinland-Pfalz, Germany, highvaluedigitalproducts@gmail.com. The application is operated for the controller's own channels. It is not currently offered as a service to unrelated customers.
Public information website
The static information pages at https://studio.chronoscan.de/ are hosted on the operator's existing Hostinger VPS in Frankfurt, Germany. Serving pages requires processing connection information such as an IP address and requested resource. The site has no account login, submission form, analytics script, advertising tracker or embedded media. The static web service disables its HTTP access log. Hosting and reverse-proxy operational logging is separate and is not represented here as fully audited. The local application database, OAuth credentials and production videos are not part of this public website.
Data processed by the local application
The application stores operator-entered brand profiles, channel addresses, production briefs, source references, scripts, editorial reviews, narration, images, videos, thumbnails, publication text and local job records. These support production, review, reproducibility and publication of the operator's content.
For YouTube connections, it stores the selected channel identifier, the result and time of an identity check, granted permission names, token expiry information and protected OAuth access/refresh tokens. Publication records may contain provider video and comment IDs, a watch URL, upload progress and processing/visibility results. It does not implement audience profiling, subscriber-list collection, viewing-history collection or YouTube Analytics reporting.
The local SQLite database and media files reside on the operator's Windows computer. Tokens and upload-session addresses are protected with Windows DPAPI; the entire media/database store is not described as encrypted by this application. Existing backup functions exclude credentials but retain publication receipts. See the retention limitation below.
YouTube and Google
This application uses YouTube API Services. Google receives OAuth requests and authorized API calls. When a package is released, Google receives the video, chosen thumbnail, title, description, requested visibility and the configured audience/synthetic-media declarations. An optional approved comment is sent as a separate API action. Processing takes place under Google's Privacy Policy and the applicable YouTube terms.
The application does not sell Google user data or use it for advertising profiles. The current creative production context is assembled from local brand profiles, briefs and creative revisions; the YouTube OAuth vault and upload responses are not inputs to that context. They are not used to train a general-purpose AI model through this application.
Other production services
The operator's configured OpenAI/Codex tools receive production prompts, research requests and creative material selected for those tasks. ElevenLabs receives narration text, voice/model settings and API requests when the operator enables speech generation. The resulting narration is stored locally. Provider account settings and provider terms determine their handling of submitted production material. No claim is made here that a consumer subscription supplies every contractual arrangement needed for all future business uses.
Instagram has separate existing connections in the local application. Those tokens are not used for YouTube and are not included in this YouTube review package. TikTok publishing is not connected. Future services require an updated notice before new processing begins.
Purposes and legal basis
OAuth authorization gives the application permission to call selected Google APIs; it does not by itself determine every legal basis under data-protection law. For this own-channel pilot, processing supports the operator's legitimate interest in producing, securing and publishing its own content, subject to the rights of affected people. Requested support correspondence is used to answer the request. Contractual or statutory bases must be recorded where the actual relationship requires them. Do not submit unrelated personal or sensitive information as production input.
Cookies, device access and information website
The local interface sets a same-site cookie for form-request protection and uses a temporary browser-bound OAuth flow. It has no advertising trackers or third-party embedded YouTube player; the local player plays the operator's own generated files. External links only navigate to the indicated service when selected.
For the future public information website, the hosting provider, access-log handling and any host-generated cookies must be documented after hosting is selected. The supplied static pages contain no tracking scripts, embedded remote fonts or analytics code.
Retention, deletion and revocation
The operator can disconnect a YouTube account locally to remove its stored authorization. This does not delete videos on YouTube. Google authorization can separately be revoked at Google account permissions. A Google-side revocation can affect multiple channel grants for the same application.
Current implementation limitation: local disconnect does not yet erase all related channel metadata, publication receipts and historical backup copies. An end-to-end deletion operation and provider-data refresh/expiry process are not yet verified. A powered-off computer cannot execute a deletion deadline. This limitation is a submission blocker, not a completed privacy feature.
The intended service rule is to resolve user-data deletion requests as soon as possible and within seven calendar days, and to refresh or remove applicable YouTube API data within thirty days. Before submission, this rule must be implemented and demonstrated across the active store and application-managed backups. Own production files and legally required business records need a separately justified retention schedule. No indefinite blanket retention is promised.
Your rights and questions
Contact the controller to request access, correction, erasure, restriction or a copy of your personal data where applicable, or to object to processing based on legitimate interests. Where processing relies on consent, it can be withdrawn for future processing. You can complain to the competent data-protection supervisory authority. The responsible authority and international-transfer information depend on the confirmed controller location and actual providers and must be finalized with those details.
Changes
The notice will be updated when the processing, recipients or retention behavior changes. Material changes must be communicated before new data uses are introduced. Current draft status is visible rather than represented as user acceptance.