Unpublished findings are worth more before the report ships.
Don't hand a draft to someone else's model.
Private LLM hosting on a dedicated machine in EU-Central, for market research firms running survey response coding, transcript analysis, or report drafting without sending respondent data and unpublished client findings through a third-party AI vendor.
Not legal advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your obligations to respondents or research clients, or on what a specific panel agreement or client contract permits. Check with your own legal or research ethics team before deciding what can run where.
Where an LLM fits into a research workflow
Research work moves through several stages that all involve either respondent data, client-confidential findings, or both, before anything is published.
Survey response coding
Coding open-ended responses into themes at a scale that would take a coding team days by hand. The raw responses can include identifying detail from respondents who were told their answers would be handled by the research firm, not forwarded to a third-party AI vendor they never agreed to.
Transcript analysis
Pulling themes and quotes out of qualitative interview or focus group transcripts. Participants in a research study are typically promised confidentiality as a condition of taking part, which makes the choice of where that transcript is processed a direct commitment to the people who gave you their time.
Report drafting
Turning coded data and analysis notes into a first draft of a client deliverable. A commissioning client's category insights and unpublished findings are exactly the kind of thing they're paying for exclusivity on, which is undermined the moment a draft passes through infrastructure shared with other firms' work.
Why a dedicated instance instead of a shared API
A research project's respondent data, coding scheme, and client deliverable all pass through related steps, often on the same files. Sending that through a shared AI API means trusting a vendor's retention and access policy with respondent confidentiality promises and client-exclusive findings at once. A dedicated GPUwerk instance keeps the raw transcripts, the coding output, and the draft report on a machine assigned to your firm alone, with no other agency's project data anywhere near it and GPUwerk not accessing workload content except at your request for support or where a legal obligation requires it.
What's actually in the contract
For your research operations lead or IT lead 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 see respondent or client 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. |
| Pricing | Spark-1x from $0.79/hour on demand, billed per minute; Spark-2x from $1.79/hour. A customer-requested stop holds the reservation at 75% of the running rate. See /pricing for full detail. |
Questions we get from research teams
Can we run client survey and interview data through an LLM?
That depends on where the model runs and who can reach it, not 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. Whether a given respondent panel or client contract permits this use is for your own legal or research ethics team to confirm.
Does GPUwerk see our respondent data or unpublished findings?
No. GPUwerk operates infrastructure, not models. Survey responses, interview transcripts, and draft reports processed on your instance are handled by software you install, and under our data processing agreement GPUwerk does not access that content except at your request for support or where legally required.
Do you sign a DPA covering respondent and client data?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge, and there are no sub-processors for instance workloads.
Does GPUwerk train on our data?
No. GPUwerk runs infrastructure, not models. There is nothing for GPUwerk to train on, since we do not access instance content except as described in the DPA.
Related reading
Private LLM hosting for consulting firms · Private AI for research and literature review · Private AI for meeting transcription
Related pages
Keep respondent data and unpublished findings off someone else's servers.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance