Cookie Policy
Last updated Effective
This policy lists every cookie and every item of browser storage that a visit to rip.fan can leave on your device today, who sets each one, what it holds, how long it lasts, how to remove it and how to change your cookie choice. Our Privacy Policy covers everything else we do with information.
1. The short version
- Two cookies of our own, only for accounts. If you sign in, Rip.fan sets one cookie that keeps you signed in and one that keeps sign-in requests safe (section 4). Signed out, our own code sets none.
- Google Analytics, under your choice. We use Google Tag Manager and Google Analytics to learn which pages and tools readers find useful. In the EEA, the UK and Switzerland a cookie banner asks first, and they set no cookies until you press Accept. Everywhere else there is no banner, and analytics cookies are on unless you turn them off.
- Ad measurement. Google's ad measurement cookie, which shows us which of our ads bring readers here, is set in the EEA, the UK and Switzerland only after you press Accept. Elsewhere it is set unless you turn it off, and never while your browser sends Global Privacy Control.
- Change your mind at any time, anywhere. The Cookie settings button at the foot of every page opens the banner, so you can accept or reject wherever you are.
- Our tools keep your lists in your browser. The collection tracker, the set checklist, the trade checker and the rip simulator's sample binder keep what you enter in your browser's local storage, and so do your light or dark choice and your cookie choice. It stays on your device and is never sent to us. Signed in, the collection tracker keeps your collection with your account instead.
- Cloudflare may set a security cookie. Cloudflare carries all of the site's traffic, and its security features can set a cookie of their own. When we checked on October 15, 2026, no page we opened on rip.fan set one.
- Partner sites have their own cookies. Once you leave Rip.fan through a partner link, the partner's site may set cookies under its own policy.
2. What cookies and browser storage are
A cookie is a small text file that a website asks your browser to keep. Your browser sends it back to that website with each later request, which lets the site recognize your browser from one page to the next. A cookie set by the site you are on is a first-party cookie, even when a script from another company sets it. One set by another company whose content the page loads, on that company’s own address, is a third-party cookie.
Local storage is a space in your browser where a site’s own pages can keep information on your device. Unlike a cookie, it is never sent to the site with your requests: only the site’s pages, running in your browser, can read it. It has no expiry date. It stays until the site’s pages remove it or you clear the site’s data in your browser.
Browsers also offer session storage, which is cleared when you close the tab, and other kinds of storage for larger amounts of data or for working offline. Rip.fan uses none of them.
The rules in the EEA and the UK allow storage that is strictly necessary for a service you ask for, such as keeping a list you build in a tool, without asking for your consent. Analytics and advertising cookies need your consent first.
3. What Rip.fan keeps in your browser
Rip.fan writes to your browser’s local storage only when you use a feature that needs it, including the buttons on the cookie banner. Opening a page writes nothing. Each item stays in your browser alone, and is never sent to us or to anyone else.
| Name | Set by | What it holds and why | When it is written | How long it lasts | Needed? |
|---|---|---|---|---|---|
ripfan-theme | Rip.fan, in local storage | Your choice of light or dark mode, so the next page you open looks the same. | Only when you switch to light or dark mode with the button in the footer. | No expiry date. It stays until you clear this site's data in your browser. | No. Without it the site follows your device's own light or dark setting. |
ripfan-consent | Rip.fan, in local storage | Your answer on the cookie banner, Accept or Reject, and when you gave it, so the banner does not ask again on the next page. | Only when you press Accept or Reject on the cookie banner. | Until you clear this site's data in your browser. After 13 months the banner asks again, and your new answer replaces the old one. | Yes, to keep your choice. Without it the banner would ask on every page. |
ripfan-collection | Rip.fan, in local storage | The cards you list in the collection tracker: each card's set, number and name, and how many you have. No prices: the tracker prices the list again from the newest weekly price check each time it opens. | When you add, change or remove a card, read in a CSV file or clear the list. | No expiry date. It stays until you clear it on the tool or clear this site's data in your browser. | Only to keep your list between visits. Without it the tracker still works, for one visit. |
ripfan-account | Rip.fan, in local storage | The number 1, which says this browser has signed in to a Rip.fan account, so our pages ask our account service who you are only on a browser that has signed in. It holds no name, email address or session. | When you sign in. | Until you sign out, or our account service says your session has ended. Clearing this site's data removes it too. | Only to show the header icon and the card buttons signed in without asking our service on every page. Without it the site asks when you open Your cards. |
ripfan-checklist | Rip.fan, in local storage | The cards you tick in the set checklist, set by set, and the set you last opened, so the checklist opens where you left it. | When you open a set, or tick or untick a card. | No expiry date. Unticking a card removes its tick, but the set you last opened stays until you clear this site's data in your browser. | Only to keep your ticks between visits. Without it the checklist still works, for one visit. |
ripfan-trade | Rip.fan, in local storage | The cards on each side of a trade in the trade checker, and how many of each. No prices. | When you add, change or remove a card on either side, or clear both lists. | No expiry date. It stays until you clear it on the tool or clear this site's data in your browser. | Only to keep both lists between visits. Without it the trade checker still works, for one visit. |
ripfan-sample-binder | Rip.fan, in local storage | The sample slabs you keep from the rip simulator, 90 at most. For each one: the sample pack and its edition, the card's name, set, number and sample grade, and the addresses of its picture and of its page on Rip.fan. No dates, no prices and no count of packs opened. | Only when you press Add to my sample binder, take a slab out, or empty the binder. | No expiry date. It stays until you clear it on the tool or clear this site's data in your browser. | Only to keep the slabs you chose between visits. |
Some browsers, such as Safari, may delete what a site keeps in local storage if you have not visited the site for a while, so save a CSV copy of any list you want to keep. The collection tracker, the set checklist and the trade checker each offer one.
You can clear most items on their own tool: the collection tracker and the trade checker each have a Clear button, and the sample binder has an Empty the binder button. The set checklist lets you untick cards, and it still remembers the set you last opened. Clearing this site’s data in your browser removes all of them at once, along with your light or dark choice and your cookie choice, so the banner asks again.
4. Cookies Rip.fan sets
Our own code sets two cookies, and only when you use an account. Both are sent only to rip.fan and only over HTTPS, and the pages themselves cannot read them. A reader who never opens the sign-in form gets neither.
| Name | Set by | What it holds and why | When it is set | How long it lasts | Needed? |
|---|---|---|---|---|---|
__Host-ripfan_session | Rip.fan, as a cookie | A random number that tells our account service which signed-in session your browser holds. It holds no name or email address. Our service keeps only a scrambled form of it, so it can end the session at any time, and the page itself cannot read the cookie. | When you sign in, by an emailed link or with Google. | 60 days after you last used it, and never more than a year. Signing out deletes it at once, and Sign out everywhere ends it on every browser. | Yes, to keep you signed in. Without it you are signed out. |
__Host-ripfan_browser | Rip.fan, as a cookie | A random number that lets our account service check that a sign-in request, a sign-in link or a Google sign-in comes from your own browser, so another site cannot sign you in or out in your name. It holds nothing about you. | When you open the sign-in form or start Google sign-in. | One day, or until you sign in, when it is deleted. | Yes, to sign in safely. Without it a sign-in link asks you to confirm your address first. |
Apart from these, Rip.fan's own code sets no cookies, and it uses no session storage, offline storage or other way of recognizing your browser. The analytics cookies in section 5 are set on rip.fan by Google's script, and only under the choice you make. When you press Reject, our code deletes them.
These cookies are strictly necessary for the account you ask for, so they need no cookie choice. Signing out deletes the first, and signing in deletes the second.
Our fonts and site images are served from rip.fan itself, so no font service or image service learns that you visited, apart from the card pictures in section 7.
If we add another cookie of our own, we will list it here before it is used.5. Google Analytics and Google Tag Manager
We use Google Tag Manager to load Google Analytics, which counts the pages and tools readers use, so we can see what is useful and what is not. Google Tag Manager itself sets no cookies. Every page tells Google's tags the choice you made before they send anything, using Google's Consent Mode:
- In the EEA, the UK and Switzerland, a banner asks first, and analytics and ad measurement are off until you press Accept. Until then Google's tags set no cookies and read none. They may send Google a note that a page was opened, with no cookie and nothing that recognizes your browser, which Google uses to estimate how many visits it could not count.
- Everywhere else, no banner appears, and analytics and ad measurement are on unless you press Cookie settings and then Reject.
- Reject turns both off wherever you are, and deletes the Google cookies already set on rip.fan.
- Global Privacy Control. If your browser sends it, ad measurement stays off wherever you are, even after you press Accept.
Google works out which of these applies from your approximate location. These are the cookies Google's tags may set on rip.fan:
| Name | Set by | What it holds and why | When it is set | How long it lasts | Needed? |
|---|---|---|---|---|---|
_ga | Google Analytics, on rip.fan | A random number that tells Google Analytics your browser is the same one on a later page or visit, so it can count readers rather than page loads. It holds no name or email address. | Only while analytics are allowed for you: after you press Accept in the EEA, the UK and Switzerland, and until you press Reject everywhere else. | Two years from your last visit, Google says. Pressing Reject deletes it. | No. The site works the same without it. |
_ga_ and a code | Google Analytics, on rip.fan | Keeps track of your current visit for Google Analytics: when it started and how many pages it has had. | Only while analytics are allowed for you, as for _ga. | Two years from your last visit, Google says. Pressing Reject deletes it. | No. |
_gcl_au | Google Ads, on rip.fan | Lets Google Ads tell that a reader who came from one of our ads went on to read the site, so we can see which ads bring readers here. | In the EEA, the UK and Switzerland, only after you press Accept. Elsewhere unless you press Reject. Never while your browser sends Global Privacy Control. | Three months, Google says. Pressing Reject deletes it. | No. |
If your browser runs no JavaScript, a page asks Google Tag Manager for an empty page instead, which sets no cookies and sends no analytics. What Google receives, and how long it is kept, is set out in our Privacy Policy. Google handles it under its own privacy policy.
6. Cookies Cloudflare may set
Cloudflare, Inc. sits in front of our server and carries every request to rip.fan. Its security features can set the cookies below on rip.fan. Cloudflare says that these cookies are strictly necessary for the service it provides, and that cookie data may be processed in its data centers in the United States.
| Name | Set by | What it holds and why | When it is set | How long it lasts | Needed? |
|---|---|---|---|---|---|
__cf_bm | Cloudflare | Part of Cloudflare's bot protection (Bot Management or Bot Fight Mode), which spots automated traffic. Cloudflare says the cookie holds information it uses to work out a bot score, encrypted so that only Cloudflare can read it, and that a separate cookie is made for each site, so it does not follow you from site to site. | Only while Cloudflare's bot protection is switched on for rip.fan. When we checked on October 15, 2026, no page we opened set it. | Cloudflare says it expires after 30 minutes of inactivity. | Cloudflare describes it as strictly necessary for its bot protection to work. |
cf_clearance | Cloudflare | Proof that your browser passed a Cloudflare security check, so you are not asked to pass it again on the next page. | Only if Cloudflare asks your browser to pass a security check before it lets a request through. | 30 minutes by default, Cloudflare says. Each site can change this in its Cloudflare settings. | Cloudflare describes it as strictly necessary: after a check, it is what lets your browser reach the site. |
Cloudflare documents other cookies for features such as load balancing and waiting rooms. Rip.fan runs on a single server, and none of those features is part of how the site is delivered.
Cloudflare Web Analytics, which counts visits and measures how quickly pages load for us, runs a small script on our pages. Cloudflare says it uses no cookies or other storage in your browser and does not fingerprint your browser, so it needs no cookie choice.
Cloudflare also asks browsers that support network error reports to tell it when a page on rip.fan fails to load. That is a setting your browser keeps for the site, not a cookie, and a page that loads normally is not reported.
Cloudflare’s handling of this information is described in its own privacy policy.
7. Card pictures from Scrydex
Card pictures load straight from Scrydex’s image server, so your browser asks Scrydex for each picture and Scrydex receives your IP address and your browser’s user agent. Our pages send only the site’s address, rip.fan, as the referrer. When we checked on October 15, 2026, Scrydex’s image server set no cookies. If that changes, we will list its cookies here.
8. After you leave through a partner link
Partner links go first to a short redirect page on our site, which sets no cookies of its own and stores nothing. When you go on, you arrive on the partner’s site, which is run by someone else.
The partner’s site may set its own cookies, for example to remember that you came through our referral link so it can credit us, to keep you signed in, or for its own analytics and advertising. Some partner links pass through the partner’s own link service first, which may set cookies of its own. These cookies are set under the partner’s own cookie and privacy policies, not ours, and we cannot read them. Our Affiliate Disclosure explains how partner links work.
9. The card scanner
The card scanner adds no cookies and no storage of its own. When you press “Add to my collection” after a scan, the card goes into the collection tracker’s list in your browser, ripfan-collection, in the table above.
10. Your cookie choice
In the EEA, the UK and Switzerland, the first time you open a page a banner at the bottom of the screen asks whether you allow Google's analytics and ad measurement cookies. To tell where you are, the page asks Cloudflare, which already carries the request, for your country, and we keep no record of it; if the country cannot be told, the banner asks. Elsewhere no banner appears, and Cookie settings opens the same choice. It has two buttons of the same size, Accept and Reject, and the site works the same whichever you press. If your browser blocks site storage, your answer could not be kept, so the banner does not ask, and in those countries Google's cookies stay off.
- Your answer is kept in your browser, as ripfan-consent in the table in section 3, so the banner does not ask again on the next page. After 13 months it asks again in the EEA, the UK and Switzerland.
- To make or change a choice, press Cookie settings at the foot of any page, wherever you are. The banner opens, and your answer applies at once.
- Withdrawing consent by pressing Reject stops Google's cookies from then on and deletes the ones already set on rip.fan. It does not undo what was counted before.
11. Controlling cookies and storage in your browser
Every major browser lets you see, block and delete cookies and site data. The steps change from time to time, so check your browser’s own help pages. In current versions:
- Chrome: Settings, then Privacy and security, then Third-party cookies, or Delete browsing data.
- Safari on a Mac: Settings, then Privacy, then Manage Website Data.
- Safari on an iPhone or iPad: the Settings app, then Apps, then Safari, then Advanced, then Website Data.
- Firefox: Settings, then Privacy and Security, then Cookies and Site Data.
- Edge: Settings, then Privacy, search, and services, then Delete browsing data.
You can usually clear the data of one site only, such as rip.fan, without touching any other site. A private window keeps nothing after you close it. Blocking all cookies does not stop Rip.fan from working, but it may stop Cloudflare from letting your browser through after a security check, and it stops you signing in to an account.
Clearing rip.fan’s data deletes your collection tracker list, your set checklist ticks, your trade checker lists and your sample binder. Save a CSV copy of anything you want to keep first. It also signs you out. What your account holds stays with your account.
12. Global Privacy Control and Do Not Track
Global Privacy Control is a signal your browser can send to tell sites not to sell or share your information. We treat it as your choice to opt out: while your browser sends it, Google's ad measurement stays off wherever you are, even if you press Accept, without you having to do anything else. Analytics follow your region's default and any choice you make with Cookie settings.
Do Not Track is an older signal with no agreed meaning, so we do not act on it.
13. Changes to this policy
We will update this policy before we add any cookie or storage item. The “Last updated” date at the top of this page shows the latest version, and the “Effective” date shows when this version first applied.
14. Contact
Questions about cookies or browser storage on Rip.fan go to editor@rip.fan. You can also read our Privacy Policy and our Terms of Use.