FAQ

No. The story planner, prose editor, codex, maps, timelines, kanban board, and every export work with AI disabled. If you never connect a provider, nothing you write is ever sent to any AI, anywhere. The AI features are an opt-in layer, not the foundation.

Convenience, not creation. The AI exists to save you time on the tedious parts: it pulls characters, factions, and locations out of messy lore dumps and files them in your codex, cross-links entries, extracts timeline events, catches plot holes, and answers questions about your own world. It can draft a starting point from a scene summary you wrote, grounded in your codex, but LoreLynx is built for writers who want organization and convenience from AI, not a machine that writes their book.

Locally: LM Studio and Ollama, both first-class. Everything runs on your own hardware and your prose never crosses the internet. In the cloud, bring your own key for OpenAI, Anthropic, Mistral, Gemini, or OpenRouter. Keys are stored encrypted on your device, never on our servers.

No. Your manuscripts, lore, and notes are never used to train any model, not by us and not through us. We also do not sell or license your content. The full promise is spelled out on the Your Words page.

Only you, unless you choose otherwise. Projects sync to your account and are isolated from every other account. You can invite specific people into a project by email, as co-writing editors or as read-only beta readers, and you can change their role or remove them at any time. Share links are read-only, show prose and chapter structure only (never your notes or drafts), and can be revoked at any time. Publishing to the public book feed is a separate, explicit action, and even then only released chapters are shared, plus any codex entries you choose to put on the book's World page, picked entry by entry with spoilers held back until the chapter you set is out.

Yes. Any scene, passage, or codex field can be marked as excluded from AI, and excluded material is stripped before anything is sent to a model, even when AI features are on. Every generation also comes with a context breakdown showing exactly what was included, so you never have to guess.

Generations are grounded in your canon. LoreLynx assembles context from your codex (pinned entries, entities linked to the scene, and names it detects in your text) and instructs the model to use only established characters and places, never to invent new ones. The context breakdown shows you what was sent with every generation.

Always, in one click. Manuscripts export as PDF, DOCX, EPUB, or Markdown, the Project Bible compiles your codex, lore, timeline, and outline into Markdown, PDF, or DOCX, and the whole project (lore, codex, outline, timeline, prose) exports as a single JSON file you can back up or re-import. LoreLynx also keeps recent snapshots on your own device. There is no export paywall and no lock-in.

Yes. Collections group related books and share a codex, core canon, and a series timeline across them, so book three knows what book one established. Each book keeps its own outline and manuscript.

Deleting your account removes your projects, prose, lore, images, and account data from our systems. It is a real delete, not a soft one, and there is no retention period on your creative work.

LoreLynx is built for desktop browsers, where a planning and writing workspace has room to breathe. The site pages and reading published books on the feed work well on phones, and a fully responsive app is on the radar as the beta matures. For planning, worldbuilding, and writing, use a laptop or desktop.

One person. LoreLynx is designed, built, and maintained by a solo developer, a senior software engineer with a passion for fantasy novels who wanted a worldbuilding tool that treats writers with respect: craft tools first, AI for convenience, and privacy promises simple enough to actually keep. There is no growth team and no engagement metrics to feed. The upside for you is a short feedback loop: the person reading bug reports is the same person who wrote the code, and the roadmap is shaped by what writers ask for.