Information & control
Privacy notice
ClipBot is used locally by its owner. This notice describes the current development application and separates available controls from services that have not been activated.
Current limit: historical cleanup and scheduled data maintenance are being prepared and tested in isolation. They have not been applied to the owner’s production data or installed as a maintenance service. Protected or unclassified copies require review; no claim of complete production erasure or Google audit clearance is made.
Information the application uses
When authorized YouTube features are used, ClipBot can access the connected channel’s identity, video identifiers and metadata, upload and processing status, and video analytics. Its current requested permissions include upload, read-only YouTube access, read-only analytics and read-only monetary analytics. A permission declaration does not mean every feature is active or every possible field is collected.
ClipBot also stores owner-provided campaign requirements and source references, transcripts, rendered media, caption edits, approval records, schedules, publication and campaign receipts, and local diagnostic records. These support content preparation, duplicate prevention, recovery and campaign deadlines.
Purpose and sharing
Supported, approved YouTube actions send the necessary media and request information to YouTube. Use of YouTube API Services is also governed by the YouTube Terms of Service; Google’s handling of information is described in the Google Privacy Policy.
Content Rewards submissions are made by the owner through its standard website. ClipBot does not automate that site. Receipt and decision evidence is recorded locally. Whop Workforce is under evaluation and is not an active connector.
Clip preparation can use configured AI services for source analysis and editing assistance. Development records may be shared with reviewers expressly authorized by the owner. This build does not offer third-party account management, sell personal information, or use website advertising trackers.
Storage and security
OAuth credentials use the operating system’s credential store. ClipBot does not request a Google password. Application records, media, evidence, exports and backups reside on the owner’s Windows computer and inherit its access protections; the entire data directory is not claimed to be encrypted.
Information is not uploaded to this information website. Do not send passwords, tokens or other credentials by email.
Revoke access and request deletion
In ClipBot, open Campaign Operations → Connections & startup → YouTube access and stored API data. Select the exact account and review the revocation and cleanup preview. Revocation records a persistent account block, requests token revocation at Google, and removes the local credential and supported caches when those steps succeed. Failures remain visible and retries are bounded.
You can also revoke authorization directly in Google’s account permissions. Contact clipbotoperations21@gmail.com to request review or deletion of stored information.
The historical cleanup control inventories selected backup, export and evidence folders before applying a confirmed cleanup. It removes known stored API responses, clears API data in recognized backups, and removes recognized account-specific API exports. It compacts the managed SQLite files; a failed checkpoint or compaction remains unresolved. It preserves local media approvals, owner-provided campaign records and the record of consumed upload attempts so deletion cannot cause another upload.
Protected evidence, changed files and unclassified records remain listed as unresolved. They are not silently erased or reported as clean. Copies outside the inventoried folders require the owner’s attention. Deletion of local records does not delete a video or account on YouTube; those actions require a separate authorized request through YouTube.
Retention and maintenance
The optional maintenance path is separate from the installed local monitor. Once separately configured and started, it checks existing YouTube authorization daily, removes all supported analytics, research and learning caches on each cycle, clears historical API receipt data at a conservative 27-day threshold, and reports file or authorization problems. Overdue authorization blocks ordinary account use. The explicit existing-authorization check verifies the same channel without cleaning data or reconnecting. Fresh consent may resolve an overdue check, but a persistent privacy request still blocks account use. Confirmed revocation triggers the cleanup path; an unavailable check is not treated as proof of revocation.
Maintenance is not activated in the current production installation. A stopped computer or service cannot perform scheduled work; missed checks are handled on the next run. Completion and unresolved copies must be inspected before any deletion deadline or audit-compliance claim is made.
This website
This static package contains no sign-in, forms, embedded video, analytics scripts or advertising scripts. This website is hosted on Cloudflare Pages. Cloudflare processes requests to serve and protect the site, which can include IP addresses and connection information. See Cloudflare’s Privacy Policy. Optional Web Analytics and other added tracking are not part of this package.
Changes and contact
Before using data for a new purpose or enabling a broader service, the notice and relevant owner consent must be updated. Public contact: clipbotoperations21@gmail.com. Effective date: 23 September 2026.