An unreleased game is a leak waiting to happen.
Don't hand the script to someone else's model.
Private LLM hosting on a dedicated machine in EU-Central, for game studios working with narrative drafts, dialogue, playtest feedback, or community moderation data that shouldn't sit on shared AI infrastructure.
Not legal advice. This page describes GPUwerk's infrastructure and contractual commitments only. Whether a given use of unreleased game content or playtester data is permitted under your publisher agreement, NDAs, and applicable regulation is a determination for your own studio leadership and legal counsel.
Three ways unreleased content leaves the building, one shared answer
A leaked plot twist or an early screenshot can flatten a marketing beat months before launch, and a shared AI vendor's retention policy is one more place that content can end up. All three raise the same infrastructure question before anything else: where does the model actually run.
"Writers use LLMs to draft and iterate on dialogue and branching narrative"
Generating dialogue variants or fleshing out a branch tree is exactly the kind of repetitive, high-volume work an LLM helps with, and exactly the kind of content a leak site would want early. On a GPUwerk instance, the machine is assigned to your studio alone, in EU-Central. GPUwerk operates the machine but, under the data processing agreement, does not access your content except at your request for support or where a legal obligation requires it.
"Playtest feedback needs summarising across hundreds of sessions"
Aggregating open-ended playtester comments is useful, and it can include personal data from testers alongside unreleased build details. A dedicated single-tenant machine means no other tenant's workload, and no vendor model training, is anywhere near that dataset.
"Community managers already paste chat logs into consumer AI tools for moderation help"
Asking a public AI tool to help triage or summarise flagged community chat is common, and rarely reviewed for what unreleased content or user data went in alongside it. A sanctioned alternative on your own instance, same chat interface, keeps that workflow off third-party infrastructure. See the private ChatGPT setup →
What's actually in the contract
For your studio's IT, legal, or production lead to review directly. This is a description of infrastructure, not a certification record.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your studio |
| Who operates it? | PRINT IT! SE, a Societas Europaea registered in Prague, Czech Republic. No US parent entity. |
| Who can reach the instance? | Through the instance itself, only holders of your SSH keys; password login is disabled fleet-wide. GPUwerk keeps infrastructure administrator access to the underlying machine, as on any hosted service, and under the DPA does not use it on your content except at your request for support or where a legal obligation requires it. |
| Does GPUwerk read scripts, narrative drafts, or playtest data? | No. We host the hardware and, under the DPA, do not access, read, copy, index or analyse workload content. |
| Sub-processors for the workload? | None, listed at /legal/sub-processors |
| DPA (GDPR Art. 28)? | Published at /legal/dpa, no charge |
| Data on termination? | Container and workspace volume deleted from the node, then the node is sanitised before reassignment. Filesystem deletion, not a cryptographic erase; export what you need before terminating, since it isn't reversible. |
Questions we get from game studios
Can we run unreleased narrative and dialogue scripts through an LLM here?
On a dedicated GPUwerk instance, the machine is assigned to your studio alone, in EU-Central, and GPUwerk does not access, read, copy, index or analyse workload content except at your request for support or where a legal obligation requires it. Whether a given script is cleared under your own confidentiality and publisher agreements to be processed on any external infrastructure is a separate question for your studio's leadership and legal counsel.
Does GPUwerk train on our game content?
No. GPUwerk operates infrastructure, not models. Whatever you run on your instance is your software and your data, and under our data processing agreement GPUwerk does not access that content except at your request for support or where legally required.
Is this suitable for playtest feedback that includes tester personal data?
GDPR still applies to any personal data in playtest feedback, regardless of where you process it. A dedicated instance with an Article 28 DPA covers the infrastructure side; the analysis, retention, and consent basis for that feedback is a decision for your own studio and, if you use one, your data protection officer.
Do you sign a DPA?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge, and there are no sub-processors for instance workloads.
Related pages
Put the unreleased build on hardware your own team controls.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance