Home Privacy
Privacy
This page is written to describe what the software actually does. If the code and the page ever disagree, the code is the bug and the page gets fixed the same day, not the other way round.
The game
Campaign data, transcripts, characters, world state, dice and their seeds, in one SQLite file in your application data directory. The engine binds to loopback only, so it is not reachable from your network. A cloned voice is recorded on your machine and never uploaded, and deleting a campaign deletes its synthesised speech from the cache.
Only what you configure, and only to where you point it. A local model: nothing. Your own key: directly from your machine to that provider, under their terms, with no middle step. Your key lives in your operating system's secret store, never in a config file. One honest exception: bringing a rulebook can send pages of your own copy, once, to the model endpoint you configured, so the engine can propose its system. Switch that pass off and the book is read entirely on your machine. An ingested book is never redistributed either way.
None ships today and none is enabled by default. If it is ever added it will be opt-in and carry counts only: never transcript content, never character names, never anything you typed.
The website
No cookies, no analytics, no fingerprinting, no pixels, no cookie banner because there is nothing to consent to. The site is static files: pages, styles, scripts and images.
Two things by nature of being a website: the pages themselves, and two fonts from Google Fonts, which your browser may cache. Nothing else is fetched from anywhere. The theme you pick is stored in your own browser's local storage and goes nowhere.
Exports are plain Markdown and the database is ordinary SQLite, so your campaigns are yours to copy, back up, read or delete. Nothing is proprietary and nothing is locked.
The rule this page lives by
The project's own privacy documentation is written to describe what the code does, and when the two drift, the code is the bug. The same rule binds this page: if a feature ever changes this story, this page changes in the same release, or the release waits.
LOOM