ClippedUp / Public documents

Data Deletion Instructions

How to request removal of information, what existing controls do, and which deletion procedures still need to be completed.

Public draft · Version 1 · Effective date: [Not set — pending approval]

1. Operator and request contact

ClippedUp is based in the United Kingdom. Send privacy/deletion enquiries to clippedup.app@gmail.com. You do not need an account to raise a concern about your personal information.

Pending review[LEGAL COMPANY OR INDIVIDUAL NAME, trading as ClippedUp]
Pending review[COMPLETE BUSINESS ADDRESS — including PO Box number if used, town/city, postcode and any additionally required geographic/registered address.]

2. Request deletion by email

There is no self-service account, project/video or conversation deletion button. Email clippedup.app@gmail.com with the subject “ClippedUp data deletion request”. Supply only what is needed to identify the request.

Trial users can provide a project or clip reference if known. Do not share result links publicly because they may expose content. Someone featured in a recording can raise a request without registering. If you do not know an identifier, describe the material so the operator can discuss locating it.

Do not send passwords, API keys, full card numbers or unnecessary identity documents. Any identity/authority checks should be proportionate and use a suitable agreed transfer method.

  • Account email, if you have one.
  • Whether the request covers the whole account or particular recordings, clips, chats, presets or records.
  • A relevant project/clip reference or filename, if known.
  • Whether you are the account holder or are concerned about yourself in another person’s recording.
Pending reviewMailbox monitoring, the responsible person, identity checks and a tested cross-system deletion procedure must be verified. Email does not automatically run deletion code. There is no automated acknowledgement or completion tracker.

3. What a request may cover

Scope may include profile/authentication records; upload sessions and source parts; projects, clips, thumbnails and older rendered versions; transcripts, captions and assessments; conversations, briefs/templates and usage records; and relevant support/technical records.

A business customer may control the uploaded personal data. The operator must establish the applicable role and coordinate the request where necessary, rather than disclose another customer’s media or ignore the requester.

Specific information may need retention for a valid legal duty, security need, dispute hold or other exception. The reason, category and period or criteria must be explained. Billing records are not automatically erasable on account closure; that does not justify keeping all media.

4. Timing and confirmation

Under UK GDPR, requests normally require a response within one month, subject to applicable identity/clarification rules and lawful extensions or exceptions. This is not a guarantee that every stored object or backup is erased in that time. A lawful extension, partial refusal or necessary retention needs an explanation and complaint route.

Completion needs verification, not just disappearance of a database or library entry. A response should distinguish removed information, any justified retained records, provider/backup limitations and remaining actions for the requester.

You can contact the UK Information Commissioner’s Office or another competent authority without ClippedUp’s permission.

Pending reviewNo verified acknowledgement process, provider deletion workflow or backup-erasure period is established by this draft. These must be approved and tested rather than promised in advance.

5. What existing controls do

Removing a source may affect projects that reuse it. A verified deletion procedure must follow those references without removing unrelated material. This page performs no deletion action.

  • Delete a reusable brief or custom template: removes that saved item, not past chats, videos, projects or exported results.
  • Clear the manual cut list: removes queued selections, not uploaded sources or finished clips.
  • Log out: removes the browser sign-in token, not the account, recordings or other stored references.
  • Clear browser site data: removes that browser’s identifiers/preferences/drafts, not cloud records or a subscription.
  • Wait for a manual preview link to expire: expires that grant, not the recording or other result links.
  • Cancel a subscription: changes billing according to Stripe’s configuration, not the existence of account/media data.

6. Billing is separate

If subscribed, use Dashboard → Plans → Manage subscription where available, or contact clippedup.app@gmail.com if it is unavailable. Availability and cancellation depend on the active billing configuration.

Say explicitly if you also want subscription cancellation when requesting account deletion. An email, browser reset or deletion of a user record does not automatically stop Stripe billing. Consumer cancellation and refund rights are unaffected.

Pending reviewThe operator must verify an alternative cancellation procedure before accepting real payments.

7. Copies outside ClippedUp

Downloaded files, copies saved by others from result links, and material you upload separately elsewhere are not automatically removed by a ClippedUp deletion request. Contact the holder or destination platform where appropriate. The operator must still meet applicable duties to notify recipients or assist removal; this is not a blanket exception.

8. Planned YouTube connection — not available

The current app does not connect to YouTube. A future connection could be revoked through Google account permissions or a Disconnect control once implemented. Email would also provide a route for requests about stored connection/API data.

Revocation and API-data deletion must meet YouTube’s applicable deadlines, including the relevant seven-calendar-day obligations. The general one-month legal response wording is not a substitute. No token purge or automated cleanup process currently exists.

Revoking a connection does not itself remove videos uploaded to a channel; those can be managed in YouTube Studio. Provider-derived connection/API data is distinct from an original source you independently upload to ClippedUp.

Pending reviewThe future connection, revocation/deletion and retention processes must be implemented and tested. TikTok/Instagram deletion or deauthorization callbacks are not implemented either; an email-instructions page does not replace a required callback endpoint.

Questions about these drafts or your information?

clippedup.app@gmail.com

Draft — under review. No effective date has been set. This document is not legal advice or a certification of compliance.