Usage analytics information
Effective October 29, 2026 · Updated October 30 · Automatic measurement
Automatic measurement without a popup.
Public screen visits and feature use are measured automatically. No analytics cookie or persistent browser identifier is stored. Use Exclude my visits in the footer to stop collection. DNT/GPC and previous opt-out choices are respected.
How visitors are estimated
The server briefly uses the network address and browser request information to derive a site-specific daily key. Raw IP and User-Agent strings are not stored in analytics. A new key is used each day; old keys are removed on the next collection request. When network metadata is unavailable, a temporary value valid only for the current page is used.
Across multiple dates, visitors are the sum of daily estimates. We do not connect identities across days or classify long-term new/returning visitors. Shared networks, VPNs and address changes affect accuracy. Sessions restart after 30 minutes of inactivity or a new KST day.
What we measure
We measure screen/hero/ability views, feature interactions, selected patch and language, device/browser/OS categories, country and referring domain when available, restricted campaign tags, estimated active time, load times and categorized errors.
Only visits identified by coarse IP geolocation as Gwangyang, South Korea are grouped separately. Other city names, coordinates and addresses are not stored. Carrier routing and VPNs can make this differ from a visitor’s actual location.
When city metadata is absent, the server checks only Gwangyang IP ranges from the free DB-IP dataset locally. Visitor IPs are not sent to an external lookup service; this does not identify a precise residence. IP Geolocation by DB-IP · 2026-10 · CC BY4.0
What we do not store
Analytics does not store raw IPs, accounts/emails, typed searches, full share settings or referrer URLs, keystrokes, screen recordings, Steam accounts or actual matches. Functional preferences and administrator login cookies are separate. Infrastructure and authentication provider logs are also separate.
Bugs & feedback
Your message, page, language, device type, browser and OS are sent to the owner and kept for up to 90 days. Do not include passwords, codes or personal data. Raw IP addresses are not stored.
Please try later. To prevent spam, a network can send five reports daily, at least one minute apart. If the site-wide limit is reached, try tomorrow.
Match review · BETA
Public account IDs are sent to OpenDota for lookup. Saved IDs, notes and custom goals stay in this browser and are not sent to AI or visitor statistics. Preset types and outcomes are counted as feature usage. Daily salted browser/network hashes and a functional cookie enforce free quotas.
Sources & free-service policy
Free upstream requests share a site-wide budget:100 units/day by default,300 when a successful response confirms at least1,000 remaining that day,500 with at least2,000. The30/minute,5 new matches and 1 parse/browser/day and IP guardrails remain. Parsing costs10 units; normal reads cost1. Source pauses and headroom are respected; no automatic parsing or polling.
Update notices
The update notice above the coffee button in the lower-right corner opens once per browser per local day. This browser remembers the last seen date and dismissed notice version, without adding a visitor identifier. Automatic opens, icon opens, dismissals and reopens follow the same analytics exclusions and retention rules.
Retention and exclusion
Detailed events are retained for 30 days; daily aggregates and minimal visit summaries for up to one year, with cleanup on requests. Cumulative session/view totals and the collection start date are retained. Visitor statistics are protected by administrator authentication. Opting out stops future transmission; existing statistics expire under the retention policy.
Contact: yjne1879@gmail.com