1. Scope and current status
This policy covers the public Clip Operations dashboard operated under the HypeCircuit product name, its private approved-clip library, and a separately operated private clip worker. There is no production social-posting connection.
The public website does not run product analytics or advertising trackers, follow platform accounts, record public streams, or expose creator media. A private worker may check and monitor only operator-attested Twitch or Kick sources, keep a short rolling media buffer while an authorized source is live, analyze permitted moment signals, create candidate drafts, send scoped private-review notifications, and transfer human-approved renders to the operator-only library. The website reports when signed settings and telemetry synchronization with that worker is unavailable.
A controlled Twitch preparation path may authorize the operator’s own account using exactly clips:edit. A separate TikTok Sandbox path may authorize an operator-owned target account using user.info.basic. No public posting or native Twitch Clip action is enabled. Hosting, workspace-authentication, private worker hosting, Twitch or Kick source access, Telegram, and storage providers may process information needed for their configured task under their own terms.
2. Source and approval records
The control plane may store a typed platform handle, display label, source type, priority, content lane, detection preset, follow/pause/mute state, signed-in operator identifier, authorization attestation and version, confirmation time, permitted source use, commercial-use and destination scope, expiry and revocation terms, non-secret Telegram preferences, desired worker configuration revision, sanitized worker health counters, aggregate candidate signals, safety/rights results, operator decision, feedback reason, timestamp, and credential-free audit event. A typed handle is not by itself an externally verified platform identity.
The private worker may temporarily store rolling source segments, local detector state, candidate metadata, draft previews, subtitle timing, operator decision audit records, and approved artifacts. The private library stores an approved MP4 plus minimum title, caption, source label, score, size, and timestamps. The dashboard must not fabricate worker telemetry or candidates when synchronization is absent.
3. Twitch operator and TikTok Sandbox information
After an operator completes a configured authorization flow, the service uses only information necessary to maintain and verify that connection:
- authorization data: access and refresh tokens, token expiry, and exact granted scope;
- basic platform identity: Twitch user ID, login, display name, avatar URL, and broadcaster type, or TikTok app-specific Open ID, display name, and avatar URL;
- security metadata: operator identifier, hashed one-time OAuth state, verification timestamps, and non-secret outcomes; and
- revocation state: whether remote revocation was confirmed or manual revocation is required.
Twitch requests exactly clips:edit; TikTok requests exactly user.info.basic. Tokens use provider-specific AES-GCM encryption keys and are stored only as ciphertext in the managed server database. Encryption keys, client secrets, the operator allowlist, and plaintext tokens are excluded from client code and the database. Unexpected scope causes rejection rather than retention.
4. Why information is used
Control-plane records support rights verification, source-state management, transparent ranking, safety review, human decisions, future calibration analysis, and auditability. Twitch operator and TikTok Sandbox data is used only to verify and maintain the intended account connection and honor disconnect or revocation.
The service is not designed to sell personal information, build advertising profiles, target minors, inspect connected-account video libraries, or infer sensitive personal traits from creator streams. Its permitted worker analysis is limited to moment-quality and safety signals needed to prepare approval drafts.
5. Private processing, not public posting
The Twitch preparation authorization requests only clips:edit, but the native Create Clip action is disabled. The TikTok authorization requests only user.info.basic and does not request video.upload, video.publish, video-list, or another media scope. The service cannot Direct Post or publish publicly.
Private source processing is separate from social posting. It requires a current creator authorization record and explicit worker activation. A Telegram text alert is also separate from sending a video preview; the latter requires a permitted private-review destination. Any future public-delivery scope requires an explicit product decision, updated notice and consent, platform approval, and a new review of creator-rights, content-safety, destination, revocation, and final human-approval controls.
6. Storage and security principles
Client secrets and account tokens remain server-side, encrypted at rest, excluded from browser storage, screenshots, analytics, and support messages, and accessible only to the relevant authorization service. Telegram bot tokens and raw private-chat identifiers stay on the private worker; dashboard fields accept only non-secret labels and preferences. A separate worker-control secret authenticates configuration and health synchronization.
The service applies secure one-time OAuth state, exact least-privilege scope checks, account-identity verification, authenticated operator mutations, signed and replay-resistant worker requests, token refresh controls, and credential-free audit events. No security measure eliminates all risk; key rotation and incident procedures must be maintained before broader use.
7. Retention and deletion
Account tokens are kept only while the controlled connection remains active and necessary. Disconnect deletes the local encrypted record unconditionally and requests provider revocation when the corresponding external gate is available. If remote revocation cannot be confirmed, the dashboard requires manual removal through the platform’s account Connections settings.
OAuth state expires after ten minutes. Local watch/source records remain until an operator unfollows or deletes them. The current private worker is designed to prune its rolling segment buffer after roughly thirty minutes; rejected draft media is deleted, while approved artifacts may remain in the private worker and library until the operator removes them. Candidate, audit, and approval records may be retained as needed for security, rights, approval, and revocation evidence. Final production retention periods and deletion tooling must still be published.
8. Sharing and service providers
Information would be shared only with providers needed to host, secure, process, or deliver an approved workflow. Providers should receive only the data needed for their task and be subject to appropriate contractual and security controls. The operator must publish its finalized provider list and cross-border processing information before production launch.
9. Choices, access, and revocation
Twitch and TikTok users may decline or revoke authorization through their platform. Creators may exercise revocation rights under their agreement. The operator must provide a verified method to request access, correction, deletion, or restriction where applicable and must authenticate requests before disclosing information.
10. Children
The service is not intended for children and must not target minors with gambling or other age-restricted content. If information is collected contrary to applicable age requirements, processing must stop and the information must be deleted as required.
11. Changes and contact
This policy must be updated before production activation to identify the operator, jurisdiction-specific rights, finalized retention periods, service providers, and a public privacy contact. Material changes should be dated and communicated appropriately.
A dedicated public privacy address has not yet been published. During the prototype stage, contact the person or workspace channel that provided access. Do not include passwords, client secrets, access tokens, or unredacted creator agreements in an initial request.