Our policy for creators

If your game is in our compendium, you decide what AI is allowed near your text. Every AI feature that can touch it is listed below, and any of them can be switched off for your game — individually, or all of them.

A switch on this page exists because a game's rights holder asked us to throw it. A few exist for our own reasons instead — usually licensing or a technical limit — and those say so.

What a switch actually does

It stops the feature from running on your content. Not hides the button — stops the work. The switches are enforced in our backend, at the point where text would otherwise leave our servers, including the bulk jobs that process a catalog overnight and the copy-on-write path that fires when a game master edits one of your entries at their own table.

A build check fails if someone adds a new way to send a game's text to a model without consulting these switches first, and a test asserts that a switched-off game makes no outbound call at all. That's the part we can prove rather than promise.

What can be switched off

Some of these write something and keep it; the rest only read your entries while answering a question at someone's table.

These write something and keep it

  • Entry summaries. Reads an entry and writes a short summary of it, plus a description of what it looks like.
  • Meaning-based search. Reads entry text so search can match on meaning rather than exact words. With this off, search still works — it matches words instead.
  • Entry artwork. Draws a picture for an entry from its description.

These read your entries and keep nothing

  • Rules answers. Answers a rules question by reading the relevant entries and explaining them.
  • Character-creation help. Reads a game's character options to help a player build a character.
  • Scene drafting. Reads a game's places, threats, and factions to draft a scene for the table.
  • At-the-table suggestions. Reads entries mid-session to suggest what might happen next.
  • Recap detail. Reads entries the table encountered so a session recap can say what they were.
  • Encounter balance. Reads stat blocks to judge whether a fight is a fair one.
  • Writing help in notes. Reads entries a note refers to while helping a GM finish or tidy that note.
  • Search result ordering. Reads candidate entries to put the most relevant one first. With this off, results are ordered by score alone.

Switches in use

Loading the current switch record…

What these switches don't cover

They govern your content, not a table's own. A group's session recordings, their recaps, and portraits of the characters they invented are theirs, and they are governed by that group's own AI settings rather than by yours. Switching your game's features off doesn't reach into anyone's private campaign, and it was never meant to.

Our wider commitments — that we never train models on anyone's content, and that the product works with AI switched off entirely — are on the AI policy page. Licensing and attribution for everything in the compendium is on the legal page.

Changelog

This page gets a dated entry for every substantive change, because the record is the only reason to believe any of it.

  • 2026-08-11: Some technical consolidation around how we manage these switches internally.
  • 2026-07-27: First published, with per-feature switches enforced in the backend and Stonetop switched off across the board.
If you hold the rights to a game and want any of this changed for it, write to hello@narrative.sh and tell us which switches you want off. We'll do it and say so here.