Private post-game coaching, by design.

Static website

The GitHub Pages website contains the 150-course Free library and stores course step, answer-count, and mastery progress in your browser's local storage. This information is not uploaded to Repertoire /64. Premium lessons are not included in this static package; the Premium link opens the separately authenticated hosted website.

When you submit a Chess.com username for an Elo lookup, your browser sends it directly over HTTPS to api.chess.com with cookies and referrer information omitted. The static website displays the public response and does not save the username.

Hosted Premium checkout

GitHub Pages contains no payment form, API secret, gateway callback, private receipt, or Premium entitlement logic. Its Premium links open the authenticated standalone Repertoire /64 website. There, checkout requires the verified email from Discord sign-in and explicit acceptance of the purchase terms.

The hosted server sends Plisio the checkout email, random order ID, selected Premium plan, corresponding $1.99 or $11.99 USD source amount, source currency, and fixed callback and return URLs. It stores the account identifier, email, order and provider references, trusted invoice URL, selected product and term, price, currency, status, consent and payment timestamps, entitlement expiration where applicable, and returned crypto amount/currency. It does not store wallet private keys, seed phrases, or the full callback payload.

Only a signed, fully completed Plisio callback can activate Premium. The private receipt uses a secure HttpOnly browser token while only its SHA-256 hash is stored. The token expires after 30 minutes and is consumed on reveal or explicit close. Payment records are retained while needed to provide access, resolve disputes, prevent duplicate activation, and meet legal obligations; deletion can be requested through official support, subject to required record retention.

Premium payments use the authenticated standalone Plisio checkout and support Bitcoin (BTC), Ethereum (ETH), Litecoin (LTC), Bitcoin Cash (BCH), and Solana (SOL). Gift-card codes and card details are not accepted through Discord. Repertoire /64 does not collect them; never post or send that information in a support ticket or message.

Information the extension handles

• The Chess.com username you choose to save.
• Extension preferences.
• Public completed-game PGNs and metadata retrieved from Chess.com.
• Local Stockfish review results.
• A visible game-over signal. The extension does not read chat, passwords, authentication cookies, private messages, or provide live move recommendations.

Extension use and storage

The extension sends the saved username over HTTPS only to api.chess.com to retrieve public player and completed-game data. The username, settings, completed game, and analysis are stored in Chrome's local extension storage. Stockfish runs locally on your device.

Repertoire /64 does not receive this extension information on a developer analytics server, sell it, use it for advertising, or make it available for human review.

Permissions

• Storage saves local settings and reviews.
• Alarms waits for the completed PGN to become available.
• Notifications tells you a review is ready.
• Chess.com page access detects only the visible completed-game state.
• api.chess.com access retrieves public player and completed-game data.

Retention and control

Website progress remains until you clear site data or use Clear local progress. Anyone using the same browser profile may be able to see that local progress. Use a separate browser profile on shared computers.

Extension information remains until you overwrite it, clear the extension's data, or uninstall the extension. You can change the username or disable automatic review at any time.

External links

Reputable YouTube lessons, the Chrome Web Store, Discord support, and Google Forms open only after you choose their links. Those services then receive the information normally associated with your visit and apply their own privacy policies. Repertoire /64 sends no course progress or game analysis through those links.

Limited Use

Information is used only for the disclosed post-game coaching features. Repertoire /64 complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Support and moderator applications

The support-team application form is hosted and processed by Google Forms under Google's policies and the form owner's settings. Repertoire /64 support staff may review the responses you choose to submit when considering your application.

Responses remain in the form owner's Google account until they are no longer needed for recruitment or moderation records. Access should be limited to the server owner and designated support leads. You may request deletion through the official support Discord.

Provide only information relevant to the application. Never submit passwords, authentication codes, API keys, wallet seed phrases or private keys, payment details, or unnecessary sensitive personal information.

Discord support triage bot

The support triage bot reads messages only in selected bug-ticket channels or threads and the designated ⭐ reviews location. It does not read other server channels or direct messages. Messages are treated as untrusted input: their text receives automated, best-effort sanitization and redaction before a triage record is stored in a private GitHub repository. Attachments and linked content are not downloaded.

Negative sentiment, criticism, or a low review never causes a fix or any other code change. A reported issue must be independently reproduced before it may produce a tested draft change for human review. The bot never merges, deploys, or publishes a change automatically.

Sanitized triage content remains while the ticket is open and is scheduled for purging 30 days after closure. Minimal audit metadata—such as Discord message or channel IDs, a content hash, and triage status—may be retained to prevent duplicate handling. You may request earlier deletion through the official support Discord.

Automated redaction cannot guarantee detection of every secret or personal detail. Do not post passwords, authentication codes, API keys or tokens, wallet seed phrases or private keys, payment details, or unnecessary personal or sensitive information in tickets or reviews.

Contact and changes

Material data-practice changes will be disclosed before they begin. Ask support or report a bug in the official Repertoire /64 Discord server. Discord channels may be public, so never post passwords, authentication codes, API keys, wallet seed phrases, payment details, or private personal information.