Privacy Policy

This policy explains what information Rip.fan handles when you visit rip.fan, use its tools or write to us, why we handle it, who else receives it, how long it is kept and what you can do about it.

Accounts on Rip.fan are optional, and we sell no one's information. We use Google Analytics, loaded through Google Tag Manager, to count which pages and tools readers use, under the cookie choice you make. Signed out, the tools keep your lists in your own browser; signed in, your collection and watchlist are kept with your account, and our server keeps no record of the pages you read.

1. Who we are

Rip.fan is a hobby publication about online card rips. The operator of rip.fan (“Rip.fan”, “we”, “us” and “our”) decides how the information described here is used, and is its controller under the GDPR and the UK GDPR.

You can reach us about anything in this policy at editor@rip.fan.

2. The short version

• Accounts are optional. You can read every page and use every tool without an account. If you sign in, we keep your email address, your collection, your watchlist and your session (section 3).
• Google Analytics, under your choice. We use Google Tag Manager and Google Analytics. In the EEA, the UK and Switzerland a cookie banner asks first, and they set no cookies until you press Accept. Everywhere else they are on unless you turn them off with Cookie settings at the foot of any page. No ad network, no social media buttons and no tracking pixels (section 12).
• Cookies of our own only for signing in. Our own code sets two cookies, and only when you use an account: one keeps you signed in and one keeps sign-in requests safe. Signed out, our tools keep your lists in your browser’s local storage, which never reaches us. Google's analytics cookies are set only under your choice. Cloudflare, which carries the site’s traffic, may set a security cookie, as our Cookie Policy explains.
• No access log. Our server keeps no record of the pages you read.
• We sell nothing. We do not sell your information. Outside the EEA, the UK and Switzerland, Google's ad measurement runs unless you turn it off with Cookie settings, and never while your browser sends Global Privacy Control. Inside them it runs only if you press Accept.
• Where your information goes, and when. Google receives what Google Analytics counts, under your cookie choice. Scrydex receives your IP address when your browser loads a card picture. A partner site sees you arrive when you press Continue on a leaving page. If you write to us, our email provider holds your message. If you sign up for the weekly brief, the service that sends it receives your address. If you sign in, the service that sends our emails receives your address for your sign-in links and any watch email, and Google takes part only if you choose to sign in with Google. OpenAI reads the photos you choose to scan with the card scanner.

3. What we collect, and why

When you open a page

Every request for a page, a picture or a file on rip.fan passes through Cloudflare, Inc., which protects the site and delivers it quickly, and then reaches our server, which DigitalOcean hosts in New York.

• What Cloudflare handles. Your IP address, the address of the page you ask for, and the headers your browser sends with the request, such as its user agent (the kind of browser and device), its language and the page that sent you. Cloudflare uses them to deliver the page, encrypt the connection and block attacks and automated abuse, under its own privacy policy. Cloudflare also asks browsers that support network error reports to tell it when a page fails to load. A page that loads normally is not reported.
• What our server keeps. Our web server, Caddy, is set to keep no access log, so it keeps no record of the pages you read or of your IP address. When a request fails inside our server, for example while one of our services restarts, Caddy can write an error line to the server’s system journal. Such a line can hold the address asked for, the headers your browser sent and your IP address. The journal is capped at 500 MB, and its oldest lines are deleted as new ones arrive.
• Cloudflare Web Analytics. Cloudflare adds a small script to our pages that counts visits and measures how quickly each page loads, and shows us the totals. It sends Cloudflare the page’s address, the page that sent you, the kind of browser and device, and the page’s load timings. Cloudflare says it uses no cookies or other storage in your browser and does not fingerprint your browser, so it cannot follow you from visit to visit.
• Why. To deliver the site, keep it working and secure, and see which pages are read and how fast they load.

Card pictures

Card pictures on card pages, set pages, the topic pages and some tools and articles load straight from Scrydex’s image server, not from ours. Your browser’s request tells Scrydex your IP address and your browser’s user agent. Our pages tell your browser to send only the site’s address, rip.fan, as the referrer, so Scrydex does not learn which page you were reading. Scrydex handles these requests under its own privacy policy, and when we checked on October 15, 2026, its image server set no cookies.

The card prices and card lists come to our server from Scrydex once a week. That exchange holds nothing about you.

Your browser’s storage

