LLM hosting a Luxembourg data protection officer can sign off on.
Dedicated single-tenant infrastructure in EU-Central, operated by an EU entity with no US parent in the chain, and the paperwork your DPO and compliance team will want before production data, including client or fund data, touches it.
Not legal advice. This page describes GPUwerk's infrastructure, corporate structure, and contractual commitments. Whether it satisfies your specific obligations under Luxembourg or EU data protection law, or any sector-specific rules that apply to regulated financial entities, is a question for your own data protection officer or legal counsel, not for this website.
What a Luxembourg buyer actually checks first
Luxembourg's economy runs on financial services and fund administration more than most EU member states, so a vendor evaluation here often has both a data protection officer and a compliance function in the room, sometimes with an outsourcing or third-party risk framework layered on top of ordinary GDPR review. Three questions tend to come first regardless of which team is asking.
Where does the data sit?
On a dedicated machine in EU-Central, in the Czech Republic. It's not a region toggle in a US console; it's a specific rack, and the operating company is a Societas Europaea registered in Prague with no US parent.
Who is the vendor, legally?
PRINT IT! SE. Company details, including the address and the competent supervisory authority for GPUwerk's own processing, are published at /legal/imprint. This is a Czech entity, not a Luxembourg one, so GPUwerk itself is not subject to oversight by the CNPD, the same way any other EU-Central vendor you'd work with wouldn't be.
Can procurement get the paperwork?
Yes. A standard Art. 28 GDPR data processing agreement is at /legal/dpa, and there are no sub-processors on instance workloads, listed at /legal/sub-processors. No certifications such as ISO 27001 are claimed; if one is required under your firm's own outsourcing policy, ask before assuming it applies.
Fund administration and financial services adds a layer
If your firm is a regulated entity under CSSF supervision, an LLM hosting decision may fall under your outsourcing policy in addition to GDPR, which typically means a documented risk assessment before any vendor touches client or fund data, regardless of where that vendor sits in the EU. GPUwerk's role here is limited to what it can state factually: single-tenant infrastructure, an EU operating entity, no sub-processors on instance workloads, and a standard DPA. Whether that combination satisfies your specific outsourcing framework is a determination for your compliance function to make, not this page. See private LLM hosting for financial services for the sector-specific version of this discussion.
The general landscape, stated plainly
Luxembourg's national supervisory authority is the CNPD (Commission Nationale pour la Protection des Données), based in Luxembourg City, and it oversees data protection compliance for companies established or processing data in Luxembourg. GPUwerk isn't a Luxembourg entity and isn't overseen by the CNPD; it's overseen by the competent Czech authority instead, the same as any other EU-Central vendor. What GPUwerk can state factually: the infrastructure runs in EU-Central under an EU entity, GDPR and the EU AI Act apply to processing done there the same way they apply anywhere else in the Union, and a standard Art. 28 DPA is available so your own DPO can run their normal review. Beyond that, how Luxembourg's implementing legislation, or CSSF outsourcing rules where they apply, interact with your specific use case is a question for your own counsel, not a hosting vendor's marketing page.
For the compliance file
The facts to check against your own checklist.
| Question | Answer |
|---|---|
| Operating entity | PRINT IT! SE, Societas Europaea, Altajská 1568/2, Vršovice, 100 00 Praha 10, Czech Republic |
| Where is data physically processed? | EU-Central, on a dedicated single-tenant machine assigned to you |
| US CLOUD Act exposure? | None. No US parent, no US region, no US-incorporated entity in the chain. |
| Pricing | $0.79/hour for a single DGX Spark, $1.79/hour for a two-node cluster (128GB unified memory each) |
| Who can access instance content? | Through the instance itself, only holders of your SSH keys; password login is disabled fleet-wide. GPUwerk keeps standard infrastructure administrator access, and under the DPA does not use it on your content except at your request for support or where a legal obligation requires it. |
| Sub-processors for the workload? | None, listed at /legal/sub-processors |
| DPA (Art. 28 GDPR)? | Published at /legal/dpa, no charge |
| Certifications held | None claimed, including ISO 27001. Confirm directly if your outsourcing policy requires one. |
Questions we get from Luxembourg buyers
Where is the hardware located?
EU-Central, in the Czech Republic, roughly the same distance from Luxembourg City as Frankfurt or Munich, well within the low-latency range most Luxembourg offices see from any EU-Central provider.
Which authority is responsible for data protection oversight?
GPUwerk is operated by PRINT IT! SE, registered in Prague, so the competent Czech supervisory authority applies to GPUwerk directly. Your own company's processing is separately overseen by the CNPD (Commission Nationale pour la Protection des Données) in Luxembourg, the way it would be regardless of which EU vendor you hosted with. That's a question for your own data protection officer, not something GPUwerk can answer on your behalf.
Is a DPA available under Art. 28 GDPR?
Yes, published at /legal/dpa at no charge. There are no sub-processors for instance workloads, listed at /legal/sub-processors.
Is this legal advice?
No. This page describes GPUwerk's infrastructure and corporate structure. Whether it satisfies your specific compliance obligations, including any sector-specific rules from the CSSF, is a question for your own data protection officer or legal counsel.
Related pages
Send your DPO's questions our way.
We'll tell you plainly what's covered and what isn't, before it goes into a contract.
Talk to us Deploy an instance