dBase title="Privacy Policy: Jigwright" description="Jigwright collects no data from HullForge. It transmits nothing and contacts no servers." > dsection class="datum pt-12 sm:pt-16"> dp class="annotation">Jigwrightd/p> dh1 class="mt-5 text-[clamp(1.875rem,4vw,3rem)] font-extrabold text-scribe"> Privacy Policy d/h1> dp class="mt-4 font-mono text-[0.8125rem] text-alloy-dim"> Last updated 16 August 2026 d/p> d/section> ddiv class="scribe my-12 sm:my-14">d/div> ddiv class="prose-body max-w-2xl pb-8"> dp class="lede"> HullForge collects no data, transmits no data, and contacts no servers. d/p> dp> It is a local bridge between Claude and an Unreal Engine editor running on the same machine. All communication happens over the loopback interface (dcode>127.0.0.1d/code>). No component of HullForge makes an outbound network connection, and there is no Jigwright server anywhere to receive one. d/p> dh2>What HullForge processesd/h2> dp> To do its job, HullForge reads and writes data inside your Unreal project: asset names and paths, property values, level contents, Blueprint and PCG graph structure, editor log output, and viewport screenshots when you ask for one. d/p> dp> dstrong >This data is processed locally and passed only to the Claude client that asked for it.d/strong > HullForge does not copy, retain, aggregate, or forward it. d/p> dp> Your conversation with Claude is governed by da href="https://www.anthropic.com/legal/privacy" rel="noopener">Anthropic's Privacy Policyd/a >. That relationship is between you and Anthropic, and Jigwright is not a party to it. Be aware that anything a tool returns, whether an asset name, a screenshot, or a log line, becomes part of that conversation exactly as if you had typed it. d/p> dh2>What HullForge stores on diskd/h2> dp> Two kinds of file, both local and both removable. One inside your project at dcode>Saved/HullForge/session.jsond/code>, and one under dcode >%LOCALAPPDATA%/HullForge/sessions/d/code >. Each holds a port number, a random session token, the project name and path, and a process id. d/p> dp> They exist so a client can find a running editor without configuration. They contain no personal information and no project content. Both are deleted when the editor closes, and stale entries are swept on the next startup. Deleting them by hand is safe. d/p> dp> HullForge also keeps a short rolling buffer of recent editor log lines dstrong >in memoryd/strong > so they can be returned by its log tool. It is bounded, never written to disk, and discarded when the editor closes. d/p> dh2>Third partiesd/h2> dp> None. HullForge has no analytics, no telemetry, no crash reporting, no licensing check, and no update check. It bundles no third-party service. d/p> dh2>Data retentiond/h2> dp> Jigwright retains nothing. The session files described above are deleted when the editor closes. d/p> dh2>Securityd/h2> dp> The bridge binds to loopback only and is not reachable from other machines. A random token is generated per editor session, and clients must present it. That token is stored in plaintext in the session files. d/p> dp> This protects against accidental connections, dstrong >not against a hostile user already logged into your machined/strong >. Anyone running as your account can read those files and reach dcode >127.0.0.1d/code > regardless. HullForge is not a security boundary against local attackers, and is not intended as one. d/p> dp> HullForge deliberately does not expose an arbitrary code execution tool. Every capability is a specific, typed operation. d/p> dh2>Childrend/h2> dp> HullForge is a developer tool and is not directed at children. d/p> dh2>Changesd/h2> dp> Material changes to this policy will be published on this page with the date above updated. d/p> dh2>Contactd/h2> dp> Questions about this policy or about HullForge's data handling: da href="mailto:support@jigwright.com">support@jigwright.comd/a >. d/p> d/div> d/Base>