Privacy policy

Google and YouTube access

When the operator grants access through Google OAuth, ClipForge verifies the selected YouTube channel, uploads videos with their titles and descriptions, checks upload status, and retrieves view counts for the videos it tracks. Google handles the sign-in and consent screens.

Video files and upload metadata are sent to YouTube to perform the requested upload. The visibility configured by the operator determines who can view the uploaded video. The app uses information received from Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

Google user data is used only for the authorized channel connection, publishing, upload monitoring and reporting. At the operator’s request, the public project dashboard shows confirmed publication links and stored cumulative view counts with their measurement times. It is not sold, used for advertising, or used to train machine-learning models.

Other platforms and media delivery

Instagram, TikTok and X are connected separately through Buffer. For requested publications, Buffer receives the finished video and caption, publishes to the authorized account, and provides publication status and available statistics. These connections do not grant Buffer access to the app’s Google OAuth credentials.

A temporary public HTTPS address provided through Cloudflare may deliver one selected finished video to Buffer during a delivery attempt. Other project files, credentials and reports are not served by that video endpoint. The endpoint closes when the attempt finishes; the selected social platform retains its own published copy. Buffer, Cloudflare and the destination platforms process the information needed to provide their services under their respective policies.

Storage and removal

OAuth credentials and detailed project records are stored on the operator’s computer. The public website has no sign-in form and never receives OAuth credentials, passwords, local file paths, raw logs or private account aliases. Its reduced dashboard snapshot includes connection flags, processing states, storage totals, published clip titles and links, and available measured view counters. The snapshot is dated and does not prove the current state of the local process. The operator can remove local credentials and records. To revoke the app’s Google access, use Google Account connections. Published videos can be managed separately in YouTube Studio.

Original media and local reports remain in the project until the operator removes them. Temporary processing files are removed after processing. Finished local exports are removed only after all selected destinations confirm publication. The operator can also disconnect other platforms in their account or Buffer settings; removing local records does not itself delete a published social post.

Website visits

These pages contain no analytics scripts or forms. The hosting provider may log requests for security and service operation.

The dashboard uses a local script to render status. Only after the visitor selects “Poveži lokalni studio” does it request reduced status from ClipForge at 127.0.0.1 on that visitor’s own computer. The browser may request local-network permission. The local endpoint accepts this website’s exact origin; other project routes remain inaccessible from other websites. No local video files or detailed reports are uploaded through this status connection.

Operator and contact

The local studio is operated by Nikola Đurović for WorkflowMinute. Support contact details are shown on the Google consent screen. The WorkflowMinute channel identifies the project. The operator controls local storage and can remove local data and revoke account access as described above.