Why Local?

Your writing stays on your computer.

StoryBook AI is built around a simple idea: your stories, ideas and AI conversations belong to you. Nothing is sent to StoryBook servers — because there aren't any.

100% local by design

StoryBook itself does not send your manuscript, notes, Story Bible or AI conversations to external services. There is no telemetry, analytics, tracking, cloud sync or automatic update check in the application.

Fonts and example assets are bundled with the app, and AI runs against a local model on your own computer or network using the endpoint you configure.

Manuscript stored locally
Story Bible stored locally
No telemetry or analytics
No external fonts or CDNs
No cloud sync
Only your configured AI endpoint

Local means local

StoryBook does not call home. It does not send analytics, load Google Fonts, fetch interface assets from a CDN or upload your writing. The application uses local browser storage and communicates with the AI endpoint you configure.

What StoryBook does not claim

“100% local” describes StoryBook's application code and data flow. It does not mean your entire computer makes zero network connections while StoryBook is open. Chromium, the operating system, browser extensions and other software can make their own connections.

Why this matters for writers

Local-first is not just a privacy checkbox. It changes the relationship between the writing tool and your manuscript. StoryBook does not need a StoryBook account, a credit balance or a cloud workspace to function. Your project remains yours to keep and work with locally.

The same principle extends to AI: the writing assistant can run on hardware you control, using models you choose.

Can I verify this myself?

Yes. StoryBook AI is open source. The source code is available for inspection, including the network layer and local-model configuration.

View source on GitHub →