Protect user privacy by default
Context
- Authentication method and the scope of personal information collection are decisions that are costly to change later
- Parlourite is a casual board game site with little intrinsic need to hold personal information
- Looking ahead to AI research use and public replay sharing, operating without personally identifying information is safer
- At the same time, without authentication, continuity of match history, settings, and rankings cannot be guaranteed
Options
Baseline: email + password. Evaluation criteria:
- C1: User privacy / C2: Security (resistance to account takeover)
- C3: UX (registration and login friction) / C4: Recoverability (loss scenarios)
- C5: Legal compliance cost (GDPR / Japan’s Act on Protection of Personal Information) / C6: Implementation and operational cost
| Option | C1 | C2 | C3 | C4 | C5 | C6 | Total |
|---|---|---|---|---|---|---|---|
| Email + password (Baseline) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Email + magic link | 0 | + | + | + | 0 | 0 | +3 |
| OAuth (Google / Apple etc.) | — | + | + | + | - | + | +1 |
| Passkey only + no personally identifying information | ++ | ++ | + | - | ++ | 0 | +6 |
Decision
Use Passkey (FIDO2 / WebAuthn) as the sole authentication method, and collect no personally identifying information such as name, email address, or phone number.
- Account creation is completed by Passkey registration alone
- Recovery codes are self-managed by the user
- Non-recoverable loss scenarios are accepted as a tradeoff and clearly stated in the Terms of Service
- Only a user-chosen display name is used for rankings, replays, and similar surfaces
Rationale
- Holding no personally identifying information contributes simultaneously to privacy protection, breach-risk reduction, and lower compliance cost
- Passkey offers strong phishing resistance and improves security compared to password-based operation
- Consistent with the two-click play policy (2026-10-18-two-click-play): the model of “sign up lightly only when it becomes necessary” holds
- Non-recoverability is an acceptable tradeoff given the nature of a game-play site (unlike financial or medical services)
Consequences
- Positive: Minimized impact of any potential breach, reduced GDPR / APPI exposure, compatibility with future replay publishing and research use
- Negative: No recovery path on Passkey loss, inconvenience for users on environments without Passkey support
- Follow-up: Continued monitoring of browser / OS coverage; recovery UX improvements to be examined in a separate ADR