Privacy Policy

ClippedUp is the video-clipping service at clippedup.app. The operator is based in the United Kingdom. Our intended audience is worldwide and aged 18 or over.

For account administration and operating the service, the operator determines why and how information is used. A business uploading recordings about other people may be the controller, with ClippedUp acting as its processor. Those roles and an appropriate data-processing agreement must be confirmed; this notice is not that agreement.

We receive information you enter, files you upload, material produced during processing and technical information from use of the service. Recordings may include people who do not have a ClippedUp account.

An email address and password are required for an account, and a video is needed for a processing request. Optional instructions and styles are not required for every feature. Without necessary information, the corresponding feature cannot be provided. Signing up is not a legal requirement.

• Account information: email, supplied name (or a name derived from the email), account identifier, password hash, role, plan and creation date.
• Trial information: a browser-generated trial identifier, related projects and clip counts. A trial is not necessarily anonymous personal data.
• Uploaded media: video/audio, file name, size, format, part checksums and storage references used for uploading, processing and reuse.
• Generated material: transcripts and word timings, clips, thumbnails, captions/corrections, titles, selected timestamps, editorial assessments and framing metadata.
• Creative instructions: chat messages/replies, conversation history, topics, creative notes, reusable briefs and template preferences.
• Usage and processing records: allowances, request identifiers, stages, timestamps and errors.
• Subscription records: Stripe checkout/customer/subscription identifiers, plan, status, amount/currency and cancellation status where billing is used.
• Support messages and information needed to identify a request.
• Browser and connection information: browser storage and device/request information. Hosting or analytics services may receive IP addresses, page URLs and interactions.

For AI clipping, the server extracts audio and sends it through the Emergent integration to OpenAI transcription. Transcript text/timings and creative instructions are used by OpenAI language models to identify and assess moments. Transcripts and results are saved for editing and reuse.

The AI Clip Specialist sends messages, recent conversation context, the current brief and attached-file metadata to the language model. Attaching a video alone does not begin transcription; generation has a separate confirmation step. Chat itself uses AI before generation is confirmed.

Automatic framing, when enabled, detects face positions and estimates visible speaking activity on the server to compose the frame. It does not implement named-person identification or identity matching between people. Images and derived information can still be personal data.

Manual Clips trims selected timestamps on the server without calling the AI transcription/highlight service or adding AI captions/framing. It still uploads, stores and processes media. Reusing a source previously processed with AI does not erase that earlier processing or transcript.

Creator Studio is different: after you confirm Generate, reduced-size full-clip review copies, photos shown as timed stills, available original audio and an optional brief are sent through Emergent to Google Gemini. Gemini reviews all selected assets to propose visual observations, source moments and an edit order. These observations, selections, briefs, jobs and finished montages are saved. Video is sampled internally by the provider; this is not frame-perfect analysis. Uploading and preparing previews alone do not call Gemini.

AI replies, captions, titles and scores can be wrong. Scores are editorial assessments, not predictions of views or decisions about legal rights. Review results before sharing. The app has no general-model training workflow; this does not establish providers’ retention or use under their contracts.

The operator must approve and document these bases before a final policy takes effect. Contract necessity for an account holder does not automatically justify processing other people in their recordings.

Accepting terms is not blanket privacy consent. Consent, if used, must be specific and withdrawable. Special-category or criminal-offence information may require additional conditions; a contract or content licence alone is insufficient. Do not upload highly sensitive information until suitable conditions and safeguards have been agreed.

• Requested accounts, uploads, editing, AI/manual clipping and downloads: contract performance or requested pre-contract steps where the individual is a party; necessity and third-party content roles need confirmation.
• Trial limits, reliability and investigation of misuse/errors: proposed legitimate interests in a functioning, proportionately protected service; necessity, balancing and retention must be documented.
• Support: contract where relevant, legitimate interests for general enquiries, and legal obligations for applicable data-protection duties.
• Subscriptions and required accounting records: contract and identified legal obligations.
• Optional analytics or replay: basis and applicable consent/exception requirements remain undecided. No app-level consent control is currently implemented.

The following services appear in the application’s current data flows. Their legal roles and full contractual terms still need confirmation. There is no advertising or data-sale workflow in the reviewed app, but that does not establish all organisational or provider practices.

• Emergent-hosted infrastructure and object storage: application delivery, persistent media storage and the AI integration layer. Application metadata is stored in MongoDB; this is not a claim that MongoDB Atlas is the contracted host.
• OpenAI through Emergent: transcription, text-based clip assessment and conversational planning.
• Google Gemini through Emergent: visual/audio review of selected Creator Studio clips and photos, optional briefs, and montage selections. Provider retention, regions and data-use terms still need confirmation.
• Stripe: hosted checkout and subscription management when used. The app stores references and status, not full card numbers or CVCs. Stripe may collect billing details and process information under its own terms.
• PostHog/platform scripts: analytics is configured through an Emergent endpoint, with session-recording-related options. Actual collection, configuration and retention remain unverified.
• Google Fonts and Fontshare: browser font requests disclose connection/request information to those hosts.
• Google/Gmail: the supplied support/privacy mailbox uses Gmail. Mailbox access and retention must be managed by the operator.

