Skip to content
FUT Dealer
Last updated · 2026-10-22

Privacy Policy

This is not copied boilerplate. Every line below was written from the code that actually ships, and it changes in the same commit the code does. It is an inventory: one section per address anything is sent to, and what that address receives.

The short version

Most of what FUT Dealer does happens inside your browser. Some things do leave it, and each of them is named below with the address it goes to: your sign-in, the club you ask our server to build a squad from, one line of totals per trading day so the Logs pane reads the same on every device, the item id and price of each card the tool bought for you so the Transfer List shows its purchase price on every device (kept 90 days), your buys and near misses to the community feed (your name only if you switch it on), your matched sales for the website's trade strip, the destinations you type in yourself for alerts, a short report when EA stops a Trader run, and a request for a public price file.

Nothing is sold. Nothing is used for advertising. Nothing is used for anything other than running the tool you are paying for.

api.futdealer.com, our own server

Signing in. Your email and password, once, so we can check your subscription is active. A token comes back.

Signing in with Google. If you press Continue with Google in the tool instead, the tool sends our server a one-time challenge (a hash of a random secret that stays in the tool) and the browser label, and opens futdealer.com, where you sign in with Google and press Allow. Google tells futdealer.com your email address and your Google account id; we keep that id with your account so that only the same Google account can sign in this way. The tool then sends the secret to collect its token. The sign-in attempt, with the IP address it came from, is deleted within a day.

That token is stored in the extension's service worker and the page can never read it. That is on purpose. The page it runs on is full of scripts that are not ours, and your subscription credential has no business passing in front of them.

The browser label goes with your email and password, at sign-in only, and nowhere else. It is the browser name and version, so that the device list on your account page says "Chrome 140" instead of a row of numbers you cannot recognise.

Every call after that carries two things: the session token, and the version number of the extension you are running.

Solving a challenge. When you ask for a squad, we send the challenge's requirements and the cards in your club: each card's id, rating, nation, league, club, rarity and rarity groups, position, quality, our own price estimate, and flags saying whether it is a duplicate, untradeable, an icon, a hero, an evolution, an academy player, on loan, in your active squad, in storage, a women's card, and whether you are its first owner. We also send the settings you chose for that solve: the card ids you told us to protect or to force into the squad, whether icons, heroes, evolutions and your active squad may be used, whether position should be ignored, the rating window for a special card, how many squads you want and how many slots each has, whether the answer should be the cheapest or the lowest rated, which cards you would rather it spent first (stored, untradeable, duplicates), how long the search may run, and EA's own chemistry thresholds as we read them off the page. Your own exclusions are applied on your machine before anything is sent, so a card you protected is filtered out rather than uploaded and trusted to be left alone. If EA has changed something the tool needs, the diagnostic below rides along on this request. The squad is computed on the server and eleven ids come back.

What we keep about a solve is one row per attempt: your account id, the time, how long it took and whether it succeeded. That row is what counts the free plan's allowance for the day and what tells us the solver is healthy. Your club is not stored.

Votes, including the ones you do not cast. When SBC sets or packs are on screen, the extension asks us for the thumb counts on the ones you can see, without being told to, so it can draw them. That request carries your token, and the answer includes how you voted on each one, so it is tied to your account rather than anonymous. Casting a vote sends the set or pack and which way you voted.

Your daily trading totals. The Logs pane is a row per day: how many requests and searches that day took, how many cards were bought and sold, how many runs you started, the coin profit, the profit as estimated when each card was bought, and how many buys had no price to estimate with. Those totals are sent to us and kept on your account, for the last 90 days, so the pane reads the same on your laptop as it does on the machine you traded from. What is sent is the day and those nine numbers. Not a card, not a player, not a price, not a listing and not a trade id: the log itself never leaves your browser (the exceptions are the sales shown on futdealer.com, below, and the stop report that follows). Because two EA accounts can share one browser, each day is filed under the EA account it belongs to, and what identifies that account in our database is a one-way keyed hash of your EA persona id rather than the id itself. The id is sent so that we can compute the hash; it is not stored and it is not written to any log. Days recorded before your copy of the extension started marking them cannot be attributed to an EA account, and those are never sent. Pressing the X on a day deletes it here and on our server, on every device.

A report when EA stops a run. When EA itself stops a Trader run on a paid account (a rate limit, a captcha, a full pile, a soft ban), the tool sends one short report so we can tell you which step EA refused: a random id for that report, the time, EA's three-digit code, the step it happened on (a search, a buy, a bid, a listing, a move, a relist or an SBC submit), the pace the run was on (Act Like Human or the delay you chose), a random id for this browser, and your EA persona id, which is turned into the same one-way keyed hash as the day totals and then discarded. Not the message on screen, not a card, a player, a price or a trade. A stop you press yourself, or one of the tool's own, sends nothing. Each report is kept for 30 days and then deleted on its own, and only we can see it.

