Your data

Creator runs on your machine and keeps everything there. Nothing you make leaves your PC. This page lists what can send anything, 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.

Creator needs an active Crucible license; see Licenses and account. What the license check involves is set out in the license terms.

Four things can send something. The license check runs by itself; the other three wait for you:

What	When it sends	What it sends
The license check	Each time Creator starts, and once for each new version.	Your license key and a device identifier, to the payment and licensing provider and, for a new version, to Crucible’s store service. Finding those services may use public DNS services, which see only the address being looked up.
SEND FEEDBACK and SEND REPORT (in HELP, on the ABOUT tab)	Only when you press SEND in one of them.	What you typed and the version line. No name is attached. SEND REPORT adds the support bundle described below. It is posted in the #feedback forum on Discord, where the Creator team and the other members of that server can read it.
The relay (for browser LLM clients)	Only after you type a relay address and press PAIR. Off unless you run your own relay.	Only if you pair a relay.
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; it stays on your PC and is never reachable from the internet, and Creator holds no LLM account of its own. Creator reads your Rust content from your own Steam install, and a private copy, if you make one, is copied from that same install; neither touches the 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), whether tooltips show, whether the walk readout shows, the last Mirror Duplicate axis, the map image colors you changed, the paths of your recently opened maps, whether Creator reads Rust’s files from your Rust install or from a private copy, the last Rust build the “Rust has updated” notice named, and the last Rust build whose prefab changes the “Rust updated” note named or you hid. No passwords, no keys.
Private copy of Rust’s files (optional)	%LOCALAPPDATA%\Rook\Creator\content\	Empty unless you make a private copy. A copy is Rust’s own art, copied from your install, about 50 GB per copy.
Prefab lists of Rust builds	%LOCALAPPDATA%\Rook\Creator\catalog\	One small text file per Rust build Creator has opened: Rust’s own prefab ids and paths, nothing of yours. Creator compares a new build with the last one to show what a Rust update changed and to check a map before you save it. It keeps the four newest of each Steam branch and deletes the rest by itself.
Relay keys	%LOCALAPPDATA%\Rook\Creator\relay\	Settings for pairing the relay.
Recipes	%LOCALAPPDATA%\Rook\Creator\recipes\	Generation recipes you or your LLM saved.
Scatter presets	%LOCALAPPDATA%\Rook\Creator\scatter\	The scatter presets you saved: a list of prefabs and the rules for placing them.
Reference file places	%LOCALAPPDATA%\Rook\Creator\references.json	Where the reference models of your prefab packs are on this PC: for each pack that has one outside its own folder, the pack’s full path and the file’s full path. It is written when you save such a pack and never leaves this PC. The pack’s own companion file holds the file’s name and never a folder. Entries for a pack that is no longer on disk are dropped the next time the file is written.
Sockets, agreement record	%LOCALAPPDATA%\Rook\Creator\	Socket definitions you authored, and a note that this PC accepted the agreement.
New-map scratch file	%LOCALAPPDATA%\Rook\Creator\scratch\<number>\Untitled.map	The blank starting island a new or generated map opens before it is built. One file per open Creator window. Your map is written to your maps folder when you save it.
Queue folders	Documents\Creator\Maps\<queue name>\, or the folder you choose	What a queue of generations made: the maps it kept, a picture of each, and queue.json, the queue’s record of its seeds, settings and results. Yours to keep or delete.
Run reports	Beside a map you saved, as <map name>.report.json	What the generation that made the map did: its size, seed and settings (which can include the path of a heightmap file you imported), what it placed, and what it could not place and why. Written when you save a map generated in this session. Yours to keep or delete.
Copies for Crucible Local Server	output\creator\ inside the Crucible launcher’s folder	Copies of your maps made when you choose FILE > Test in Crucible Local Server…: the map, and its sidecar and server settings file when it has them. A sidecar can hold the settings a map was generated with, which can include the path of a heightmap file you imported. Testing the same map again replaces its copy. Yours to keep or delete.
The launcher’s agreement record	config\settings.json inside the Crucible launcher’s folder	When you accept the launcher’s license agreement in Creator, Creator writes that agreement’s date into the launcher’s own settings file, so the launcher does not ask you again. Every other setting in that file is the launcher’s and stays exactly as it was. Creator never creates the file.
Setup files	Where you save them	The generation settings you exported with EXPORT SETUP. A setup made on a heightmap you imported names that file’s path. Yours to keep, share or delete.
Last queue settings	%LOCALAPPDATA%\Rook\Creator\queue\last.json	The settings of the last queue you started, so the next one starts from them. Replaced by your next queue.
Quit record	%LOCALAPPDATA%\Rook\Creator\quit-trail\	A few lines per Creator window saying how far it got while closing. Nothing of yours. Creator clears old ones itself.
Generation timing records	%LOCALAPPDATA%\Rook\Creator\genprofile\	How long each step of a generation took and the memory it used, with the map size and the seed. Creator clears old ones itself.
Autosaves and crash copies	<persistent data>\Autosave\	Copies of your map, and a crash report when something goes wrong.
Screenshots	Pictures\Creator	The F12 viewport shots.
Map images	Beside your map for the Map Overview’s EXPORT PNG; wherever you save them for FILE > Export Map Image…	Pictures of your map from above. Creator never deletes them. See The map overview.
Diagnostic runs, support bundles	Desktop\CreatorDiag\ and Desktop\Creator-support-*.zip	What you make with F9, with HELP > CREATE SUPPORT BUNDLE and with HELP > SEND REPORT. A bundle leaves your PC only when you press SEND in SEND REPORT or post it yourself; see below.
Layer files	The folder you choose in TOOLS > Layer Files…, by default <map name>-layers beside the map	The layer files you exported: each terrain layer of that map as images and as exact files, a manifest listing them, and, when you export them, the map’s paths and prefabs as paths.json, prefabs.json and prefabs.csv. Creator never deletes them.
Validation reports	Desktop\CreatorDiag\validate\, or the folder you choose	A Map Validator report you saved: <map>.validation.txt and .json, each finding with the game’s own prefab path and a world position. The map is named by its file name only, never its folders.
Comparison reports	Desktop\CreatorDiag\compare\, or the folder you choose	A Compare Maps report you saved: <name>.compare.txt and .json, each difference with the game’s own prefab path and a world position. Each map is named by its file name only, never its folders.

<persistent data> is %USERPROFILE%\AppData\LocalLow\Rook\Creator. Before 0.1.8 three of these folders had other names. The first start of 0.1.8 renames two of them, with nothing copied and nothing for you to do; where your files live says which, and what is left behind.

What a support bundle contains

A support bundle is a zip on your own Desktop that you send if you choose to, by posting it yourself or by pressing SEND in HELP > SEND REPORT. It holds the build and content versions, your GPU and memory, which map you had open (its name and size, 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.

Your Windows user name, license keys and tokens are removed.

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 map still opens in RustEdit for whoever owns it. Creator never shows or sends a RustEdit map’s password.

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

How to delete everything

Removing Creator is removing folders.

1. Delete %LOCALAPPDATA%\Rook\Creator. That is any private copy of Rust’s files (the big one), your relay settings, your recipes, your sockets and the prefab lists of Rust builds.
2. Delete %USERPROFILE%\AppData\LocalLow\Rook\Creator. That is the autosaves, the crash copies and the logs.
3. Delete Pictures\Creator and Desktop\CreatorDiag if you want the screenshots and diagnostic runs gone. If you used a version before 0.1.8, the folders it left under their older names are listed in where your files live; delete those too.
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.