Legal

Privacy Policy

What FiveDock collects, why, who else sees it and how long we keep it, including the things we deliberately cannot see, because they are encrypted with a key we do not hold.

In effect since September 7, 2026

1.Who is responsible, and for what

FiveDock plays two roles at once, and nearly everything below follows from which one applies.

We are the controller: of the data about you: the account you signed up with, the plan you are on, the emails we send you, the log of your visits to fivedock.dev. We decide why and how that is processed, and this policy is our answer for it.
We are a processor: of the data your server sends us: your files, your players’ identifiers, the events in your Black Box, the rows the database tools read. Your city decides why that data exists and what happens to it, and we act on your instructions. Questions about why it was collected are for the city to answer.

Controller: SDN Ventures LLC
Privacy contact: [email protected]

2.What we collect

We collect what the service needs and nothing more. There is no analytics product on this site, no advertising network, and no profile of you being sold to anybody.

Account: Your email address, display name, the language you chose, and the account identifier from Discord if you signed in with it. There is no password: sign-in is a link we email you, or Discord.
Billing: Which plan you are on and whether it is paid. Card details, billing addresses and tax numbers go to Skalp, the merchant of record, and never reach us.
What your server uploads: The files, screenshots and clips your scripts and your players send us, plus the folder, size and checksum we need in order to store them and to notice a duplicate.
What the agent reports: Error traces, performance samples, the resources and assets on disk, deploy and restart events, the structure of your database, the rows a staff member with the right role asked to see, and the encrypted backups themselves.
Technical: IP address, browser and device, and which pages you opened on fivedock.dev, in server logs, kept briefly, and not assembled into a profile.
What you write to us: Support email, and the content reports anyone can send from the report page. A report asks for a link and a reason. It does not ask who you are, and we do not keep the sender’s address.

3.Your players’ data

Black Box, the database tools and the CDN necessarily touch data about real people who never signed up with us: in-game identifiers, a Steam or Discord hex, an IP address in a connection log, a screenshot with a character and sometimes a face in it. Your city is the controller of all of it. We hold it for you, under these rules:

We process it to run the service and on your instructions. We do not mine it, sell it, or use it to build anything of our own.
Identifiers are masked by role. A support-level staff member sees a shortened form; seeing the whole thing takes an elevated role and leaves a record of who looked.
Events, screenshots and logs fall out of the system on the retention your plan sets, or earlier if you delete them.
You can export a player’s data from the panel as an evidence package. To delete it, write to [email protected]. There is no self-service button for that yet. If a player writes to us directly we point them at your city, because you are the one who has to answer them.

If your city needs a signed data-processing agreement, write to [email protected] and we will send one. Most European cities do, and it is worth having whether or not anybody asks you for it.

4.Why we process it, and on what basis

For readers in the EU and the UK, and everywhere that has copied the framework:

Purpose	Legal basis (GDPR)
Running your account, hosting and serving your files, keeping the backups you asked for	Performance of a contract, Art. 6(1)(b)
Knowing which plan you are on and enforcing its limits	Performance of a contract, Art. 6(1)(b)
Rate limits, abuse handling, fraud prevention, keeping the platform standing	Legitimate interest, Art. 6(1)(f)
Answering you, and telling you about incidents and changes to your service	Performance of a contract, and legitimate interest
Keeping the records we are required to keep, and answering a lawful request	Legal obligation, Art. 6(1)(c)
Product news, and anything that is not about your service	Consent, Art. 6(1)(a). Withdrawn with one click

We do not sell personal data, we do not share it for advertising, and nothing about your account is decided by an automated system on its own.

6.What we cannot see

Some of this is how the system is built, so it is not a policy we could change on our own.

