Data sources.
Lock Lab uses public community data, official changelogs, and game-reference assets. Availability and coverage can differ by player, match, region, patch, and provider.
Deadlock community API
Match history, detailed scoreboards, item events, hero statistics, counters, ranks, and leaderboard records are retrieved from the community-operated Deadlock API. Lock Lab caches responses to protect the service and labels unavailable records instead of substituting mock data.
Steam public profiles
Public display names, avatars, and profile links are hydrated from Steam Community public profile surfaces and cached in Lock Lab's search index. Lock Lab never requests or stores Steam passwords. Steam and its profile assets remain subject to Valve's terms and privacy policy.
Official changelog
Patch articles originate from Valve's official Deadlock changelog. Lock Lab links the original post and separates official changes from its own summaries, comparisons, and expected meta implications. Unreviewed patch-detail pages are withheld from search indexing and advertising.
Deadlock Wiki and visual assets
Item and ability references may use locally cached files synchronized from the community Deadlock Wiki, which publishes community contributions under its stated site licensing terms. Hero, ability, item, rank, game, and trademark assets ultimately remain the property of Valve and their respective rights holders. Lock Lab uses them for identification and commentary in an independent fan analytics context; rights or attribution requests can be sent to hello@locklab.gg.
Hosting, security, monitoring, and advertising
Cloudflare provides delivery, hosting infrastructure, and security controls. Lock Lab uses a cookie-free first-party route counter for basic service monitoring and does not send analytics data to Google. Google and a Google-certified consent platform may process advertising requests only if advertising is enabled in the future.