What we hold, and why.

1. Who is responsible

Jainil Ramji is the data controller for the personal data described here — meaning we decide what is collected and why. Questions, requests and complaints go to switchjainil@gmail.com, and we aim to answer within 30 days.

2. What we collect

Everything below is either given to us directly or produced by using the product. There is no third-party data broker in this list, and nothing is bought in.

Account

• Email address. Your identifier for signing in, and how we reach you about the account.
• Password. Stored only as a salted PBKDF2-HMAC-SHA256 hash. We cannot read it, and cannot tell you what it is.
• Account timestamps — when it was created, which plan it is on, and how many renders it has used in the current period.

Billing

• Stripe customer and subscription references. Short opaque identifiers that let us ask Stripe about your subscription.
• Plan and renewal date.

Your footage and the videos we make

• Files you upload, kept in storage scoped to your account.
• Render records — the title, format settings, retention score and the reasons behind it, duration, file size, and whether the run succeeded or was rejected.
• Clip records — for each segment used, its source, source URL, original title and author, licence, and where in the source it was taken from.
• Finished videos and thumbnails, until you delete them.

Connected YouTube account

• An OAuth refresh token for the channel you connect. This is what allows uploading on your behalf, and it is the most sensitive item we hold.
• Channel name and channel ID, so the app can show which channel it is about to publish to.
• The video ID and URL of anything we upload for you.

We ask Google only for the permission needed to upload to your channel. We do not read your comments, your subscriber list, or your analytics. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Render agent

If you run the render agent on your own machine, we store a token for it, the time it was last seen, and the machine name it reported during pairing, so the approval screen can tell you which computer is asking.

Technical logs

• IP address, held in memory to enforce rate limits and in server logs for a short period.
• Request and error logs, used to find faults.

3. Why we hold it, and on what legal basis

Where the basis is legitimate interests, you can object at any time and we will stop unless there is a reason we must continue. Where it is consent, you can withdraw it as easily as you gave it — see the Cookie Policy.

4. Who else sees it

We do not sell personal data. We do not share it with advertisers. It goes to the following processors, each because the product cannot work without them:

We may also disclose data where the law requires it, or to establish or defend a legal claim. If ClipForge is ever sold or merged, account data would transfer with it, and we would tell you before that happened.

Transfers outside the UK and EEA

Some of these providers process data in the United States. Those transfers rely on the European Commission's Standard Contractual Clauses, the UK Addendum where applicable, or the provider's certification under the EU–US Data Privacy Framework.

5. How long we keep it

Deleting your account removes the account record, your uploads, your renders and thumbnails, your clip history, your render-agent tokens and your YouTube token. Billing records that we are legally required to keep survive it; nothing else does.

6. Your rights

If you are in the UK or the EEA you have the rights below. We honour them for everyone, wherever you are, because operating two standards is how the wrong one gets applied.

• Access. Get a copy of what we hold. Activity → Your data → Download my data, or ask us.
• Portability. That copy is machine-readable JSON, so you can take it elsewhere.
• Rectification. Correct anything wrong. Most of it is editable in the app.
• Erasure. Delete the account and its contents. Activity → Your data → Delete account. It is immediate and cannot be undone.
• Restriction and objection. Ask us to stop a particular use, including anything based on legitimate interests.
• Withdraw consent. For anything you consented to, at any time, without affecting what was lawful beforehand.

None of these cost anything, and using one will never get your account treated differently. If you think we have handled your data badly, tell us first at switchjainil@gmail.com — and if we do not put it right, you can complain to your national data protection authority. In the UK that is the Information Commissioner's Office at ico.org.uk.

7. How it is protected

• Everything is served over HTTPS, with HSTS set on live traffic.
• Passwords are salted and hashed with PBKDF2-HMAC-SHA256. Plaintext is never stored.
• The session cookie is HttpOnly, SameSite=Lax and Secure in production, so scripts cannot read it and other sites cannot ride on it.
• Every request for a render, an upload or a job is checked against the account that owns it before anything is returned.
• Sign-in, sign-up and pairing are rate limited, so guessing is slow.
• A Content Security Policy restricts what the pages may load, and the API refuses cross-origin credentialed requests.

No system is beyond compromise. If a breach happens that is likely to put your rights at risk, we will notify the relevant supervisory authority within 72 hours of becoming aware of it, and tell you directly without undue delay.

8. Children

ClipForge is not for people under 16, and we do not knowingly collect their data. If you believe a child has created an account, write to switchjainil@gmail.com and we will remove it.

9. Cookies

One cookie is needed to keep you signed in. Anything beyond it is optional and asked for first. The Cookie Policy lists every one by name.

10. Changes

If this policy changes in a way that materially affects you, we will email the address on your account before the change takes effect. The date at the top always reflects the current version.