Gallery sets you marked as placed in-game. When you mark a Gallery set as placed in-game, or clear the mark, we keep on your account the set, the grade you marked (or a note that the mark was cleared, so an older device cannot bring it back), a revision number and a random id for the last change, so that a repeated request is not applied twice. That is what makes the mark show on every device you sign in on. Each mark is filed under the same one-way keyed hash of your EA persona id as the day totals, never the id itself, and the marks are deleted with the account.

A diagnostic when EA changes something. EA renames things inside its own web app and the tool goes quiet without anybody noticing. When the tool finds that a piece it needs has gone missing, or that one it can work around has stopped answering, it sends the names of those pieces, the EA year and our version number, and two things that arrived with FC27: EA's own build number, as it appears in the address of their script files on the page, and the list of internal names the tool could not find on that build together with what happened to each one. Both were added because EA now scrambles the code names inside its app and those names change with every build, so without the build number two different faults arrive looking like one. A copy that finds nothing wrong sends this never. A copy that has found something reports it on up to three separate page loads and then stops, because one report can be lost on the way and three different moments are what covers an outage at our end. It rides on a request you were already making, and that request carries your token, so we know which account it reached us from and use that only to stop one account flooding the table. What is stored is one shared row per distinct set of names, with no column for an account, an email or a device.

We never send your in-game name, your EA session or your coin balance. Your EA persona id goes only with the day totals, the Gallery marks and the stop reports above, the SBC submit counts and, from the phone app, the request for that EA account's Stats. Each time it is turned into a keyed hash and discarded. The phone app keeps the last persona id it saw on your phone, so Stats can show that account before EA is opened again.

The community feed, and whose name is on it

FUT Dealer has a public feed on our Discord where subscribers' buys and near misses are posted. Every buy and near miss is posted there, without a name. The switch in Notification Settings decides only whether your name goes with it, and the first time you turn it on you are shown a notice saying so.

What is posted: whether it was a buy or a miss, the card and the player's name, its rating, what you paid, what it is worth, whether that value came from the live market or from the price file, whether you are on console or PC, and the version of the extension you are running. The profit is worked out from those. With the switch on, your name appears on the post: the display name Discord gives us if you linked Discord to your account, and otherwise the username you chose when you signed up. With neither, the post goes without a name. Your email address is never used here. With the switch off, the post says only that it was a subscriber. Nothing else about your account is posted. If you press Share on a filter while signed in, it is posted to #snipe-filters with that same name over it, whatever the switch says, and the name is who pressed Share, not who built the filter.

Your sales on futdealer.com

The home page of futdealer.com shows a strip of recent sold trades. When you are signed in and Books matches a sale on your transfer list to a card the tool bought, we receive the player's name, the card's id and rating, what the tool paid, what it sold for and EA's trade id. We compute the profit ourselves. It is filed under your account so that we can cap it and delete it; the website shows only the player, the rating and the profit, never your name, your account or when it sold. Rows are deleted after 30 days, and we delete yours sooner if you ask.

The Leaderboard in the app. It shows every FUT Dealer app user the ten accounts with the highest profit, whether or not they turned anything on. Each appears under the name and crest of your EA Ultimate Team club, as the web app shows them in its top bar, which the tool sends with your daily Logs totals; until it has, under an alias our server makes (such as Swift Falcon 42) and a generic badge. Never your name or your email. With one number: the profit in your Logs, estimated when each card was bought, over every day you have kept. It is a number your tool reported, not one we checked with EA. If you do not want to appear, contact support and we hide your account from it; we may also hide an account, or a club name, after reviewing it.

futdealer.com, this website

Saving a filter uploads it. Not sharing it, saving it. Every time you press Save on a filter, the extension sends that filter and the trading settings saved with it here and gets a short code back, so the code is ready if you ever want to pass it on. It is stored under that code, and anybody who has the code can read it. Nothing about your account goes with it: there is no token on that request and the code is not linked to you.

Sharing it is a second, separate thing. Pressing Share on a saved filter posts its code, with a short summary of what the filter hunts, into the public #snipe-filters channel on our Discord. That one happens only when you press it, and only once per code.

A filter is what you told the tool to hunt: the player or the card type, the prices, and the trading settings you saved beside it. It is not your club, your ledger or your account.

Payment happens on this website and never in the extension. We keep your email, your order number and your payment method for invoicing and support. Your card details never pass through us.

Linking Discord, if you press it. The account page can link your Discord account, and any account can do it, free ones included. What we store is your Discord user id and the username Discord gives us, on your account. We ask Discord for the identify scope and, so we can add you to our server, guilds.join. Not your email, not your other servers, not your connections.

