Privacy Policy

The operator of a protected game server decides whether to enable the service, which settings to use, and what action to take on a detection. That operator is generally the primary contact for its players and is responsible for providing any notice, lawful basis, consent, or appeal process required by applicable law.

ChrononLabs generally processes player data as a service provider or processor for the server operator when scoring gameplay, hosting the dashboard, and returning detections. ChrononLabs determines limited independent purposes for platform security, abuse prevention, legal compliance, support, service reliability, and the opt-in global ban network. For those purposes, ChrononLabs acts as a controller. You can contact ChrononLabs at support@chrononlabs.net.

The customer game server receives player events and relays selected identifiers and gameplay telemetry to ChrononLabs-controlled infrastructure. ChrononLabs stores and analyzes that information, creates detection results, profiles, evidence, and replays, and returns relevant results to the customer through the service and dashboard. The off-server scoring and profiling described in this policy occurs on ChrononLabs infrastructure, not on the customer game server.

• Account and customer data: Information provided when a customer creates an account, buys services, configures a server, contacts support, or uses the dashboard.
• Website security data: IP address, user-agent, authentication events, and essential cookies used for login, fraud prevention, and session security.
• Player and session identifiers: Steam ID or other game-account identifier, display name, server and session identifiers, sequence identifiers, timestamps, and other records needed to associate events with a session or enforcement record. Some integrations may also transmit a player IP address as connection metadata, but new player profiles and stored detection objects do not retain it.
• Gameplay and input telemetry: Events received by the customer game server and relayed to ChrononLabs, such as movement, view angles, mouse or command input, firing, hits, damage, weapon state, target and engagement data, connection quality, and detailed gameplay or control inputs recorded over time.
• Derived analytics and profiles: Accuracy and performance statistics, behavioral patterns, detection scores, risk indicators, replay data, infraction history, ban status, and other conclusions generated from gameplay telemetry.
• Device and technical data: Operating environment, connection, hardware, software, and diagnostic information when made available by the game server, browser, or integration.

Player telemetry may be pseudonymous, but it is not treated as anonymous while it remains linked or reasonably linkable to a Steam ID, session, server, detection, or ban record.

• Score gameplay sequences and detect suspected cheating.
• Provide player analytics, detection evidence, replays, alerts, and enforcement tools to the relevant server operator.
• Apply or support server, server-network, or opt-in global ban checks where the operator enables those features.
• Investigate false positives, appeals, abuse, security incidents, and service failures.
• Test, validate, secure, and improve detection models and service performance, using deidentified or pseudonymized data where reasonably practicable.
• Comply with law and enforce our agreements.

ChrononLabs uses automated analysis on its infrastructure to identify gameplay patterns associated with suspected cheating and returns the results to the customer. If the operator enables automated bans, a detection may restrict access to the server. The operator may also enable enforcement across its server network or the opt-in global ban network, which can affect access to multiple participating servers. The operator controls its review and appeal settings and must provide human review where required by law.

Depending on the processing and jurisdiction, we rely on performance of a contract, legitimate interests in operating and securing the service and protecting fair gameplay, or compliance with legal obligations. Core anti-cheat processing is not based on optional player consent. ChrononLabs determines and documents the lawful bases for processing performed on our infrastructure. Customers do not select or state those bases in the player notice generator.

Anti-cheat processing continues while you remain connected to a protected server. If you do not agree to the processing described in this policy, do not connect to the server or disconnect immediately. This does not limit any right you may have to object to, restrict, or request deletion of personal data under applicable law.

We may disclose information to:

• The customer or server operator that submitted the data and its authorized administrators.
• Hosting, infrastructure, security, communications, payment, and support providers that process data for us under appropriate contractual restrictions.
• Other protected servers or operators when an authorized customer enables server-network or global ban-sharing features.
• Authorities, advisers, or counterparties where reasonably necessary to comply with law, protect rights and security, or complete a corporate transaction.

We do not sell player personal information or share it for cross-context behavioral advertising.

• Website sessions: Website IP addresses, user-agents, and essential session data are normally deleted after one week of account inactivity unless a longer period is required for security, disputes, or law.
• Player IP metadata: Player IP addresses are not retained in player profiles or new stored detection objects. Legacy player IP histories are removed by the database migration deployed with this policy change.
• Gameplay telemetry: Raw and derived telemetry is retained while needed to score events, investigate detections, create evidence or replays, support player appeals where the operator has enabled the opt-in appeal feature, and preserve historical infraction context for authorized server operators. Raw gameplay telemetry and detailed replay source data stored as detection objects are retained for no more than 12 months from collection, subject to shorter deletion where required by law.
• Detection profiles and evidence: Derived statistics, detection and infraction history, and replay evidence may be retained to support player appeals where the relevant operator has enabled that feature and to allow authorized server operators to review a player's historical infractions and enforcement context over time. These records may remain linked to an account identifier while relevant to an active ban, appeal, dispute, or long-term enforcement review.
• Active ban records: A limited enforcement record, including the account identifier, ban scope, reason, start date, expiry, and status, may be retained for the duration of the ban. The default ban duration is 25 years. That period describes the default ban expiry and is not a universal retention period for every related data category.

Primary service infrastructure is currently hosted in Germany. If personal data is transferred outside Switzerland, the EEA, or the UK to a country without an applicable adequacy decision, we use an approved transfer mechanism such as standard contractual clauses or another legally recognized safeguard. A copy of the applicable safeguards, or information about where to obtain them, may be requested at support@chrononlabs.net.

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data, and to complain to a data-protection authority. We may request reasonable information to verify control of the relevant account or identifier.

For data collected through a game server, contact the server operator first because it controls the server configuration and can identify the relevant session. You may also email support@chrononlabs.net. We may refer the request to the operator or coordinate with it where required.

Customers must make a complete notice reasonably accessible through their server listing, website, rules, or another public surface where available. They must also show players a prominent short notice when they join and, where technically possible, before detailed gameplay and input telemetry is relayed to ChrononLabs for off-server analysis. The notice must describe the relay and ChrononLabs processing, categories of data, purposes, profiling or scoring, retention, sharing, automated enforcement where enabled, and how players can exercise rights or appeal. A generic statement that a server uses “security tools” is not enough if it hides material processing.

Customers can adapt our player data notice template. The template is a starting point and must be completed to match the operator's identity, enabled enforcement and sharing settings, players, jurisdiction, and actual use of the service. ChrononLabs supplies the descriptions of its processing purposes, legal bases, and retention practices.

Our customer service is not directed to children. A server operator that permits minors to play is responsible for age-appropriate notices, permissions, consent, and other protections required by applicable law.

Privacy and data requests may be sent to support@chrononlabs.net. Please include the relevant Steam ID or other account identifier, server name, and approximate session date where available.