Incident reports and client site details.
Not something to type into a shared chatbot.
Private LLM hosting on a dedicated machine in EU-Central, for security guard companies drafting incident reports, summarizing patrol logs, or building shift schedules on a machine assigned to your company alone.
Not legal or compliance advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your obligations as a security guard company, and it is not a claim of any specific certification on GPUwerk's behalf. Check with your own advisor before deciding what can run where. See also private LLM hosting for property management for the client-site side, and private LLM hosting for staffing agencies for the roster and scheduling side.
Where an LLM fits into a security guard company's office
This is about reporting and scheduling behind the desk, not decisions made by a guard on post.
Incident report drafting
Turning a guard's handwritten or dictated notes on an incident, time, location, people involved, actions taken, into a structured report in the format your client expects. That report names people and describes an event at a specific client site, exactly the kind of record most companies would rather not send to a shared vendor's servers.
Patrol log summarization
Rolling a week of checkpoint scans and patrol notes into a short summary for a client's monthly report, so an account manager isn't manually compiling logs from every site before every meeting.
Shift scheduling
Turning a roster of guard availability, site coverage requirements, and licensing constraints into a draft schedule, then drafting the shift confirmation messages that go out to each guard. See the private AI shift scheduling guide →
On certifications and compliance frameworks
GPUwerk has not published ISO 27001, SOC 2, or any other formal certification, and this page makes no claim that hosting on GPUwerk satisfies any specific data protection or licensing regulation on its own. What GPUwerk provides is a dedicated single-tenant machine, a published GDPR Article 28 DPA with no sub-processors for instance workloads, and a documented answer to who can reach the machine and what happens to data on termination. If your compliance program requires a specific framework, that gives your own advisor a concrete starting point to assess against your requirements, not a substitute for the assessment itself.
What's actually in the contract
For your operations manager or IT contact to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your company |
| 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 incident and site 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 |
| Certifications? | None published (no ISO 27001 or SOC 2 claimed). Assess against your own compliance requirements. |
| 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 security guard companies
Is it safe to put incident reports and site details into 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 company 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 incident or client data meets your own regulatory obligations is for your own advisor to confirm.
Is GPUwerk certified for handling security incident records?
GPUwerk has not published ISO 27001, SOC 2, or similar certifications. If your compliance program requires a certified provider or a specific control framework, a dedicated single-tenant instance with a published DPA and no sub-processors gives you a documented starting point to assess against your own requirements, not a substitute for that assessment.
Do you sign a DPA covering client site and incident 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 incident reports?
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 property management · Private LLM hosting for staffing agencies · Private AI for shift scheduling
Related pages
Keep incident records 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