1. What this policy covers
This policy explains the cookies and similar browser storage used on our website, reclipit.io, and in the ReclipIt app at app.reclipit.io. It adds detail to section 12 of our Privacy Policy.
Cookies are small files a website stores in your browser. Local storage and session storage keep information in your browser in a similar way: session storage is cleared when you close the tab, and local storage stays until you clear it.
2. What we don’t use
We don’t use advertising, analytics or tracking cookies, and we don’t load analytics or advertising scripts on our website or in the app. Our own servers don’t set cookies.
The cookies described below are set by the providers that handle sign-in and payments for us, when you use those features.
3. Sign-in cookies
Clerk, our sign-in provider, sets cookies that are needed to sign you in, keep you signed in and protect your account against misuse. They’re set when you open the sign-in page or the app:
- __client, on clerk.reclipit.io: identifies your sign-in with Clerk. It can’t be read by scripts on the page. It can stay in your browser for up to 10 years; signing out ends the sign-in it refers to.
- __client_uat (and a variant of it with a short suffix), on reclipit.io and its subdomains: records when your sign-in last changed, so the app knows when to check it. It can stay in your browser for up to 10 years.
- __session (and a variant of it with a short suffix), on app.reclipit.io: a short-lived sign-in token that the app sends with its requests. Clerk renews it automatically while you’re signed in.
- __cf_bm and _cfuvid, on clerk.reclipit.io: set by Cloudflare, which Clerk uses to protect its sign-in service against bots and abuse. __cf_bm lasts about 30 minutes; _cfuvid is removed when you close your browser.
These cookies are necessary for signing in. If you block them, you can’t sign in. Clerk can change their names and lifetimes when it updates its service.
Signing in with Google. If you choose to sign in with Google, you go to Google’s sign-in page, where Google uses its own cookies under Google’s privacy policy.
4. Checkout cookies
When you open the checkout, the payment form of Whop, our payment provider, loads from whop.com. It may set its own cookies that are needed to process the payment and prevent fraud, under Whop’s privacy policy. We don’t read or control these cookies.
5. Information kept in your browser
The app keeps some information in your browser’s local storage or session storage. It stays in your browser and isn’t sent to us, except where we say so below.
Your choices and unsent work (local storage, until you clear it):
- whether the sidebar is collapsed, and how your History list is shown;
- the introduction tours you’ve already seen;
- the last video style you used;
- clip selections you haven’t sent yet, and an unsent feedback draft, so you don’t lose them.
Temporary sign-up, sign-in and checkout information:
- the YouTube link you pasted on our website before signing up, for up to 2 hours (local storage), so your project can start after you sign in. The link is sent to us when your project starts;
- the page to return to after signing in or after checkout (session storage), removed once it’s used, after 2 hours at most, or when you close the tab;
- a short note that a payment is being confirmed, for about 90 seconds (local storage);
- a short note that stops the app from sending you back to the sign-in page in a loop, for about 1 minute (session storage);
- a one-time reference for the withdrawal form, so that the same request isn’t sent twice (session storage, removed when you close the tab).
Diagnostic storage. Only if you open a diagnostic link we give you while helping you with a problem: a technical log of processing updates, kept in your browser until you clear it.
On our website. reclipit.io remembers which example video it showed first, so that a reload shows a different one (session storage, removed when you close the tab).
6. Images from YouTube
When the app shows a YouTube video’s thumbnail, for example after you paste a link or in Recently Reclipped, your browser loads the image directly from YouTube’s image servers. YouTube receives your IP address and browser details, under Google’s privacy policy. See our Privacy Policy, section 7.
7. Your choices
You can delete or block cookies and browser storage in your browser settings. If you block sign-in cookies, you can’t sign in. If you clear browser storage, the app forgets your choices and any unsent work described in section 5.
We use only cookies and browser storage that are needed for the features you use, or that remember choices you make. We believe these don’t require your consent under the rules that apply to us, so we don’t show a cookie banner. If that assessment changes, or if we start using cookies that do need consent, we’ll ask for your consent first (section 8).
8. Changes to this policy
We update this policy when the cookies or browser storage we use change, and we change the date at the top. If we ever want to use cookies that need your consent, such as analytics or advertising cookies, we’ll ask for your consent first.
9. Contact
Questions about cookies or your personal data: support@reclipit.io. Our Privacy Policy explains your rights.
ReclipIt is operated by LeksCo, a sole proprietorship (eenmanszaak) registered in the Netherlands with the Chamber of Commerce (KvK) under number 92728960, VAT ID NL004973705B94. Our full business details are in our Terms of Service, section 19.