Private AI for crisis communications drafting
A drafting model set up on a dedicated machine before an incident lets the comms team iterate on a crisis statement without leaving early drafts in an AI vendor's logs. Those drafts matter because each one says things the company hasn't decided to say yet, whatever the final statement turns out to be.
What a draft holding statement contains
Comms teams often draft a holding statement, or several versions of one, before all the facts of an incident are confirmed: a data breach, a product recall, an executive departure, an accident at a facility. Early drafts tend to include speculation about scope and cause, internal assessments of how bad the situation might be, and language the legal team hasn't cleared yet. If an early draft describing a breach as "affecting an estimated 40,000 accounts, likely including payment data" leaked before the confirmed number was public, that's a worse outcome for the company than the incident itself, because it looks like the company knew more, sooner, than it disclosed.
Using AI for tone, structure or a fast first pass under time pressure is a legitimate use, and crisis response is a writing task where a fast first draft helps. The question is where the draft goes while it's being written.
What changes when drafting runs on a dedicated Spark
Sending a crisis draft to a third-party AI API puts the company's unapproved account of its own crisis on a vendor's systems, under that vendor's retention terms, when the company has the least control over the narrative. Running the drafting model on a dedicated DGX Spark sends every draft, from the first rough pass to the version legal signs off, to your own model on a machine assigned only to you. No AI vendor retention or training policy applies. The Spark is GPUwerk's hardware, operated under its published DPA.
In practice that's Open WebUI as a drafting interface the comms lead uses directly, iterating on tone and structure as with any drafting tool.
Why speed matters here specifically
The first few hours after an incident becomes known often set the tone for how the whole event is covered. A comms lead working through several versions of a holding statement in that window has no time to sort which details are safe for a general-purpose AI tool. In practice everything goes in, speculation and unconfirmed numbers included, because redacting under deadline isn't realistic. A private drafting tool set up before any incident removes that decision from the worst possible moment.
Set it up in advance, not during the incident. With an instance and the comms team's tools already configured, the first draft can start within minutes of the incident being flagged, not after someone requests access to a new AI tool and waits for approval.
A worked example
Say a manufacturing company discovers a defect in a product already shipped. The first internal draft of a customer notice might describe the defect's likely cause before engineering has confirmed it, estimate how many units are affected before a recall scope is set, and include a rough cost estimate for legal to review. None of it is meant for publication. It's a working document to align the team on what the statement needs to cover. If that draft sat in a third-party AI vendor's logs, a data request, a subpoena or a vendor breach could surface a document suggesting the company privately estimated the defect's scope well before its public statements did, even if the estimate was wrong and revised twice. Keeping the drafting history on a dedicated machine removes the AI vendor's copy, so the record is governed by your own retention decisions and the hosting DPA, not a model provider's log policy.
What this doesn't solve
A private model doesn't make a statement legally accurate, doesn't replace review by legal and executive leadership before anything goes out, and doesn't manage who inside the company can see draft versions. That stays an internal access-control question. What it removes is one specific window of exposure: the period between an incident happening and a statement being approved, when the company's own words about itself are at their most sensitive and least final.