Privacy Policy
This policy describes the current build of the Clip Studio. It must be reviewed before production launch or the addition of analytics, accounts, persistent user storage, or payments.
What the Clip Studio processes
When you start a job, the recording you upload and the optional transcript file are sent to the server and processed by the pipeline: transcription, service-structure mapping, moment selection, caption building, and rendering. Transcription runs on the deployment’s own hardware. When AI selection is enabled, transcript text (not the video) is sent to the configured language-model endpoint. The job record stores the transcript text, stage progress, and clip metadata so you can watch progress, cancel, and download the result.
Storage and deletion
Uploads and rendered clips are written to a per-job workspace on the processing server’s disk so the finished MP4 can be reviewed and downloaded. Finished jobs and their files are deleted automatically after about 24 hours; deleting a job through the API removes its record, the uploaded file, and the rendered output immediately. The current repository does not use a database service or third-party object store.
Hosting and technical logs
The company that hosts a deployed copy may process standard request information such as IP address, browser type, requested path, referring page, and timestamps for security and operations. The final production host and retention settings have not been selected in this repository.
If you email [email protected], the email provider will process your address, message, and attachments so we can respond. Do not send confidential pastoral information or sermon media by email.
Cookies and analytics
This repository does not install analytics, advertising trackers, user accounts, or a cookie consent system. If those services are added, this policy and any required consent controls must be updated before they are enabled.
Accounts and future features
Accounts, billing, per-user job history, scheduling, and direct publishing are not active. Before they are added, the product needs a documented processor list, storage locations, retention and deletion rules, security controls, and customer data terms.
Your choices
Nothing uploads until you choose a file and start a job, and every job requires an explicit rights confirmation. You can cancel a running job from the studio, and you can ask for a job’s files to be deleted using the contact address above.
Changes
The effective date will change when this policy is materially updated. A production launch should not rely on this policy without legal and operational review.