Privacy

The hosted service at trylore.xyz is run by Vedaang Singh, and your account and your content live in a Postgres database he runs. If you install Lore yourself from the source, the same tables are created on a database you control and he never sees any of it. The rest of this page says which is which.

All of it sits in one Postgres database, and you can read the schema in lib/db/schema.ts:

• Your account: email address, the name you typed, a scrypt hash of your password, and a session record while you are signed in. If you sign in with Google instead, the account row holds the tokens Google issued.
• Your brands: the handle you connect, the brief you write, the categories and the voice document Lore builds from your posts.
• Posts pulled from X for the handles you connect, with their public like, reply, retweet and view counts.
• Drafts, the edits you make to them, and the rules Lore writes from those edits.
• Interview sessions and the messages in them, chat history with Lore, ideas, notes and files you save to the vault, and any learning report it generates.
• If you link Telegram, the chat id of that conversation so the bot knows where to send briefs.
• Scheduled posts, and a log of background runs and credit usage.

There is no analytics script, no advertising pixel and no third-party tracker on any page. The only cookie is the one that keeps you signed in.

The same tables, on your own Postgres, on whatever machine you point DATABASE_URL at. Nothing in that database is sent anywhere by Lore itself. The two exceptions are the ones below: the model provider you connect, and the shared relay if you use it.

Lore cannot write without a model, and the model is never local. Whatever you connect is where the prompts go: Anthropic if you use Claude or an Anthropic key, OpenAI if you use Codex or an OpenAI key, OpenRouter if you use an OpenRouter key, and OpenRouter passes the call on to whichever model you picked there.

Those prompts carry your drafts, your own posts, your voice document and rules, your interview answers, and any article or thread you asked Lore to read. Once a prompt leaves, that provider handles it under their own terms and their own retention policy, which we have no control over. When you use the Claude Code or Codex CLI, Lore runs it with tools switched off and with DATABASE_URL, AUTH_SECRET and every API key stripped from the environment it gets.

The relay exists so you can try X lookups and voice interviews before paying for keys. It only gets used when you have no key of your own for that feature, and setting LORE_RELAY=off turns it off completely. It receives four things: the X handles and search terms being looked up, the text being read aloud, the voice clips being transcribed, and your install's relay key. It never receives your drafts, your database or your model prompts.

The relay keeps a small row per install: a SHA-256 hash of the key, how many credits are left, daily totals, and a salted hash of the IP address that registered it. Plain IP addresses are not stored. When you unlock the free credits it also stores your X user id and handle, and your GitHub user id and login if the GitHub step is on, so the same account cannot claim starter credits twice.

When you connect a handle, Lore fetches that account's public profile and its public posts going back about six months, through twitterapi.io, with your key or through the relay. It reads them to work out how you write and to show you your own numbers, which is the whole point of the product. It uses no X login and holds no X token, so it cannot read anything a logged-out visitor could not read, and it cannot post. Every draft ends at a Post on X button that opens X with the text filled in, and you press send.

On the hosted service, rows stay until you delete them or delete your account. Deleting a draft, a note or a brand removes it from the database. A copy can survive in a database backup for a while after that, and relay key rows stay until the key is revoked.

On a self-hosted install nothing expires on its own, because it is your database. Running docker compose down -v or dropping the database removes everything.

Hosted: message @vedsayys on X from the account you signed up with, or from an address you can prove is yours, and ask for the account to be deleted. It gets removed within 30 days at the latest, along with the brands, drafts, posts, interviews and notes attached to it. There is no self-serve delete button yet, which is worth knowing before you sign up.

Self-hosted: drop the database, or delete the rows you want gone. To disconnect from the relay, delete the relay key row in instance_settings, or set LORE_RELAY=off.

If this page changes in a way that matters, the date at the top changes with it. Questions about any of it go to @vedsayys. Security problems go through the private advisory form on the repository, covered in SECURITY.md.