Trust

Three things leave your machine, and you set off all three yourself.

Your campaign is a local database file on your disk. When you ask for a draft, the context that draft needs goes to Anthropic. When your campaign is indexed so the app can recall it, six layers go to Voyage AI, and two of those are not invented fiction: your session records and your private DM notes. When you import a PDF, the book's text goes off your machine too. Neither vendor trains on any of it, though the Voyage side of that has a date on it and one real caveat. The full account is on the privacy page.

Stays on your machine

  • your campaign database file
  • every NPC, location, session log and note
  • your exports
  • campaign search, which reads the database directly
  • your AI usage count

Never exists: a cloud copy of your world, an account holding your campaign, a licence check phoning home.

Leaves your machine

You set these off

  1. Ask for a draft to Anthropic the slice of context that draft needs. No training, 30-day default deletion. No account or campaign identifier attached.
  2. Index for recall to Voyage AI six layers: Core, RelationshipWeb, ThematicFingerprint, TemporalContext, and SessionContext and DmAnnotations, which are your session records and your private notes rather than invented fiction. No training or retention after 13 August 2026. Runs when you press Regenerate in Settings, when you use Ask Campaign, or as part of generating. Not on save, not on a timer.
  3. Import a PDF to Anthropic the full text of the book. The file stays local; the text does not.

These happen on their own, and carry no campaign data

  1. Update check, seconds after launch to an Amazon S3 bucket the request and nothing else.
  2. Fonts, when the window opens to Google Fonts four typefaces. Google sees your IP, as any web request would.

Full export, built in

verified 2026-07-02

Full campaign export (JSON, Markdown wiki-style with links, and CSV) ships today via the Export Campaign wizard. Your world is portable from day one.

Verify it yourself: Settings → Export Campaign, try it on day one

The sunset promise

If Campaign Familiar ever winds down, a bring-your-own-key build is released so the app never goes dark. Your database keeps working either way, because it's a file on your disk.

What telemetry exists

verified 2026-08-13

None. There is no analytics, no crash reporting, and no usage report in the app. There is no licence check phoning home either: your AI usage is counted in the local database so you can see it in Settings, and that count stays on your disk. Two things do leave on their own and neither carries campaign data: the update check a few seconds after launch, and the four typefaces the window loads from Google Fonts. This website uses Fathom Analytics: aggregate visit counts, no cookies, no cross-site tracking, and nothing that identifies you kept past a short anonymising window, which is why there is no consent banner to click. The precise version is on the privacy page.

Verify it yourself: the itemised account is on /privacy, written against a manifest of every outbound call in the app

The app works forever without a subscription

Organizing, browsing, editing, and search never require a subscription. The subscription only powers generation.

Antivirus that inspects encrypted traffic doesn't break it

verified 2026-08-14

Many antivirus products, and most corporate networks, inspect encrypted traffic by sitting between the app and the vendor. Campaign Familiar keeps working: it checks certificates against your operating system's own trust store, which is where those products install themselves. You will never be asked to turn your antivirus off to use this app. An earlier version of this page said the opposite; it was written from an assumption rather than a test, and the test says otherwise.

Verify it yourself: tested against live Norton HTTPS scanning, on all four of the app's network paths

Questions this page doesn't answer? Write to me, and you'll get a straight answer.