Privacy Policy

1. Overview

This Privacy Policy explains how Foxsy AI (“Foxsy AI”, “we”, “us”, “our”) collects, uses and shares information when you access the FoxLeague websites, apps and on-chain Services. We are committed to protecting your privacy and complying with applicable data protection laws, including the EU General Data Protection Regulation (GDPR).

FoxLeague needs no account beyond your wallet: you sign in by signing a message with your MultiversX wallet. We do not ask for your name, email address, phone number or postal address. If you choose to sign in with Google, where FoxLeague offers it, Para creates that wallet for you (see section 3) and your email address goes to Google and Para, not to us.

2. Data Controller & Contact

Foxsy AI, a Wyoming corporation
30 N Gould St Ste R
Sheridan, WY 82801, USA
Email: contact@foxsy.ai

Depending on your location, local entities or partners may act as processors on our behalf.

3. What We Collect

Wallet & on-chain data: your public wallet address; the network you are connected to; your $FOXSY and EGLD balances where a check needs them (for example the registration fee check or the onboarding EGLD bonus, which goes only to wallets that hold almost no EGLD); the player NFTs held by your wallet; the transaction hashes of the actions you take on FoxLeague smart contracts (registration, shop payments, training slots, sync, marketplace auctions, fusion, tournament entries, prizes and refunds).

Sign-in data: when you sign in, the server creates a session tied to your wallet address that expires after 24 hours. Your browser keeps the session token in session storage until you close the tab or log out. We record when your wallet was last active.

Sign-in with Google (optional): where FoxLeague offers it, you may sign in with your Google account instead of a wallet app. Google confirms your account to Para (Capsule Labs, Inc., doing business as Para), which creates an embedded MultiversX wallet for you. The wallet’s key is split into parts. One stays in your browser, protected by a passkey you create with Para. Para holds another. Our servers receive only the wallet address, as with any other wallet. Your email address stays with Google and Para: the app shows it only in your browser, to name the account you are signed in with.

Team & game data: team name, optional coach name, team badge, formation and lineup choices, training sessions, match results (scores, per-player ratings and match events), match replays, tournament entries and standings, ELO rating and league, marketplace listings, bids and sales, fusion history, shop purchases and refunds, records of onboarding EGLD bonuses, notifications and your notification settings.

Team badge: the badge is generated by sending your team name to a third-party AI image model, currently Google Gemini. The image is stored on IPFS through our own node. Content on IPFS is public and content-addressed: anyone with the address can retrieve it. We cannot guarantee its removal from every IPFS node.

Web push (optional): if you turn on push notifications, your browser gives us a push subscription (an endpoint address and encryption keys) that we store to send you notifications. Turning them off removes it.

Telegram account (optional): if you connect it in Settings, we keep your Telegram user id and username with your account to send you messages about FoxLeague, including announcements and benefits for your team. It is not shown to other players. You can disconnect it at any time.

Technical data & logs: our web servers log the IP address, time, requested page and browser type of each request. The backend uses the IP address of a request for rate limiting. Failed sign-ins are limited to 10 per minute per IP address and per wallet; past that limit the address or the wallet is refused for 5 minutes, while a valid signature always signs you in. The records we keep of failed sign-ins and of the sign-in that creates your account hold a fingerprint of the IP address instead of the address itself: a 12-character keyed hash (HMAC-SHA256) under a secret only our server holds. It shows us that several attempts came from the same source. We also use it to alert our administrators when several paid team registrations in one day come from accounts created from the same source. For the limit and the fingerprint an IPv6 address counts as its /64 network. When the app hits an error it sends a report with the error, the app version and your wallet address if you are signed in. When you file a bug report, the app takes a screenshot of the page you were on as the report opens and sends it with your report, unless you remove it before sending; only FoxLeague’s administrators can see it.

KYC / AML data (when required): identity documents, proof of address and liveness checks collected by regulated providers; we receive pass/fail signals and limited metadata.

Communications: messages sent to support or posted in official channels (Telegram).

4. Why We Process Data (Legal Bases)

