Private LLM hosting for companies in Australia.
Dedicated NVIDIA DGX Spark hardware in EU-Central, run by a Czech company, for teams in Australia who want inference workloads on a dedicated, single-tenant machine rather than a shared US API. This is a statement about where the hardware sits and who has access to it, not a GDPR compliance claim.
Not legal advice, and not a GDPR compliance claim. Australia is not an EU or EEA member. GDPR does not apply to an Australia-registered company by default. This page describes where GPUwerk's hardware sits and who operates it; it does not tell you whether GDPR, the Privacy Act 1988, or some other framework applies to your business. Confirm that with your own counsel before treating this as a compliance answer.
Why dedicated infrastructure matters, with or without a GDPR requirement
A company in Sydney, Melbourne, or Brisbane working with client records, contracts, or proprietary source code often has a straightforward reason to avoid routing prompts through a third-party US API: the data leaves the building and lands on shared, multi-tenant infrastructure operated by a vendor with its own terms and its own government's legal reach. A dedicated DGX Spark node in EU-Central, running a model you choose, keeps prompts and outputs on hardware assigned to you alone. Nothing about that requires an EU or GDPR justification; it's a straightforward infrastructure and access-control decision.
Where does the data sit?
On a dedicated machine in EU-Central. Nothing routes through a US inference API or a shared multi-tenant pool.
Who operates it?
PRINT IT! SE, a Societas Europaea registered in Prague, Czech Republic. Company details at /legal/imprint.
Does the Privacy Act 1988 apply here?
Australia's Privacy Act 1988, and the Australian Privacy Principles within it, govern personal information handled by many Australian organisations, with oversight from the OAIC. Whether and how it governs your use of an EU-based processor is a question for a lawyer familiar with Australian privacy law, not this page.
Dedicated hardware vs. a shared API
Australia is not an EU or EEA member, so GDPR does not bind an Australian company by default. If your company handles personal data belonging to EU residents, that data may fall under GDPR regardless of where your company is registered, but that is a fact-specific question this page cannot answer for you. Confirm that with your own counsel before treating any part of this page as a compliance determination. Separately from that question, a company handling client contracts, financial records, or anything sensitive has a plain infrastructure reason to prefer a single-tenant GPU node over a shared US API: your prompts don't sit in a request queue alongside other tenants' traffic, and the operator can't retrain a model on your inputs by default, because the model and the hardware are yours for the duration of the reservation.
For the compliance file
The facts to check against your own checklist, not a substitute for your own legal review.
| Question | Answer |
|---|---|
| Operating entity | PRINT IT! SE, Societas Europaea, Prague, Czech Republic |
| Where is data physically processed? | EU-Central, on a dedicated single-tenant machine assigned to you |
| Supervisory authority for GPUwerk | Czech Office for Personal Data Protection (ÚOOÚ) |
| Does GDPR apply to your company by default? | No. Confirm with your own counsel whether an EU nexus applies to your specific processing |
| Does Australia's Privacy Act apply to your company? | Depends on your organisation's size and sector; confirm scope with your own counsel and OAIC guidance |
| US CLOUD Act exposure for GPUwerk infrastructure? | 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); a customer-requested stop holds the reservation at 75% of the running rate |
| DPA available? | Yes, at /legal/dpa. Confirm fit with your counsel |
Questions we get from buyers in Australia
Does GDPR apply to a company registered in Australia?
Not by default. Australia is not an EU or EEA member, so GDPR does not automatically apply to an Australian company. Australia has its own framework, the Privacy Act 1988 and the APPs, overseen by the OAIC. Whether GDPR applies to any specific processing you do depends on facts your own counsel should assess.
Why would a company in Australia use an EU-hosted LLM provider?
Common reasons include EU or UK clients who ask where data is processed, and a preference for keeping prompts off shared US hyperscaler infrastructure and on dedicated, single-tenant hardware. Neither is a GDPR compliance claim on GPUwerk's part; it's a statement about where the hardware physically sits.
Is a DPA available?
Yes, a standard Art. 28 GDPR-style data processing agreement is published at /legal/dpa. Whether it fits your obligations under the Privacy Act is a question for your own counsel.
Is this legal advice?
No. This page describes GPUwerk's infrastructure and corporate structure only. It makes no claim about your compliance obligations under Australian law, GDPR, or any other framework.
Related pages
Dedicated infrastructure, no shared US API in the loop.
A single-tenant node in EU-Central, at a fixed hourly rate.
Talk to us Deploy an instanceSee also: dedicated vs. shared GPU, data sovereignty vs. data residency, the private LLM hosting overview, and full pricing.