Policy · Cookies
Cookie policy.
Last updated · September 26, 2026
1. What are cookies?
Cookies are small text files stored on your device when you visit a website. They let a site remember you across pages and between sessions. Clipflow uses them to run the service, to remember a few choices you make, and — only if you accept — to credit the partner who referred you. Every cookie we set is named below.
2. Cookies we use
2.1 Strictly necessary
- Authentication session — Supabase sets a secure, HTTP-only cookie after you sign in so the app knows you're logged in. Without this you cannot access the workspace.
- Current workspace — a small cookie (
clipflow.current_workspace) remembers which workspace you last used, so navigating to the dashboard lands on the right one. - Session check —
cf_session_verified_atrecords when your sign-in was last verified, so the app does not re-check it on every page. - Sign-in link —
cf_link_requestedis set for one hour when you ask for a sign-in or password-reset email, so the link opens where you meant to go in this browser; removed once the link is used. - Channel connection —
composio_pendingis set for up to 30 minutes while you connect a social account and removed when you come back from the provider. - CSRF protection — Next.js sets a token cookie to prevent cross-site request forgery on server actions.
These are exempt from consent under GDPR Art. 5(3) and the ePrivacy Directive because the service cannot function without them.
2.2 Functional
- Language —
clipflow_localeremembers the language of the site, from your browser setting or the language switcher. - UI preferences — theme, sidebar state, keyboard-shortcut dismiss flags — stored in your browser's localStorage, never sent to our servers. Clearing site data removes them.
2.3 Analytics
We measure visits and feature use with Umami, hosted in the EU. Umami sets no cookies and stores nothing in your browser; it counts page views, referrers, device type and country without cross-site tracking and without storing IP addresses. When you are signed in, product events carry your Clipflow account ID — never your name or email. We do not use Google Analytics, Facebook Pixel or Hotjar. Page-speed measurements (Vercel Speed Insights) are cookieless as well.
2.4 Referral links
- Partner program (only if you accept) — if you arrive through a Clipflow partner's link and click “Accept” in the cookie banner, our partner platform FirstPromoter sets
_fprom_refand_fprom_tidso the partner is credited if you subscribe later. They last for the partner program's referral window. Without a partner link nothing is set, and if you click “Decline” the FirstPromoter script never loads. - Customer referral links — opening a referral link from an existing Clipflow customer (for example the “made with clipflow.to” mark on a video) sets
clipflow.ref_codeand, if the link names a channel,clipflow.ref_sourcefor 30 days, so that customer is credited if you sign up.
2.5 Advertising
We do not run ads and set no advertising cookies.
3. Third-party services
Some features load third-party scripts that may set their own cookies when you actively use them:
- Stripe Checkout — when you click “Subscribe”, Stripe's checkout page (not ours) sets cookies required for fraud prevention. Covered by Stripe's privacy policy.
- Error tracking (Sentry) — when enabled in production, Sentry may set a session cookie to correlate errors across pages. No PII is captured.
4. Your choices
- “Decline” in the cookie banner keeps the partner-program cookies off. To change your answer later, clear this site's data in your browser and the banner asks again.
- You can block all cookies in your browser settings — but then the service cannot keep you logged in and will not work.
- Clearing your browser's local storage removes all functional preferences (you'll see the first-run tips again).
- You can delete your account from Settings → Profile — this removes all server-side data along with the cookies it sets.
5. Changes to this policy
We'll update this page when our cookie usage changes and list the change in our changelog. Material changes (new trackers, new third parties) will prompt an in-app notice on your next login.
6. Contact
Questions about cookies? Email privacy@clipflow.to.
This policy is provided as plain-language summary, not legal advice. See our Privacy Policy and Terms of Service for the full legal basis.