Client strategy doesn't belong in someone else's model.
Keep it on your machine.
Private LLM hosting on a whole dedicated machine in EU-Central, for management and strategy consulting firms that need to draft deliverables without exposing client engagement material to a third-party AI vendor.
Not a substitute for reading the engagement letter. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on any specific client's confidentiality clause. Check the actual clause, or your own counsel's reading of it, before deciding what can run where.
Why firms end up here
Case teams already use AI tools to draft slides and synthesize interview notes. The question is which tools, and where the client's strategy goes while they do it.
Consulting NDAs tend to go further than a typical vendor agreement
A client's confidentiality clause often names specific restrictions on where their information can be processed and by whom, stricter than a standard commercial NDA. Consumer AI products, whose terms may allow retention or review of what's submitted, are a hard sell against that kind of clause. The infrastructure question is separate and answerable: does the machine belong to your firm, and who else can reach it.
"The provider trains on what we submit"
On a GPUwerk instance, the model runs on hardware assigned to your firm alone. 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. There is nothing for us to train on, and no other tenant shares the GPU.
"A competitor's engagement runs through the same vendor"
Consultants routinely work with competing clients on separate engagements. A shared AI vendor processing both raises questions a client's procurement team will ask. A dedicated instance per firm, not per vendor account, keeps that answer simple. See the private ChatGPT setup →
Where firms use it
Draft assistance for case teams, reviewed by the engagement lead before anything reaches a client.
Deliverable drafting
First drafts of slide narratives, synthesis memos, and workstream summaries, built from interview transcripts and client data on the same instance, instead of copying them into a browser tab.
Interview and workshop synthesis
Summarizing stakeholder interviews and workshop notes into themes for the case team to validate, without the transcripts leaving your firm's infrastructure.
Proposal and pitch drafting
First drafts of proposal language grounded in prior work product stored on the instance, kept separate from any client's live engagement data.
What's actually in the contract
For your risk lead or IT director to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your firm |
| 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 engagement material? | 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 firms
Is it safe to put client engagement material into an LLM?
That depends on where the model runs and who can reach it, not on the model itself. On a GPUwerk dedicated instance in EU-Central, the machine is assigned to your firm alone and reachable only through your SSH keys; GPUwerk does not access, read, copy, index or analyse what runs on it except at your request for support or where a legal obligation requires it. This describes our infrastructure, not your obligations under a client's NDA or engagement letter, which are for your own counsel to assess.
Does GPUwerk train on the engagement material we process?
No. GPUwerk operates infrastructure, not models. Your documents are processed by software you install on your own instance, and under our data processing agreement GPUwerk does not access that content except at your request for support or where legally required. There is nothing for GPUwerk to train on.
Do you sign a DPA covering client engagement data?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge. There are no sub-processors for instance workloads, listed at /legal/sub-processors.
Does this satisfy a specific client's data-handling clause?
No. This page describes our infrastructure and standard contract terms, not a review of any specific client's engagement letter or data clause. Check the actual clause against what's described here, or against your own counsel's reading of it, before relying on this for a given engagement.
Related pages
Talk to us before you commit a workflow to it.
A short call covers what runs where, who can see it, and what a given client's clause still requires.
Talk to us Deploy an instance