Privacy Policy
What we collect, why, and how to get rid of it. We have kept this short because we collect very little.
Last updated
Who is responsible
The operator decides how your data is handled here. Contact: our address.
What we collect
- Your email address and a password hash
- Only if you create an account. Passwords are hashed with scrypt. We cannot read yours, and neither can anyone who steals the database.
- A session cookie and a device cookie
cs_sessionkeeps you signed in.cs_devicecounts the free daily allowance for people who have not signed in. Both are strictly necessary for the service to work, so we do not ask for consent to set them. No advertising or analytics cookies are set.- Links you submit and the clips you make
- The source URL, your in and out points, crop, caption text and chosen plan limits. Kept while the clip exists.
- Clip files
- Stored temporarily so you can download them, then deleted automatically as space is needed.
- Technical logs
- IP address, time and request path, kept briefly to spot abuse and to debug failures.
- Accounts you connect
- If you connect YouTube, TikTok or Instagram so we can post for you, we keep the access token that platform gives us, encrypted, and the titles, captions and times of the posts you schedule. We use it only to upload the clips you tell us to. Disconnecting deletes the token; you can also revoke our access from the platform's own settings.
- Team membership
- If you join a team, the other members can see the clips you make and the posts you schedule, and you can see theirs.
- Reports you file
- Your reason and message. If you file a copyright claim we keep your name and email, because the law requires a claim to identify who made it. A copyright claim may be shared with the person whose clip you reported, which is how counter-notice works. Reporter IP addresses are stored only as a one-way hash, used to stop one person filing the same report repeatedly.
We do not collect payment card details. Checkout happens on our payment provider's systems. We receive only a subscription status and an identifier.
Why we are allowed to hold it
- To provide the service you asked for: account, clips, plan limits. (Contract.)
- To keep the service working and safe: rate limits, abuse prevention, logs. (Legitimate interests.)
- To handle reports and takedowns. (Legal obligation and legitimate interests.)
- To take payment. (Contract.)
Who else sees it
- Our hosting provider, which runs the server the service sits on.
- Our payment provider, if you buy a plan.
- The platform you clipped from sees a request from our server for the video, as any viewer would.
- The platforms you post to. A clip you post or schedule is uploaded to the account you connected, with the title and caption you wrote.
- Translation, speech and stock-footage services, if you use those features. The words spoken in your clip, or the caption you typed, may be sent to a translation or text-to-speech provider, and a search word to a stock-footage library.
- Anyone you send a clip to. Clip links are unguessable but not secret. Treat a clip URL as public once shared.
We do not sell your data, and we do not share it for advertising.
How long we keep it
- Clip files: until storage is needed, typically days.
- Account details: until you delete the account.
- Sessions: 30 days, or until you sign out.
- Technical logs: a short rolling window.
- Reports and takedown records: kept as a record of what was actioned and why.
Your rights
You can ask for a copy of what we hold, correct it, or have it deleted. Write to us and we will act within 30 days. Deleting your account removes your email, password hash, clip records and sessions. Takedown records may be retained where we need them to show why a clip was removed.
Depending on where you live you may also have the right to object to processing, to restrict it, or to complain to a data protection regulator.
Children
The service is not intended for children under 13 and we do not knowingly collect their data. If you believe a child has an account here, tell us and we will remove it.
Where your data sits
Our server is hosted in the region chosen at setup. If you are in the EU or UK and your data moves outside it, that transfer relies on standard contractual clauses or an adequacy decision.
Security
Passwords are hashed with scrypt. Sessions are opaque random tokens in httpOnly cookies, revocable server-side. Traffic is encrypted in transit. No system is perfectly secure, and we will tell affected users promptly if something goes wrong.
Changes
If this policy changes materially we will say so on the site before the change takes effect.