Privacy Policy

Who is responsible

Alejandro Medina, in Mexico, decides what BinderLoot does with your personal data. This document calls that person "the operator".

Write to the address at the end of this page for any question about your data.

The short version

BinderLoot runs no advertising and no cross-site tracker. Nobody buys your data, because nobody is offered it.

The site counts page views with Plausible, which sets no cookie, keeps no personal data and never follows a reader to another site.

The site keeps the data an account needs, and it gives you a button that deletes the account.

What the account holds

BinderLoot keeps this data about a collector.

• Account: the name, the username, the email address and a one-way hash of the password.
• Profile: the biography text, the four sharing switches and the beginner setting.
• Library: the printings you own, their finish and condition, your binders, your pockets, your decks and your wishlist.
• Session: the session record of the browser, with the IP address and the browser identification, so a sign-in survives a page load.
• Payment: the Stripe customer identifier, the brand and the last four digits of the card, and the date of a patron payment.
• Activity: the source of the visit that created the account, which is a campaign name, the site that linked to BinderLoot, Legendsverse or direct. A dated record of each sign-in, of the first time the collection held 10 copies, of each visit to the patron page, of a patron payment with its amount, and of each click to TCGplayer. A dated record of each add to the collection with its game and its number of copies, of each new deck with its game, of the moment the profile became public, of each copied profile or binder link, of the installation of the app, of each day the installed app opened, and of each Learn guide opened while signed in.
• Notifications: for each device where you turn on notifications, the push address that the browser gives, the two keys that encrypt a message for that device, a device label such as Chrome on Android, and the dates the device was added and last received a message. The two notification choices under Settings. A message travels encrypted through the push service of the browser, for example Google, Apple, Mozilla or Microsoft. A device record is deleted when you turn notifications off on that device, when you delete the account, or when the push service reports that the device no longer exists.

The photograph of a card

The card scan sends one photograph to a card recognition service. The service reads the card name and answers.

BinderLoot never stores the photograph. Neither the browser upload nor the server keeps a copy after the answer arrives.

The photograph is drawn down to 1280 pixels in your browser before it travels, so the upload carries fewer pixels than the camera took.

Why the operator uses this data

Each purpose below is the reason one field exists. No field serves a purpose that this list does not name.

• To run your account and to sign you in.
• To keep and to show your collection, your binders, your decks and your wishlist.
• To keep your daily challenge answers and your streak, and to count the share of right answers of each day.
• To take the one-time patron payment and to keep the record that tax law requires.
• To send the account messages: the email verification, a password reset and a security notice.
• To send product news and patron mail through BYOMailer.
• To send the notifications that you turned on.
• To keep the service available, which includes the rate limits that stop an abusive request.
• To count sign-ups, returns and payments. The operator reads these counts as totals that hold no name and no email address.

What the browser stores

BinderLoot sets a session cookie and a sign-in cookie that remembers you. Both are needed for the account to work.

The browser also keeps your appearance setting and your Learn progress in local storage. That data stays in the browser and never reaches the server.

When you play the daily challenge without an account, BinderLoot sets a cookie that holds a random code and nothing else. The code keeps your one answer of the day. Your daily streak stays in local storage. When you create an account and open the daily challenge, the browser sends that streak to the server one time, and your account keeps it.

The site sets no advertising cookie and no analytics cookie. Plausible counts a page view without one.

The services behind the product

These services process data on behalf of the operator.

• Stripe processes the patron payment. Stripe receives your email address and your card details, and BinderLoot receives neither the card number nor the security code.
• The card recognition service receives one photograph of a card, for the length of one request. It receives no account data.
• An email provider delivers the account messages, which carry your email address.
• A hosting provider runs the servers and the database that hold the data of this page.
• A search engine indexes the card catalogue. Its index holds catalogue data alone, and no collector data.
• Plausible counts the page views of the site. It receives the address of the page, the referrer, the country and the type of device. It receives no account data and no identifier of a reader.
• BYOMailer receives the name and the email address of an account when the account is created, so the operator can send product news. When the collector becomes a patron, BYOMailer also receives the tag bl_patron. Adding one card to the collection, saving a wish, creating a deck, and creating a binder add the tags bl_added_to_collection, bl_added_to_wishlist, bl_deck_created, and bl_binder_created. Those same updates record how many copies are owned as bl_collection_size, how many wishes are saved as bl_wishlist_size, the games of the collection as bl_games, and the reference value of the collection in US dollars as bl_collection_value. Opening the patron page while signed in, before becoming a patron, adds the tag bl_viewed_patron. Once an hour, a collector who added or changed a collection lot in that hour has those four values recorded again.

What Scryfall and Wizards of the Coast receive

Scryfall is the source of the card catalogue. BinderLoot reads from Scryfall on a schedule, from its own servers.

Neither Scryfall nor Wizards of the Coast receives your account data, your collection or your decks.

What other people see

A profile is private when the account is created. Nobody but you reads it until you turn it on under Settings.

A public profile shows the username, the biography and the sections you turned on: the collection, the binders, the decks and the wishlist.

The patron page names the patrons whose profile is public, with their username, and counts the others without a name.

A public profile is a public web page. A search engine can index it, so publish nothing there that you want to keep private.

Turn a section off, or turn the profile off, and the page hides that data again.

How long the data stays

The account data and the library data stay until you delete the account. The deletion is immediate.

The copy at BYOMailer stays until the collector unsubscribes through a link in those emails, or writes to the operator. Deleting the BinderLoot account does not remove that copy.

A payment record stays as long as the tax law of the country of the operator requires.

A session record expires on its own, and a sign-out removes it.

Your rights

You can exercise these rights at any time, and the operator answers within 30 days.

• Read the data: every field of your account is shown under Settings and in your library.
• Correct the data: change the name, the username, the biography and the email address under Settings.
• A change of the email address under Settings updates the account and does not update the copy at BYOMailer.
• Take the data with you: the collection, the binders and the wishlist each export as a CSV file.
• Delete the data: the Settings page deletes the account and its library.
• Object, restrict or complain: write to the operator, and, if the answer does not satisfy you, write to the data protection authority of your country.

Where the data is

The servers of the operator and the services named above are in the United States and in Europe.

A transfer out of your own country uses the safeguards that the applicable law requires, which includes the standard contractual clauses.

Children

BinderLoot is not for a person under 13 years of age.

If the operator learns that an account belongs to a child under 13, the operator deletes that account.

Security

The site is served over HTTPS. A password is stored as a one-way hash, and it is never readable.

The account supports a passkey, which is stronger than a password. Add one under Settings.

No system is perfect. If the operator learns of a breach that affects your data, the operator writes to you.

Changes to this policy

The operator can change this document. The date at the top of the page shows the last change.

A change to the data the site collects, or to the services that receive it, is announced by email before it starts.

Contact

Alejandro Medina answers every question about this document at [email protected].