1. About the service
Clip Operations is the product name for HypeCircuit’s clip-review dashboard. “Operator” means the person or organization that deploys and controls the service. This draft does not identify, establish, or claim a separate legal entity.
The public website is an operator control plane. A separately deployed private worker may monitor only Twitch or Kick sources the signed-in operator has attested are authorized, keep a short rolling buffer while a source is live, analyze permitted signals, prepare candidate drafts, and place approved vertical files in a private library. The website itself does not scrape, record, or expose public stream media. Dashboard-to-worker settings and telemetry require a dedicated signed control connection; the interface says when that connection has not been acknowledged.
“Follow for clips” records the operator’s authorization attestation and selected scope. It does not follow a social account, prove a typed identity, or by itself activate external monitoring. TikTok remains a later delivery destination: no upload, Direct Post, or public posting is active.
2. Approval-first operation
The private worker may identify and prepare a candidate draft only from an activated, authorized source, but a designated person must make the final decision. No clip may be published publicly until the operator confirms the exact media version, caption, destination, rights record, and applicable safety checks. Approved files may be stored in the operator-only private library; this is not public publication.
A quality score never overrides source authorization, intellectual-property rights, platform rules, creator restrictions, revocation, destination scope, or safety policy. Detection settings trade recall against review volume only. No detector is represented as perfect.
3. Authorized use and accounts
You may use the dashboard only if the operator has invited or authorized you. You must protect your access, provide accurate information, and use the service only for lawful business purposes. You may not probe, bypass, or interfere with access controls, safety gates, approval records, or publishing restrictions.
Any Twitch or TikTok account connection must be authorized by that account holder through the platform’s own consent flow. Creator permission to reuse footage does not automatically authorize acting through a creator’s platform account or publishing to it.
4. Creator rights and permissions
Only footage covered by valid permission or another valid rights basis may be processed. The signed-in operator is responsible for creator approval. “Follow for clips” is the operator’s recorded attestation of that approval and stores the operator, time, permitted source use, commercial-use scope, destination accounts, term or expiry, and revocation terms. It is not independent legal verification and does not prove that a typed handle matches the intended platform account.
Before activation, the exact platform identity and official connector must also be verified. If authorization is withdrawn, expires, or becomes uncertain, live checks, collection, new processing, and publishing must stop. The operator must maintain a reviewable record of the rights basis and each final publishing decision.
5. Prohibited and restricted content
The service must not be used to publish unlawful, deceptive, exploitative, or rights-infringing content. The product’s hard gates include:
- no gambling promo codes, affiliate calls to action, deposit inducements, guaranteed-win claims, or underage-targeted gambling content;
- no third-party sports, tournament, film, music, or broadcast footage without documented rights;
- no doxxing, graphic harm, credible threats, sexual content involving minors, or other high-risk sensitive content; and
- no destination or commercial use outside the verified creator permission profile.
Flagged content may require editing, additional evidence, rejection, or escalation. The final approver remains responsible for the decision.
6. Twitch operator connection
The dashboard contains a fail-closed preparation flow that an allowlisted operator may use to connect the operator’s own Twitch account. It requests exactly clips:edit, validates one-time anti-forgery state, exchanges authorization codes only on the server, rejects unexpected scopes, verifies account identity, and encrypts access and refresh tokens before storage. The operator may reverify or disconnect; local disconnect deletes stored tokens unconditionally and requests Twitch revocation only when the controlled external gate is available.
This operator-account connection does not itself create a native Clip, grant creator rights, or authorize VOD retrieval. Native Twitch Clip creation remains disabled. Separately operated source monitoring requires a current creator authorization record, an approved source connection, explicit worker activation, and the fixed safety gates.
7. Telegram approval inbox
Telegram is treated as a private approval inbox, not a public publishing destination. Bot credentials and private chat identifiers stay on the private worker and are not accepted through the dashboard. Dashboard settings store only non-secret notification preferences.
A text alert and a video preview are different rights uses. Media may be transferred to a private Telegram inbox only when the creator’s recorded scope permits that review destination and the same current rights and safety gates are checked. The safe dashboard default is metadata-only. Telegram approval never authorizes public posting.
8. TikTok integration
The dashboard contains a restricted Sandbox Login Kit authorization flow using only user.info.basic. Its start requires a signed-in, allowlisted dashboard operator and explicit server configuration. No upload, Direct Post, or public posting capability is active. Any future scope expansion requires a separate product decision and TikTok approval. video.upload and video.publish remain disabled.
9. Service changes and availability
The pre-launch service may change, pause, or be withdrawn. Production service levels, warranties, indemnities, liability limits, payment terms, governing law, and venue have not been established in this draft and must be completed by the operator, with legal review, before a public commercial launch.
10. Suspension and termination
The operator may suspend access, source monitoring, processing, review delivery, or future delivery when permission, security, safety, platform compliance, or account authorization is missing or disputed. Revocation must stop new processing and invalidate queued actions.
11. Contact
A dedicated public legal or support address has not yet been published. During the current prototype stage, contact the person or workspace channel that provided access. Do not send credentials, access tokens, private creator agreements, or other sensitive data through an unverified contact channel.