EMPIRE SCOUT
Privacy
Empire Scout stores only the account and service data needed to provide and protect your membership.
Account information
Discord sign-in provides your Discord user ID, username, display name, and avatar reference. We use the stable Discord ID to bind access and do not request your Discord password.
Billing information
Payment details are collected and processed by PayPal. Empire Scout stores PayPal order or subscription identifiers, status, plan, billing dates, and the Discord account reference needed to verify access, but never stores full payment-card or bank details.
Device and usage data
We store a one-way token for the linked extension device, recent access time, and successful scout usage needed to enforce plan limits. We do not sell personal data.
Browser extension data
The Empire Scout extension runs only on Pokémon Showdown pages. To provide its visible research features, it reads the battle format, public player names, and Pokémon already visibly shown in the active battle, then sends those specific inputs to Empire Scout over HTTPS for a user-requested or enabled search. It does not collect browsing history, read other websites, access Showdown passwords, issue battle commands, or access hidden battle information.
Retention and security
Account, billing, and audit records are retained while needed to operate the service, resolve disputes, and meet legal obligations. Session and device tokens are stored as one-way hashes.
Optional extension community chat
Joining community chat shares your Discord-linked display name, messages, and online presence with other participating members. Messages are kept on the server for up to 7 days, limited to the newest 500. Reports are retained for up to 30 days for moderation. You may separately opt in to sharing whether you are playing or watching and the battle format. Game links, opponents, teams and private battle details are not shared as activity. Activity is self-reported, and presence expires after 65 seconds without a heartbeat. You can leave chat, turn off activity sharing, delete your messages, block members and report abuse. Basic chat identity, block and moderation settings persist until removed through support.
Developer API
Developer API access is separate from extension membership. We store hashed API credentials, key prefixes, subscription or free-gift records, and request identifiers, account identifiers, categories, months, outcomes and timestamps for quota enforcement and abuse prevention. The raw API key is shown once and is not retained. Request-accounting records do not store search bodies. You can revoke a key or cancel API billing independently; contact support for account-data removal.
Your choices
You can unlink a device, manage or cancel billing, and sign out through the dashboard. Contact support to request account-data deletion, subject to records we must retain for legal or fraud-prevention reasons.