Privacy Policy
Last updated
In short
- An account is optional. It needs a username and an email address, with a password or a Google account.
- News comes by mail only when you ask for it, and every mail has a link to stop it.
- Visits are counted with Google Analytics, but only once you allow it in the cookie banner. No advertising and no tracking across websites.
- We only learn your name or email address when you send them to us yourself.
- Two technical cookies, a third when you sign in, a fourth when you choose where prices come from, a fifth when you choose how prices are shown and a sixth when you choose which countries Cardmarket's sellers come from and a seventh with your answer to the cookie banner, listed on the cookie page.
- Some images load from servers run by Riot Games.
- Feedback sent from the bar above the footer is kept on the site.
- Pictures from the card scanner stay on the site and are deleted after 60 days.
- The contact form, the feedback form, the news form and the sign-up form are guarded by a check from Cloudflare.
About this policy
This policy explains what Riftbound.org learns about you when you visit and what happens to that information. The site is run by Riftbound.org, who is responsible for the data described here.
Riftbound.org is a fan project. It is not run by Riot Games or UVS Games, and neither of them receives data from us.
What the site receives
You can browse the whole site without telling us who you are. An account is optional, and what it stores is described below.
Like every website, the site receives some technical data each time your browser asks for a page:
- your IP address,
- the date and time of the request,
- the page you asked for and the page that linked you to it,
- the type and version of your browser and operating system.
The server can keep this data in its log files. The site also stores a random session identifier in a cookie. While you are signed in, that identifier is tied to your account. Otherwise it is tied to nothing.
Cloudflare, which stands in front of the site, passes on the country it reads from your IP address. On your first visit that country picks the marketplace your prices come from, euro prices from Cardmarket in Europe and US dollar prices from TCGplayer elsewhere. The site keeps the marketplace, in the cookie described on the cookie page, and not the country.
When you write to us
The contact form asks for your name, your email address, a subject and your message. The site sends these to our mailbox by email. It does not keep a copy in a database of its own.
If you write to [email protected] instead, we receive your email address and what you wrote.
The feedback bar above the footer of every page opens a form that asks what you want to tell us and, only if you would like an answer, your email address. You can add a screenshot of the page as it is shown in your browser. Your browser makes that screenshot itself, and it is only sent when the box for it is ticked. The site keeps feedback in a database of its own and mails a copy to our mailbox. With it, the site records the address of the page, the size of your browser window and the type of browser you use, so that we can find the cause of what you report.
We use these details to answer you and to deal with what you wrote about, and for nothing else. Messages and feedback are deleted once they are no longer needed for that.
When you make an account
An account is made on the sign-up page with a username, an email address and a password, or with a Google account. The site stores the username and the address, the password in a hashed form that cannot be read back, the day the address was verified, the marketplace you chose to see prices from, how you chose to see prices and the seller countries you narrowed Cardmarket's to once you choose them, the decks you like, and the dates the account was made and last changed. While you stay signed in, which you do unless you untick the box for it on the sign-in page, it also stores a random token that matches the cookie in your browser.
When you sign up or sign in with Google, Google sends the site the number of your Google account, your email address and whether Google has verified it, your name and a link to your profile picture. The site keeps the number, so that it knows your account the next time, and the address as the address of your account. The name is used once, to suggest a username, and the picture is not used at all. An account made this way has no password. When an account with the same address exists already, Google is connected to that account.
The address is used for the mail that asks you to verify it, for the link to choose a new password when you ask for it, and for the news by mail when you tick a kind of news on the sign-up form or on your account page. The username is shown on the site as the name of your account, and it will be shown with anything you share on the site once that is possible.
The sign-in page counts wrong passwords per account and per IP address, so that guessing a password gets slow after a few tries. That count is kept for a minute.
Your account stays until you have it removed. There is no button for that yet. Write to us and it is done by hand, together with everything stored under the account.
When you ask for the news by mail
You can ask for the news by mail with the form on the news pages, on the sign-up form or on your account page, and pick the kinds of news you want. The site stores your email address, the kinds you picked, a random key for the link that changes or ends the subscription, your account when the address is the one of an account, and the day the subscription was confirmed.
Nothing is sent before the address is confirmed: with the link in a mail sent to it, or, when you ask on the sign-up form, by verifying the address of your new account. An account whose address is verified already needs no confirmation for its own address. Every new article of a kind you picked is then mailed to you once, with its summary and a link to it. Every mail has a link to change what you get or to stop, and stopping removes your address from the list.
When you scan cards
The card scanner is open to signed-in users, and the camera button in the search box lets any visitor search with a photo of a card. Your browser asks you before the page may use your camera, and the camera is only on while the scanner is open or while you take a photo for the search. Nothing is sent until you press the shutter or choose a picture. Then the part of the view inside the card frame, or the picture you chose, goes to the site.
On the site's own server the picture is compared with the pictures of the cards and, when that leaves a doubt, the text on it is read. The picture is not sent to any other service. With it, the site stores the text it read, the card it matched and how sure it was, and the card you took, under your account when you are signed in and under no name otherwise, so that we can see where the scanner went wrong and make it read cards better.
The picture is deleted after 60 days. What was read and the card you took stay with your account until you have it removed. A photo sent from the search without an account is not tied to you, and what was read from it is kept without a name.
When you import cards
Your collection, a list or a binder can take cards from a file, a pasted list or a link, and the deck builder can take a deck from a pasted list or a link. A file is read in your browser and its text goes to the site, which finds the cards in it and shows them to you before anything changes. The text is not kept. The cards you then import are stored with your account like the ones you add one at a time.
A link to a page of another website is opened for you by BrightData, a service that fetches web pages, so that the site itself never contacts that website. BrightData receives the address you pasted, and not your IP address or anything about your account. The site keeps the cards read from the page for half an hour, so you can import them, and nothing else about the page. A link to a page of this site is read on the site itself, as far as you may see that page.
What the site does not do
- It does not count visits with Google Analytics before you allow it in the cookie banner.
- It does not show advertising.
- It does not follow you across other websites or build a profile of you.
- It does not sell or trade data about visitors.
Why the data is used
The technical data is used to send you the pages you ask for, to keep the site secure and to find the cause of errors. Under the GDPR and the UK GDPR the legal basis is our legitimate interest in running a working and safe website, Article 6(1)(f). Messages and feedback are handled on the same basis, our interest being to answer the people who write to us and to fix what they report. The data of an account is handled to provide the account you asked for, Article 6(1)(b). Pictures from the card scanner and photos sent from the search box are handled to find the card you asked for on the same basis, and kept for a while after that in our legitimate interest in making the scanner read cards better, Article 6(1)(f). The news by mail rests on your consent, Article 6(1)(a), which you withdraw with the link in any of its mails or on your account page. Files, lists and links you import are handled to provide the import you asked for, Article 6(1)(b). The counting of visits with Google Analytics rests on your consent, Article 6(1)(a), which you give in the cookie banner and can withdraw on the cookie page at any time.
Others who receive data
Riot Games
Card images are stored on this site where possible. Other images, and the icons for domains, rarities and rules text, load straight from image servers run by Riot Games at rgpub.io. To fetch them your browser connects to those servers. Riot then sees your IP address and the type of browser you use, the same as when you visit the official Riftbound site. The privacy notice of Riot Games covers what happens to that data.
Cloudflare
To keep automated senders out, the contact form, the feedback form, the news form and the sign-up form run a check called Turnstile, a service of Cloudflare. It loads from Cloudflare when you open one of those pages or the feedback form, and not before. Cloudflare receives your IP address and technical details of your browser, and tells the site whether the check passed. It does not receive your message, your feedback or the details of your account. The privacy policy of Cloudflare covers that data.
Google Analytics
Once you have allowed it in the cookie banner, every page loads the Google tag, a script from Google that counts the visits. Google then receives the address of each page you open, how far you scroll it, clicks on links to other websites and searches on the site, together with your IP address, the language and size of your browser and the kind of device, and it sets two cookies to tell visits and visitors apart. From this Google makes the reports the site reads, which hold counts and no single visitor, and it uses the data for its own purposes as well, which this page of Google describes. Before you allow it, nothing loads from Google. The cookie page lists the cookies and lets you withdraw your answer.
Google sign-in
When you choose to sign in with Google, you leave for a page of Google, which asks you to allow it and sends you back. Google receives your IP address and learns that you signed in to this site. That happens only when you press the Google button, nothing loads from Google before. The privacy policy of Google covers that data.
Google Maps and your place
The events pages can draw a map of the stores. The map is Google Maps and loads only when you press the button that asks for it; before that, nothing loads from Google. Once it loads, Google receives your IP address and the part of the map you look at. The privacy policy of Google covers that data. The site counts how often the map is drawn, as a number per day with nothing about you in it. When you press "Near me", your browser asks you whether the page may know where you are; the place is used for that search, kept in the address of the page and nowhere else. Without a place of your own, the page starts from the country and city that Cloudflare reads from your IP address and passes on with the request, which the site does not store.
BrightData
When you import cards from a link to another website, the site asks BrightData to open that page and hand it back. BrightData receives the address of the page, which can hold a code the other website put in its export links, and opens the page from its own network. It does not receive your IP address, your account or the cards you import. The privacy policy of BrightData covers that data.
Hosting and mail
The company that hosts the site handles the technical data on our behalf in order to deliver the pages. Messages from the contact form, copies of feedback, the mails about your account and the news by mail travel through the mail service the site uses.
Fonts
The fonts are served by the site itself. No font service is contacted.
Links
Websites we link to, such as the official Riftbound site and the Riot store, have privacy policies of their own.
How long data is kept
Session data expires after 2 hours without activity and is then removed. Log files are kept only for as long as they are needed to deal with faults and misuse. Pictures from the card scanner and photos sent from the search box are deleted after 60 days, and what was read from them stays with the account, or without a name when there was none. The cards read from a link are kept for half an hour. An account is kept until you have it removed, and a news subscription until you end it.
Your rights
Depending on where you live, the law gives you rights over data about you. These can include the right to see that data, to have it corrected or deleted, to limit or object to its use, and to complain to the data protection authority of your country.
Without an account, the site does not know who its visitors are. To find technical data about you we usually need the IP address and the time of your visit. A message or feedback can be found by the email address that was sent with it, and an account by its username or email address.
Children
The site is meant for a general audience and does not knowingly collect personal data from children.
Changes
If the site starts to handle data differently, this page is updated first. The date at the top shows when it last changed.
Contact
Do you have a question about this policy, or do you want to use one of your rights? Use the contact form or write to [email protected].