← LoreLynx

Your words are yours

What we do, and deliberately do not do, with your writing

Writers are right to be suspicious of tools with AI in them. So here is the whole deal, in plain language, with nothing buried in a terms document.

Our stance on writing with AI

We believe AI belongs in writing as an aid, not an author. It is genuinely useful for the work around the words: filing your lore, cross-linking your codex, catching continuity slips, helping you get unstuck. We do not recommend using it to write your prose outright. The voice that makes a story worth reading is yours, and no model has one.

We know it is a little hypocritical to say that while shipping an AI drafting feature. But our job is to provide every tool a writer could want and leave the choice of which ones to use where it belongs, with you. If AI drafts are part of your process, treat them as scaffolding: argue with them, rework them, overwrite them. The words you keep should be yours.

That choice is built into the app itself. Every feature you do not want is a toggle away: switch it off and it disappears from your workspace entirely, not grayed out, gone. Switch it back on whenever you like. You are in full control of which tools you ever see.

We never train on your writing

Your manuscripts, lore, and notes are not used to train any AI model, not by us and not through us. We do not sell your content, license it, or share it with third parties. Your work exists in LoreLynx for exactly one purpose: so you can keep writing it.

AI is optional, and off means off

Every feature of LoreLynx works with AI disabled: the story planner, the prose editor, the codex, maps, timelines, exports, all of it. If you never connect a provider, nothing you write is ever sent to any AI, anywhere. There is no hidden analysis, no background processing, no fine print.

Or keep the AI on your own machine

LoreLynx treats local AI as a first-class option, not an afterthought. Connect LM Studio or Ollama running on your computer and every AI request stays on your hardware. Your prose never crosses the internet at all.

Your API keys stay on your device

If you use a cloud provider (OpenAI, Anthropic, Mistral, Gemini, OpenRouter), you bring your own key. Keys are stored encrypted in your browser and are never saved on our servers. When you use an AI feature, your request goes to the provider you chose under your own account, subject to their privacy terms, and we do not store the content of those requests.

Mark anything as off-limits to AI

Any passage of prose and any codex entry can be excluded from AI context. Excluded material is stripped out before anything is sent to a model, even when AI features are on. Spoilers, private notes, and unfinished ideas stay between you and the page. You can also see exactly what was sent with any generation via the context breakdown.

Take everything with you, any time

Your whole project exports in one click: the manuscript as PDF, DOCX, EPUB, or Markdown, and the entire project (lore, codex, outline, maps, timeline, prose) as a single JSON file you can back up, inspect, or re-import. There is no lock-in and no export paywall.

Backups you control

Besides cloud sync, LoreLynx automatically keeps recent snapshots of your project on your own device. You can download or restore them from Settings without needing our servers at all.

Sharing is read-only and revocable

Share links show readers your prose and chapter structure, nothing more. Your planning notes, summaries, beats, and drafts are never exposed through a share link, and you can revoke any link whenever you like. A codex entry reaches readers only when you publish it yourself, one entry at a time, to your book's World page on the feed; your notes never do.

Delete means delete

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

The fine print, minimized

The formal versions of these promises live in the Privacy Policy and Terms. If anything here ever seems out of step with how the app behaves, tell us. That would be a bug, and we treat it like one.