Alpha ex Machina · Playtest
Privacy notice
Updated November 9, 2026
Alpha ex Machina is a card game operated by Alpha ex Machina, LLC, an Iowa limited liability company. This notice covers this playtest website and its game accounts. For privacy questions or requests, email privacy@alphaexmachina.app.
You can download printable cards and guides and read our policies without signing in. Playing the online game, using campaigns, and opening your collection require an external sign-in.
Information used for sign-in
Google and Microsoft handle authentication. We receive and store the provider name and the provider’s stable account identifier, together with a randomly generated game account ID. We use these identifiers to recognize your account, save your collection, and recover it on another device.
We do not collect or store your provider password. Our sign-in requests do not ask for your name, email address, profile photo, contacts, messages, or files. Extra profile claims a provider returns are discarded. Provider tokens are used to complete sign-in and are not retained in the game’s account database. Linking a second provider happens only when you choose to link it; matching email addresses do not merge game accounts.
Game information
Account storage contains your owned card copies, starter choice, saved deck titles and card choices, favorite deck, tutorial completion marker, save revisions, alpha balance, and your market orders and recent trades. Other players see the prices and quantities of orders and trades in the market, never who placed them. Deck titles are private account data unless you share a deck; avoid putting personal information in them. Deck titles are checked automatically for offensive language.
When you choose “Create deck code” under “Share my deck,” the server stores a copy of that deck’s title and card list under a short code, without your account ID. Anyone with the code or deck link can preview that copy without signing in; saving a copy to a game account requires sign-in. The copy does not change when you edit or delete your deck, and deleting your account does not remove it; to remove a shared copy, send its code with a privacy request.
A learning campaign, such as FIN 3400, offers an optional course receipt for a professor. If you make one, the server stores the name you enter, when you made the receipt, and a random receipt code. Anyone who has the code or the receipt link can see that name, the course, which lessons the server verified, and when, without signing in. The receipt does not show your game account ID, provider, alphas, or collection. You can correct the name twice; the receipt then also shows each earlier name and when it changed. Withdrawing the receipt or deleting your account removes the name and the code, and the link stops working at once. Copies a professor saved, such as a printout or a downloaded list, stay with them.
Multiplayer servers store room membership, a protected room password, deck selections, readiness, game state, moves, timestamps, and preset emotes. Other players see numbered seats such as “Player 1” and the information the rules reveal during a match. They do not receive your provider identifier or game account ID. The game has no player usernames or free-text player chat. While you wait in the public lobby, it keeps your table, chosen company, join and check-in times, and whether you accepted a match; after a match starts, it keeps that match's room for ten minutes. Other players see the companies at each table and how long it has waited, never who is waiting.
Both campaigns, including their deck choices, rewards, and active matches, and unfinished solo games and tutorials are saved to your account on the server. Your preferences, such as sound, game speed, and the screen tips you closed, and your KPIs are saved to your account too.
Decks can be used without an account. Browser drafts keep their card choices and titles in this browser’s storage; clearing site data removes them. A draft is saved to your account only if you choose to copy it there. Copying a draft gives no cards. A shared recipe link carries a deck’s title and cards in the part of the address after #, which browsers do not send to our server; anyone you give the link can read them. Deck analytics play their games in your browser and send no deck list to us. The guest tutorial keeps its match in page memory only and awards no account rewards. Leaving or reloading the tutorial clears that match.
Why we use this information
We use account and game data to authenticate you, save and recover collections, run matches, enforce ownership and game rules, respond to support requests, and investigate errors or abuse. We do not sell or rent this data or use it to train general-purpose AI models.
We also use anonymous match data to improve the game’s computer opponents: results, such as which version of a computer opponent played and whether it won, and the card lists of the decks played in finished free-play and campaign matches, without deck names. This data isn’t linked to your account.
Play statistics
The game records how it is played, so we can see which parts work and which need repair: the pages and game screens you open, how long a page is visible, matches started and finished with their mode, CEO, cards played, and result, tutorial and lesson steps reached, decks shared and deck analytics started, card packs and market orders, settings changed, sign-in results, page load times, and script errors. With them we store the browser and system family (such as Safari on iOS), the device type, the window size, the language, the country of the network address, the site that linked to the visit, and the game version. We do not store your network address, name, email address, or game account ID with them. Play statistics use no cookie or browser storage of their own.
While you are signed in, the statistics carry a code derived from your game account ID, so we can count returning players and see how play changes over time. Public pages, such as the course samples and How to Play, count visits without this code. Using Decks while signed out also counts without an account code. The statistics stay in the operator’s Cloudflare storage and go to no other company. We keep each recorded event for 180 days; after that, we keep only daily totals that name no one, and the days on which each code played. Deleting your account deletes the statistics stored under its code.
To stop sending them, turn off Send play statistics in Account → Settings. The game then sends none while you are signed in to that account. The records that run your account and matches continue.
The main page’s Active accounts total counts accounts with an authenticated request in the last 24 hours, including test accounts. This count is separate from optional play statistics and works when those statistics are off. For this count we keep only a code derived from your account ID and the most recent request time. Expired entries are removed when activity is updated or counted, and during the daily cleanup. The public sees only the total, never account codes or identities.
The game operator may access necessary records for support, security, maintenance, or legal obligations. We do not give other players access to your private account records. We may disclose information when required by law or when necessary to protect users and the service.
Advertising and privacy choices
The public guides, card catalog, game previews, and FIN 3400 lesson readings may display one Google AdSense advertisement per page. These pages run at guides.alphaexmachina.app. The game server uses Cloudflare’s IP-country information and your ad-free status to choose whether and how to serve an ad. It sends only that decision to the page. We do not send game account IDs, sign-in identifiers, or game records to Google for advertising.
In the European Economic Area, UK, and Switzerland, Google’s dialog asks for your choices before AdSense requests an ad. The dialog may receive your IP address and browser information. If you decline or a choice is unavailable, ads stay off. Use Privacy and cookie settings below the page to revisit your choices.
In the United States, these pages request non-personalized ads using Google’s restricted data processing setting. Google and its ad partners may read or set cookies or use web beacons, IP addresses, and other identifiers to deliver and measure ads. Read how Google uses data from sites that use its services.
Visitors with other or unknown IP locations read these pages ad-free. Ads also stay off for signed-in ad-free accounts and when your browser signals Global Privacy Control or Do Not Track.
The browser draft builder and public market board can also show one ad. The game host displays your browser drafts and market controls separately from the ad. Trades and account decks open on the game host.
Ad-free payments
If you subscribe, Stripe collects payment details, email address, billing location, and information it needs for payment, tax, and fraud prevention. Checkout may use Stripe’s Link service. We do not receive your full card number. We store the Stripe customer and subscription identifiers, plan, status, and paid period to provide ad-free access. The operator uses payment records for billing, tax, refunds, disputes, and support.
Service providers and optional feedback
Google and Microsoft process your authentication under their own policies: Google Privacy Policy and Microsoft Privacy Statement. Alpha ex Machina’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements where applicable.
Cloudflare delivers and protects this website and, on alphaexmachina.app, stores game account and multiplayer records for the operator. It processes traffic information such as IP addresses, request details, browser information, and security events. Cloudflare may also collect page and performance measurements through its analytics service. See the Cloudflare Privacy Policy. Stripe processes payments under the Stripe Privacy Policy, and its Link service under the Link Privacy Policy. Providers may process information in the United States and other countries where they operate.
If you choose to send feedback through the linked Google Form or email, the operator receives what you submit, including any contact information or game details you choose to include. Our support and privacy addresses reach one Microsoft Exchange mailbox; replies use support@alphaexmachina.app. Earlier correspondence may remain in the operator's Gmail mailbox. We keep a private case record with a request summary, message references, verification status, deadlines and actions, so requests can be followed through. We keep correspondence and case records as needed to handle requests, resolve disputes, and meet legal obligations. Do not send passwords, sign-in codes or full payment details. These communication services handle submissions under their own policies.
The operator may use OpenAI's Codex to help organize support requests and prepare responses, using only the information needed for the request and settings that do not use that information to train general-purpose AI models. Sensitive account changes, refunds and legal responses require operator review and appropriate verification. See the OpenAI Privacy Policy. Contact the privacy address above about support records as well as game records.
Approved campaign test runs have a separate private feedback ticket queue. The organizer supplies your game account ID and agreed report email address. A submitted ticket includes your message, campaign version, lesson and a game snapshot; reports and replies are kept in that ticket. The operator uses Codex AI to review this material and prepare updates or clarification requests. Cloudflare Email Service carries reports and email replies. Other testers cannot read your tickets. Leave student names, personal information, passwords and other secrets out of feedback. Contact the operator at the privacy address above for a copy, correction or deletion of these separate test records.
Cookies, storage, and security
Essential cookies keep you signed in and bind a sign-in attempt to your browser. A game sign-in lasts up to seven days; a sign-in attempt lasts up to ten minutes. Older multiplayer browsers may also have a seven-day seat recovery cookie. Signing out invalidates the current game session. It does not sign you out of Google or Microsoft or clear other browsers’ independent sessions.
The ordinary game’s campaigns, matches, preferences, and KPIs use account storage, and signed out, a preference you change lasts only until you leave the page. Separate campaign test pages save progress in your browser, isolated by account, version, mode, and test run. Clearing site data removes these test saves. Decks also saves browser drafts and signed-out deck tips in this browser. Cloudflare’s security and analytics processing is described above.
On alphaexmachina.app, account and multiplayer records are kept in Cloudflare storage in the operator’s account. A separate test site keeps them on a computer controlled by the operator. Access to these records is restricted. HTTPS protects network transport; game session cookies are inaccessible to JavaScript, and the server stores hashed session tokens. No service can promise absolute security or uninterrupted access.
Retention and your choices
We retain your account identifiers and saved collection while the account is active. Signing out, deleting browser storage, or removing provider access does not by itself delete the saved game account. Multiplayer room records can remain after a match for recovery and error investigation. Ranked play stores your rating, match totals, and ten recent results while your account is active. Deleting the account removes that ranked profile. Completed ranked settlement receipts retain the rating changes and outcomes without account identifiers or deck lists, so retries cannot pay a result twice.
You can delete your game account yourself at any time: open the Account page, choose Delete account, and confirm. To request access, a copy, a correction, or restriction of your account and associated game records, or deletion when you can no longer sign in, email privacy@alphaexmachina.app with the subject “Alpha ex Machina privacy request.” State the request and which provider you use. We will arrange verification that you control the game account without asking for your password. If you cannot sign in, contact us for another verification method.
When you delete your account, or after a verified deletion request, we remove the game account’s provider links, saved binder and decks, campaign and solo progress, course receipts, alpha balance, market orders, and sessions from active account storage. The prices of past trades stay in the market’s history without any account. Room records that name the account are removed or expire on their normal schedule, usually within about eight days. A completed ranked room with a pending reward can remain until settlement succeeds, then expires within seven days. Payment and tax records that Stripe and the operator must keep by law remain after deletion. We may retain information specifically required by law or necessary to resolve a dispute; we will explain any applicable exception. We review inactive playtest records and remove data that is no longer needed.
Provider and infrastructure logs follow those providers’ own retention rules. Copies you download remain under your control. Deleting a game account does not delete your Google or Microsoft account.
Depending on where you live, you may have additional rights to object to processing, withdraw consent, receive portable data, or complain to a privacy regulator. Contact us to exercise applicable rights. We use information as needed to provide the game you request, protect and maintain it, meet legal obligations, and, where required, with your consent.
Age and changes to this notice
Game accounts are for people age 13 or older, or the higher minimum age required where they live. The online game is not directed to children under 13. If you believe a child below the applicable minimum age has provided account information, contact us so we can investigate and remove it.
We will update the effective date when this notice changes. Material changes will be announced on the sign-in or account page before they take effect; any new use of provider data requiring consent will wait for that consent.