WHL Stats does not require an account and does not sell personal information. Pageview measurement is first-party. Raw IP addresses are not written to the analytics database. Browser alerts are optional and can be disabled from the Alerts page.
1. Scope and operator
This policy covers the WHL Stats pages and services at bragsdale.net/whlstats, including the scores application, first-party analytics collector, and optional browser notifications. WHL Stats is an independent, fan-built reference operated through bragsdale.net.
WHL Stats is not affiliated with, sponsored by, or endorsed by the Western Hockey League, Canadian Hockey League, their member clubs, HockeyTech, or LeagueStat. Their websites and services have their own policies. The CHL privacy policy does not govern this independent site.
The standalone privacy, terms, and contact pages do not run the WHL Stats pageview collector.
2. What is collected
Requests and first-party pageview analytics
Like any website, the server and trusted reverse proxies receive a network address and request details so they can deliver a page, rate-limit abuse, and protect the service. The application then records a limited pageview event containing:
- the WHL Stats route and page title;
- the referring site’s origin and path, with query strings and fragments removed;
- screen dimensions, browser language, and browser-reported time zone;
- a randomly generated browser identifier stored locally for up to 90 days and a random tab-session identifier; and
- user-agent-derived device category, browser, operating system, and likely-bot flag.
Network privacy, GeoIP, and ASN data
The current network address is processed in memory to derive keyed HMAC identifiers and perform a local GeoIP/ASN lookup. The analytics database stores the HMAC values and only a masked /24 IPv4 or /48 IPv6 network prefix—not the raw address. It also records whether the address came through a trusted proxy and whether it was private or reserved.
A local DB-IP database may estimate country, region, city, time zone, autonomous system number (ASN), and network organization. These describe the apparent network exit, not a person’s verified location. Mobile carriers, VPNs, corporate gateways, hosting networks, and Private Relay can make the estimate wrong. City-level estimates are treated as low confidence and may be suppressed in the admin view. Per-request network addresses are not sent to DB-IP for lookup.
Optional push notifications
If you enable browser alerts, the service stores the push endpoint and its public encryption/authentication values, along with the settings you choose: teams, event types, fight threshold, immediate or digest delivery, digest time, quiet hours, time zone, and any weekly league or division schedule. It also keeps subscription timestamps and limited delivery status such as successful sends or failures.
Push delivery necessarily involves your browser’s push provider, such as Apple, Google, Microsoft, or Mozilla. WHL Stats does not require a name, account, or email address to create a push subscription.
Device preferences and messages
Favorite-team and display choices are stored in your browser. Notification preferences are also stored locally and, when alerts are enabled, sent to the notification service. If you email a correction, privacy, or takedown request, the operator receives the address, headers, and content that you choose to send.
3. How information is used
Deliver pages, remember device choices, queue alerts, and troubleshoot failures.
Count visits, understand popular pages and referrers, and improve mobile and browser support.
Rate-limit requests, identify automated traffic, and investigate reliability or security problems.
Review corrections, privacy questions, accessibility feedback, and rights-holder notices.
Analytics HMAC values are keyed internal identifiers. They are used to count browsers, sessions, and repeat traffic; they are not intended to identify a named person.
5. Retention
Different records exist for different reasons. Current retention practices are:
| Record | Typical period | What happens |
|---|---|---|
| Pageview analytics | 90 days | Event rows, masked network prefixes, device fields, referrers, and attached GeoIP/ASN estimates are pruned. |
| Browser analytics ID | Up to 90 days | The random visitor ID expires in local storage. The tab-session ID normally ends with the browser tab/session. |
| GeoIP lookup cache | Up to 180 days | HMAC-keyed approximate network results are pruned; raw IP addresses are not stored in this cache. |
| Operational logs | Short operational rotation | Server and proxy logs may briefly contain request addresses for delivery, abuse prevention, and diagnostics; they are separate from the 90-day analytics database. |
| Push subscription | Until disabled or expired | Removed when you disable alerts through the site or when the push provider reports the endpoint expired. Alert queue and delivery state are kept as needed to deliver and maintain the service. |
| Contact email | As needed for the request | Retained long enough to review, document, and respond to the correction, privacy, or rights issue. |
6. Your choices
- Global Privacy Control and Do Not Track: when the browser exposes GPC or a recognized DNT value, the WHL Stats application does not create or send its pageview analytics event. Necessary requests, security controls, and alerts you explicitly enable still work.
- Clear site data: browser settings can remove the local visitor ID, session ID, favorite-team choice, and saved preferences. A later visit may create a new random analytics ID unless GPC/DNT is active.
- Disable alerts: use Alerts and choose “Disable alerts” to delete the server-side subscription and unsubscribe the browser. If an endpoint has already stopped working, it is removed when the push provider reports it expired.
- Ask a privacy question: use the contact and corrections page. Because raw IP addresses are not kept in analytics and internal identifiers are keyed, the operator may not be able to connect a person to particular analytics rows.
7. Security and limits
WHL Stats uses HTTPS, same-origin controls, limited request bodies, masked network display, keyed identifiers, restricted admin access, and local database permissions to reduce risk. No internet service can promise absolute security. Please do not send passwords, government identification, medical information, or other sensitive material in a correction or contact email.
8. Children
WHL Stats is a general-audience hockey reference. It does not offer user accounts and does not intentionally ask children to provide names, addresses, or other profile information. If you believe a child sent personal information through the contact channel, please request deletion through the contact page.
9. Changes and contact
This policy may change when the site’s data practices or features change. The effective date above will be updated when a revised policy is published.
For privacy questions, corrections, accessibility feedback, or takedown requests, use the contact and corrections page. It explains what to include and links to the existing public bragsdale.net contact address.