Data storage and connections
Information about desktop versions of EUREKA from 1.38.0 onward.
Data stored on your computer
Progress, owned cards, decks, results, display name, settings, unfinished AI debates, and replays are stored on your computer. An Epic account and cloud saves are not required. See below for anonymous online authentication. To transfer progress, export a JSON file and move it to the other computer. Replay files are stored in profile_replays within the save folder and are not included in the JSON. Copy that folder as well to transfer replays.
Online debate connections
Opening Online connects to Epic Online Services (EOS) for anonymous authentication, public-room discovery, and debate relay. An anonymous ID reused by the same OS user on that device is kept in the OS credential store. An Epic account is not required. Lobbies handle public information such as display names, room names, player counts, and debate status. Decks, actions, and game state are sent to participants who need them. From 1.41.0, public EOS room information also includes estimated skill and the number of debates used to calculate it. The host handles the full debate state. Private information such as hands and decks is not sent to spectators. Full save files and owned-card lists are not stored in the cloud.
For data handled by EOS, see the Epic Games Privacy Policy. Online versions up to 1.37.0 use the former SandCake shared relay and have separate connections and room lists from EOS versions.
Updates and downloads
The app requests update information from the official website at launch and when you choose Check for Updates. Update files are requested when you choose Download. These requests do not include save data or account information.
Official website
This official Eureka website has no advertising or analytics scripts, or account registration forms. Servers may retain operational access logs when you visit the site, download files, or connect to debates. For the shared operating policy, seeSandCake Studio Privacy Policy.
The restricted distribution page uses a cookie to maintain authentication. Passwords are stored on the server as one-way hashes. Repeated authentication failures are rate-limited using an identifier derived from the IP address. These data are not used for advertising or analytics. Logging out ends the distribution page authentication session.