Privacy policy

Effective date: 2026-11-16. Draft for Mark's review.

McManus Acres Corp. operates Grimoire. This policy describes the information handled by the game and its account and play servers.

Accounts and sign-in

We keep your account ID, public player ID, creation time, chosen player name, and linked sign-in methods. Email sign-in uses your email address and a temporary code. Other sign-in methods use the identifier supplied by the provider you choose. Available methods depend on configuration and can include Google, Apple, Steam and Facebook.

We process sign-in proofs and keep session and verification records to authenticate you, reconnect you and protect access. The account service stores hashes of session tokens. Browser account sign-in uses session cookies. These static information pages do not set cookies or include tracking scripts.

If you use Steam, we also record Steam's family-sharing and VAC-ban information, including the licence owner's Steam ID for a shared licence and when a ban was first observed. A first-seen ban timestamp can remain after unlinking Steam. If you request Steam friend discovery, our server asks Steam for your friend IDs and matches them to Grimoire accounts.

Playing and social features

We store your decks, card and Grimoire collection, cosmetics, in-game currency balances, rewards and quest progress. We keep ratings, results, ranked season statistics and match records. Match records include decks, placements, actions, scores, timing, game mode and technical inputs needed for replays. Server recovery records preserve active matches and drafts.

Social records include your handle and handle history, friend requests and friends, blocks, invitations, online activity and privacy choices. We also store player-name reports and moderation decisions. We use these records to run matches, save progress, support social features, prevent abuse, review reports and improve game balance.

Other players can see gameplay information. Public profiles and leaderboards show public player IDs, permitted names and statistics. Social visibility depends on your settings and the account's age category. Recorded decks and round actions can also be sent to other players for ghost practice. That feed can include recorded names when present, but excludes top-level account credentials, match and opponent-pair IDs, ratings and seeds.

Feedback and diagnostics

Sending in-game feedback sends your message, chosen player name, report ID, client and server build information, submission time, and available match, room and mode information to our play server.

Reports also include your operating system and version, device model, renderer and driver, graphics adapter and vendor, game-engine version, window size and locale. The optional game-log attachment is selected by default. You can uncheck "Include the game log" before sending. It includes a limited tail of the current log and, when available, the previous session's log to help investigate crashes.

The game removes home-folder paths and the operating-system username from diagnostic logs and device values. It removes home-folder paths from the message you type, but it does not reliably remove personal details you write yourself. Please leave passwords and sensitive personal information out of reports. Reports written offline wait on your device for a later connection.

We did not find advertising, external product analytics or automatic third-party crash-reporting SDKs in the game code reviewed for this policy. Feedback goes to our play server. Our backend also keeps aggregate operational counters.

Local storage and service providers

The game stores settings, saved decks, collection caches, reconnect information, pending commands, feedback drafts waiting to send, and replay or match history on your device. Online gameplay, retries and feedback send the relevant information to our servers.

Our servers process your connection IP address. The account service uses secret hashes of network addresses and email addresses for sign-in rate limits. Sign-in providers receive authentication requests, and the configured email service receives your address and sign-in code. The backend supports encrypted database backups to Cloudflare R2. Hosting providers process network requests needed to deliver the service, including this website.

Google Play, Apple TestFlight, Steam and any sign-in provider you use may handle information under their own privacy terms. Their independent collection is separate from the game records described here.

Children and age information

The backend asks for birth month and year when creating a new account through Grimoire's own email sign-up and refuses sign-ups that indicate an age under 13. It keeps an age category and the year it was calculated. For teens, it also keeps the date at the end of the month they turn 18. This date reveals birth month and year; it is cleared when the category changes to adult. A hashed refusal record prevents another attempt with the same email identity for 30 days.

This is not an age check on every sign-in. Provider sign-ins, older accounts and legacy imports are assumed to be 13 or older. Teen accounts and accounts without an age answer receive private defaults. The native client reviewed for this draft does not yet present the backend's age-answer step.

If we identify an existing account as belonging to a child under 13, the backend blocks sign-in and schedules deletion, with a default seven-day period for a parent to contest the finding. Contact contact@mcmanusacres.com about a child's account or an incorrect age finding.

Retention and deletion

There is no general automatic expiry for active account, gameplay, social, moderation or feedback records. Expired authentication material and invitations have maintenance cleanup rules. Local game files remain until changed or removed. Backup copies have separate retention rules.

To request account deletion or access to your information, contact contact@mcmanusacres.com. Include your player name or public player ID and sign-in method so we can identify the account. Do not send passwords or sign-in codes. We may need to verify that the account is yours.

The backend's ordinary deletion process defaults to a 14-day waiting period and revokes sessions. Signing in again before deletion is due cancels an ordinary pending request. Active match-server use can delay completion. The waiting periods are configurable.

Completed backend deletion removes sign-in identities, the current player record and the covered social records. Some historical match and ranked records, account lifecycle and age-action records, and reduced currency audit records remain. Reduced audit entries have a configurable purge period with a default of about seven years. This does not mean every retained record is anonymous or expires after seven years.

The backend deletion process does not automatically delete play-server feedback files, legacy server files, local device files or backup copies. Tell us if your request includes feedback you submitted. There is no timed server-feedback deletion rule in the reviewed code. Offsite backup defaults keep hourly copies for 48 hours, daily copies for 30 days and weekly copies for 12 weeks; locks and backup safety rules can keep some copies longer.

Contact

For privacy, access, deletion or children's account questions, contact McManus Acres Corp. at contact@mcmanusacres.com.

This draft still has a placeholder contact address and needs operator review before publication.