FutSBC

Privacy Policy

Last updated 27 August 2026

FutSBC solves Squad Building Challenges inside the EA SPORTS FC Ultimate Team Web App, on your own device. It never sees your EA login, and it cannot submit a squad, open a pack or redeem a Player Pick without you pressing a button first. This page lists everything that leaves your device, why, and how to stop it.

1. Solving happens on your device

The solver runs in your browser or in the app. Your club is read from the page the Web App already loaded and kept in memory for the session. It is not uploaded to solve a challenge.

2. Shared game data (on by default, one switch to turn off)

To keep prices and challenge lists accurate for everyone, FutSBC forwards a narrow selection of what the Web App loaded to the shared FutSBC database:

• Transfer market search results — card prices and BIN listings
• SBC sets and challenges, with their requirements and rewards
• Evolutions and objectives catalogues
• Price fields of cards in your club — for each card definition (the card itself, e.g. “Saka 88 Rare”), EA’s listed min/max, last sale and average price, plus the card’s public attributes (rating, position, nation, league, club, play styles). This is what lets the solver price cards EA ships unpriced. It is sent at most every ten minutes, only for cards whose price changed, and it does not include the item id of your copy, whether it is tradeable, its contract, or how many you own.

Catalogue data is sent at most once a day per device, and the server keeps only the first copy it receives that day, however many people send it.

Under the same switch, FutSBC also sends a small set of product events to its own server — which feature was used (solve pressed, squad submitted, packs opened), the app version, and the text of errors raised by FutSBC’s own code. These carry no card ids, no squad contents, no coins and no EA identifiers. They are used only to see which features work and which break. FutSBC uses no third-party analytics, advertising or tracking service.

Turning it off: open the FutSBC popup (extension) or Settings (app) and switch off Share public game data. From that moment nothing in this section is sent, and every feature keeps working.

3. What is never sent

• Your EA account, its email, password, session id, cookies or any authentication token
• Your coins, your transfer history, your trade pile or watchlist contents
• The squads FutSBC builds or submits for you
• Your name, your location, or anything you typed into the Web App

Credentials are stripped twice: once on your device before a request is made, and again on the server before anything is written to disk. Any field whose name looks like a session, token, auth header or cookie is dropped without being read.

4. Device id

On first run FutSBC generates a random string — twelve bytes, no relation to you, your machine or your EA account — and sends it with shared data to rate-limit abuse and to keep one device’s contributions together. Clearing the extension’s storage (or reinstalling the app) mints a new one.

5. FutSBC account (optional)

You can use FutSBC without an account. If you create one, we store your email address, a salted password hash (never the password), the date the account was created, and your Pro status. An account is used for:

• Syncing your FutSBC settings (solve options, filters, language) between your devices.
• Syncing the request meter — timestamps of the SBC submissions and pack openings FutSBC made for you, so the hourly and daily counters shown in the app are the same on every device. No squad contents, only “an SBC was submitted at this time”.
• Unlocking Pro features you have paid for.

Password reset emails are sent only to the address on the account. You can delete the account at any time from Settings → Account → Delete account; this removes the email, hash, synced settings and meter immediately and cannot be undone.

6. Payments

Pro is sold as a subscription. On the web and in the Chrome extension it is processed by Stripe; on iOS by Apple through the App Store. FutSBC never sees or stores your card number — only the fact that a subscription is active, and until when. Stripe’s own privacy policy applies to the payment itself.

7. Server logs

Like every website, the server sees the IP address a request arrives from while handling it. It keeps no access log; connection-level error logs are capped and rotate away within days. IP addresses are never written into the contributed data, never stored alongside your device id or account, and never used to build a profile.

8. Where the data lives

On a single server in Helsinki, Finland, operated by Hetzner Online GmbH within the EU. Traffic to it is encrypted (TLS). Shared game data is kept while it remains useful for pricing history; account data is kept until you delete the account. Nothing is sold, and nothing is shared with third parties other than Stripe and Apple for payments.

9. Relationship with EA

FutSBC is an independent project. It is not affiliated with, endorsed by, or connected to Electronic Arts Inc. EA SPORTS FC and Ultimate Team are trademarks of Electronic Arts Inc. Using third-party tools with your EA account is subject to EA’s own terms; FutSBC never acts on your account without a button press from you.

10. Changes

If what the software sends ever changes, this page changes with it, and the date above moves. Material changes are also noted in the release notes shown in the extension and the app.

11. Contact

Questions, or a request to delete what a device or an account has contributed: privacy@futsbc.app. For a device without an account, include the device id shown at the bottom of the extension popup — it is the only handle that exists.