Privacy policy.
Effective August 19, 2026. Lock Lab is the operator of this independent public Deadlock analytics service. This policy explains what the service processes, why it is needed, and how long it is kept.
Public game and profile data
Lock Lab displays publicly available Steam profile details and public match data returned by Steam and Deadlock community data providers. These records are processed to provide player discovery, match reports, rankings, and analytics. We do not ask for Steam passwords and do not provide Steam sign-in. Cached public identities and selection-popularity signals are retained while they remain useful to the search index; correction, objection, or removal requests can be sent to the address below.
Basic traffic and reliability monitoring
Lock Lab uses a cookie-free first-party counter to record the requested public route, event type, timestamp, and a sanitized application error code when an error occurs. This supports basic page-view totals and reliability diagnostics. It does not collect page query values, referring pages, device classifications, raw IP addresses, full user-agent strings, persistent visitor identifiers, or third-party advertising identifiers. Monitoring events are deleted after 90 days. Lock Lab does not use Google Analytics.
Storage used by the site
Lock Lab stores up to ten recently selected public player profiles in your browser's local storage so you can return to them quickly. You can clear that list from the search interface or by clearing site data in your browser. Our hosting and security provider, Cloudflare, may set strictly necessary security cookies such as __cf_bm to detect abusive or automated traffic. The private administrator area uses a secure, HTTP-only session cookie with a maximum twelve-hour lifetime; ordinary visitors do not receive that session cookie.
Google advertising and cookies
Advertising is currently disabled. Lock Lab may display advertising through Google AdSense in the future. Before advertising is enabled, Lock Lab will configure and test a Google-certified consent-management platform where required. Third-party vendors, including Google, may then use cookies, web beacons, IP addresses, or similar identifiers to serve, measure, limit, or personalize ads according to a visitor's choices and local requirements. Learn more about how Google uses information from sites that use its services. Visitors can manage personalized advertising through Google Ads Settings.
Community voting
Community Favorites stores a vote together with a pseudonymous, salted one-way digest derived from the visitor's network address. The raw address is never stored in the voting table. The digest prevents duplicate votes and lets the visitor change, remove, or clear their votes. Inactive vote identifiers are deleted after 400 days.
Search and abuse protection
To protect public endpoints, Lock Lab keeps a salted one-way request fingerprint and a short-lived request count. The stored value is not a raw IP address. Rate-limit buckets are deleted after seven days. These safeguards are used for service security and availability, not advertising profiles.
Third-party services and international processing
Cloudflare provides hosting, delivery, and security. Steam supplies public profile surfaces. Community Deadlock API providers supply public match and rank data. Google may process advertising requests only if advertising is enabled in the future. These providers operate under their own privacy terms and may process data in countries outside your own. See the source ledger for named links and roles.
Your rights and contact
You may ask to access, correct, delete, restrict, or object to personal data associated with an identifiable public profile or service identifier. Applicable rights vary by location and may include the right to complain to your local data-protection authority. Send privacy, removal, or rights requests to hello@locklab.gg or use the contact page. Include the relevant Steam account ID or public profile URL when the request concerns player data.