// legal

Privacy policy

Last updated: 2026-05-11

One page. No tracking pixels. No re-marketing graphs. Below is what we collect, why, and how to delete it.

01 · What we collect.txt
When you submit a brand brief or a clipper application, we collect the information you fill in (name, email, company, social handles, payment preference, optional sample clip URLs). When you visit the site we receive standard server logs (IP, user-agent, request paths) which are retained for 30 days. We do not run ad-network pixels or third-party behavioural trackers.
02 · Why we collect it.txt
Brand briefs go to our sales inbox so we can reply with a proposal. Clipper applications go to our ops inbox + a private vetting board. Server logs are used to keep the site online and to identify abuse.
03 · Who else sees it.txt
Form submissions are routed to Resend (transactional email) and, when configured, to our private Notion / Google Sheets workspaces. We do not sell or share form submissions with any third party.
04 · Cookies.txt
We do not set any first-party cookies for our own purposes. We do not use marketing cookies, retargeting pixels, or third-party analytics cookies. When the optional Cloudflare Turnstile anti-spam challenge is shown on a form, Turnstile may set a short-lived cookie to verify your browser; that's the only third party that can set a cookie on this domain. We do save a localStorage draft of your in-progress clipper application so you can come back to it later — clear it by submitting the form or by clearing your browser storage.
05 · Your rights.txt
Email legal@clipclip.am to request a copy or deletion of any data tied to your form submissions. We respond within 30 days. Residents of the EU / UK / California have the rights afforded by their local laws (GDPR / CCPA); contacting us is the way to exercise them.
06 · Retention.txt
Form submissions are retained for as long as the related engagement is active, plus 2 years for tax/audit reasons. Server logs are retained for 30 days.
07 · Security.txt
Form submissions transit over TLS. Our vendor stack (Resend, Notion, Google) maintain SOC 2 / ISO 27001 controls. Our own access is single-sign-on with mandatory 2FA. We do not store payment instruments on this site; payouts run on Stripe Connect / standard bank rails.
08 · Changes.txt
If we change this policy in a way that materially affects what we do with your data, we'll update the 'last updated' date and (for active accounts) email you.