Your data

Creator runs on your machine and keeps everything there. The only thing it sends on its own is the license check below; everything else waits for an action of yours. This page lists what sends anything, what it sends, and where everything is stored so you can read it or delete it yourself.

Creator sends no telemetry

No analytics, no usage reporting, no crash upload, no heartbeat, no “anonymous statistics”. There is no code in Creator that reports what you do with it.

The license check. Each time Creator starts, it checks your Crucible license with Lemon Squeezy, the store that sells it, exactly as Crucible Heightmap does: it sends your license key and this PC’s activation ID, and reads back only whether the license is valid and which product it is for, never your name or email. It uses the license the Crucible launcher saved when you activated, so it works however you start Creator. Offline, it keeps working for 3 days from the last successful check. See Licenses and account. Entering a key in Creator’s license window activates this PC with Lemon Squeezy, which sends the key and your PC’s name, as the launcher does.

Beyond that, two things can send something, and each one waits for you:

What	When it sends	What it sends
The relay (for browser LLM clients)	Only after you type a relay address and press PAIR. The alpha hosts no relay, so this is off unless you run your own.	MCP messages between your LLM client and Creator. It carries no map data of its own.
A documentation link	Only when you click one in the HELP menu.	Nothing. It hands the address to your browser; Creator fetches nothing.

Everything else is local. The CONNECT server that lets Claude Desktop and Claude Code drive Creator listens on 127.0.0.1, which is your own machine and nothing else: no port is opened to your network or to the internet, and Creator holds no LLM account of its own. Syncing your Rust content copies files from your own Steam install and touches no network.

What is stored, and where

Where your files live is the full list of folders. This table is the same set read a different way: what each thing holds, and whether it is sensitive.

What	Where	Holds
Your maps	Wherever you save them	Your work. Creator never copies a map anywhere else on its own.
Settings	The Windows registry, under HKEY_CURRENT_USER\Software\Rook\Creator	Preferences and window sizes: camera speed, keyboard shortcuts, view toggles, graphics choices, snap settings (including the tunnel-grid snap and the gizmo’s local or world space), the paths of your recently opened maps, and the last Rust build the “Rust has updated” notice named. No passwords, no keys.
Content snapshot	%LOCALAPPDATA%\RustCreator\content\	Rust’s own art, copied from your install. About 50 GB per snapshot. Beside it, a small list of monument names Creator has read off Rust’s own prefabs, so the monument list in Creator Mode reads in the game’s words.
License	The Crucible launcher’s own license file, which Creator reads and updates (encrypted by Windows for your user). A copy of Creator the launcher did not install keeps it in %LOCALAPPDATA%\RustCreator\crucible-license.json.	Your license key, this PC’s activation ID and when it was last checked.
Relay keys	%LOCALAPPDATA%\RustCreator\relay\	A key pair for “remember this PC”, generated here and never sent anywhere, plus the relay address you typed.
Recipes	%LOCALAPPDATA%\RustCreator\recipes\	Generation recipes you or your LLM saved.
Sockets, agreement record	%LOCALAPPDATA%\RustCreator\	Socket definitions you authored, and a note that this PC accepted the agreement.
New-map scratch file	%LOCALAPPDATA%\RustCreator\scratch\<number>\Untitled.map	The blank starting island a new or generated map opens before it is built. One file per open Creator window, in a folder named for that window’s process number with a small owner.lock beside it while the window is open. It is replaced by that window’s next new map and removed when Creator next starts after the window has closed, never while it is open. Your map is written to your maps folder when you save it.
Quit record	%LOCALAPPDATA%\RustCreator\quit-trail\<number>.txt	A few lines per Creator window, named for its process number, noting each step it took while closing, so a crash on the way out says how far it got. Step names, the version, the process number and an exit code: nothing of yours. Creator keeps the newest 64 and deletes older ones when it starts.
Autosaves and crash copies	<persistent data>\Autosave\	Copies of your map, and a crash report when something goes wrong.
Screenshots	Pictures\Rust Creator	The F12 viewport shots.
Diagnostic runs, support bundles	Desktop\RustCreatorDiag\ and Desktop\Creator-support-*.zip	What you make with F9 and with HELP > CREATE SUPPORT BUNDLE. Nothing is uploaded; see below.

<persistent data> is %USERPROFILE%\AppData\LocalLow\Rook\Creator. The folders that still read RustCreator and Rust Creator are the same app, kept under their old names so an update does not strand your settings and snapshots; where your files live explains it.

What a support bundle contains

A support bundle is a zip on your own Desktop that you send if you choose to. It holds the build and content versions, your GPU and memory, which map you had open (its path, size, prefab count and a hash of the file, never the map itself), the newest diagnostic report, the newest crash report, the head and tail of the session logs, the names of your saved preferences with no values, and the warnings Creator showed you.

Two kinds of thing are removed before anything is written:

• Paths, so your Windows user name and folder layout become placeholders like %USERPROFILE%.
• Keys, so a license key, a CONNECT server token or a relay pairing code is replaced by its length: -license=<redacted:36 chars>. That tells support a key was present without publishing it.

Crash reports written beside your autosaves go through the same pass, because their own message asks you to attach them. Every file in the bundle says at the top that this happened, so a <redacted:36 chars> is recognisable as deliberate and not as a corrupt file.

Your maps and your screenshots are never collected automatically. If a map matters to a bug, you attach it yourself.

Caution

A support bundle is meant to be read. It carries your log, which includes the folder names of what you opened and any message Creator printed. Open the zip and look through it before you post it anywhere public.

Map passwords in RustEdit maps

A map made in RustEdit can carry an edit password. Creator keeps it and never shows it: the bytes are carried through load and save unchanged, so the map still opens in RustEdit for whoever owns it, and nothing in Creator displays, logs, prints or sends the password. The MAP DATA panel lists it like every other block in the file, showing its name and its size in bytes and never its contents. It is not in a support bundle, not in a diagnostic report, and not available to an LLM through CONNECT.

That is deliberate: the password usually belongs to somebody else, whoever made the map you downloaded.

How to delete everything

Creator has no uninstaller step that phones home, so removing it is removing folders.

1. Delete %LOCALAPPDATA%\RustCreator. That is the content snapshot (the big one), your relay keys, your recipes and your sockets.
2. Delete %USERPROFILE%\AppData\LocalLow\Rook\Creator. That is the autosaves, the crash copies and the logs.
3. Delete Pictures\Rust Creator and Desktop\RustCreatorDiag if you want the screenshots and diagnostic runs gone.
4. Delete the HKEY_CURRENT_USER\Software\Rook\Creator registry key to clear your preferences. Skipping this leaves settings behind and nothing else.
5. Your maps are wherever you saved them, and Creator never touches them again. Keep or delete them yourself.

To free a PC from your license, use Deactivate in the Crucible launcher’s Account panel: see Licenses and account.