Current general project-results links and individual clip playback, download and thumbnail links do not require login when the identifying URL is known. Someone with a link may access the associated result, including media or project/clip details. Account-specific library and editing controls are different from link access.

Manual source previews use an owner-issued, time-limited access link. That does not make every exported manual clip or general results link owner-only. Treat result links as shareable, not as confidential access controls.

New Creator Studio asset thumbnails and montage exports use separate owner-authenticated endpoints. They are not available through those legacy known-link routes. Preview/download copies fetched into your browser remain accessible on that device until released or saved by you.

ClippedUp uses browser storage and embedded services may use additional storage. Local storage is not cleared just because a tab closes. Session storage normally lasts for that tab session, but browser restore behaviour can vary.

Clearing site data may sign you out or remove unsaved selections and trial/upload references. It does not delete uploaded files, chats or other server records, and is not a substitute for an analytics consent or objection control.

• Sign-in token: valid for seven days, with no separate automatic local-storage expiry. Logout or an unsuccessful account load clears the stored token.
• Trial identifier, theme preference, last selected AI conversation and manual source: stored locally with no app-set expiry found.
• AI upload retry reference and file signature (name, size and last-modified time): cleared after successful attachment; interrupted entries may remain.
• Manual titles, timestamps and queued selections: session drafts cleared by the cut-list reset action.
• Creator Studio selected asset identifiers, optional brief, target length and request reference: saved in session storage for that signed-in account. Deselecting or clearing a draft does not erase stored media.
• Completion animation marker: session storage used to avoid replaying the animation.
• Analytics/provider storage: names, purposes, payloads, recipients and lifetimes have not yet been established.

The app has no general automatic retention/deletion schedule for accounts, source media/upload parts, clips/thumbnails, transcripts, conversations or project records. Failed uploads and superseded rendered objects may remain. Removing a brief or custom template does not remove historical projects or media. Creator Studio also retains manual revision settings, the original AI edit plan, reusable rendered-shot caches and older output objects. Manual adjustments are rendered on the server without another Gemini review.

Normal worker cleanup removes local temporary processing directories. Persistent object storage, logs, provider-held copies, backups and abrupt crashes are separate matters. Manual preview grants expire after 60 minutes; that expires access, not the recording.

Contact clippedup.app@gmail.com to request deletion. There is no self-service account, project/media or chat deletion control. An email is an operator-handled request, not an automated erase action.

• Read the draft deletion instructions

A UK operator and worldwide audience do not mean UK-only storage. The application code does not establish where all infrastructure, AI, analytics, payment and email data is processed or which transfer safeguards apply.

Depending on applicable law and the processing basis, you may request access, correction, erasure, restriction or portability. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. Rights can be subject to exceptions.

Your right to object: you may object to legitimate-interests processing on grounds relating to your situation. You may object to direct marketing at any time if it is introduced.

Contact clippedup.app@gmail.com. You do not need an account to raise a concern about yourself in a recording. Provide only what is needed to locate the issue. Proportionate identity/authority checks may be required; do not send passwords, card details or identity documents unless necessary and a suitable method has been agreed.

UK GDPR requests normally require a response within one month, subject to applicable identity/clarification rules and lawful extensions or exceptions. That is a legal response framework, not a promise that every file and backup disappears within one month. Any lawful extension, refusal or necessary retention needs an explanation.

You may complain to the UK Information Commissioner’s Office without our permission, or to another competent local authority. Additional international notices, rights and representative obligations remain to be assessed.

• UK Information Commissioner’s Office — complaints

ClippedUp is intended for adults aged 18 or over. There is no age-verification process in the current app. Adult account eligibility does not prevent children appearing in recordings; uploaders still need a lawful basis and permissions. Contact us about suspected child use or concerns about a child’s information.

The app uses hashed passwords, access checks on account operations and bounded manual-preview grants. No system is guaranteed secure. The link-access limitations above must not be read as a promise of owner-only access or end-to-end encryption.

No YouTube, TikTok or Instagram connection is currently implemented. The following describes planned handling only, not a working feature or provider approval.

The intended YouTube feature will use YouTube API Services. With your authorization, ClippedUp would send a selected finished clip and the title, description, audience/privacy settings and metadata you explicitly confirm. Your original source is supplied by you, not downloaded from YouTube.

The exact scopes, returned account/channel fields, encrypted credentials, upload identifiers/statuses and retention must match the implementation. Upload permission must not be described as unrestricted access to your profile/channel.

Google handles information under its privacy policy. Google account permissions can revoke a future connection. An in-app Disconnect and API-data deletion process must be built and tested. Disconnecting or deleting connection data will not itself remove videos already on your YouTube channel; manage those in YouTube Studio.

• Google Privacy Policy
• Google account permissions