Product copy, reviews, and support tickets carry your catalog and your customers.
Keep both off a shared API.
Private LLM hosting on a dedicated machine in EU-Central, for online retailers running product description generation, review summarization, or customer support without routing catalog data and customer messages 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 for customer personal data or your rights over your own catalog and pricing strategy. Check with your own legal or privacy team before deciding what can run where.
Where an LLM fits into a storefront
Online retail generates a steady stream of text work that is well suited to an LLM and, in most shops, still done by hand or sent through a public tool with no review of what data went along with it.
Product description generation
Turning a spreadsheet of attributes, supplier copy, and variant data into consistent, on-brand listing copy at catalog scale. The source data is often supplier-confidential and the output needs to match a house style, which makes a general-purpose chat tool with no memory of your last thousand listings a poor fit anyway.
Review summarization
Rolling hundreds of reviews per SKU into a short summary of what customers actually say, for merchandising or supplier feedback. Review text can include names, order details, and complaints, which is customer personal data the moment it is tied to an identifiable buyer.
Customer support
Drafting responses, summarizing a ticket thread, or triaging incoming messages by intent. Support conversations routinely include order numbers, addresses, and payment disputes, all of which are more comfortably kept off a shared vendor's servers. See the private AI customer support guide →
Why a dedicated instance instead of a shared API
Sending catalog data, reviews, and support tickets to a shared AI API means every prompt leaves your infrastructure and lands on hardware you don't control, subject to a vendor's own retention and access policy. A dedicated GPUwerk instance runs the model on a machine assigned to your business alone: no other retailer's traffic shares the GPU, and GPUwerk does not access, read, copy, index or analyse your workload content except at your request for support or where a legal obligation requires it. The trade-off is real: you run and maintain the inference stack yourself, or with our help during a first-engagement rollout, rather than calling someone else's endpoint.
What's actually in the contract
For your privacy lead or IT lead to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your business |
| 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 catalog or customer 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 online retailers
Can we run product catalog and order data through an LLM safely?
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 business 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 specific use of order or customer data has a valid GDPR basis is for your own legal or privacy team to confirm.
Does GPUwerk see our catalog, pricing, or customer support transcripts?
No. GPUwerk operates infrastructure, not models. Product data, pricing logic, and support transcripts 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 customer order and support 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 retail and e-commerce (customer analytics and pricing) · Private AI for customer support · Private AI for support ticket triage
Related pages
Keep the catalog and the customer file 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