Cookie Policy
Outside the United States, RipClip sets no advertising or tracking cookies unless you accept them; in the US the advertising pixels are on until you opt out with "Do not sell or share my info". Always on: one cookie to keep you signed in, one random device ID that stops the free credits being claimed twice, and a few settings saved in your browser so the editor remembers how you like it. Optional: Marketing (the TikTok Pixel and the Meta Pixel, which we use to measure our own ads on TikTok, Facebook and Instagram and to show them to people likely to want RipClip) and analytics cookies. Google's sign-in script is also optional and only loads if you allow it or click "Continue with Google".
A creator's public profile (ripclip.org/username) asks the same cookie choice as our other pages and sets no Analytics or Marketing cookie unless the visitor allows it. Connecting an AI assistant or making a developer key (Account > Connect to AI) sets no new cookie: the approval screen uses your sign-in cookie, and the assistant holds its own passes, not a cookie from us.
Strictly necessary (always on)
These are needed for RipClip to work, so they don't need consent. You can still block them in your browser, but then you won't be able to sign in.
| Name | What it does | How long |
|---|---|---|
ripclip_session | Keeps you signed in, or keeps the project you are trying without an account. Signed so it can't be forged, and not readable by page scripts (HttpOnly). | 14 days, or until you sign out |
ripclip_session_ws | Only if you are in a Studio team: which workspace you picked (your own or the team's). It holds the team owner's account ID, nothing else, and is checked against your team on every request. Not readable by page scripts (HttpOnly). | 180 days, or until you sign out or switch back |
ripclip_device, and ripclipDevice (browser storage) | A random device ID, set when you try RipClip, sign up or sign in. It lets us give the free credits to one account per person; only a one-way code made from it is stored with us. Not readable by page scripts (HttpOnly); the browser-storage copy brings it back if cookies are cleared. | Up to 400 days |
ripclip_oauth | Protects the "Continue with Google" redirect against forgery. | A few minutes, during sign-in only |
ripclipConsent (browser storage) | Remembers your choice in the cookie banner. | Until you change it or clear your browser |
rcInv, rcTpl (browser session storage) | Only if you open an invite link or a preset share link before you have an account: carries the link's code to your sign-up, so the invite is counted and the preset is added. Used for nothing else. | Until you close the tab |
Preferences (browser storage, never sent to us)
These stay in your browser. They are never sent to our servers or shared, and nothing breaks if you clear them.
| Name | What it remembers |
|---|---|
opusLastProject | The project you had open, so "Continue editing" works |
ripclipPanel | Which editor panel you had open |
ripclipSnap, ripclipLocks | Timeline snapping and track locks |
ripclipRecentEmoji | Emoji you used recently |
ripPostPlatform | The platform you last planned a post for |
Marketing: TikTok Pixel and Meta Pixel
Outside the United States both pixels are off by default and load only after you choose "Allow all" or switch on Marketing in the cookie settings. In the United States they are on until you opt out: choose "Essential only" in the banner, or press Do not sell or share my info at the bottom of any page and switch Marketing off. A yes covers the pixels the banner named when you gave it: if we add another, the banner asks again. If your browser sends the Global Privacy Control signal, neither loads, whatever you chose.
TikTok Pixel
The TikTok Pixel is a script from TikTok (analytics.tiktok.com) that we use to measure our own TikTok ads. It loads on ripclip.org only while Marketing is on (above). It tells TikTok which pages were viewed, how they were used (clicks, time on the page, the page's title and description tags, load speed) and when someone signs up or buys a plan; if you consented, a hashed email address is sent to match the event to an ad. What it sets, under TikTok's privacy policy:
| Name | What it does | How long |
|---|---|---|
_ttp | Set by the Pixel on our site. A random visitor ID TikTok uses to match our ad measurement to the ad. | Up to 13 months |
_tt_enable_cookie | Set by the Pixel on our site. Records that the Pixel may use its cookie. | Up to 13 months |
| Cookies on TikTok's own domain | Set by TikTok when the Pixel contacts it, under TikTok's policy. | As TikTok states |
Meta Pixel
The Meta Pixel is a script from Meta (connect.facebook.net) that we use to measure our own Facebook and Instagram ads and to help Meta show them to people likely to want RipClip. It loads on ripclip.org only with Marketing switched on. It tells Meta when a page is viewed, when you open the sign-up form (Lead), pick a plan (ViewContent), press Get clips (GetClips), open the Help chat (Contact), open the payment page (InitiateCheckout), when you make an account (CompleteRegistration), when you start a free trial (StartTrial) and when you pay for a plan (Subscribe, with the plan's price). So that an ad blocker doesn't lose a sign-up, our server sends Meta the same events with the same event ID (Meta's Conversions API), and Meta counts each pair once; the server copy is sent only while your Marketing choice is on. With those events go your browser details, your IP address, the Meta cookies below and, for the account, trial and plan events, your email address (and RipClip account ID, once you have one) as one-way codes (SHA-256 hashes), so Meta can match the event to an ad. What it sets, under Meta's Privacy Policy:
| Name | What it does | How long |
|---|---|---|
_fbp | Set by the Pixel on our site. A random browser ID Meta uses to connect our events to its ad measurement. | 90 days |
_fbc | Set by the Pixel when you arrive from a Facebook or Instagram ad: the ad click's ID (fbclid). | 90 days |
rc_mk | Set by RipClip. Records that Marketing is on with the Meta Pixel offered, so our server may send Meta the same events. It holds "1" and nothing else. | Up to 400 days, or until you switch Marketing off |
| Cookies on Meta's own domains | Set by Meta when the Pixel contacts it, under Meta's policy. | As Meta states |
Switch Marketing off, or choose "Essential only", with the cookie settings link at the bottom of any page (in the US it reads "Do not sell or share my info"). The pixels then stop loading, our server stops sending Meta anything, and we delete the Meta identifiers we kept with your account; delete the cookies above in your browser if you want them gone now.
Marketing: the referral cookie
When you arrive from a RipClip affiliate's link (?ref=), and Marketing is on, RipClip sets one first-party cookie so the affiliate who sent you is credited if you sign up and pay. Without Marketing nothing is stored: the code stays in the page's memory and only counts for a sign-up in the same visit.
| Name | What it does | How long |
|---|---|---|
rc_ref | Set by RipClip. Holds only the affiliate's code from the first affiliate link you used. | 60 days, or until you switch Marketing off |
Analytics (only if you accept)
RipClip counts page views on its public pages in its own database, anonymously and without a cookie. With each page view we record where that visit came from (the referring site's name, the link's campaign tags and the page you landed on), also without a cookie and without anything that could recognise you on a later visit; choosing "Essential only" stops this too. Only if you give analytics consent can an analytics cookie be set, to tell visits apart; no outside analytics service is used. What we record about using the product is described in the Privacy Policy.
With analytics consent, these are set on ripclip.org (the site and the app share it, so a visit that ends in an account keeps where it came from). When we test two versions of the first screen of the signed-out page, two more remember which version you saw so you see the same one each time and we can count how each did:
| Name | What it does | How long |
|---|---|---|
rc_aid | A random visitor ID, to tell visits apart in our own database. | 400 days |
rc_ft | Where your first visit came from: the referring site, the page you landed on and the link's campaign tags (utm_source, utm_medium, utm_campaign, utm_term, utm_content). With Marketing on for the Meta Pixel, also the Meta ad click's ID (fbclid). | 90 days |
rc_lt | The same for this visit. | Until you close the browser |
rc_lv (browser storage) | Which version of the first screen you saw. Deleted when you withdraw analytics consent. | Until you withdraw consent or clear your browser |
rcLvSeen (browser session storage) | That this visit was already counted. | Until you close the tab |
Optional: Google sign-in
The "Continue with Google" button is provided by Google Identity Services, a script loaded from accounts.google.com. When it loads, Google receives your IP address and may set its own cookies, under Google's cookie policy. We load it only if you choose "Allow all" in the cookie banner, or at the moment you click "Continue with Google". Email sign-in works without it.
Sign-up check (Cloudflare Turnstile)
If we switch it on, the email sign-up form shows Cloudflare Turnstile, a check that you're a person, loaded from challenges.cloudflare.com only when the sign-up form opens. It is there for security, so it doesn't need consent. Cloudflare says Turnstile doesn't use cookies for advertising or tracking.
Connecting social accounts
When you connect Instagram, Facebook, Threads, TikTok, YouTube or X, you're sent to that platform's own website to approve access. Those sites set their own cookies under their own policies. RipClip doesn't place cookies for them.
Changing your choice
Use the cookie settings link at the bottom of any page. Choosing "Essential only" is always as easy as "Allow all", and it never limits what RipClip can do apart from preloading the Google button; it keeps the TikTok and Meta pixels and the analytics cookies off.