Updated October 9, 2026
Privacy &
launch updates.
When you select “Get launch updates,” you ask Spynncaster to email you game news and launch updates. Signing up is optional and does not create a game account.
What we collect
We save your email address, the time you signed up, which form you used, and the version of the signup notice you accepted. We also save a protected representation of your private unsubscribe key.
Where it goes
The list is stored privately on Spynncaster’s DigitalOcean server, separately from game accounts. It is available to the site operator through authenticated server access. We use it for Spynncaster news and launch updates, do not sell it, and do not publish it.
Leaving the list
After signing up, save the private unsubscribe link shown with your confirmation. That link lets you remove your signup immediately. Opening it does not unsubscribe you until you press “Remove my signup.” Future update emails will also include an unsubscribe link.
If you sign up again with the same address, keep your original link. Duplicate signups do not replace it. Active signup information is kept while you remain on the list; unsubscribing deletes that entry from the active database.
Friend invitations and beta access
Claiming a friend invitation is separate from subscribing to launch updates. We record contact details you provide to the developer, the inviting account, your email address, verification and expiry times, and whether the invitation has been redeemed. We use these records to verify access, prevent invitation reuse, and link your invitation to your game account. The inviter can see whether their invitation was claimed, but not the recipient’s email through this feature. Verification emails are transactional, not marketing subscriptions. Temporary abuse-prevention counters use a keyed hash of your network address.
Site operation
Discord Gauntlet accounts
“Continue with Discord” asks Discord to verify your identity, Spynncaster server membership and selected guild, and to share your email when available. We store your Discord ID, username, server display name, selected guild, email and its verification status, plus Gauntlet checkpoints and your highest cleared level. These create a provisional Spynncaster account or use an account already linked by the owner. We do not merge accounts just because names or emails match. Full app beta access is approved separately. Signing in does not subscribe you to launch marketing or authorize us to read Discord messages.
Your display name, guild and highest cleared level are visible to signed-in Gauntlet members on the leaderboard. Email and account-link details stay private to the operator. An HttpOnly sign-in cookie remembers this browser for up to 90 days; local browser storage holds account-specific progress waiting to sync. Discord membership and guild are checked at sign-in; an existing remembered session is not automatically revoked when a Discord role changes. You can sign out on the welcome page. We do not retain Discord access or refresh tokens.
Contact the Spynncaster owner through our Discord to request correction or deletion of your account, contact details and Gauntlet records. We keep them while your account is active, unless you request deletion. Restarting a Gauntlet erases the saved climb but preserves your leaderboard best.
During the private beta, the developer can view invitation delivery status, installation-link clicks, app contact after an invitation code or login is supplied, signup progress, and game participation/results. A download click does not prove installation. We also receive feedback you choose to send. This information is used to support testers and improve onboarding and game reliability, not advertising. We do not make continuous screen recordings. Feedback and private operator notes may identify your account; please do not include passwords. This beta information is separate from the public site's anonymous totals. The private operator console uses secure login cookies, including an optional 30-day Remember me session.
Updated apps automatically report runtime errors, displayed error notices, stalled Gauntlets and unconfirmed gameplay exits. Private reports include app version/build, device model and OS, relevant code locations and recent game state. Signed-in reports identify the game account; pre-login reports are unassigned. A Gauntlet report can include the last 32 observed arrivals, catches, misses and touch positions, along with level, tier and save/connection status. A short active-game checkpoint helps diagnose an unexpected restart; it does not prove that the app crashed. If a runtime error occurs during a battle, the app also attempts one reduced-size screenshot of the rendered battlefield, which may include Mage Names. Account/login forms, other apps, passwords, invitation codes, session tokens, raw device logs and audio are excluded. This is not continuous screen recording or a complete touch history. Up to 32 unsent reports (2 MiB total) are held privately on the device for up to seven days and retried for their original account, or separately without an account for pre-login reports. Server cleanup removes error screenshots after seven days and error reports after thirty days. Reports are available only in the developer’s authenticated workspace.
Sign-in areas use the essential cookies described above. We keep daily totals of new launch signups, film plays, landing-page views, and clicks on Discord or Kickstarter links when available. The /play page also keeps hourly totals of those actions, measurement choices, and whether the Meta script loaded, to diagnose missing measurements. A random ID for each measurement request is retained for up to two days to prevent retries from counting twice; it is not reused across visits. For the /play landing page, totals may be grouped by a small set of campaign and creative labels from the link. These totals contain no email addresses, visitor identifiers, browsing histories, raw link parameters, or referrers. They count activity, not unique people, confirmed Discord joins, installations, or Kickstarter signups. We honor browser Do Not Track and Global Privacy Control signals for these counts. Your browser sends network information, including your IP address, to load the site. To limit automated signups and repeated event requests, we temporarily store a keyed hash of your network address and an attempt count, never your raw address in the signup database. Those counters expire within two hours and are cleared on a later signup or event request.
Optional advertising measurement
The /play page offers optional Meta advertising measurement, separately from the anonymous totals above. Meta’s code loads, and server delivery begins, only after you allow measurement. It can send Meta the landing-page view, three seconds of visible trailer playback, and a Discord or Kickstarter link click, together with approved campaign labels, a Facebook click ID when present, browser/network information, and Meta cookie identifiers. Our server can send the same consented events through Meta’s Conversions API, using matching event IDs to prevent double counting. Pending events may temporarily include your IP address, browser user-agent and Meta cookie or click identifiers; they are removed after successful delivery or rejection, or expire within 24 hours. Changing your choice cancels pending delivery from the current page; events already delivered cannot be recalled. Meta may associate these with your activity on its services to measure advertising and build advertising audiences. A link click does not confirm you joined Discord or signed up on Kickstarter.
“No thanks” keeps Meta measurement off without limiting the page. “Measurement choices” on /play lets you change that choice. We store the choice in this browser for up to 180 days; declining removes the Meta cookies we can access for this site. Do Not Track and Global Privacy Control prevent this optional measurement. No game-account information, beta invitation codes, or launch-list emails are sent by this integration. Other site pages do not load it. See Meta’s privacy policy for how Meta handles information it receives.