Privacy policy
Tournament alerts with optional session controls. Your preferences and recent matches stay in your Chrome profile.
Last updated: 18 November 2026 · Contact support
Who publishes this extension
Showdown TourWatch (formerly Showdown Break Alerts) is published by CrispyCrust007. Contact: CrispyCrust007@gmail.com.
This is an independent companion for Pokémon Showdown. It is not affiliated with or endorsed by Pokémon Showdown, Pokémon, Nintendo, The Pokémon Company, Google, or Cloudflare.
What the extension handles
- Your choices: setup-guide completion, per-tournament team-warning acknowledgements, theme preset and custom background/highlight color preferences, filtered/all notification coverage, tournament keywords and exclusions, optional display name, notification preferences, consent records, selected account identifier, and automatic ready-up preferences.
- Public tournament information: announcement titles, room identifiers, announcement source, timestamps, announcer names, and your recent matching announcements.
- Optional session information: only after you enable session controls and grant Chrome access to play.pokemonshowdown.com, the extension reads the account display name and identifier, connection status, enrolled tournaments, format and bracket information needed to identify your matches, opponent identifiers, match links, readiness state, and a reference to the team currently selected in Showdown.
- Showdown tabs: optional session controls locate open Showdown tabs to use the existing session. The extension does not inspect other websites or your general browser history.
Optional tournament statistics and replay links (version 2.2+)
Statistics recording is a separate opt-in. It can use the existing optional Showdown site/scripting access while Join and Ready controls are Off. It records your account identity, tournament rooms and formats, entrant names and counts, bracket structure and results, your opponents, match outcomes and times, and saved replay URLs. Only information necessary for your recorded tournaments is retained; ordinary chat, PMs, passwords, authentication cookies, login tokens, and packed teams are not copied into the statistics database.
History is stored in IndexedDB in this extension’s origin in your own Chrome profile. Tournament payloads are encrypted with AES-256-GCM and unique random IVs. The nonextractable Web Crypto key is stored by Chrome in the same extension database. Random record IDs, state/timestamps, and hashed instance references used for lookup/deletion remain outside encrypted payloads. This is not a separately password-protected vault and does not protect against someone controlling your Chrome profile, browser, or device. Each user/profile has its own database; there is no automatic sync or developer database.
History is retained until you delete it or remove/lose the extension profile. There is no automatic pruning of old tournament records. Snapshots and per-record fields have processing bounds (up to 2,048 entrants, 4,096 bracket nodes/matches, depth 32, 128-player round-robin tables, 600 summary timeline entries); incomplete or unsupported information is labeled rather than fabricated. Browser storage quotas still apply. The statistics page displays origin usage estimates and offers a request for protection against automatic storage eviction, which Chrome may decline without showing a permission popup; the result is displayed next to the control. It provides record deletion, clear-all, backup/export and restore/import. Encrypted backups use a user-selected password, PBKDF2-SHA-256 (310,000 iterations), and AES-256-GCM; forgotten passwords cannot be recovered. In version 2.7.1, export offers an explicit Without password option that downloads readable JSON instead. Anyone with that file can read its player/account identifiers, tournament history and replay URLs. Encrypted export remains the recommended default and new encrypted backups require at least six characters; existing backups use their original password. Both formats contain all journal records. Imports are validated, preserve existing local records and encrypt newly restored records in the local journal. No exported file is uploaded to the developer. The user controls where the downloaded file is saved or shared. Imports are limited to 70 MB files and 20,000 records, merge missing records, and keep existing local records. Export before changing extension IDs or moving between unpacked and Store installations.
Pausing recording stops future statistics collection and automatic replay requests; existing history remains. To stop all Showdown page access, also disable session controls and revoke Chrome’s optional permission. Delete extension data removes the statistics records and their key as well as other extension settings. Deleting a local record or backup does not remove any replay already hosted by Showdown.
In version 2.5, one optional checkbox enables tournament history recording together with automatic replay uploads. Both start Off until you explicitly accept the displayed disclosure and Chrome grants the optional Showdown access. Existing history-only choices from older versions stay history-only until you explicitly enable uploads; upgrading or revisiting setup never enables sharing by itself. Enabling this combined feature asks the existing Showdown client to upload your own finished battle logs to Showdown’s replay service. These logs may include usernames, revealed battle information, and battle chat; upload visibility is governed by Showdown’s own settings. The extension does not change battle visibility or upload logs to the publisher. The finished battle must remain available, and success is not guaranteed. Only a returned or API-verified replay URL is labeled as saved; requests without a validated link are labeled unconfirmed. You can also attach an existing replay URL manually. Version 2.2 stores replay links, not offline copies of replay logs or videos.
Statistics begin when enabled. They do not reconstruct an entire previous account history. Connection gaps, replaced tournaments, unsupported placements, and uncertain identity after a refresh are shown as incomplete/unknown. Exact placement ranges are derived conservatively; stage statistics currently target standard single elimination. Other brackets can be stored and displayed without inventing unsupported placement calculations.
Reload continuity and replay recovery (version 2.2.1+)
When optional Showdown page access is enabled, a small continuity marker is kept in that Showdown tab’s sessionStorage. It contains a random tournament token, opaque hashes, phase/membership flags, an opaque Ready-request receipt, and a recent-observation timestamp; it does not contain usernames, brackets, teams, replay links, or login credentials. It allows an ordinary page reload to retain the existing tournament identity and Ready preference, including result tracking after elimination. Fresh creation/end events reset the marker; only recent compatible markers are reused. Full extension-data deletion clears these markers in connected Showdown tabs. History remains in the extension’s encrypted IndexedDB database.
Replay confirmations are read directly from Showdown’s upload-success popup message and, for older clients, its upload-success dialog. Confirmed URLs are queued until the extension saves them. With replay saving enabled, recorded finished own matches without a saved replay URL may also be checked through the HTTPS Showdown replay JSON API, using omitted credentials and bounded retry intervals. The check verifies the battle identity and your account among the replay’s players and returns only its validated URL to the extension; replay logs, passwords and input logs from that response are not returned or archived by this verification. A missing, inaccessible or unverifiable replay remains unconfirmed. The API checks are read-only and do not change replay visibility. Separately enabled replay uploading can retry Showdown’s native save command after a transient failure, or after an unconfirmed request has waited at least one minute and a replay lookup has failed. Automatic sends are capped at three per battle and two per connected-session processing pass; lookup checks are capped at eight per match with five-minute retry spacing. Existing confirmed links are not re-uploaded. A user can explicitly retry Save replay later.
Version 2.2.1 also repairs the specific empty-registration duplicate produced by a short page reload in version 2.2.0, when one matching later record can be established. The earlier entry time, instance aliases and registration details are retained in the surviving encrypted record. Records with actual match data, conflicting candidates or a known new creation event are not merged by this repair.
Enrollment and played totals (version 2.2.2+)
Manual Showdown joins are recorded under the same opt-in as extension-assisted joins; they do not need an alert rule. Leaving and rejoining the same known tournament keeps one history entry and retains the membership events in its encrypted timeline. Tournaments played requires at least one observed battle room or own battle-start/result event. A signup, a start announcement, an unobserved gap or a room-less administrative advancement alone does not qualify. Records without a confirmed battle remain in history so missing data is not silently erased.
All-tournament alerts and notification history (version 2.3.0+)
You can explicitly choose filtered alerts or all new signup announcements observed in the main Tournaments room. Saved name filters are preserved while all-alert coverage is selected; a blank filter does not silently opt into all alerts. The destination room is obtained from the public announcement rather than a user-entered room filter. This coverage does not guarantee that every tournament on the server is announced there.
A history entry is created after Chrome accepts a tournament notification; this does not prove the operating system displayed a banner or that you read it. Tests and duplicate announcements do not create additional entries. A successful extension Join can mark its original entry as joined. With existing optional Showdown page access enabled for session controls or statistics, a currently enrolled tournament can mark one uniquely matching recent room/title alert as an observed join. This adds no site permission and does not enable page access by itself. Without that evidence, the label remains No join recorded; it is not a claim that you never joined. Existing entries are retained without invented join metadata. No account name is added to this notification-summary log.
Setup, Ready warnings and replay reliability (version 2.4+)
The initial three-step guide explains basic alerts, optional Join/Ready and optional statistics/replay uploads. In version 2.4.1, continuing from the required first-step checkbox saves basic monitoring consent. The next two steps offer separate optional checkboxes: choosing Join/Ready or statistics requests Showdown access directly from that checkbox gesture, then enables only that feature if Chrome grants access. A declined request leaves the feature Off and does not block continuing with alerts. In versions 2.4.1 and earlier, replay uploads had a further separate checkbox. Version 2.5 replaces that with one history-and-replay opt-in, disclosed before enabling, while preserving existing upload opt-outs. Skipping optional choices does not enable them; revisiting preserves existing choices. Completing or deferring the guide saves a local completion marker. You can reopen it from Dashboard or Settings, which also keeps all permission and preference controls available. Notification coverage and appearance preferences are in Settings. Version 2.5.1 offers neutral Dark and White presets plus two custom colors, stored locally; Dark is the default. The bundled Privacy Policy opens in the same extension tab with Dashboard, Statistics and Settings navigation; the public website remains a standalone policy.
Enabling automatic Ready for a team-building, unknown-team or Tours Minigames tournament requires an acknowledgement that team edits may be needed between rounds and that failing to follow room rules can cause disqualification. The acknowledgement is stored with that tournament’s existing local preference and expires with it. Existing team-building On choices without this acknowledgement are paused until it is provided. The extension does not inspect host instructions, decide whether edits are necessary, or make team changes.
For recorded own matches, upload readiness can use Showdown’s server-finished flag or a bounded scan of the last 30 queued battle protocol lines for a win/tie marker, even if animations are paused. This detection returns only known finished own battle identifiers; it does not copy those protocol lines or battle chat to the journal. Classic upload-success popup callbacks and server popup confirmations can return an authoritative replay URL. Unmatched confirmations remain in a bounded queue until their match is recorded and the link saves successfully. Encrypted match metadata includes bounded upload/lookup counters, attempt times and error summaries. A one-time reindex of recent missing-replay records covers the prior 30 days without deleting history. Pending final-match work can continue after a tournament ends or the extension worker restarts. Closed/unavailable battles and inaccessible private replays may still need an actual saved URL from the user; success is not guaranteed.
Notification expiry and automatic recovery (version 2.6+)
Notifications default to one minute, configurable in Settings. Chrome alarms and up to 200 local notification identifiers and creation/expiry timestamps allow overdue notifications to be removed after a worker restart or device sleep. Metadata is removed when notifications close or expire. Legacy sticky notifications without saved deadlines are cleared once on upgrade; alert history is retained. OS behavior and delayed alarms can affect timing. Ready reminders occur only when effective automatic Ready is Off and an enrolled match offers a Ready action. Hashed opening receipts share the existing bounded local deduplication mechanism; raw challenge messages are not archived.
With statistics recording enabled, missing own match results and times can be checked against known battle rooms. A recent recorded battle may reconnect in the background inside your existing signed-in Showdown tab, without selecting the room or opening a browser tab. This sends normal room-join traffic and can make your presence visible there. An unavailable room can produce Showdown's own error. Replay saving retains its existing consent requirement; enabled replay verification can derive result/time metadata from that exact replay. Only bounded match metadata and validated links return to the extension, not replay logs, chat, passwords, input logs or teams. Already available own battle queues are inspected for player, start-timestamp and win/tie markers without archiving them.
Recovery covers pending finals and records with saved replays but missing results/times. Encrypted metadata retains observation/recovery times, source labels and bounded retry counters. At most two matches are checked per processing pass, at intervals of at least two minutes per match, with twelve unsuccessful checks; a verified ongoing battle does not consume that finish-recovery budget. Records from the preceding 30 days are reindexed once without deleting history. Server start timestamps, live observed finishes and recovered finished-by bounds are distinguished. Missing exact end times are not invented. A verified final on the recorded single-elimination bracket can establish a recovered outcome; its source and missing end announcement remain noted. Later authoritative tournament events can enrich it. Expired/inaccessible battles or unsaved/private replays may remain incomplete.
Native best-of sets (version 2.7+)
For your recorded native best-of-three, five, seven or nine sets, the journal retains the set identifier, score and result separately from its individual game identifiers, game numbers, opponents, results, source-labeled times and replay URLs. Games are counted once; the parent set is not counted as another game and has no single replay URL. Only bounded own-match metadata is returned from set protocol summaries, not raw HTML or battle/chat logs. Pending known sets may reconnect in the existing Showdown tab under the same recovery limits to discover their individual games; unavailable rooms and custom host-managed sets may remain incomplete.
Automatic Ready can also click Showdown's native next-game confirmation, only when both existing global and tournament controls allow it and any team-warning acknowledgement is satisfied. It does not select moves or make team edits. An opaque per-game receipt in the existing account-scoped page-session continuity marker prevents repeated confirmations through ordinary reloads. When automatic Ready is Off, a manual reminder can be shown instead. The existing optional page-access and history/replay choices apply; no new host or Chrome permission is requested.
Optional feature suggestions (version 2.7.1+)
The Dashboard links to a short suggestion form bundled with the extension. Entering a title and suggestion does not store it in the journal or send it automatically. Choosing Open email draft passes only that title and suggestion to Gmail using its compose URL, addressed to CrispyCrust007@gmail.com. No history, replay files, diagnostics or authentication details are attached. Gmail can process the draft under its own policies; you choose whether to send it. If you send it, the publisher receives the message and sender address to consider the suggestion or respond. You can instead copy the text into your preferred email service. The extension does not read your email account.
What is not collected
The extension does not copy your passwords, authentication cookies, login tokens, payment information, private messages, or packed team contents into its own storage. It does not install analytics, advertising trackers, or keylogging. It does not play battle turns or provide battle decisions.
Why the information is used
Information is used only to filter tournament announcements, display requested desktop alerts and recent matches, show current enrollment, and provide the optional Join, automatic Ready, and match-link features. The global Ready control and the tournament-specific control must both be On for automatic Ready. Team-building formats default to Off; confirmed Random Battle formats outside Tours Minigames default to On after session controls have been enabled.
Storage and retention
Settings, consent records, a bounded notification-summary log, and up to 200 tournament preferences are stored locally in this Chrome profile using chrome.storage.local. In version 2.3.0 the alert log keeps at most 50 entries for up to 30 days, with a 64 KiB UTF-8 JSON payload cap; oldest entries are removed automatically when limits are reached. Each summary contains a bounded title, announcement/destination room, time, up to three matching filter labels, and a join-observation time/source if established. It excludes raw announcement HTML, brackets, battle/replay logs, teams and account identifiers. This compact log is Chrome local storage, separate from the encrypted tournament-statistics journal; clearing one does not clear the other. Tournament preferences older than 30 days are removed when the extension next runs. Settings remain until you clear them, delete extension data or uninstall the extension. Notification summaries are also subject to the limits above, checked at startup, when new alerts are recorded and when history/enrollment is refreshed.
Temporary connection details, the current enrolled-tournament view, pending Ready-attempt signatures, notification destinations and announcement duplicate-alert keys use memory or chrome.storage.session and are cleared when the browser session ends, the extension is reloaded or removed, or you delete extension data. To prevent repeated match-start notifications after a browser restart, version 2.2.2 retains up to 300 hashed account-and-battle alert receipts with timestamps in chrome.storage.local for up to 30 days, removed at startup or when recording a new receipt. The receipts are opaque hashes rather than plain account names or battle links; they are not a separate encrypted vault. Delete extension data clears them. Disabling session controls clears the current enrollment view. If statistics recording is separately enabled, Showdown page access continues for that feature; revoke optional permission to stop both.
The publisher does not operate a database or server receiving this information. Browser-profile data is protected by Chrome and your device/account security; the extension does not add a separate password or claim to encrypt all locally stored preferences.
Network connections and recipients
After you choose to start alerts, the public monitor connects directly to wss://sim3.psim.us/showdown/websocket. It subscribes to the main Tournaments chat room as a guest and sends a read-only room query to maintain that connection. Showdown receives the connection IP address, room subscriptions, and normal protocol traffic.
Optional session controls act through your existing Showdown page. Pressing Join sends a tournament enrollment request to Showdown. If you enable automatic Ready, Showdown’s own Ready handler can upload your selected team and send challenge/accept requests to the Showdown server. Your tournament participation and match activity may be visible to opponents and other room users according to Showdown’s normal rules and privacy settings. The extension does not send private messages or chat posts. Separately enabled replay saving can upload battle logs as described above.
Information is not sold or shared for advertising, profiling, credit decisions, or unrelated purposes. There are no automatic data uploads to CrispyCrust007. If you email support, your email address and message are received through the publisher’s Gmail account and used to respond to that request; do not include passwords, authentication tokens, or private team exports.
Your controls and deletion
You can pause tournament notifications, disable optional session controls and revoke the site permission, turn automatic Ready Off globally or for an individual tournament, clear announcement history, or choose Delete extension data in settings. Deleting extension data stops monitoring, revokes Showdown page access, clears the extension’s saved settings/history/preferences and its notifications, and returns it to the initial disclosure screen.
These controls do not delete your Showdown account, remove you from tournaments, undo a Ready request already submitted, erase Chrome’s own browsing history, or delete records held independently by Showdown. Uninstalling the extension removes its Chrome storage. Refreshing the Showdown page also removes its temporary page observer.
Limited use and security
Use of information handled by Showdown TourWatch is limited to its disclosed tournament-alert, participation, statistics, and replay-link features. Data is not used for advertising or unrelated purposes. The extension’s use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Extension network connections use WSS or HTTPS. All extension logic is included in the submitted package; remote announcements are treated as data and are not executed as code. Optional page access is limited to play.pokemonshowdown.com and can be revoked.
This policy website
This page contains no analytics scripts, forms, cookies set by the site, or third-party fonts. It is served as static files by Cloudflare. Like any hosting provider, Cloudflare can process connection information such as IP addresses, requested URLs, browser details, and security/operational logs under its own privacy policy. Visiting this page is separate from the extension’s tournament monitoring.
Policy changes and contact
Last updated: 18 November 2026. Material changes to extension data handling will be reflected here and in the in-product disclosure before new handling begins. For support, privacy questions, or requests concerning support emails, contact CrispyCrust007@gmail.com.