Summary
What we set
| Name | Purpose | Lifetime |
|---|---|---|
| Session cookie | Keeps you signed in and ties each request to your account. Signed and HTTP-only, so scripts in the page cannot read it. Without it, signing in is impossible. | 30 days, or until you sign out |
| Theme preference | Remembers whether you chose light, dark or system appearance. Stored in your browser's local storage rather than sent to us. | Until you clear site data |
| OAuth state | A short-lived value set while you are connecting a channel, so the reply coming back from the platform can be proved to belong to your request. This is a security control against cross-site request forgery. | Minutes, deleted once the connection completes |
| Sign-up destination | Remembers where you were heading (a link you pasted, a plan you picked) while you confirm your email, so the verification link can take you back there. HTTP-only, like the session cookie. | 24 hours, deleted once you verify |
| Editor settings and recovery | The clip editor remembers panel sizes and view toggles in local storage, and keeps a copy of unsaved edits and the editing assistant's conversation in session storage so a reload or crash does not lose your work. All of it stays in your browser. | Settings until you clear site data; copies until you close the tab or sign out |
These are all first-party and strictly necessary, which is why they do not require consent under UK and EU rules. Blocking them stops the service working.
Analytics
We use Vercel Analytics to count page views and see which pages people actually reach. It is aggregated and privacy-friendly by design: it sets no cookie, assigns no persistent identifier, and cannot follow you to another website. We see totals, not individuals.
We do not use Google Analytics, advertising pixels, session recorders or heatmap tools.
Third-party content
When you connect a channel, you are sent to that platform's own consent screen, which is their page and may set their own cookies under their own policy. That happens on their domain, not ours. What each platform then does with your data is covered by their privacy policy, and for Google that is linked from our privacy policy.
Clip video files are served from our own storage, so playing a clip on ClippingSpace does not load an embedded player from anywhere else and does not hand a third party a request from your browser.
Controlling cookies
Every browser lets you see, block and delete cookies, usually under Privacy settings. Blocking the session cookie will sign you out and stop you signing back in, so use a private window rather than a block rule if you want a clean slate.
Clearing site data for clippingspace.tech removes everything in the table above. Nothing we set survives that.
Questions go to support@clippingspace.tech, and the wider picture is in the privacy policy.