Your backups. They are encrypted on your machine, with your key, before they are uploaded. What we hold is ciphertext. We cannot read it, and we cannot produce its contents for anybody who asks us to, because there is nothing to produce.
Your database password. It never leaves your machine. The agent connects to your database locally; what reaches us is the answer to a specific question a staff member with the right role asked.
Your server. The agent connects out to us and nothing connects in. We cannot reach your machine, and we cannot make it do anything that is not on the fixed list of commands built into the resource.

What we can see is exactly what the agent sends and what your scripts upload. The agent ships as source and runs on your machine, so if this matters to you, read it, or have somebody read it for you.

7.Cookies and analytics

There is no analytics product on this site and no advertising network. We do not know how long you looked at the pricing page. Three things are stored in your browser, all of them because the site does not work without them:

Session: Set when you sign in, so the panel knows it is you. It goes when you sign out.
Active city: Which of your workspaces the panel is showing. It is a preference and it grants nothing: it is checked against what your account may actually see.
Theme and language: Dark or light, and the language you picked, so the site does not forget between visits.

None of them tracks you across other sites, which is why there is no consent banner to click past. If we ever add something that needs one, you will be asked first, and "no" will keep working.

8.Where the data is

We are a United States company. Your files live in Cloudflare’s object storage and are served from whichever edge is nearest your players, which is what a CDN is for. Our own systems (the API, the gateway, the worker and the databases) run with the hosting provider in section 6. When personal data from the EU, the UK or Switzerland goes to a country without an adequacy decision, we rely on the European Commission’s Standard Contractual Clauses with the recipient, alongside encryption in transit and at rest. Ask at [email protected] for a copy of them, or for where a particular system runs.

9.How long we keep it

Retention for your city’s own data is the one your plan sets, and it is on the pricing page. In summary:

Data	How long
Account and workspace	Until you close it, then 30 days
Files you uploaded	Until you delete them; 30 days after the account closes
Encrypted backups	The retention your plan sets, then deleted
Black Box events, screenshots and clips	The retention your plan sets
Server logs and IP addresses	90 days
Content reports and what we decided	2 years

Invoices, and the records tax law requires, live with Skalp on its own retention. Anything not listed above goes when the account does.

10.How it is protected

The main measures:

TLS everywhere, the agent’s connection included. It is refused unless it is encrypted.
The signing keys are split, so that the part of our system which relays a command to your server cannot sign one, and the part that can sign never leaves the API.
A role on every destructive action, a confirmation before it runs, and a second approver available for restores.
An audit trail for every action taken on your city, ours included.

If a breach affects your data we will tell you, and the relevant authority, within the time the law requires, and we will give a full account of what happened.

11.Your rights

Wherever you live, and whether or not the law where you live grants them, you can ask us to:

tell you what we hold about you, and give you a copy of it;
correct anything that is wrong;
delete your account and what belongs to it;
hand your data over in a format you can take somewhere else;
stop processing that rests on our legitimate interest, and withdraw any consent you gave.

Write to [email protected]. We answer within 30 days, 45 for a request under California law, and we may ask you to show the account is yours before we act on it.

You can also complain to a data protection authority: in the EU, the one where you live; in the UK, the ICO.

If you live in California, Virginia, Colorado, Connecticut or another US state with a privacy law, you have the equivalent rights under it, plus the right not to be treated worse for using them. We do not sell or share personal information for cross-context behavioral advertising, so there is nothing there for you to opt out of.

12.Children

FiveDock is a tool for the people who run a server, not a service for children, and you must be at least 16 to hold an account. Players on your city may well be younger. Their data reaches us as a processor, and the responsibility for handling a minor’s data lawfully sits with the city that collected it. If you believe a child’s data reached us and should not have, write to [email protected] and we will remove it.

13.Changes to this policy

We update this policy when what we do changes. The date at the top says when the current version took effect, and for a change that materially affects you we tell you by email or in the panel before it applies.

14.Contact

Privacy requests: [email protected]
Everything else: [email protected]

Also worth reading: Terms of Service.

Questions about this document: [email protected].