What we store and why
Each kind of data, why we hold it, how long, who sees it and how to get it changed or removed.
| Data | Why we store it | How long | Who sees it | Access, change and deletion |
|---|---|---|---|---|
| Account | Sign in, billing contact, and who belongs to your organisation. | To be confirmed | You, members of your organisation by role, and Sculk staff when you ask for support. | Edit in your account. Request export or deletion on the Contact page. |
| Organisation and server config | Run your detections and keep a record of every change, including who confirmed it. | To be confirmed | Your organisation by role. | Export or delete on request. Deleted automatically after churn. |
| Detection events | Show what happened on your server and tune detections. | 90 days (Pro plan: 180 days). Raw IP addresses are kept 30 days, then only a /24 hash. | Your staff, with identifiers masked unless their role allows more. | Request access or deletion on the Contact page. |
| Cases and bans | Record why an action was taken so staff can review it and players can appeal. | Cases and their evidence summaries: 1 year after closing. Bans: while active, plus 1 year. | Your staff. The player sees the reason and evidence summary the server chooses to show, through appeals. | Players appeal through the appeals portal. Other requests on the Contact page. |
| Evidence | Back up a case with a screenshot or flight-recorder capture. | 30 days. | Your staff. Captured when a case or a staff member asks for it; Pro adds flight-recorder evidence on every case. | Expires on its own. Earlier deletion on request. |
| Sculk History entries | Let servers that opt in see a player’s record from other Sculk servers. It is a record, not a ban. | Entries expire by default: 2 years for cheating entries, 6 months for others. Overturned entries disappear from other servers immediately. | Servers that opt in, the player, and Sculk staff. | Players view and dispute their entries on My history. Access and deletion requests are answered within a month. |
| Sculk History identifiers | Match the same player across servers without storing readable identifiers. Never used: hardware tokens, IP addresses, or Discord data obtained through our own Discord app. | As long as the entry they belong to. | No one can read the originals. Only HMAC hashes of the license, license2, fivem and steam identifiers are used. A 2-of-4 match counts as the same player; one match is shown as “possible” and never acted on. | Removed with the entry. Request deletion on the Contact page. |
| Discord links | Verify players and sync roles when you enable Verify. | Until unlinked, until the player asks, or 30 days after your organisation churns. | Your staff, by role. | Unlink from the verification flow, or ask on the Contact page. |
| Billing | Charge your subscription and issue refunds. Stripe handles payment details. | To be confirmed | Stripe, and Sculk staff who handle billing. | Manage in the billing portal. Refund window is 14 days. |
| AI conversations (Sculky) | Answer questions about cases and propose config changes. Off until your organisation owner turns it on at a consent screen. Text is processed and stored by DeepSeek in the People’s Republic of China, under PRC law, outside the EEA, the UK and Australia. Before sending, the names Sculk knows for your organisation are replaced by tokens. A name Sculk does not know is sent exactly as typed, so do not type names or personal details that are not already in your Sculk records. Never sent: identifiers (raw or hashed), IP addresses, hardware tokens, emails, Discord ids, payment data, chat text and screenshots. | Conversations (with tokens in place of names): 90 days. Token counts and cost per call: 2 years. Config proposals: for the life of the config history. How long DeepSeek keeps what it receives is set by DeepSeek’s own policy and is outside Sculk’s control. | The person who asked, your organisation by role, and Sculk staff for support. | Delete on request. The AI cannot ban, unban or apply a change on its own. |
Automated decision-making disclosure
Some actions in Sculk AC happen without a person approving them first. This is what they are and what they are not.
What can happen automatically
Each detection declares a confidence class in code, and the class caps the strongest action the detection can take on its own. The engine enforces the cap, so no config value, preset or Sculky proposal can raise it. Owners can lower caps, never raise them.
- Deterministic: up to a permanent ban, after at least 2 samples and all context checks.
- Strong: up to a kick. A temporary ban only with a second independent signal of a different family.
- Statistical: warn and send to the staff review queue. Never kick or ban.
- Client: warn. It can raise server sampling or request a screenshot. Never kick or ban.
- Prevention: cancel the action, such as an explosion or an entity spawn. It never acts on the player.
What always needs a person
A ban from a statistical or client signal cannot happen: those can only flag for review. Sculky, our AI, never bans, never unbans and never applies a change on its own.
Sculk History
By default a server denies entry on confirmed, active entries from contributors past their probation period, with a 2-of-4 identifier match. The server owner can switch this to allow with flags, hold for staff review or require Verify, and staff can override it for one player. An entry under dispute stops denying until the dispute is decided. History never denies on any entry other than cheating:confirmed.
How to ask for a human review
If a server removed you or took an action against you, use the appeals link on the rejection card to ask the server’s staff to review the evidence. To dispute a Sculk History entry, use My history. Requests about how we process your data go to the privacy channel on the Contact page.