One internal workflow
From authorized footage to short-form content.
CLIPOPS is software used by Bohuslav Horký to operate the Zyvrix short-form content business, currently focused on gaming. Its primary business direction is paid clipping assignments and campaigns. It combines local video processing with controlled review and a YouTube publishing integration.
Prepare and review
Local tools transcribe supplied footage, select segments, create vertical compositions and render captions. Quality and rights checks are recorded before a clip can proceed. Some text-review steps use external AI services.
Control delivery
A local draft editor shows the destination channel, title, description, requested visibility and publishing checks. Saving a draft does not upload it. YouTube delivery is currently disabled.
Who uses CLIPOPS?
CLIPOPS currently serves the project owner's internal media operation, including the Zyvrix Gaming channel. It is not offered here as a public service, and this website has no registration, account connection or upload function.
CLIPOPS is the application name. Zyvrix is the media brand. CLIPOPS is operated by Bohuslav Horký, a natural person operating from the Czech Republic. Zyvrix is not a separate legal entity.
Business scope and intended workflow
- Paid clipping campaigns — primary direction: the intended Hermes-managed workflow is to find suitable assignments, work with lawfully accessible sources, produce clips, publish them on the appropriate thematic channel and track results. This describes the business objective, not proof of an accepted assignment, earned payout or a completed public-publishing workflow.
- Licensed esports recordings — supplementary direction: public recordings may be used only within documented licence terms, rights-holder rules or specific permission. A public URL alone does not authorize acquisition, downloading, editing, republication or commercial use.
- Original productions: the operator may set a creative brief for content using owned, licensed or generated materials. A complete autonomous brief-to-original-content workflow is a target capability; it is not claimed as implemented. The current documented production path processes supplied authorized video.
One operator does not mean that every source is owned by that operator. CLIPOPS is not a public application for customers to connect their accounts. Source or campaign permissions should define the permitted uses and may cover further clips while that scope remains valid; fresh manual permission for each clip is needed only where the applicable conditions require it. Before any new external source enters production, evidence must cover its intended use and any processing of identifiable people. A licence, public availability or campaign brief is not automatic evidence of that basis. Historical test material is excluded from production reuse and public publication.
Current scope
The YouTube integration uses YouTube API Services for account checks, controlled uploads and basic video statistics. Support for selecting private, unlisted or public visibility exists, but public delivery and API audit approval are not established by this website. Other social-platform publishing integrations are not currently offered.
Automation does not establish copyright permission, guarantee accurate captions or certify platform compliance. Unresolved checks can prevent publication.
Contact
Website domain: zyvrixmedia.com. This informational website uses static Cloudflare Pages hosting; its Pages address is zyvrixmedia.pages.dev. Web Analytics remains disabled; this website includes no custom analytics, cookies, forms, login or embedded media. Cloudflare still processes technical traffic data to deliver and protect the site; see the Privacy Policy.
Operator: Bohuslav Horký, Czech Republic, under the Zyvrix brand.
Support and privacy: clip.ops11@gmail.com. For a data request, identify the channel or material concerned and the request scope. Never send a password or token. See data requests and account disconnection.
Registered working files follow category-specific retention rules. Active or shared files remain protected, and historical files are not deleted on age alone. These rules do not automatically erase API records, tokens, audit copies or backups.