Privacy policy

Last updated: 4 October 2026

After a Million Games is a browser board-game website run by Thibault Castells at after-a-million-games.com. This page explains what the website collects and how it uses that information. For privacy questions or requests, contact thib.castells@icloud.com.

Accounts and Google sign-in

We store your email address, display name, account ID, creation time, access status and connected login methods. The owner reviews invitation requests and records each approval or refusal.

If you choose Google, we request only openid, email and profile. Google supplies an account identifier, verified email address and basic profile information. We use the identifier to recognise your account, the email address to manage access, and your name as an initial display name. We do not use or store your Google profile photo. We do not request access to Gmail, Drive, contacts or other Google content.

Google handles its own sign-in under Google’s privacy policy. After a Million Games does not receive your Google password or keep Google access or refresh tokens. You can revoke the connection through your Google account’s connections page; doing so does not delete your After a Million Games account or game records.

If you use a After a Million Games password, we store a salted password hash, not the password itself. When email verification or recovery is available, we use your address to send the requested account message through our mail provider. Private links expire after 30 minutes and work once.

Games and other players

We save room codes, game settings, player names and seats, linked account IDs, game dates and times, moves, random outcomes, game states, scores and results. These records let you resume tables, see results, replay decisions and help us fix game errors.

People at your table can see your display name and the information the game rules reveal to them. They cannot read your email address or another player’s hidden hand through the game interface. Full game records stay private to the operator. The game catalogue shows total completed matches across players, without listing their accounts.

AI moves can run on our server. When a table uses an external AI service such as TypeSafe, that service receives game context and legal move choices to choose its moves. That context can include player display names. We do not send TypeSafe your email address, Google account identifier, password or sign-in tokens. We also keep AI request counts and usage costs to manage the service.

If you save a favorite card setup, we keep its name and public card choices with your account so you can use it on other devices. Other players cannot see your favorites. You can rename or delete them in game setup; backups may retain older copies.

After an Asterhall game ends, any table member can choose to share a read-only game report. Anyone with their link can see all players’ display names, scores, the game seed when available, final card counts, collection and turn history without signing in. The link does not give access to accounts, email addresses, other games or raw game records. Each member controls their own links and can replace or stop them. Stopping a link cannot erase copies a recipient already saved; backups may retain the report snapshot and the hash of its token.

Subscriptions and Paddle

The current owner preview uses Paddle's sandbox for test payments. We send Paddle your account email and display name when you start checkout. Paddle hosts checkout and the billing portal; payment details go directly to Paddle. We do not store full card numbers or card security codes.

We store Paddle customer, subscription, price and transaction IDs, payment amounts and currencies, billing dates, status, refund details and signed billing events. We link those records to your account to check AI access, handle payment changes and resolve errors. Billing records and their backups remain after cancellation; they currently have no automatic expiry. We do not use them for advertising.

For games hosted with paid AI access, we also keep a billing usage summary: the host's account and payment period, game start and end times, whether the game finished, and counts and times of accepted AI actions. It stays after a room is closed or its game history is deleted. It excludes private game content and free guest play. We may share this summary with Paddle to review a refund request; usage alone does not decide whether a refund is due. These summaries and their backups currently have no automatic expiry.

The account page loads Paddle's checkout software, which connects to Paddle and receives connection details such as your IP address and browser information. Paddle describes its use of information in its privacy policy. Your browser briefly keeps a pending checkout ID in session storage so you can return to checkout after signing in.

Cookies, preferences and security logs

After a Million Games uses a secure session cookie to keep you signed in, a short-lived cookie to complete Google sign-in, and a preference cookie containing only google or password to suggest your last login method. Sessions expire after 12 hours without use or seven days in total. The Google sign-in cookie lasts up to ten minutes; the login preference lasts up to 180 days. A separate preference cookie remembers only your last selected Asterhall AI model for up to 180 days. Your browser may also save game settings such as sound preferences.

The server receives connection details such as your IP address, browser information, requested page and request time. Web-server logs support troubleshooting and abuse prevention. The app uses hashed IP addresses and account details for request limits. The Google callback route does not write its URL to web-server access or error logs.

We do not use advertising cookies or third-party audience analytics. You can clear cookies and browser storage in your browser settings; this signs you out and clears saved preferences.

Storage, sharing and retention

Accounts and game records live on our private server, with backups. Completed game records may also be copied to a private archive operated by Thibault Castells. Connections to that archive use a private encrypted network. Accounts and full game records currently have no automatic expiry, and backups may contain older copies.

We use this data to run accounts and games, review access requests, prevent abuse and fix faults. Access is limited to the operator and the services needed to run the website, including hosting, Google sign-in, TypeSafe for AI play and a mail sender when enabled. Those providers may process information in other countries. We do not sell personal information or share it for advertising. We may disclose information when the law requires it.

Contact thib.castells@icloud.com to request access, correction, export or deletion of your account information and game data. We may ask you to confirm control of the account. We will explain any records that need to remain for security, legal reasons or other players’ game history, and how backups affect removal.

Changes

We will update this page when these practices change. Before using Google account data for a new purpose, we will explain the change and ask for consent where required.