What the link does. While your subscription is active you hold the Subscriber role in our Discord server, and the username is what appears over your own posts if you turned the community feed on. When the subscription ends, is refunded, or you unlink, the role comes off on its own, within a few minutes rather than instantly: our server checks the two against each other every five minutes. Unlinking removes the id and the username from your account; past orders keep the record of the link they already had.

discord.com and api.telegram.org, only if you set them up, and only if you allow them

If you paste your own Discord webhook or your own Telegram bot token and chat id, the extension sends the run events you asked for to the destination you chose: a buy, a miss, a stop, a captcha warning. We do not choose those destinations and we do not receive a copy.

If you set none of them up, the extension sends nothing to either service. This is separate from the community feed above, which is ours and has its own switch.

Since 0.9.7.82 these two are OPTIONAL permissions in Chrome rather than part of the install. The extension is not allowed to reach either address until you press Allow on its options page, and it only asks when you have actually entered a webhook or a bot token. You can take the permission back at any time from Chrome's own extension settings, and everything else goes on working.

Chrome grants access per site rather than per address, so the permission you give covers discord.com. What limits it to your own webhook is the extension itself: it refuses to store any Discord address that is not a /api/webhooks/ one, and it only ever posts to the address you saved.

The price hosts

prices-001.pale.tools, prices-002.pale.tools and prices-003.pale.tools. The extension asks one of these for a public price file covering every player, a few times a session. It is a plain request for a file anyone can download, and the only things the address says are the game year and whether you are on console or PC. No card you are looking at and nothing about your account goes with it.

www.futbin.org. When a price is still unknown after that, the extension searches this public price site by the player's name, with the game year. The name of the footballer is the whole request. Nothing about you or your club is attached.

Every one of them sees your connection

A request cannot be made without one. Each of the addresses above, ours and the two price sites, receives the ordinary metadata of the connection itself: your IP address, the time, and what your browser says it is. We do not control what a third party does with that, which is why the list of addresses is as short as the tool can make it.

Everything travels over HTTPS. Nothing is sent over a plain connection.

What stays on your machine

Your trading ledger, row by row. Every search, buy, listing and price the tool has seen is stored in IndexedDB in your browser, and each of those rows stays there, except the sales shown on futdealer.com, described above. We have no way to reach them. What does leave is the day totals described above, which are counts and a coin figure and name nothing you traded. The community feed above posts a line about a buy as it happens; it does not send the ledger.

Your EA account. The extension never reads, stores or sends your EA login token. The one thing about your EA account that we receive is the persona id, with the day totals, the Gallery marks, the stop reports, the SBC submit counts and the phone app's Stats request, and we keep only a one-way keyed hash of it.

Your daily search count. The free plan allows 100 transfer-market searches a day, and the counter that enforces it is kept in your own browser and is never sent to us. It is counted there rather than on our server so that no search has to wait for a request of ours: pressing Start asks our server once for a licence permit, and the tool renews that permit while a run is going, but nothing is sent per search. It is tied to the installation, not to your email, so signing out does not reset it. The number of searches shown in the Logs pane is a different thing and does travel, as one of the nine day totals above.

Crash details. When something in the tool throws an error, the message, where it happened and which browser you are on are written to your own browser's storage so you can look at them. They stay there. They reach us only if you press Export and send us the file yourself.

There is no behavioural tracking, no advertising cookie and no third-party analytics script in the extension.

Limited use

Our use of the data described above is limited to providing and improving the features you are using. We do not sell it, we do not transfer it to anybody except as needed to run those features, we do not use it for advertising or to build a profile of you, and we do not use it to determine creditworthiness or for lending. No human at FUT Dealer reads your data except where you have asked us for support, where the law requires it, or to investigate abuse or a security problem.

How long it is kept, and how to have it deleted

Solve rows (account id, time, duration, success) are kept while your account exists: they are what the daily allowance is counted from and how we can tell whether the solver is working.

Your account record (email, subscription dates, order history, the devices signed in) is kept while the account exists, and invoicing records for as long as the law requires them.

Your day totals (the day, the nine numbers, the keyed hash of the EA persona and a random id for the browser they came from) are kept for 90 days and then deleted on their own. Pressing the X on a day deletes it at once, everywhere. They all go when the account goes.

Your ledger rows and your crash details are erased when you clear site data in your browser, and we cannot erase those for you because we cannot reach them. The day totals on our server are the exception and we can delete those, either by the X in the pane or by asking us.

Write to us from the support page from the email address on the account and we will delete the account and everything tied to it.

Permissions

The extension requests one permission, `storage`, so it can remember your settings, and access to the addresses named above and to EA's own web app page, which is where it runs. It does not request access to all sites, to your tabs, or to your browsing history.

Download the app