Data processing agreement
Purpose and scope
This agreement covers personal data that [Legal entity name and registration: being finalised] ("Sculk", the processor) processes for the customer (the server owner's organisation, the controller) when the customer uses Sculk AC. It applies from [Policy effective date: being finalised] and is part of the Terms of service. It does not cover data for which Sculk is itself the controller (accounts, billing, support and Sculk History), which the Privacy policy describes.
Roles
- The customer is the controller of what its game servers send to Sculk: detection events, cases, evidence, bans, appeals, player lists and per-server player references, join decisions, Verify links created for its servers, and configuration. It decides the purpose (running anticheat and moderating its own server) and the lawful basis, and it tells its players.
- Sculk is the processor. It processes that data only to provide the service, on the customer's documented instructions: this agreement, the customer's configuration, and requests made through the dashboard or API.
- Sculk is a controller for Sculk History, the cross-server record. A customer who contributes an entry chooses to share it and stays responsible for it being accurate. Sculk decides how the shared record is stored, matched and shown.
Details of processing
| Subject matter | Running the Sculk anticheat service for the customer |
| Duration | While the customer has an active plan, then the deletion schedule below |
| Data subjects | Players of the customer's game servers; the customer's staff |
| Data types | Display and character names; keyed hashes of licence, Steam, Discord and hardware identifiers and hashed IP addresses; in-game behaviour records; case notes and screenshots; ban and appeal records; staff account details |
| Special categories | None intended. The customer must not send them. |
Sculk's obligations
Sculk will:
- process the data only as instructed, and tell the customer if it believes an instruction breaks the law;
- keep everyone with access to the data bound to confidentiality;
- keep technical and organisational measures that fit the risk: encryption in transit, hashing of identifiers with separately held keys, encrypted backups, and role-based, logged staff access;
- use only the sub-processors listed in the Privacy policy, bind them to equivalent terms, and give the customer notice of a new one before it handles the customer's data, with a right to object (the customer's remedy is to cancel);
- help the customer answer a request from a player to access, correct or delete their data: the customer can erase a player in the dashboard, and Sculk staff can export a player's data on request;
- tell the customer without undue delay after it becomes aware of a personal data breach affecting the customer's data, and give the details it has;
- help with data protection impact assessments and consultations where reasonably needed;
- delete the customer's data as set out below, and give the customer the data it asks for before then;
- make available the information needed to show compliance, and allow an audit by the customer or an auditor it appoints, with reasonable notice and subject to confidentiality and to the security of other customers.
Retention and deletion
Retention periods are set in code and published on What we store and why. In short: detection events 90 days (180 on Pro and Network), evidence 30 days, cases 1 year after closing, bans while in force plus 1 year. When the customer's plan ends, Sculk deletes its data within [Days to delete a former customer data after review: being finalised] days after review, subject to the law. A person does this, not an automatic job. Sculk may keep what the law requires it to keep, such as financial records, and says what and why on request.
Sub-processors and transfers
The current sub-processors are listed in the Privacy policy. They include Discord (for Verify sign-in, the bot and linked roles) and DeepSeek (People's Republic of China), which receives data only after the customer's organisation owner opts in to the AI features (Sculky, the Case Analyst and support answers), with names replaced by tokens. Where personal data leaves the customer's region, Sculk relies on the transfer mechanism the law requires.
The customer's obligations
The customer must have a lawful basis for the data it sends, inform its players, respond to its players' requests, configure Sculk and its staff access sensibly, and not send data it has no right to send. The customer decides the actions its server takes. Detection is not a guarantee, and a decision to ban is the customer's.
Contact
Data protection contact for Sculk: [Privacy requests contact: contact details are being finalised].