01The short version
If you use Clippingnet to cut a local video file, that file is read directly by your browser and never transmitted anywhere — we have no server in that path, so there is nothing for us to collect even if we wanted to. If you paste a direct video URL or a YouTube link, that link is used to load the video into your browser session; we don't log or retain the links you paste. We don't require an account, we don't sell data, and we don't run advertising trackers.
02Why this policy is unusually short
Most privacy policies are long because they're describing a lot of data flowing through a lot of systems. Clippingnet's core function — cutting a clip from a local file — has no server in the loop at all. The video is decoded, trimmed, and re-encoded entirely inside your browser tab using standard web APIs (the File API for reading, MediaRecorder for exporting). That's not a policy promise we're asking you to trust; it's how the tool is built, and you can verify it yourself by watching your browser's network activity while you use it.
Privacy by architecture, not by policy: we'd rather build a system where there's nothing to collect than build a system that collects everything and promise not to look at it.
03What we collect, by feature
Data handling differs depending on which of the three source types you use. Here's the complete breakdown:
| Feature | What touches a network | What we retain |
|---|---|---|
| Local file | Nothing — read and processed entirely in-browser | Nothing |
| Direct video URL | The URL you paste, fetched by your browser to load the video | Not logged or retained by us |
| YouTube link | The video ID, sent to YouTube's player to embed it | Not logged or retained by us (see YouTube's own policy below) |
| Page visit | Standard web request (IP address, browser type) to load the page itself | Basic, aggregated server access logs, kept briefly for abuse prevention |
We don't require sign-up, so we don't have your name, email, or account history tied to your use of the clipping tool itself. If you email us through the contact page, that email and its contents are retained as normal correspondence — see Data retention.
04What we architecturally cannot collect
- The contents of any local video file you load — it's never uploaded, so it's never in our possession.
- Your exported clips — the export happens on your device and downloads directly to your own disk.
- A history of what you've clipped — there's no account system to attach a history to.
- Playback or usage analytics tied to the video content itself (what you watched, for how long, what you cut).
05Cookies and local storage
We don't set tracking or advertising cookies. The site may use minimal, functional browser storage (for example, remembering a UI preference like whether you've dismissed a notice) — nothing that identifies you personally or persists your video content. You can clear this at any time through your browser's settings without affecting the tool's functionality.
06Third-party services
A few parts of the page load resources from outside domains, each limited to a specific purpose:
- YouTube (Google): when you clip from a YouTube link, the video is played through YouTube's own embedded player. That interaction is subject to Google's Privacy Policy, not this one, since we don't control what YouTube's player does on its end.
- Google Fonts: the page's typefaces are loaded from Google Fonts' CDN, which involves a request to Google's servers to fetch the font files.
- Sample video hosting: the practice/demo videos on some pages stream from a public Google Cloud Storage bucket maintained by the Blender Foundation's open movie project — this only loads if you click to try a sample.
We don't embed advertising networks, social media trackers, or third-party analytics scripts beyond what's described above.
07Data retention
Since the core tool doesn't collect video content or account data, there's little to retain in the first place. Basic web server access logs (used only for security and abuse prevention) are kept for a short, limited period and then discarded. Correspondence sent to our contact addresses is kept as long as needed to resolve the matter, and generally no longer than that.
08Your rights
Depending on where you live, you may have specific legal rights over personal data — under GDPR in the EU/UK, CCPA in California, or similar laws elsewhere. Because we retain so little personal data in the ordinary course of using the tool, most of these rights are already satisfied by design, but here's what applies where there is data:
Access
Ask what data we hold about you — for most users, the honest answer is "essentially none" beyond brief server logs.
Deletion
Request deletion of any correspondence or data we do hold, such as an email thread with our support address.
Correction
Ask us to correct any information tied to you that's inaccurate, wherever we hold it.
Objection / restriction
Object to or ask us to limit any processing of your data — again, most relevant to correspondence, not the tool itself.
To exercise any of these, email us at hello@clippingnet.com and we'll respond directly.
09Children's privacy
Clippingnet isn't directed at children under 13, and we don't knowingly collect personal data from children. Since the tool doesn't require an account or collect video content, there's little practical exposure either way, but if you believe a child has provided us personal information (for example, through the contact form), email us and we'll delete it.
10Changes to this policy
If this policy changes in a way that meaningfully affects how data is handled, we'll update the effective date at the top of this page. Because the tool's core architecture (no upload, no server in the clipping path) is a product decision, not just a policy statement, we don't expect this document to change often.
11Contact us
Questions about this policy, or about how a specific feature handles data, are welcome — we'd rather explain clearly than have you guess.