Operator and contact
Matchkeep is operated by Beacon Hobbies. For privacy questions or requests, email contact@beaconhobbies.com. California is the selected governing jurisdiction for the draft Terms; applicable privacy rights depend on the law that applies to you and the operator.
Information we handle
When you sign in with Google, Matchkeep handles account details such as your name, email address, profile image, and provider account identifier, along with the authentication information needed to keep your account working. Authentication sessions can include an IP address and browser user agent.
Event information may include event names and descriptions, display names, player tags, game and faction details, roster status, signups, pairings, schedules, scores, rules, correction requests, host decisions, and event activity. Do not add sensitive personal information that is not needed to run an event.
If you submit a bug report or suggestion, Matchkeep stores its category, description, any steps and page location you provide, your account identity, and the submission time. Verified support operators can review the private support queue to investigate and respond. Do not include passwords, authentication codes, private invite links, or other secrets in a report.
For optional event payments, Stripe collects payment and payout details on its hosted pages. Matchkeep stores connected account and transaction identifiers, fee amounts, payment and refund status, and payment activity linked to the event and participant. Event organizers can review their event’s payment records; participants can view their own status. Matchkeep does not store card numbers or bank account details.
How information is used
We use account and session information to sign you in, keep your session active, and apply event permissions. We use event information to operate signups, rosters, pairings, match reports, corrections, schedules, and standings, and to maintain an accurate event history.
Event visibility and providers
Hosts choose whether an event is public or private. Public event pages and published results may be visible to anyone. Private event information is intended for authorized event members and hosts. Players can use the available privacy choice to hide their player name from public event pages.
Matchkeep uses Google for sign-in, Vercel for application hosting, Turso for its database, and Stripe for optional event payments. The exact provider legal names, data regions, and any additional production logging or monitoring services still need confirmation.
Retention and deletion requests
We intend to keep account information while the account is active. To request account deletion, email contact@beaconhobbies.com. Beacon Hobbies will verify the request and aims to remove or de-identify account information in the active service within 30 days. Some identity-free event records may remain to preserve tournament results or resolve a dispute; any exception should be limited and documented.
Event, roster, match, result, correction, and rules history is intended to remain while an event is active and for up to 24 months after it ends. An event owner can request earlier deletion by contacting us; the draft target is to complete verified requests within 30 days. Participants can ask the event organizer to correct or remove roster details. Event history may be de-identified and retained when needed to keep results accurate.
The selected backup-retention target is no more than 30 days. The active Turso plan and any separate recovery copies still need to be checked; deleted information may remain in a backup until it expires. We will publish the verified period in the final notice.
Your choices
For display-name or roster changes, contact the event organizer. For account deletion, access, correction, or another privacy request, email contact@beaconhobbies.com. Requests are handled manually while Matchkeep has no self-service deletion controls. We will verify requests and respond under applicable law.
Security, children, and changes
We use the safeguards configured for the service and its providers, but the specific safeguards and incident contact need to be confirmed before making a detailed security statement. The minimum age and any parental-consent rules also need to be set before launch. We will update this notice when data practices change and include its effective date in the approved version.