Lorekeeper privacy policy

Last updated: 7 October 2026

Lorekeeper is a free, open-source desktop app for keeping D&D session notes. It is made by Yonatan Karp-Rudin (yonvata@gmail.com). The source code is at github.com/yonatankarp/lorekeeper.

The short version

Lorekeeper has no accounts and no analytics. Your notes stay on your computer, unless you share a campaign with your party: then it syncs through a Lorekeeper sync server, end-to-end encrypted, so the server can't read it. If you turn on a backup, they go straight from your computer to your own Dropbox, Google Drive or GitHub account, and nowhere else. If you sign in to D&D Beyond, Lorekeeper only reads the characters you import from there; your notes are never sent to D&D Beyond.

What Lorekeeper stores

• Your notes are plain text files in the folder you choose on your computer (by default Documents/Lorekeeper). Each session's notes file records your computer's UTC offset when it's made (for example utc-offset: +02:00), so notes show in the right order and time zone.
• Settings are stored in the app's configuration folder on your computer.
• Thumbnails of the pictures in your notes, for the connections map, are kept in the app's cache folder on your computer, outside your notes folder.
• Sign-in tokens for the backups you turn on, your D&D Beyond sign-in session if you sign in there, and the keys and tokens of shared campaigns, are stored in your system's password storage (macOS Keychain, Windows Credential Manager or the Secret Service on Linux). They are only ever sent to the service they belong to.

Nothing is sent to the developer. Lorekeeper does not collect usage data, crash reports or personal information.

Backups to Dropbox, Google Drive and GitHub

Backups are optional and off until you sign in. When you do, Lorekeeper uploads your notes from your computer directly to your own account:

• Dropbox: Lorekeeper can only access its own folder, Apps/Lorekeeper.
• Google Drive: Lorekeeper uses the drive.file permission, so it can only see and change files it created itself, in a Lorekeeper folder with a folder for each campaign. It cannot see the rest of your Drive.
• GitHub: Lorekeeper creates a private repository called lorekeeper-notes in your account and backs up each campaign to a folder in it. GitHub's sign-in grants access to your repositories in general; Lorekeeper only uses the repository it created for your notes.

Lorekeeper only uses this access to back up your notes and, when you click Restore, to download that backup to your computer. It does not read other data, and nothing is shared with, sold to or used by anyone else, including the developer.

Lorekeeper's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Characters from D&D Beyond

Importing characters is optional. When you sign in to D&D Beyond in Settings, you sign in on D&D Beyond's own page, so your password goes to D&D Beyond and never to Lorekeeper. Lorekeeper keeps the sign-in session D&D Beyond gives it in your system's password storage, sends it only to D&D Beyond, and uses it only to read the characters (and campaign pages) you import or refresh. What it reads is written into your PC pages on your computer; nothing goes to anyone else.

Shared campaigns

Sharing a campaign with your party is optional. A shared campaign syncs through a Lorekeeper sync server: by default lorekeeper.yonatankarp.com, run by the developer, or another server an invite link points to (Lorekeeper shows which before you join).

• End-to-end encrypted: notes, images, file names, the campaign's name and players' character names are encrypted on your computer with the campaign's key before they're sent. The key is made on the sharing player's computer and travels only inside invite links (in the part after #, which never reaches the server). The server stores and passes on encrypted data it can't read.
• Your time zone: your session notes files carry your UTC offset (see above), so your party sees your notes in order and at the right time in their own time zone. It's inside the encrypted files, so your party can see it (and, in your private notes, whoever reads those), but the server can't.
• What the server sees: that a campaign exists, how many files it has and how big they are, when they change, which member wrote a private file, and the IP addresses of the computers that connect. Lorekeeper stays connected for each of your shared campaigns while it runs, whichever campaign you have open, so the server and that campaign's party (who see who's online) can tell when Lorekeeper is running on your computer. Other members can't read your private notes, but can tell when someone in the campaign wrote one. It keeps no logs of notes, keys, tokens or invites.
• Private notes: notes in a shared campaign's Private folder (and quick notes starting with ~) are synced encrypted like everything else and served only to you, on your computers, or to you and the campaign's DMs if its owner allows it (the app always shows which). Your teammates never receive them, and neither does the campaign's owner, unless the owner has said they're the DM. The owner decides who is a DM (and a DM who manages players can invite more), so "you and the DM" means whoever holds the DM role at the time. Making a shared note private doesn't take back the copies other players already synced. The server owner could in principle access the database, but can't decrypt anything in it without the campaign's key, which never reaches the server. Removing a player deletes their private notes from the server. Whoever redeems a re-invite for you becomes you in that campaign, private notes included, so the owner or a DM who manages players could in principle read them that way; you'd see "Signed in on another computer".
• One campaign per folder: a shared campaign never sends the folder of another of your campaigns kept inside it (as older versions kept the first campaign in the Lorekeeper folder, which holds the folders of campaigns made or joined since), private notes included.
• Secrets: the campaign's key, your sign-in token for it, and the server's creation key (if you share a campaign) are stored only in your system's password storage, never in settings or notes, and only ever sent to that server (the key never is).
• Invite links in a browser: opening an invite link shows a page from that sync server. The page's script hands the link to Lorekeeper on your computer (a lorekeeper:// link, which your browser may ask before opening), and its Open in Lorekeeper button does the same. The key stays in the part after # and isn't sent anywhere else. Lorekeeper then shows which server the invite is for and joins only when you click Join.
• When the campaign's owner removes you, stops sharing, or you leave or remove a joined campaign from Lorekeeper, its token is deleted from your computer; your notes stay.
• Leaving deletes your private notes in that campaign from the server. Stop sharing (the owner) deletes the whole campaign from the server: every file, everyone's private notes, members and invites.

Other network requests

• Updates: Lorekeeper checks GitHub for new versions once a day. Like any web request, GitHub sees your IP address. You can turn this off in Settings.
• Links you click open in your browser.

Removing access and data

• Sign out of a backup in Settings > Backups, or of D&D Beyond in Settings > General. This deletes the stored token or session from your computer.
• You can also revoke Lorekeeper's access in your Google account, Dropbox settings or GitHub settings.
• Backed-up notes stay in your own account until you delete them there.
• A campaign you share stays on the sync server until you Stop sharing it (Settings > General > Party…), which deletes it there. Delete campaign moves a campaign's folder to your system's Trash; for a campaign you share it offers to stop sharing first.
• Uninstalling Lorekeeper leaves your notes folder in place; delete it yourself if you want.

Changes

If this policy changes, the new version will be published here with a new date.

Contact

Questions: yonvata@gmail.com or open an issue.