Matchbook

Privacy policy

Last updated: 31 October 2026. Matchbook is operated by Sergii Sergieiev. Contact support@tcg.ninja about this policy or your data.

Data we collect and why

When you sign in with Google, Matchbook stores your Google account identifier, email, name, and profile image to identify your account and display your profile. Browser sessions and OAuth connections allow you and your authorized AI clients to access that account.

We store the tournament details you choose to submit: names, dates, game formats, venue names and optional venue cities and countries, decks, opponent names or nicknames, results, scores, and notes. We use these records to maintain your journal and calculate your statistics. Venue information describes events; the service does not request GPS location. Use nicknames where possible and avoid sensitive personal information in notes.

We keep registration and sign-in audit records, including your name, email, time, and login provider, for service administration. Account data and audit records are accessible to authorized service administrators.

When you invite a friend, we store the invitation, its status and the email address if you provide one. Matchbook does not send an email; you can share the link yourself. When an invitation is accepted, we store the friendship. Each person separately controls which statistics, clubs and tournament results they share.

AI connections and recipients

Connecting an AI client grants it permission to read, create, update, and delete records in your Matchbook account. The MCP server receives the tool arguments that client sends and returns the requested records. It does not retrieve your full conversation history. Matchbook does not need your Google password or AI provider API key.

Google processes sign-in; our hosting provider Hostinger operates the server infrastructure. The AI provider you connect receives tool responses under its own terms and privacy policy.

Optional website analytics and cookies

The website uses a session cookie to keep you signed in. If the operator enables PostHog, it also collects page views and browser interaction events and associates them with your Matchbook user ID, email, and name after sign-in. PostHog may use browser storage for analytics. Session recording is disabled. MCP tool calls do not initialize browser analytics.

Retention

Tournament and account records remain stored until removed; there is currently no automatic retention limit. Login audit records are retained separately and are not automatically removed when profile details change. Friend invitation links expire after seven days; expired invitation records are not automatically erased. Browser sessions expire after 30 days. OAuth authorization codes expire after five minutes, access tokens after one hour, and refresh tokens after 30 days; expiration prevents use but does not automatically erase the stored rows.

Your controls

You can correct records and delete individual matches through your connected AI client. Disconnect the client in its connection settings to stop using that connection. Disconnection does not delete your Matchbook journal or guarantee immediate server-side token revocation; contact support if you need access revoked.

For a copy of your data, account deletion, or removal of audit records, email support from your registered address. These requests are handled manually after verifying ownership; there is currently no self-service account deletion or export page. Do not include passwords or access tokens in support messages.