Privacy
This page says what Fanxy records about you, why, and what you can do about it.
1. What we record
When you create an account and play, Fanxy records:
- Username and team names. You choose them. Other members see them; “Who can see it” below says where.
- Email address and phone number. What you sign in with: an account has one of the two, or both, and you can change them in Profile. They are used to sign you in, to check that an account is yours when you ask for help, and — for your email address — to send you the emails listed under “Emails we send”. Other members do not see them.
- Password. Stored only as an argon2id hash. Nobody, including staff, can read it.
- Device identifier. A random value kept in a cookie on your device. The game’s database stores only a hash of it: with each sign-in session, in the list of devices your account has used (with the first time, the last time and the number of times the account was seen on each device), and with bets you place.
- IP address. The game’s database stores it only as a hash: with each sign-in session, in the list of devices your account has used, with bets you place, and in the audit log entries described below.
- Browser user agent. The description of browser and system that your browser sends. It is stored with each sign-in session and in the audit log entries described below.
- Play history. Your squads and the changes you make to them, the challenges you send and receive, your matches and results, the bets you open or place, every change to your points, check-ins, missions, achievements, the friends you invited, tournament entries and rankings.
- Settings and visit marks. Your language and colour theme, the time you last signed in, and the time you last marked the “Since your last visit” card on Home as read.
- Acceptance of the terms. The time you accepted the Terms of use, and which version.
- Two-step sign-in key. Only for staff accounts that turn two-step sign-in on.
- Fair-play flags. When the automated checks flag an account, the flag, the evidence it rests on and what staff decided about it are recorded.
- Audit log entries. The audit log records every action staff take from the list in the Terms of use, and these actions you take on your own account: changing your password, setting a new password with a reset link, changing or removing your sign-in email or phone, signing out other devices, and closing your account; for a staff account, also turning on two-step sign-in. It also records the end of a suspension that has run out, and each password reset email the site sends for the account, with the IP hash and the browser user agent of the request that asked for it. An entry about a changed email or phone holds the old and the new value in masked form: a phone number cut down to its country code and last three digits, an email address cut down to its first character and its domain (a short address is hidden completely). The entries for changing your password, setting a new password with a reset link, changing your sign-in email or phone, signing out other devices and closing your account also hold the IP hash and the browser user agent of your request. An entry for a staff action can hold the IP hash and the browser user agent of the staff member’s request. Entries in the audit log cannot be edited or deleted.
Fanxy does not ask for your real name, date of birth, address, identity documents or payment details.
The web server in front of the site may also keep ordinary access logs: IP address, time, and the address that was requested.
2. Why we record it
- To run your account and the game: sign-in, squads, matches, bets, rewards and rankings.
- To keep the game fair: limiting how many accounts one device or network can create, applying the same-device rule, and spotting accounts that work together to move points. The device and IP hashes and your play history are used for this.
- To protect accounts: limiting repeated sign-in attempts, and signing out other devices when a password or a sign-in email or phone is changed.
- To sort out problems and complaints, including checking what staff did and why.
We do not use this information for advertising. The site has no advertising, no analytics and no tracking by other companies. We do not sell your information, and we do not give it to other companies for advertising or for their own use.
3. Who can see it
Other members can see the following about you:
- On leaderboards, including tournament boards and the board on Home: your username, team name, rank, score, and your wins, draws and defeats; on a board that has closed, also the prize you were paid.
- In the list of opponents on Challenges: your username, Elo, the number of your matches that counted for ranking, and the name and value of the squad you would play with. Members who were active most recently are listed first.
- In a challenge or a match with you: your username, Elo, team name and the stake, and after the match both line-ups, each player’s points and the result.
- On bets: every member can open the list of bets and the page of any bet. A bet shows the username of the member who opened it, its escrow and the total staked on each outcome. A bet also has a name, which is fixed when the bet is opened: the form that opens a bet fills in the names of the two teams of the match at that moment. Through a bet, every member can also see the team names and usernames of the two players of the match and, once the bet has been settled, the result of that match. So when there is a bet on a match of yours, members you never played can read its result. From the moment a challenge is accepted until kick-off, the match can also appear, with its two team names, on the page where members choose a match to open a bet on.
- When your account is suspended, banned or closed, it is not listed among opponents. While it is suspended, a member who tries to accept a challenge you sent is told that your account cannot play.
Other members do not see the individual bets you place, your points balance, your email address or your phone number.
Staff can see your account details and history, including the hashes, flags and audit log entries listed above, in order to run the game and deal with problems. The changes they make are recorded in the audit log; looking at an account is not recorded.
Your password cannot be seen by anyone.
4. Images from another server
Player photos and club badges are loaded by your browser directly from the Premier League’s public image server (resources.premierleague.com). Like any web server, it receives your IP address and browser details when your browser asks for an image.
We send that server nothing about your account. The site tells your browser to pass on only the name of this site, not the page you are on.
5. Emails we send
Fanxy sends email in two cases only: when someone asks for a password reset link for your email address on the Forgot password page, and when your password has just been changed. There are no marketing emails or newsletters.
Emails are sent through Elastic Email, an email delivery service. To deliver them, it receives your email address, your username and the content of the email, including any password reset link. We do not send it anything else about your account.
7. How long we keep it
Your account and play history are kept for as long as your account exists, also after it has been closed. The site does not delete them on a schedule.
A sign-in session stops working in each of the cases below. Its record is kept so that sign-ins can be reviewed if something goes wrong.
- 30 days after you signed in.
- You sign out, or sign in again in the same browser.
- You sign out a device, or all your other devices, under Signed-in devices in Profile.
- The password is changed or reset. After a change, the device you used gets a new session and stays signed in; after a reset with a link, every device is signed out.
- The sign-in email or phone is changed or removed. When you do it, every other device is signed out; when staff do it, every device.
- The role of the account is changed.
- Staff suspend or ban the account. A suspended account can sign in again; a banned account cannot.
- The account is closed, by you or by staff at your request.
Records of matches, bets and point changes involve other members too, so they are kept even after an account is closed. The audit log is kept as well: its entries cannot be edited or deleted.
8. Closing your account and removing your data
You can close your account yourself in Profile, once nothing of yours is still in play: no bet you opened or staked on that is not settled yet, no accepted match that is still to be played, and no tournament you are entered in that has not finished. The page lists whatever is still in the way. Some of it you can clear yourself: withdraw a bet that is still open and that nobody has staked on, or leave a tournament that has not started. A suspended account cannot close itself until the suspension ends, and a staff account must have its staff role removed first.
Closing an account does not erase anything. The account is signed out everywhere and can no longer sign in. Challenges still waiting for an answer, both the ones it received and the ones it sent, are closed, and every stake is returned in full to the member who sent the challenge. Its points stay with it, and its email address, phone number and username cannot be used for a new account. It is left out of the leaderboards and of the prizes paid when a weekly or monthly board closes; an account that staff close while it is entered in a tournament is also left out of that tournament’s ranking and prizes. On a board that became final before then, its row stays where it finished, keeps the prize it was paid, and is shown as a closed account, without the name.
This site has not published a support contact yet. When it does, requests to reopen an account or to remove its data go to that contact.
Personal data is removed by a senior administrator, and only for an account that is closed and has nothing in play. Removal cannot be undone, and the account can never be reopened afterwards.
What is removed
- The email address, the phone number, the password hash and, if there is one, the two-step sign-in key.
- The username: on the account and on every leaderboard, including the boards of closed periods, it is replaced by a neutral name made up by the system. The account’s referral code, which carries part of the name, is replaced too.
- Team names: on each team the name is replaced by a neutral one; on leaderboards the team name is removed.
- The sign-in sessions, with the device hashes, IP hashes and browser user agents stored in them; any password reset link; and the IP hashes in the list of devices the account has used.
What is kept, and why
- The records of matches, bets, stakes and point changes, because other members’ records depend on them, and the rest of the account’s play history: squads (under their neutral names), check-ins, missions, achievements, invitations, tournament entries and rankings. Also the fair-play flags recorded about the account, and a few account details that do not say who you are: its language, the time of its last sign-in and its acceptance of the terms. Each bet you placed keeps the device hash and IP hash stored with it. Wherever a username is shown, the neutral name is shown in place of the old one.
- The old team names in two places that removal does not rewrite. First, the names of bets that were opened on your matches: the name of a bet is written once, when the bet is opened (the form fills in the two team names of that moment), and the pages of those bets still show it. The name of a bet you opened yourself is not rewritten either. Second, the copy of the team name inside the frozen line-ups of matches you have played: the database does not allow this copy to be edited, so that a line-up cannot be changed after people have staked on a match. The copy stays stored, but no page shows it any more.
- The list of devices the account has used, because it enforces the limit on how many accounts one device can create. From then on it holds no IP hashes: only the device hashes, with the first time, the last time and the number of times the account was seen on each device.
- Audit log entries, because the log cannot be edited or deleted. They can hold a username or a team name the account had when staff changed it, the name of a bet that staff voided, messages and reasons that staff typed (for example when they suspended or banned the account, or adjusted its points), the masked form of a sign-in email or phone that was changed, and the IP hash and browser user agent described under “What we record”.
9. Changes to this notice
When this notice changes, the date at the top of this page changes with it.