Local data

• Generated region state is saved as local JSON when you use Save JSON, and inside the vault under state/ when you export.
• Vault files are written only into folders you picked in that session, and existing files are never plainly overwritten — an entry must be a merge, an explicit overwrite, or skip-if-exists.
• Last-used settings are stored locally so your setup survives a restart.

Local AI

• The director passes are optional. When enabled, the desktop app sends those requests to a model running on your machine — either the app's bundled llama.cpp runtime or a provider you run yourself, such as Ollama, LM Studio, or llama.cpp.
• If you use the bundled runtime, the one-time model download fetches the model file from the internet after you approve its size and license. Generation requests themselves never leave your machine.
• Director actions use a constrained set of validated operations with narrowly scoped permissions over the region state. They cannot touch anything else.
• The in-app update check contacts the public release feed to compare versions; it installs nothing without you.

DFRPG content boundary

• The bundled DFRPG-facing data uses structural data, tags, references, and original content to support table prep. Published rules text and stat blocks remain in their source books, which you should still use at the table.
• Encounter and lair shortlists reference the free public monster library by id; the library's own licensing and credits are published with the library.

This site

• These pages are static files. The site sets no cookies and runs no analytics script.
• The releases page reads the public GitHub release feed to show current file sizes and dates; that request goes to GitHub from your browser, subject to GitHub's own terms.