Privacy Policy

Last updated: April 27, 2026

This document covers Grimoire deployments that use the frontend, multiplayer backend, and optional account features shipped in this repository. Site operators should review and adapt this policy before using it in production.

Information Grimoire Processes

Grimoire can store decklists, notes, room names, player display names, and gameplay state. Depending on deployment settings, the application may also process account identifiers and authentication tokens through a separate auth backend.

How Data Is Used

Data is processed to provide deck building, shared links, multiplayer synchronization, account session handling, and basic security controls such as request logging and rate limiting.

Local Browser Storage

The app stores some information in your browser, including saved decks and local settings. Clearing site storage or using a different browser profile can remove that data.

Server Logs and Security

Self-hosted deployments may log request metadata such as timestamps, IP addresses, requested paths, and response codes to diagnose service issues and protect the service from abuse.

Third-Party Services

Card search uses Scryfall data. Account features may depend on a separate authentication service configured by the site operator. Those services may have their own privacy practices.

Your Choices

You can avoid cloud-backed features by using a deployment without account integration. If you use an authenticated deployment, use contact.continental-hub.com for requests related to access, correction, export, or deletion of personal data.

Contact

Use contact.continental-hub.com for questions about this Grimoire deployment.