Privacy policy | StatChecked

This policy explains what information StatChecked (statchecked.com and shore-software.com, operated by Shore Software, “we”) collects, how it is used, who it is shared with, and the choices you have. If you have a question that this page does not answer, email shoredynamics@gmail.com.

Information we collect

Information you enter

Riot IDs you search for. When you look up a League of Legends player, the Riot ID and region are sent to our server and on to the Riot Games API.
Hex Pitch accounts. If you create an account to play Hex Pitch online, we store your username, display name, the email address you provide (optional), a salted hash of your password (never the password itself), your games, moves, chat messages and rating.
Hex Pitch games against the computer. When you play the computer on statchecked.com, we record the game — the line-ups, every move by you and by the computer, and the score — to improve the computer opponent. The recording is linked to your account if you are signed in, and is anonymous otherwise; no IP address is stored with it.
Daily games (League of Legends, Honkai: Star Rail, Path of Exile and Lost Ark). If you play while signed in, we store each day’s result for each game, the friends you add (with each other’s friend code) and the groups you join. Your display name, points and stats appear on each game’s public leaderboard unless you turn that off; your friends can always see your stats.
Worlds pick’em. If you make picks on the site, we store them with your account. If you use our Discord bot, we store your Discord user ID and display name, your picks, the servers you picked from (so each server gets its own leaderboard), and for each server its name, icon, chosen poll channel and ping setting. Your display name, points, record and picks appear on the public pick’em page and leaderboard unless you hide yourself, on the site or with /mypicks in Discord. In a Discord server you picked in, your name and picks are always shown to that server: in the bot’s polls, and on the server’s page on this site to signed-in members (people with the page’s link who aren’t members see only players who haven’t hidden themselves).
chess.com and Lichess usernames you look up. They are sent to the chess.com Published-Data API or the Lichess API, and the public games returned are stored to build reports faster.
Game votes and suggestions. A vote is stored with a one-way hash of your IP address and browser, only to allow one vote per month; suggestions are free text you choose to send.
Messages you send us by email.

TrailMap (Outdoors)

If you sign in to TrailMap, we store the information needed to run it for you and the friends you add: your account and display name; if you connect Strava, your Strava athlete ID and OAuth tokens (encrypted) and the activities, routes and photos Strava shares with your permission; any Garmin, GPX or Apple Health files you upload and the activities read from them (from an Apple Health export we keep only workouts that have a GPS route, with their sport, distance and, if you agree, heart-rate summary; everything else in the file is read and discarded); photos you upload, including their location data; routes, group hikes, comments and kudos you create; your live location while you choose to share it; and, if you use safety check-ins, your plan, return time and the emergency contact’s phone number you enter. This information is visible only to you and to people you have added as friends, except that an emergency contact receives the check-in details if you are overdue.

Public trail pages. Anyone can browse the trails database without an account. Reviews, star ratings, condition reports and trail photos you post there are public and shown with your display name; trail photos are re-encoded when uploaded so their location and camera data is removed. When one of your recorded activities covers a whole trail, its time is saved to that trail’s leaderboard. Your times are shown to your friends, and to everyone only if you turn on public leaderboards (off by default); activities that are private on Strava or hidden from friends never appear on public leaderboards. Anyone signed in can report a post, and posts reported by several people are hidden.

Public game data we store

To show statistics, we store public data returned by the Riot Games API: match records (including the Riot IDs of players in those matches), ranked standings over time for profiles that are viewed, and aggregated champion statistics. We also store Formula 1 timing data published by Formula 1. None of this is linked to you as a visitor.

Information collected automatically

Server logs. Our hosting provider records technical information about requests, such as IP address, browser type, the page requested and the time. Our own request log records the page, the result and how long it took, without your IP address. We also keep a security log of sign-in attempts (successful and failed, with the username), account sign-ups, and requests we refused or rate-limited, with the IP address and time, to detect and stop attacks. We use logs only to operate and secure the service. Per-address counters used for rate limiting expire within minutes to hours.
Browser storage. We use your browser’s local and session storage for conveniences: your theme, your last-used region and section, units, recent searches, whether the little characters on the home pages are on, your daily-games progress, chess game reviews you ran (so they reopen instantly), saved League teams, TrailMap map preferences, offline map areas and trip checklists, the Discord servers whose pick’em pages you’ve opened (their names and icons), and your site sign-in token. This stays on your device and you can clear it at any time. We don’t set first-party cookies.
Advertising cookies. See the next section.

Advertising

StatChecked is free and is supported by advertising served by Google AdSense. We do not show advertising on the Formula 1, TrailMap, Honkai: Star Rail, Path of Exile or Lost Ark pages.

Google and other third parties may place and read cookies in your browser, or use web beacons and your IP address, to collect information as a result of ad serving on this site.
Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the internet.
You may opt out of personalized advertising by visiting Google’s Ads Settings. You can also opt out of some third-party vendors’ use of cookies for personalized advertising at aboutads.info.
To learn how Google uses information from sites that use its services, see How Google uses information from sites or apps that use our services.

Visitors in the European Economic Area, the United Kingdom and Switzerland are asked for consent through Google’s certified consent management platform before advertising cookies are used, and see only non-personalized, limited ads if they decline. You can change your choice at any time.

We don’t sell personal information for money. Letting Google and its partners use advertising cookies for personalized ads may count as “selling” or “sharing” under some US state laws. You can opt out with Google’s Ads Settings or aboutads.info above, or by blocking third-party cookies in your browser.

How we use information

