Privacy policy

Draft — pending legal review. This text is not yet a published legal policy. Square brackets mark facts the owner has still to supply.

Who we are

The service is run by [Legal entity name and registration: being finalised] ("Sculk", "we"). For privacy requests write to [Privacy requests contact: contact details are being finalised]. This policy covers sculkac.com, the dashboard, the Discord bot, the player pages (appeals, My history, Verify) and the Sculk resource that runs on a game server. It applies from [Policy effective date: being finalised].

The plain-language table of every kind of data, how long we keep it and who sees it is on What we store and why. If this policy and that page ever differ, tell us at the privacy contact above and we will fix the one that is wrong.

Two roles

  • Sculk as controller. For your account, billing, support requests, and Sculk History (a record kept across Sculk servers), we decide what is kept and why.
  • Sculk as processor. For what a server owner's game servers send us (detection events, cases, bans, player lists, appeals), the server owner's organisation is the controller and Sculk processes the data for it, under the data processing agreement.

If you are a player and want to know what a particular server holds about you, ask that server's staff. We can pass a request on.

What we collect and why

Server owners and staff. Name, email address, sign-in credentials (a password hash, passkeys, authenticator secret), sessions with the IP address and browser they were made from, organisation membership and role, and an audit log of changes made. We use it to run your account and keep it secure.

Billing. Stripe takes payment. We keep Stripe's customer and subscription references, the plan, and the billing period. We never see or store a full card number.

Game server data. Detection events, cases, evidence summaries and screenshots, bans, appeals, player display names and character names, and identifiers that let a server recognise the same player again. Identifiers (licence, Steam, Discord, hardware tokens) are stored as keyed hashes with a short display mask, not as readable values. IP addresses are hashed: a hash of a full address is kept 24 hours, and a hash of the surrounding /24 range is kept 30 days.

Sculk History. When a server opts in, a confirmed cheating entry about a player can be shared with other servers that opt in. Entries match on hashes of the licence, license2, fivem and steam identifiers only. Never used: hardware tokens, IP addresses, or Discord data.

Sculk Verify. If a server turns on Verify, a player signs in with Discord and consents. We keep keyed hashes and the account's creation day, never the Discord id.

Support. Tickets and their transcripts, with the customer's Discord id and name.

Website. Cookies needed for sign-in and security. We do not run advertising trackers.

How long we keep it

Retention periods are set in code and removed by scheduled jobs, not by this text alone. The main periods:

  • Detection events: 90 days (180 on Pro and Network plans). Evidence screenshots: 30 days.
  • Cases and their evidence summaries: 1 year after closing. Bans: while in force plus 1 year.
  • Sculk History entries: expire after 2 years for cheating and 6 months for others, then are deleted 180 days later. An overturned entry is removed from other servers immediately.
  • Sign-in sessions: 30 days after they expire. Audit log: life of the organisation.
  • AI conversations: 90 days, with names replaced by tokens. Token counts and cost: 2 years.
  • Support tickets: 1 year after closing.
  • Fraud and accuracy records: the record of a ban that turned out to be a false positive is kept for the life of the organisation. A count of each Sculk History deny, used for our transparency report, is kept 2 years.
  • When an organisation stops being a customer, we delete its data within [Days to delete a former customer data after review: being finalised] days after review, subject to the law. This is done by a person, not automatically. Financial records may have to be kept longer where the law requires it.

The full list is on What we store and why.

Sub-processors

We use these providers to run the service:

ProviderWhat forWhere
StripePayments, invoices, refunds and disputesSee Stripe's own policy
ResendSending account and lifecycle emailSee Resend's own policy
DiscordVerify sign-in, the Discord bot and linked rolesUnited States and elsewhere; see Discord's own policy
Cloudflare (R2 storage and network proxy)Storing evidence screenshots, builds and encrypted backups; proxying traffic to the site and APISee Cloudflare's own policy
Our virtual server hostRuns the database and application servers[Virtual server host name and region: being finalised]
DeepSeekThe AI features (Sculky, the Case Analyst and support answers), only after your organisation owner opts inPeople's Republic of China

DeepSeek, in full. The AI features (Sculky, the Case Analyst and support answers) are off until your organisation owner turns it on at a consent screen. When it is on, the text of the conversation 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, we replace the names we know for your organisation with tokens. A name we do not know is sent exactly as typed, so do not type names or personal details that are not already in your Sculk records. We never send identifiers (raw or hashed), IP addresses, hardware tokens, emails, Discord ids, payment data, chat text or screenshots. How long DeepSeek keeps what it receives is set by DeepSeek's own policy and is outside our control. If your owner does not opt in, nothing goes to DeepSeek.

We will list any new sub-processor here before it handles personal data.

International transfers

Some providers above process data outside your country, including the People's Republic of China for DeepSeek (opt-in only). Where the law requires a transfer mechanism, such as standard contractual clauses, we rely on it.

Your rights

Depending on where you live, you can ask to see, correct, delete, restrict or move your data, and to object to how we use it.

Players. On My history, after you prove an identifier, you can download a file of your data and ask for deletion. The download shows your Sculk History entries and disputes, your sign-in sessions on the portal, and, per organisation, only a count of what each holds. Deleting removes your portal sessions, entries that are expired or overturned, and the text of closed disputes straight away. An accurate, active entry stays until it expires, and the answer tells you why. If anything is kept, or a server holds data about you, we queue a request for our staff and answer within a month. You can dispute any History entry about you on the same page. Sculk Verify links are seen and deleted on the verify site's own privacy page.

Server owners. You can erase one player from your servers in the dashboard (this needs a recent authenticator check). For anything else, such as exporting or deleting your organisation's data, write to the privacy contact.

Everyone. Write to [Privacy requests contact: contact details are being finalised]. You may also complain to your data protection authority.

Automated decisions

Some actions happen without a person approving them first. Each detection has a confidence class fixed in code that caps the strongest action it can take on its own. Deterministic checks can go up to a permanent ban. Strong checks can go up to a kick, and up to a temporary ban only with a second independent signal of a different family. Statistical and client signals can only warn and send the case to staff, and prevention cancels an event without acting on the player. The AI assistant never bans, unbans or applies a change by itself. Sculk History can deny a player entry to a server that chose that policy, only on confirmed, active cheating entries and never on any other kind, and a disputed entry stops denying until the dispute is decided. You can ask for a person to review any automated action: use the appeals link a server gave you, or write to the privacy contact. The full disclosure is on What we store and why.

Security

Data is encrypted in transit. Identifiers are hashed with keys held separately from the data. Backups are encrypted. Staff access is by role and is logged. We tell affected customers about a breach as the law requires.

Children

The service is for server owners and the adults who staff them. Players of a game server may be of any age the game allows. The server owner decides who may play and is responsible for lawful use of Sculk on their server.

Changes

We will publish changes here with a new effective date, and tell account holders by email when a change matters.