Your videos remain private to your account until you delete them.

Google sign-in provides your account identifier, name, email address, and profile image. When you create a job, we store its source URL or private upload reference, processing status, generated transcripts and clip decisions, and output asset references. If you join a feature waitlist, we record that choice against your account so we can contact your signed-in email when access opens.

We use a self-hosted Umami analytics service to understand aggregate page traffic and a small set of product actions such as starting sign-in, creating a job, joining the long-video waitlist, or starting a clip download. It may process a visitor’s truncated network address, browser and device information, language, referring page, and page path. The tracker respects browser Do Not Track settings and does not collect URL query parameters or hashes. Private job-detail pageviews are excluded; approved aggregate actions from those pages use a generic route. We do not send account emails, user IDs, job IDs, source URLs, transcripts, captions, or media to Umami.

• Google account profile and session data
• Source video and generated output media
• Job metadata, transcripts, and processing status
• Aggregate, privacy-filtered website analytics
• Feature waitlist participation

Uploaded source files go directly from your browser to private Cloudflare R2 storage through scoped multipart upload URLs. Processing services access only the assets registered to the job. Audio may be extracted in compressed chunks for transcription; the final clip is rendered from the original source.

AI processing currently uses Cloudflare Workers AI for transcription and the official DeepSeek API for highlight selection and clean-verbatim caption editing. Those providers process the information required to perform those steps under their own service terms.

Videos are not automatically deleted. Source files, outputs, and job records remain available until you delete the job or delete your account. This persistent retention is shown in the creation flow and Settings.

Deleting a finished job removes its registered source and output objects and associated database records. A job that is currently processing is marked for deletion and cleaned up safely when work stops. Account deletion removes all jobs and media before removing the account. Cleanup requests are designed to be idempotent.

New jobs and media belong to the signed-in user that created them. Job, upload, and media routes verify the active session and ownership at the resource level. Unauthorized requests receive a not-found response to avoid disclosing whether another user’s job exists.

Older anonymous result links created before account ownership was introduced can remain accessible to someone who possesses the unguessable job UUID. They are read-only, excluded from job libraries and sitemaps, and cannot expose the original source file.

You can delete individual jobs from your Jobs library and delete your account from Settings. You can also sign out at any time. For privacy or support questions during the beta, contact support@aivideoclipper.app.

• Delete an individual job
• Delete all media and the account
• Sign out and revoke Google access separately