To provide the tools you use: looking up players, showing matches, and running online games.
To build aggregate statistics such as champion win rates, which contain no personal information.
To keep the service secure, prevent abuse, and fix problems.
To show advertising, as described above.

We do not use the information you give us to build advertising profiles of our own.

Why we may use your information (EEA, UK and Switzerland)

Running the features you use (accounts, daily games and leaderboards, Hex Pitch, the Worlds pick’em and Discord bot, TrailMap and safety check-ins): to perform our agreement with you (GDPR Art. 6(1)(b)).
Heart-rate figures in activities you import from Strava, Apple Health, Garmin or GPX files are health data. We keep them only if you give your explicit consent (Art. 9(2)(a)) by ticking the heart-rate box when you connect Strava or upload files, and use them only to show them to you and the friends you share activities with. Without consent we don’t store heart rate. You can withdraw consent at any time on TrailMap’s Connect page, which deletes every heart-rate figure we hold for you.
An emergency contact’s phone number: our legitimate interest, and yours, in making check-ins work (Art. 6(1)(f)). The contact confirms with a texted code before receiving any alert.
Player lookups, storing public Riot, chess.com and Lichess game data and ranked history, recording games against the Hex Pitch computer, and security and rate limiting: our legitimate interests in running and protecting a statistics service (Art. 6(1)(f)). You can object at any time.
Personalized ads and advertising cookies: your consent through Google’s consent tool (Art. 6(1)(a)), which you can withdraw at any time.
Responding to lawful requests: legal obligation (Art. 6(1)(c)).

We don’t make decisions about you based solely on automated processing that have legal or similarly significant effects.

Where it’s processed

Our servers, databases and TrailMap photos are hosted by Microsoft Azure in the United States. If you use StatChecked from the EEA, the UK or Switzerland, your information is transferred to and processed in the United States. Our service providers (Microsoft, Google, Discord and Twilio) rely on the EU-U.S. Data Privacy Framework and its UK and Swiss extensions, or on the European Commission’s Standard Contractual Clauses, for these transfers.

Who we share it with

Riot Games, whose API receives the Riot IDs you look up. See Riot’s privacy notice.
Google, for advertising and consent management, as described above.
chess.com and Lichess, whose APIs receive the usernames you look up.
Strava, when you connect it to TrailMap: we request your activities using the permission you grant, and you can revoke it in Strava or from your TrailMap profile at any time.
Map and routing services (OpenFreeMap, BRouter, Photon, OpenTopoMap and similar) receive the map areas you view, the points of routes you plan, the places you search for in TrailMap, and the trail areas you browse. Open-Meteo receives the approximate location of trails whose weather you view. They do not receive your account details.
Discord, if you use our pick’em bot: Discord delivers your commands and button presses to us, and we send it the replies and poll messages it shows in your server. Server icons on pick’em pages load from Discord’s image servers.
Image servers. Champion and item images load from Riot’s Data Dragon and team logos from LoL Esports’ image servers. Like any website your browser fetches files from, they receive your IP address and browser details. Our fonts and icons are served from our own servers, not Google Fonts.
Twilio, only if you add an emergency contact to a safety check-in: it delivers the text messages to that phone number.
Microsoft Azure, which hosts our servers, databases and TrailMap photos in the United States.
Authorities, if required by law.

How long we keep it

Individual match records: deleted once the game is more than 21 days old (aggregate statistics built from them contain no personal information and are kept).
Ranked history snapshots: for as long as the service runs, to draw LP graphs.
Daily-game results, friends and groups: until you remove them or ask us to delete the account.
Worlds pick’em: 60 days after the Worlds 2026 final (mid-January 2027) we delete Discord IDs and names, the picks of players who never linked a site account, and Discord server details and polls. Picks made with a site account stay with the account until you ask us to delete it.
Hex Pitch games and chat: kept with the game until you ask us to delete the account.
Site accounts (Hex Pitch and TrailMap) and TrailMap activities, photos and routes: until you delete them or ask us to delete the account.
Recorded Hex Pitch games against the computer: for as long as they are useful for improving the computer opponent. Games linked to an account are deleted with the account.
Trail reviews, condition reports, trail photos and leaderboard times: until you delete them, delete the activity, or ask us to delete the account.
TrailMap live locations: hidden after 12 hours; safety check-in status pages expire 72 hours after the alert.
Game votes: the current and previous month only.
Server logs and the security log: 30 days in our log store (request logs also stay on the server for 7 days), then deleted.

Your rights

Depending on where you live, you may have the right to access, correct, delete or export your personal information, to object to or restrict how we use it, and to withdraw consent at any time (without affecting anything done before). To exercise any of these rights, including deleting your site account and TrailMap data, removing your Discord pick’em data, or having your Riot ID’s stored ranked history removed, email shoredynamics@gmail.com. We will respond within 30 days. You may also complain to a data protection authority: in the EEA, the one where you live; in the UK, the Information Commissioner’s Office (ICO); in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC).

Children

You must be at least 13 to create an account or use the Discord bot. If the law where you live requires a parent’s permission at your age (up to 16 in parts of the EEA), get it first. StatChecked is not directed to children under 13, and we do not knowingly collect their personal information; if we learn we have, we delete it. If you believe a child has created an account, contact us.

Security

Connections to the site are encrypted with HTTPS. Passwords are stored only as salted hashes. Databases are reachable only from our own servers and authenticate with managed identities rather than stored passwords.

Changes

If we change this policy we will update the date at the top of this page. Significant changes will be noted on the home page.