Your game. Your data.
Privacy Policy · Effective October 8, 2026
We save your career so you can keep playing. This version has no advertising or optional usage analytics. Your nickname and best season can appear on the leaderboard. You can delete your career in Profile → Settings.
Who runs the game
INVINCIBLES is operated by Islam Nur in Kazakhstan. For privacy questions, access requests, corrections or concerns, email invincibles.game@proton.me. Do not send your session cookie or recovery file by email.
What we use and why
- Career information: a random career identifier, your chosen nickname, drafts, lineups, season results, records and timestamps. We use these to provide the game, preserve career progress and display results.
- Classic rooms and earlier duels: invitation code hashes, participant career identifiers, host presence deadlines, draft choices, spin progress, reroll counts, locked lineups, 38-match season reports, rankings and action references. Rooms connect two to four players. We keep other participants’ choices hidden until every squad is locked, and save one consistent comparison. Earlier two-player duels also retain rematch requests and linked rematches.
- Build a Legend rooms: the same career-based room access, code hashes, participants, presence deadlines and retry references, together with draw state, skill choices, remaining rerolls, finished builds, Overall scores, rankings and rematch series. Choices stay hidden from other members until everyone finishes. These rooms do not add entries to the public leaderboard.
- Access information: a random session credential and, if you create one, a recovery credential. The server stores hashes of these credentials. They let us recognize the owner of a career without requiring an email address or password.
- Connection information: servers receive your IP address to deliver requests and limit abuse. The application keeps IP addresses and request counters in server memory for security rate limits. Each counter uses a 60-second window, but its IP entry can remain until the server process restarts or expired entries are removed when the counter map grows beyond 5,000 entries. Hosting and security systems may also retain connection and error information to operate and protect the service.
- Player safety: reports contain the reporting career identifier, the reported career identifier and current nickname, the selected reason, request reference, timestamps and review status. Block preferences and nickname restrictions are stored separately from game results. We use this information to review reports, limit abuse and apply your choices.
- Support messages: if you contact us, we receive your email address and the information you choose to send. We use it to respond and resolve your request.
We do not sell personal information or share it for cross-context behavioral advertising. We do not use advertising identifiers, advertising pixels or third-party analytics SDKs in this version.
To keep game actions consistent and handle retries, the server saves your draft progress, remaining rerolls, selected players and prior action responses against your career. These records support the game and safe retries; they are not optional usage analytics.
Cookies and storage
Playing or opening your career uses an essential, first-party inv_session cookie to keep access for up to 180 days. Browsing this policy, Help or the landing page does not create a new career. Existing cookies from an earlier visit may still be sent by your browser.
Your browser stores sound preferences and a nickname cache. Its unfinished solo draft reference lasts only for the current page; refreshing or reopening starts a fresh attempt without removing your career or records. The iPhone app starts a fresh attempt after returning home or relaunching. A brief background pause can preserve the current attempt while the app remains running. Retry references help safely finish interrupted recovery or deletion requests. A pending deletion reference stays on this device until deletion is confirmed, you explicitly choose to start a new career after an expired confirmation, or you clear that browser storage; the server confirmation expires after ten minutes. Recovery keys are not saved in browser local storage. In the iPhone app, the career credential is held in the device Keychain.
Classic room choices are saved against your career while the room remains available. To display a host’s code again, the code and its issuance reference are kept in temporary tab sessionStorage. This lasts for the browsing session. Codes expire after 15 minutes or when replaced; an expired local entry does not grant access. Anyone with a valid code can join a lobby until it starts or fills its four places. Keep the code private. It does not grant access to your career. The server stores the code as a hash.
Build a Legend rooms use this same cookie, career access and temporary code storage. Its standalone solo preview keeps the current build in page memory without creating a career; refreshing clears that build. Opening Play with a friend connects to the career-based room service.
Removing the app or clearing browser storage does not delete your server career. Clearing saved access can prevent you from returning. Save a working recovery file first, or use Delete Career in Settings if you want the career removed.
We use storage for game functionality rather than offering an “accept all” choice for advertising. We do not perform cross-site advertising tracking regardless of a browser's Do Not Track signal. We will explain any future optional tracking and provide the choices required before enabling it.
What other people can see
Your nickname, best squad, record and season count can appear on the public leaderboard. A shared result link displays that season and squad. Choose a nickname that does not identify you if you prefer. Other people may keep copies of a result you share; deleting your career cannot remove their screenshots or posts.
In a Classic room, participants receive the other members’ career identifiers, nicknames, host status, pick counts and squad-ready status. Everyone’s lineups, 38-match reports and rankings become visible when all squads are locked. Rooms are not added to the public leaderboard. The host starts the draft with two to four players. Host presence is checked to close abandoned rooms; leaving explicitly closes an unfinished room immediately, while an unreported disconnection closes it when the 90-second host-presence deadline expires. A guest can leave a lobby without closing it; a departure after the draft starts ends that shared game.
Earlier two-player duels retain their original rules: both lineups and paired season reports are shown after both squads lock. A linked rematch requires both players’ agreement. Its pending consent expires within 24 hours or when the original duel expires, whichever comes first. The operator can access stored room and duel data to run and support the service.
Shared draft
Shared draft is a separate, temporary two-player mode. Its server keeps a room code, participant nicknames, session credential hashes, temporary retry references, connection information, picks, rerolls and simulated season results in memory. On the website and in iPhone versions with a Shared draft nickname field, your chosen nickname is visible to your opponent. Those app versions remember the nickname from your last successful room entry on this device so you can reuse or change it. Older iPhone versions use generic Coach 1 and Coach 2 labels and replace a browser participant’s name with a generic label. Shared draft does not receive your career identifier or career credential. Changing its nickname does not rename your main career. iPhone version 1.2.1 checks Shared draft nicknames on the device and replaces opponent names it detects as prohibited with a generic label. Older apps and browser clients may apply different checks.
Players with the private code can join until both places are occupied. Picks are visible to both participants during the draft. The app and Shared draft browser page keep their separate room credential and retry reference in memory, without saving them to your career or browser storage. Leave or Back requests that the room close. If joining was interrupted, the app makes one bounded recovery attempt to close the reserved place before clearing its temporary access. Either player being offline for 90 seconds or the room reaching two hours also ends access. Closed rooms become eligible for removal after 30 seconds and are removed on subsequent server activity, or when that service restarts; this is not a strict wall-clock deletion guarantee. Shared draft rooms are not included in career backups or the leaderboard.
Career deletion and career-based blocking apply to Classic rooms, Build a Legend rooms and earlier duels. Shared draft has no linked career: leave the shared room to end access, and share a fresh code only with the friend you intend to play with. Contact support about concerns without sending your room credential.
Build a Legend rooms
Room members receive the same participant identifiers, nicknames, host status and progress information as in Classic rooms. All skill choices and finished builds become visible together after everyone finishes. The host starts with two to four players; the same leaving, 90-second host-presence deadline, blocking and career-deletion rules apply. The operator can access the stored room data to run and support the service.
Providers and external links
Our hosting provider processes game data to run the service. Our email provider processes support messages. We may disclose information when required by law or reasonably necessary to address fraud, security incidents or protect users' rights. No advertising partner receives career data from this version.
Opening a statistics source or choosing a social sharing service takes you to another provider with its own privacy practices. We do not load those services' tracking scripts inside the game. The operator and infrastructure may process data outside your country, including Kazakhstan; legal protections can differ between countries.
Squad cards are created on your device. Save Image asks permission to add the card to Photos; the app does not read your photo library. Post to X opens a draft containing text and a public result link. More passes the card, text and link to the sharing option you choose. You decide whether to publish.
How long information stays
| Information | Current retention |
|---|---|
| Career and season summaries | Kept while the career exists, until you delete it. Detailed reports are limited to the latest 20 seasons. |
| Drafts and temporary season replays | Server copies expire seven days after a draft starts and are cleaned during normal server operations. Returning home, refreshing the website or restarting the app discards the local attempt and does not immediately delete its server copy. |
| Classic rooms and earlier duels | New unfinished rooms close when the host leaves or its 90-second presence deadline expires. Cancelled room information is retained until 24 hours after creation. Completed comparisons expire seven days after the result. Earlier unfinished or cancelled duels expire 24 hours after creation. Expired records are removed during normal server operations. Deleting any participant’s career removes the shared room or duel and applies the backup protections below. |
| Build a Legend rooms | The same retention and deletion rules as Classic rooms: unfinished or cancelled records expire 24 hours after creation, completed results after seven days. Expired records are removed during normal server operations. Career deletion removes shared rooms and applies the same backup protections. |
| Session | Access expires after 180 days; records are cleaned after expiry. |
| Recovery file | A prepared file must be activated within ten minutes. An activated key works for up to one year, unless replaced, used or deleted with the career. |
| Deletion retry | A hashed confirmation reference lasts ten minutes to handle an interrupted reply. |
| Nickname reports | Up to 90 days from submission, including review status. Reports involving a deleted career are removed during deletion. |
| Blocked players | Until you unblock the player or either career is deleted. |
| Nickname restrictions | Until lifted after review or the restricted career is deleted. |
| Deletion record | A minimal hashed career identifier is retained to prevent an older backup from restoring a deleted career. |
Server error logs help troubleshoot and secure the service and can include IP addresses and request details. Nginx checks log rotation daily and keeps up to 14 rotated logs; empty logs can delay rotation, so this is not a strict 14-day deletion limit. Other system logs follow infrastructure retention settings; a fixed retention period for those logs has not yet been verified.
Automatic backups keep up to seven snapshots made on days with activity. Career deletion removes the career from the active service and scrubs these automatic backups. Restricted migration archives from earlier versions can contain historical copies; deletion records must be applied before restoration, and archive removal is handled separately. Contact us if you need help with removal from retained archives.
We also keep encrypted daily snapshots on a separate operator-owned Mac, with a rotating limit of seven verified copies. Older copies are removed after a replacement passes verification and an isolated recovery test; failed checks can delay rotation. These copies contain essential career and access data, not optional usage analytics. Deleting a career does not immediately rewrite an existing encrypted copy, so it can remain there until rotation. The latest deletion journal must be applied before any restoration to prevent deleted careers from returning. These backups depend on the Mac being available and are separate from the server snapshots described above.
Earlier versions collected first-party visit, campaign and gameplay analytics. This version stops that collection and removes those measurements from the active career store. Historical copies may remain in the restricted archives described above.
Player-safety reports, blocks and nickname restrictions are not included in the game backups described above. They are not recovered from those snapshots.
Your choices
Use Profile → Settings → Delete career to remove your career, drafts, saved results, Classic rooms and earlier duels, and recovery access. Deletion is irreversible. You can change your nickname in Profile unless nickname editing has been restricted after review. Use the leaderboard’s player menu or Player options inside a room or duel to report or block a player. Blocking hides Classic rooms and earlier duels, prevents joining those rooms together and cancels unfinished Classic games. Use Blocked players on the leaderboard to unblock them. Contact support to appeal a restriction. For other access, correction or deletion requests, contact us; we may need to verify that the career belongs to you without asking you to email its secret credentials. Rights and exceptions depend on applicable law.
Children
The game is intended for a general audience aged 13 and older. We do not knowingly collect personal information from children under 13. If you believe a child has provided information, please contact us so we can investigate and address it. Please avoid putting personal details in nicknames.
Changes
We will update the date on this policy when it changes. Material changes will be explained in the game before new practices take effect, with consent where required. This policy describes the service as it operates; it does not replace any rights you have under applicable law.