Some tools keep what you enter in your browser’s local storage, on your device: the collection tracker, the set checklist, the trade checker and the rip simulator’s sample binder. Your light or dark choice is kept there too, once you switch it with the button in the footer. If you sign in, a note that this browser has signed in is kept there too. Nothing in local storage is sent to us, and we never see it. Our Cookie Policy lists each item, what it holds, how long it lasts and how to clear it.

Search and the card tools

The site search runs in your browser. It downloads parts of the search index from rip.fan and matches your words on your device, so our server never receives what you type.

The card price lookup, the collection tracker, the set checklist, the trade checker and the card finder download our price list from rip.fan and do their work on your device. A CSV file you read into a tool is read on your device too. Nothing you type or tick in them is sent to our server, except the collection tracker's list while you are signed in, which is saved to your account (Your account, below). The calculators work the same way. While analytics are on for you, Google Analytics receives the words you searched for in the site search and the card price lookup, once you stop typing, as the next part explains.

Partner links

Partner links go first to a short redirect page on our site. That page runs a short script that takes you on after four seconds unless you choose to stay. The script stores nothing and sends nothing to us. While analytics are on for you, Google Analytics counts that you went on, and whether you pressed Continue or waited.

When you go on, your browser opens the partner’s link, which carries our referral code so the partner can credit us. Some partner links pass through the partner’s own link service first. The leaving page tells your browser to send no referrer, so the partner can tell that you came through our link but not which page you read. A partner may report to us the signups or purchases made through our link, so that it can pay the commission it owes us. From the moment you reach the partner’s site, its own terms, privacy policy and cookies apply.

Google Analytics

Every page loads Google Tag Manager, which loads Google Analytics under your region's default and any choice you make (section 12 and our Cookie Policy). While analytics are on for you, Google Analytics receives:

• The page. Its address, its title, the kind of page it is (a review, a ranking, a card page and so on) and, on a review, which site it is about, and the page that sent you.
• Your browser and device. The kind of browser and device, its language and screen size, and your approximate location, which Google works out from your IP address. Google says Google Analytics does not log or store IP addresses.
• What you do on the page. How far you scroll, links you follow to other sites, and these site events: a click on a partner link, going on from a leaving page, a search and its number of results, a card price lookup, a card scanner answer (matched or not, graded or not, priced or not, never the photo or the card), a pack opened in the rip simulator, a card added to the collection tracker, the use of a tool, a copied offer code, a confirmed weekly brief sign-up and a filter on the home page's top sites.
• A random number kept in a cookie, which lets Google Analytics tell a browser it has seen before from a new one. It does not tell us who you are.

We send Google no name, email address or other detail that identifies you, and no words you type except search terms. A search term that looks like an email address or a phone number is dropped before anything is sent. The newsletter pages whose address carries a confirmation or unsubscribe code load no Google tag at all. Nor do the account pages that a sign-in link or a watch email unsubscribe link opens.

We see the totals in Google Analytics' reports. We use them to learn which pages and tools are useful, and to fix what is not.

Email you send us

If you write to editor@rip.fan, we receive your email address, your name if your email shows one, and whatever you write. We use it to answer you, to fix an error you report or to act on your request, and we keep it as section 6 says. Our email provider stores the messages for us.

Your account

This part applies only if you sign in, which is never needed to read the site or use its tools.

