Summary
This summary is here for speed. It is not a substitute for the sections below, which are the ones that bind us.
- We collect your account details, the video you import or upload, the clips and transcripts we make from it, and, if you connect a channel, the tokens and channel details needed to publish to it.
- We use that data to run the service you asked for. We do not sell it, rent it, or share it for advertising.
- Transcription and rendering happen on our own servers in the United Kingdom. Your video is not sent to a third-party AI provider.
- Source video is deleted once its clips are rendered. Deleting a project or your account deletes the rest.
- ClippingSpace uses YouTube API Services. Section YouTube API Services covers that in full, and you can revoke our access at any time at https://myaccount.google.com/permissions.
Who we are
ClippingSpace ("we", "us") operates the service at clippingspace.tech. We are the data controller for the personal data described here. For anything in this policy, including requests to access or delete your data, write to support@platechecks.com.
This policy covers the ClippingSpace website, the web application and the background workers that process video. It applies to everyone who uses ClippingSpace, whether on a free or a paid plan.
What we collect
Account information
Your name, email address and a hashed password when you create an account, plus your plan and the editing preferences you set (default aspect ratio, clip length, caption style and size, transcript language, and whether you want an email when a project finishes). Passwords are stored only as a bcrypt hash. We never see or store the password itself.
Video you import or upload
When you paste a link, we fetch that video so it can be processed. When you upload a file, we store that file. From it we derive and store:
- A transcript with word-level timings, produced on our own servers.
- Clip metadata: start and end times, a generated title, a summary, a hook line, keywords and an engagement score.
- The rendered clip files, their thumbnails and preview frames.
- Technical details about the source: title, author, duration, platform and original filename.
Your video and its transcript may contain personal data about you and about anyone else appearing in it. We process that material only to produce the clips you asked for. It is never used to train models, never reviewed by us except where you ask for support and give us permission, and never shown to other users unless you create a share link yourself.
Connected account data
If you connect a publishing destination such as a YouTube channel, we store the access and refresh tokens issued by that platform, the account's id, display name, handle and avatar URL, the scopes you granted, and a record of what we published and when. Tokens are encrypted at rest with AES-256-GCM.
Usage and technical data
Server logs (IP address, user agent, requested path, timestamp, response code) kept for 30 days for security and debugging. Aggregate usage counters (source minutes and clips per month) so plan limits can be enforced. Page analytics through Vercel Analytics, which is aggregated and does not set advertising or tracking cookies. See our cookie notice.
YouTube API Services
ClippingSpace uses YouTube API Services. By connecting a YouTube channel you also agree to the YouTube Terms of Service (https://www.youtube.com/t/terms), and Google's handling of your data is governed by the Google Privacy Policy (https://policies.google.com/privacy).
Connecting a channel is optional and is never part of signing up. When you do connect one, we ask Google for these scopes and no others:
| Scope | What it is for | What we store |
|---|---|---|
| Upload videos to your channelhttps://www.googleapis.com/auth/youtube.upload | Publishing a finished clip to the channel you connected, either straight away or at a time you picked in the scheduler. Without it ClippingSpace can only hand you a file to upload by hand. | The YouTube video id and watch URL of each video we uploaded for you, its upload time, and whether the upload succeeded or failed. Never the video file itself once the upload finishes. |
| View your YouTube accounthttps://www.googleapis.com/auth/youtube.readonly | Showing which channel is connected, so you can tell two channels apart before you schedule a clip to one of them, and reading the view, like and comment counts on the clips ClippingSpace published so you can see which ones worked. | Channel id, channel title, handle and avatar URL, plus the view, like and comment count for each video ClippingSpace uploaded for you. Nothing about videos we did not upload, and no data about anyone who watches your channel. |
How we access it. Only through the official YouTube Data API, using the token you granted, and only while that grant is live. We never ask for your Google password and there is no field in ClippingSpace that would accept one.
How we use it. To upload the clips you chose to the channel you chose, to display which channel is connected, and to show you how those uploads performed. Nothing else.
How we store it. Tokens are encrypted at rest. Everything else is an ordinary record in our database in the United Kingdom, visible only to your signed-in account. We store no YouTube audiovisual content.
How we share it. We do not. Your YouTube data is never sold, never passed to an advertising network or data broker, never aggregated with anyone else's, and never used to train a model. Our infrastructure providers, listed under who we share it with, host it on our behalf and cannot use it for their own purposes.
How long we keep it. As the YouTube API Services Terms require, cached YouTube data is refreshed from the API at least every 30 days, and anything not refreshed inside that window is deleted. Tokens and cached channel data are deleted the moment you disconnect the channel or revoke the grant at Google.
How to revoke it. Disconnect the channel in Settings, or remove ClippingSpace at https://myaccount.google.com/permissions. Either way our access ends and the stored YouTube data goes with it. Videos already on your channel are unaffected and stay yours.
A fuller, scope-by-scope account, including the endpoints we call, is on How we use YouTube API Services.
How we use it
- To run the service: download or receive your video, transcribe it, select and render clips, store the results and show them to you.
- To publish on your behalf: upload clips to the accounts you connected, at the times you set.
- To manage your account: sign you in, apply plan limits, count usage, and handle billing status.
- To communicate: service email such as a finished project or a failed upload. Product news only if you switched it on, and you can switch it off at any time.
- To keep the service safe and working: logging, abuse prevention, debugging and capacity planning.
- To meet legal obligations where one applies to us.
We do not make decisions about you by automated means that produce a legal or similarly significant effect. Clip scoring ranks moments in your own video; it does not judge you.
Legal bases
Where UK or EU data protection law applies, we rely on these bases:
- Performance of a contract for running your account, processing your video and publishing to accounts you connected.
- Legitimate interests for security logging, abuse prevention and aggregate analytics, balanced against your rights and kept to what is necessary.
- Consent for optional product email and for connecting a third-party account, which you can withdraw at any time without affecting the rest of the service.
- Legal obligation where we must retain or disclose something by law.
Who we share it with
We share personal data only with the providers below, only so they can run parts of the service for us, and only under contracts that stop them using it for their own purposes. We do not sell personal data, and we have never sold personal data.
| Provider | What they do | Where |
|---|---|---|
| Vercel Inc. | Website and application hosting, plus privacy-friendly page analytics. | United States and European Union |
| Neon Inc. | Managed PostgreSQL database holding accounts, projects, clip metadata and connected-account records. | European Union |
| ClippingSpace processing servers | Video download, transcription, clip rendering and object storage. Operated by us on dedicated hardware, not a shared cloud tenancy. | United Kingdom |
Beyond those, we disclose personal data only:
- to a platform you connected, when publishing a clip you told us to publish;
- to anyone holding a share link you created, limited to the single clip that link points at;
- where the law requires it, or to establish or defend a legal claim;
- to a buyer, if the service is ever sold, in which case this policy continues to apply until you are told otherwise.
How long we keep it
| Data | Kept | Deleted |
|---|---|---|
| Account record (email, name, password hash, plan, preferences) | For as long as the account exists | Within 30 days of you deleting the account |
| Source video you imported or uploaded | Until its clips finish rendering, then up to 30 days | Automatically after rendering, or immediately when you delete the project |
| Rendered clips, thumbnails and transcripts | Until you delete the clip or the project | Immediately on deletion, and within 30 days of account deletion |
| YouTube OAuth access and refresh tokens | Until you disconnect the channel or revoke access at Google | Immediately on disconnect, and immediately when Google reports the grant as revoked |
| Cached YouTube channel details and the counts on videos we uploaded | Refreshed from the YouTube API at least every 30 days, in practice hourly | Automatically if not refreshed within 30 days, as the YouTube API Services Terms require, and immediately on disconnect |
| Publishing history (which clip went to which channel, and when) | For as long as the account exists | Within 30 days of account deletion |
| Server and security logs | 30 days | Rolling deletion after 30 days |
Backups are held on a rolling window and overwritten in the ordinary course, so deleted data may persist in a backup for a short period after it is removed from the live system, and is not restored to the live system.
Security
- Everything is served over HTTPS. Traffic between the app, the database and the workers is encrypted in transit.
- Passwords are stored as bcrypt hashes. OAuth access and refresh tokens are encrypted at rest with AES-256-GCM under a key held outside the database, and are never sent to your browser or written to logs.
- Sessions use signed, HTTP-only cookies. Every request for a project, clip or connected account is checked against the signed-in user, so one account cannot read another's work.
- Media files are served through signed, expiring URLs rather than being publicly listable.
- Access to production systems is limited to the people who operate them.
No system is perfectly secure. If a breach affects your personal data and is likely to present a risk to you, we will notify you and the relevant supervisory authority as the law requires.
Your rights
Depending on where you live, you may have the right to access a copy of your data, correct it, delete it, restrict or object to how we use it, take it elsewhere in a portable form, and withdraw consent you gave. You can exercise most of these directly in the app:
- Correct it: Settings, where your name, email and preferences are editable.
- Delete part of it: delete a clip or a whole project from your dashboard, which removes its files and transcript.
- Withdraw a connection: Settings, then Connected accounts, then Disconnect.
- Delete all of it: see Delete your data.
For anything not covered by a button, email support@platechecks.com. We respond within 30 days, and we will not charge you or make you justify the request. If you are in the UK you may also complain to the Information Commissioner's Office at ico.org.uk; in the EU, to your national supervisory authority.
International transfers
Our processing servers and stored media are in the United Kingdom, and our database is in the European Union. Our hosting provider operates a global network, so some requests may be served from, or logged in, other countries including the United States. Where personal data leaves the UK or EEA, it is transferred under the UK International Data Transfer Addendum or the EU Standard Contractual Clauses, or to a country with an adequacy decision.
Children
ClippingSpace is not for children. You must be at least 16 to hold an account, or older where your country sets a higher age for consent to online services. We do not knowingly collect data from children, and if we learn that we have, we delete it. If you believe a child has an account, tell us at support@platechecks.com.
Changes
We update this policy when the service changes. The date at the top of the page always reflects the current version. If a change materially affects how we handle your personal data, we will tell you by email or in the app before it takes effect, and where the law requires consent we will ask for it rather than assume it.
Contact
Email support@platechecks.com for any privacy question, data request or complaint. It reaches a person, not a queue, and we aim to reply within two working days. Other routes are on the support page.