Provide and operate the Services: sign-in (with a wallet app or, where offered, with Google through Para), teams, matches, tournaments, the shop, the marketplace, payouts and refunds (contract performance).
Verify eligibility, prevent fraud, abuse and multi-accounting, ensure fair play and platform security (legitimate interests; legal obligations).
Comply with AML / CFT, sanctions screening and other legal requirements (legal obligations).
Send service notices and, where you opted in, push notifications (legitimate interests / consent).

5. Cookies, Browser Storage & Fonts

The app keeps your sign-in session in session storage and preferences such as theme, sound and settings in local storage, in your browser. We use no advertising cookies and no third-party analytics or tracking scripts of our own. If we later adopt analytics or marketing cookies, we will present a consent banner with granular controls. If you sign in with Google, Para’s code runs in the app: it keeps its sign-in session (currently up to one week) and your device’s part of the wallet key in your browser’s local storage. It may also collect technical diagnostics under Para’s own policy. Logging out of FoxLeague deletes Para’s session and key part from your browser. The app loads its fonts from Google Fonts, so your browser sends your IP address to Google when it fetches them.

We do not sell personal data. We share it only as follows:

The MultiversX network (gateway and API): your transactions and balance queries go through them.
Wallet providers you choose to use (xPortal, MetaMask snap, MultiversX Wallet Extension, MultiversX Web Wallet, Ledger): they process your connection and signatures under their own terms.
Para (Capsule Labs, Inc., doing business as Para) and Google, only if you choose to sign in with Google where FoxLeague offers it: Google confirms your account to Para; Para runs the embedded wallet and co-signs each transaction and message you confirm, so it sees what you sign. Para processes your data under its own Privacy Policy and Terms of Service.
Google: the Gemini API receives your team name to generate the badge; Google Fonts sees your IP address when your browser fetches the app’s fonts.
IPFS: the badge image is published there.
The Autonomys Network (through its Auto Drive service): the permanent public records of tournament matches and the full replay files of recorded matches are written there once their broadcast has ended (see section 12).
Telegram: when match announcements are switched on, the tournament or 1v1 challenge name, the team names, the score and a link to watch the match are posted to the public FoxLeague Telegram group; also your messages when you contact us there. If you connect your Telegram account in Settings, our messages to you go through Telegram.
Anyone who asks the public API: the game data the app shows every visitor (wallet addresses, team and coach names, badges, player cards, ratings, results, standings, marketplace listings and sales) is also answered by the public FoxLeague API and by the read-only FoxLeague MCP server to any client, AI assistants included.
Browser push services (run by your browser vendor): deliver push notifications if you opted in.
Exchanges where $FOXSY is traded: only if you choose to use them; they collect their own data, including their identity checks, under their own terms.
Ramp Network, only if you choose Buy EGLD with card or bank where FoxLeague offers it: the app opens Ramp’s purchase window with your wallet address filled in, so the EGLD goes to your wallet. You deal with Ramp directly: Ramp takes your payment and runs its identity checks under its own Privacy Policy and Terms of Service. Our servers receive no payment or identity data from Ramp.
Hosting and infrastructure providers that run our servers, under contracts and DPAs.
Compliance & safety: regulators, law enforcement or competent authorities when legally required.
Corporate events: in a merger, acquisition or asset transfer, your information may be transferred subject to standard confidentiality safeguards.

7. International Data Transfers

We operate globally. Where data moves outside your country, we use appropriate safeguards such as Standard Contractual Clauses (SCCs) or equivalent mechanisms. If you sign in with Google, Para states in its Privacy Policy that it may process and store data anywhere in the world, including the United States. It names the EU Standard Contractual Clauses as one safeguard for transfers from the EEA, Switzerland and the UK. The permanent match records (section 12) are stored on the Autonomys Network, a decentralized network whose storage nodes can be in any country.

8. Data Retention

We keep personal data only as long as necessary for the purposes described, including tournament records, dispute resolution, security and legal compliance. Retention periods vary by category and legal requirement. In particular:

Sign-in sessions expire after 24 hours. Expired sessions are deleted by a cleanup that runs with the traffic (by default every 100 signed-in requests) and by a daily sweep.
Replay recordings of every match (casual, ranked, tournament and 1v1) are kept for as long as the game runs, so every replay stays available. A copy is kept by our hosting provider. The results and statistics of every match are kept.
Application event logs are deleted after 30 days; routine refusal notices at the lowest level (for example a match start the rules refused) after 14 days. Error and warning records, including the app’s error reports, are deleted after 90 days once resolved; an unresolved one is kept until it is resolved.
A bug report’s screenshot is deleted 90 days after it was sent. A report deleted before then takes its screenshot with it.
If you signed in with Google, Para keeps your Para account and wallet under its own policy. Your browser keeps Para’s session until it expires or you log out of FoxLeague, which deletes it.
Data written to the blockchain is permanent by the nature of the blockchain (see section 12).
Permanent match records and replay files on the Autonomys Network are never deleted: once written, a record or a replay file cannot be corrected or deleted by Foxsy AI or by anyone else (see section 12).

9. Your Rights (EEA / UK and similar regimes)

You may have rights of access, rectification, erasure, restriction and portability (subject to limits). You may object to processing based on legitimate interests and withdraw consent where processing relies on consent. You may lodge a complaint with your data protection authority. Data written to the blockchain cannot be changed or erased by us. A permanent match record on the Autonomys Network (section 12) cannot be changed or erased by us either: a team name or a title in it stays as it was written.

To exercise rights, email contact@foxsy.ai. We may request additional information to verify your identity, for example a message signed with your wallet.

10. Children

FoxLeague is not directed to children under 18. Team creation asks you to confirm you are 18 or older. We do not knowingly collect personal data from minors. If you believe a minor has provided data, contact us to delete it. A permanent match record or replay file (section 12) cannot be deleted.

11. Security

We use administrative, technical and organisational measures appropriate to the risk, including encryption in transit, access controls and logging. Signing in with your wallet never gives us your private keys. If you sign in with Google, the wallet’s key is split between your browser and Para. We never hold any part of it. No system is 100% secure.

12. Web3 Transparency

FoxLeague runs on the MultiversX mainnet. Transactions on the MultiversX network are public and immutable. Your wallet address, NFT holdings, $FOXSY balance, marketplace auctions, tournament entries, shop, training and sync payments, fusion events and the prizes and refunds paid to your wallet are written to the ledger and visible on any blockchain explorer (for example explorer.multiversx.com). Do not use a wallet you consider private for public on-chain activity. If you sign in with Google, Para co-signs your transactions, so it also sees the content of every transaction and message you confirm.

Permanent match records. Once the broadcast of a tournament match has ended, Foxsy AI writes a public record of the match to the Autonomys Network, a public decentralized storage network, through its Auto Drive service. Anyone can read a record without an account. The match page links to it. A record is permanent: once written, it cannot be corrected or deleted by Foxsy AI or by anyone else. The FoxLeague manual shows a record field by field: Permanent Match Records.

A record holds:

the tournament’s id and its title as its organizer wrote it (when the creator of a 1v1 challenge leaves its title empty, the app fills in team names)
the tournament’s format and tier, the round, the group and the leg
the match’s public id, the kickoff and the end of the broadcast
the name of each team as the match page shows it when the record is made
the score and how the match was decided (in regular time, in extra time or on penalties, with the shoot-out’s score)
links to the match page and to the replay download, the size of the replay file and its SHA-256 fingerprint
the record’s format version, the network and the time the record was made

Full replay files. For recorded matches, Foxsy AI may also write the match’s full replay file to the Autonomys Network, after its record. It is byte for byte the file the match page offers for download: the match as the match engine recorded it, with the two team names, the match engine’s settings (each player’s type included), every position and action of the players and the ball, the referee’s decisions and the score. Its size and SHA-256 fingerprint are the ones its record published, so anyone can check it. Like a record, a replay file is permanent and public. The match page links to it.

Neither a record nor a replay file holds a wallet address, a coach name, an email address, a Telegram user id or username or an IP address. A record’s tournament id leads to the tournament’s public FoxLeague page, where each team’s wallet address is public (section 6).

Every tournament format is recorded, 1v1 challenges included. Private (invite-only) tournaments are recorded too: only the invited teams can join one, but its results are public. Ranked games, casual games, developer tournaments and developer challenges get no record and no replay file, nor does a match decided without being played.

A team name or a title stays in a record or a replay file as it was written, even after the team is renamed. If you do not want a name in a permanent public record, do not use it as a team name or in a tournament title.

13. Changes to this Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by the “Last updated” date and, where appropriate, additional notice.

14. Contact