• What we keep. Your email address, the day you made your account and whether you take the watch email. The cards in your collection (each card's set, number, name and how many you have) and the cards you watch, with the day you started watching each. No prices: your cards page prices them from our weekly price check each time it opens. There is no password to keep.
• Signing in by email. We email you a link that works once, within 15 minutes. While it waits we keep your address and a scrambled form of its code, from which the link cannot be rebuilt, and we delete both when that link or another one for your address is used, when you ask for a newer one on the same browser, or when it expires. The link is tied to the browser that asked for it: opened on another browser, it asks you to confirm the address before it signs you in.
• Signing in with Google. Only if you choose Continue with Google. You sign in on Google's own page, and Google tells us your email address, that it has checked that address, and a number that stands for your Google account, which we keep to know you next time. If your address already has an account here, Google is joined to it only when Google runs that address's email (a Gmail address, or a work address on Google Workspace); otherwise you sign in with the emailed link first and link Google on your cards page. We receive nothing else from Google, and send it nothing about you.
• Sessions and cookies. Signing in sets a cookie that keeps you signed in, and the sign-in form sets a second one that keeps sign-in requests safe. Our Cookie Policy lists both. Our server keeps each session in a scrambled form, so a session can be ended at any time: it ends 60 days after you last used it, never lasts more than a year, and ends at once when you sign out. Sign out everywhere, on your cards page, ends every session you have.
• Your collection while signed in. The collection tracker and the Add to collection button save your list to your account instead of your browser. A list your browser kept from before is copied in only if you press Add them to my account.
• The watch email. After each weekly price check, if a card you watch moved by 10% or more and at least $0.50, we send one email that names the cards that moved and their prices. It holds text and links only: no images and no tracking code of our own. Turn it off on your cards page, or with the link in the email, which email apps that show their own unsubscribe button use too. We keep the day of each check we emailed you about, so no check is emailed twice.
• Packs you watch. If you press Watch this pack on our live pack values pages, the pack is stored with your account: its site and pack, their names, the day you started watching it, and its listed value per $1 when you started watching or in our last email about it, which is the figure the next email compares with. At most once a day, if a pack you watch has moved by $0.10 or more per $1 since then, we send one email that names those packs, by the same rules as the card email: the same setting and the same link in the email stop both. We keep the day of that email for three days, so no one gets two in a day. Remove a pack on your cards page; deleting your account deletes them all.
• Who handles it. Resend, Inc. sends the sign-in and watch emails, so it handles your address whenever one goes out. Your account is stored on our server, which DigitalOcean hosts.
• Limits. To stop abuse, one connection can ask for a limited number of sign-in links an hour, and so can the network it belongs to and one address, and a signed-in session can save only so often. The counts use your IP address, a scrambled form of the address and a scrambled form of the session, held in our server's memory for at most a day and never written to disk.
• The sign-in check. The sign-in form runs Cloudflare's Turnstile check, in a frame from challenges.cloudflare.com, to tell people from scripts that ask for links in bulk. Cloudflare, which already carries the site's traffic, reads your browser and connection details for the check under its own privacy policy, and tells our server only whether it passed. We keep nothing from it.
• Download and delete. On your cards page you can download everything your account holds, as JSON or as CSV, and delete your account. Deleting removes your email address, your collection, your watchlist and your sessions from our database at once, in a way that overwrites them rather than only marking them as deleted. You can also write to editor@rip.fan and we will delete it for you.
• Copies. Every night we copy the accounts database to a folder on our server that only the accounts service can open, and keep each copy for 14 days. DigitalOcean keeps its backups of the whole server for up to four weeks. A deleted account stays in those copies until they expire.

The weekly brief

This part applies only if you sign up for the weekly brief, our free email of the week's stories, which goes out on Fridays.

• What we keep. Your email address, the page you signed up from, and the times you signed up, confirmed and unsubscribed. We do not store your IP address with your subscription. While a confirmation link is waiting to be used, we also keep a scrambled form of its code, from which the link cannot be rebuilt, and the time it stops working, 48 hours after it was sent. We count the confirmation emails sent to an address each day, so that no address gets more than three a day.
• Why. To send you the weekly brief. In the EEA and the UK our legal basis is your consent, which you can withdraw at any time by unsubscribing.
• Who handles it. Resend, Inc. sends the emails for us, so it handles your address whenever a message goes out. The list itself is stored on our server, which DigitalOcean hosts.
• Double opt-in. We email you a confirmation link first. Your address joins the list only after you open that link. Until then it waits as an unconfirmed signup, and a signup you never confirm is deleted after 30 days.
• The signup limit. To stop abuse, one connection can make at most five signups an hour. The count uses your IP address, held in our server's memory for at most an hour and never written to disk.
• Unsubscribing. Every weekly brief carries an unsubscribe link, and you can unsubscribe at any time. Email apps that show their own unsubscribe button use the same link. An unsubscribed address stays on file, marked as unsubscribed, and gets no weekly brief. If the address is entered on the signup form again, a new confirmation email goes to it, and it is then treated as a new signup: deleted after 30 days unless it is confirmed.
• What the emails hold. The emails we write hold text and links only: no images and no tracking code of our own. We keep a record of which issue went to which subscriber number, so that no one gets the same issue twice. That record holds no email address.
• Copies. Our server makes a copy of the list every night and keeps each copy for 14 days, and DigitalOcean keeps its backups of the whole server for up to four weeks. A deleted address stays in those copies until they expire.
• Deletion. To have your address deleted, write to editor@rip.fan and we will delete it. It is removed from the list in a way that overwrites it, not only marked as deleted.

What we do not collect

• No passwords or payment details. Accounts sign in by an emailed link or with Google, and Rip.fan sells nothing and takes no payments.
• No advertising or social media scripts, no tracking pixels and no device fingerprinting. Our only analytics are Google Analytics, under your choice, and Cloudflare's visit counts, which use no cookies.
• No precise location. A scanner photo loses its location data on your device before it is sent.
• No sensitive information. We never ask for it, so please do not send it to us.
• We do not combine what Cloudflare, Scrydex or a partner holds about you with anything we hold.

4. Our legal bases in the EEA and the UK

If you are in the European Economic Area or the United Kingdom, the GDPR or the UK GDPR requires a legal basis for each use of your personal information. These are ours:

Where we rely on our legitimate interests, we have weighed them against your rights, and we use as little information as the job needs. You can object to that use at any time (section 9).

5. Who receives your information

We use a small number of service providers, and each receives only what it needs for the job in the table below. We do not sell or rent your information. Google's ad measurement, which may count as sharing for cross-context behavioral advertising, runs in the EEA, the UK and Switzerland only if you press Accept, and elsewhere unless you turn it off with Cookie settings. It never runs while your browser sends Global Privacy Control.

We may also disclose information when the law requires it, to answer a valid legal request, or to protect the site, its readers or anyone else from harm or abuse. If Rip.fan is ever sold or transferred, the information we hold would pass to the new operator, who would remain bound by this policy until it changes it in the way section 13 describes.

6. How long we keep it

7. Security

• Encrypted connections. Every page is served over HTTPS. Cloudflare checks our server’s certificate on every connection to it, and the site tells browsers to use HTTPS only.
• Little to lose. Accounts have no passwords. Sign-in links, sessions and Google sign-in states are stored only in a scrambled form, so our database holds nothing that would sign anyone in.
• Locked-down services. Our services run with limited permissions, and their keys sit in a file that only the system’s administrator can read.
• Careful storage. The weekly brief list stores confirmation codes only in a scrambled form, and a deleted address is overwritten in the list, not only marked as deleted. A deleted account is overwritten the same way.
• Private pages stay private. The pages we use to run the site sit behind a password and are never linked from the site.
• Browser protections. The site tells your browser that no page may use your microphone or your location or open a live camera view, and that rip.fan may not be shown inside another site’s frame.

No system is perfectly secure. If we learn of a breach that affects your information, we will tell you, and the authorities, where the law requires it.

8. International transfers

Our server is in the United States, in DigitalOcean’s New York region. Cloudflare handles each request in its network, often in a data center near you, and Cloudflare says cookie data may be processed in the United States. Scrydex, the service that sends our emails, and OpenAI, which reads the photos sent to the card scanner, may also handle information in the United States. So may Google, for Google Analytics.

If you visit from the EEA, the UK or another country with its own data protection law, your information is transferred to the United States. Our providers offer safeguards for these transfers in their data processing terms, such as the European Commission’s standard contractual clauses and the UK’s addendum to them, or certification under the EU-US Data Privacy Framework and its UK extension.

9. Your rights

In the EEA and the UK

You have the right to:

• Access the personal information we hold about you, and get a copy of it.
• Correct information that is wrong or incomplete.
• Delete your information.
• Restrict how we use it, for example while we check a correction you asked for.
• Object to a use based on our legitimate interests.
• Take your information with you in a common format (portability), where we hold it because you consented or asked for a service.
• Withdraw your consent at any time, for example by unsubscribing from the weekly brief. This does not affect what we did before you withdrew it.
• Complain to a data protection supervisory authority: in the EEA, the authority where you live or work; in the UK, the Information Commissioner’s Office. We would be glad to help first, if you write to us.

We make no decisions about you by automated means that have legal or similarly significant effects on you.

In the United States

California, through the CCPA as amended by the CPRA, and a growing number of other states, among them Colorado, Connecticut, Virginia, Utah, Texas and Oregon, give their residents privacy rights. Whether or not a given law applies to a site of our size, we honor these rights for every reader in the United States:

• Know and access. Ask what personal information we have collected about you, where it came from, why, and who received it, and get a copy of it.
• Delete. Ask us to delete the personal information we hold about you.
• Correct. Ask us to correct information that is wrong.
• Opt out. Opt out of the sale of your information, of sharing it for cross-context behavioral advertising, of targeted advertising and of profiling. Google's ad measurement may count as sharing. To opt out, press Cookie settings at the foot of any page and then Reject, or send Global Privacy Control from your browser.
• Limit sensitive information. We collect none, so there is nothing to limit.
• Equal treatment. We will not treat you differently for using any of these rights.
• Appeal. If we turn down a request, you can ask us to look at it again.

What we have collected in the last 12 months. Identifiers: IP addresses, as Cloudflare and Scrydex receive them and as they can appear in an error line on our server, and email addresses, if you wrote to us, signed up for the weekly brief or signed in. Internet activity: the pages and files your browser asks for, as Cloudflare handles them. Since October 25, 2026, if you signed in, the collection and watchlist you keep with your account. Since October 22, 2026, also the pages and tools used and the random number in the Google Analytics cookie, as Google Analytics counts them under your cookie choice. We collected them from you and your browser, for the purposes in section 3, and disclosed them only to the providers in section 5, for those purposes. We collected no sensitive personal information.

Do Not Sell or Share

We do not sell your personal information. Outside the EEA, the UK and Switzerland, Google's ad measurement runs unless you opt out, and it may count as sharing for cross-context behavioral advertising. To opt out, press Cookie settings at the foot of any page and then Reject. We also treat a Global Privacy Control signal from your browser as your choice to opt out, without you having to do anything else: while your browser sends it, Google's ad measurement stays off even if you press Accept.

10. How to use your rights

Email editor@rip.fan and tell us what you would like us to do. Please include the email address the request is about, if there is one. If you have an account, you can also download everything it holds, and delete it, yourself on your cards page.

• Checking it is you. We may ask you to confirm that the request comes from you, for example by replying from the email address it is about. We ask only for what we need to check, and we use it only for that.
• Someone acting for you. You can ask an authorized agent to make a request for you. We will ask the agent for your signed permission, and we may ask you to confirm the request with us directly.
• When we reply. For requests under the GDPR and the UK GDPR, within one month. If a request is complex we may take up to two more months, and we will tell you why within the first month. For requests under US state laws, within 45 days. If we need longer, we will tell you within those 45 days, and take no more than 45 more.
• Appeals. If we turn down your request, reply to our answer and ask us to look at it again. We will answer your appeal within 45 days and explain our decision. If you are still not satisfied, you can complain to the privacy authority where you live.
• No charge. We do not charge for a request, unless it is plainly unfounded or excessive.

Much of what passes through the site, we cannot link to you: our server keeps no access log, the storage in your browser never reaches us, and Google Analytics shows us totals, not people. For your browser’s storage, clearing this site’s data in your browser deletes it at once. For what Cloudflare, Scrydex or a partner site holds, you can also write to them directly.

11. Children

We do not knowingly collect personal information from children under 13. If you think a child under 13 has given us personal information, for example by writing to us, signing up for the weekly brief or making an account, email editor@rip.fan and we will delete it.

12. Analytics and your cookie choice

We use Google Analytics, loaded through Google Tag Manager, with Google's Consent Mode. Every page tells Google's tags your choice before they send anything:

• In the EEA, the UK and Switzerland, a cookie banner asks first, and analytics and ad measurement are off until you press Accept. Until then Google's tags set no cookies; they may send Google a note that a page was opened, with no cookie and nothing that recognizes your browser.
• Everywhere else, no banner appears. Analytics and ad measurement are on unless you press Cookie settings and then Reject.
• Reject turns both off wherever you are, and deletes Google's cookies already set on rip.fan.
• Global Privacy Control keeps ad measurement off wherever you are, even after you press Accept.

To tell where you are, each page asks Cloudflare, which already carries the request, for your country; we keep no record of it. If the country cannot be told, the banner asks. Accept and Reject are the same size, and the site works the same either way. To make or change a choice anywhere, press Cookie settings at the foot of any page. Your choice is kept in your browser for 13 months, and then, in the EEA, the UK and Switzerland, the banner asks again. Our Cookie Policy names each cookie, what it holds and how long it lasts. Google handles what it receives under its own privacy policy.

13. Changes to this policy

We will update this policy whenever what we collect, why, or who receives it changes. The “Last updated” date at the top of this page shows the latest version, and the “Effective” date shows when this version first applied. If a change matters to how we use information we already hold about you, such as your weekly brief address, we will tell you before it applies.

14. Contact

Questions, requests and complaints about this policy go to editor@rip.fan. You can also read our Terms of Use and our Cookie Policy.