Privacy

Last updated 10 September 2026

Who we are

LoreMonkey is operated by Scott Jacobs, a sole trader in Sweden, who is the controller of the personal data described here. Registration number 870923-9175. Bäverdammsgränd 174, 124 63 Bandhagen, Sweden. For anything in this policy, write to hello@loremonkey.com.

What stays on your computer

These parts of LoreMonkey run entirely on your machine and send nothing anywhere:

• Audio. Sound from your table or your Discord call is captured, turned into text, and then discarded. It is never uploaded: not to us, not to our model provider, not to Discord. If you switch session recording on yourself, LoreMonkey also saves the audio as an mp3 in your own LoreMonkey folder; that is off unless you turn it on, and the file is yours to keep or delete like any other. Recording the people at your table is a bigger step than transcribing them, so tell them before you do it.
• Transcripts. The text of your session is written to your own disk, in your LoreMonkey folder. You can read, back up or delete those files yourself.
• Your campaign notes. Character sheets, campaign files and any archive you import stay in that same folder.
• Archive search. When LoreMonkey looks something up from an old session, that search happens locally against your own files.
• Speaker attribution. Working out who is talking uses the Discord client already running on your computer. Nothing joins your voice channel and no audio is sent to Discord by us.

What we receive

The AI features need a model, and the model is not on your computer. When one of them runs, LoreMonkey sends the following to our server, which forwards it to our model provider and returns the answer:

• A recent extract of the session transcript, including the character names you have tagged people with and, for anyone in the call you have not tagged, the name Discord shows for them.
• A compressed version of your campaign and character notes.
• Passages your own archive search picked out as relevant.
• For Ask LoreMonkey, the question you typed and the thread it belongs to.

This happens when LoreMonkey checks whether the moment needs a suggestion, when you ask a question, when you generate context files from your documents, and when you ask for a session recap. It does not happen continuously, and the activity log in the app shows you every time it does.

We use that content to produce the answer and to count usage against your plan. LoreMonkey does not use it to train models, sell it or share it for advertising. Anthropic states that API inputs and outputs are not used for model training by default.

LoreMonkey's server forwards each request without writing its prompt to the account database. One kind of answer is kept, for up to 24 hours: the reply to a memory job (a recap, a session update, generating your context files), so that a retry after a lost connection can be given the same answer instead of running and billing the job twice. It is deleted after that. The server also stores usage metadata: the feature used, model name, token counts, cost, whether a live prompt was delivered, and which campaign and session the call belonged to, by the name you gave the campaign. Under Anthropic's standard API policy, inputs and outputs are deleted from its systems within 30 days. Anthropic lists limited exceptions for legal obligations and usage-policy enforcement.

Your account

We hold the small amount of information an account needs:

• Your email address, and a hashed password if you signed up that way.
• Your Discord or Google account identifier, if you signed in with one of those. We do not get your password from them.
• Which plan you are on and when it renews.
• Counters of how much of your plan you have used this month.
• The dates you confirmed you were 16 or older, and 18 or older.
• A short timeline of the account: plan changes, complimentary access, and a note when the address you connect from moves.
• The IP address you connect from, and the country it indicates. We keep the address you first signed up from and the most recent one, refreshed at most a few times an hour rather than on every request.

We hold the address because an account otherwise arrives as an email address and nothing else. It tells us roughly where our users are, so we can plan for the places people actually play from; it tells us when one person is quietly running several free accounts; and when something breaks for one person and not another, it is often the first useful clue. We do not use it to build a profile of you, we do not sell it, and it is not passed to our model provider with your session content.

Payments

Subscriptions are handled by Stripe. Your card details go to Stripe and never to us. We receive the fact that a payment succeeded, which plan it was for, and when it renews or ends. Stripe processes that data under its own privacy policy.

Who else is involved

• Anthropic receives the text described above in order to generate a response.
• Railway hosts the server that sits between the app and the model.
• Stripe processes payments.
• Google and Discord, only if you choose to sign in with them. If you connect the Discord desktop client for speaker labels, the app also uses Discord's own sign-in for the application you created, from your PC. We receive alerts about the service in a private Discord channel; one of them can carry an IP address that was refused for creating too many accounts in a day.
• GitHub serves the installer and the app's updates. The app asks GitHub for a new version when it starts and a few times a day, which shows GitHub your IP address and nothing else.
• Hugging Face and PyPI serve the speech model and, if you turn it on, the GPU runtime. The app downloads both directly from your PC.
• Cloudflare serves this website and counts its page views.

This website itself sets no cookies and runs no advertising or third party trackers. We use Cloudflare Web Analytics, which counts page views without cookies and without building a profile of you.

Anthropic and Railway are United States companies, so using an AI feature sends the text described above outside the European Economic Area, to a country with different privacy laws. Stripe, Google, Discord, GitHub, Hugging Face and PyPI also process data outside the EEA. Where a transfer needs a safeguard we rely on each provider's own data-processing terms and the EU standard contractual clauses within them. Write to us if you want a copy of the clauses covering a particular transfer, or more detail about it.

Why we are allowed to hold it

Under the GDPR we need a reason for each thing we do with your data. Ours are straightforward. We process your account details and the content you send to an AI feature because we need to in order to give you the service you signed up for. We keep short operational logs, usage counters and the IP address you connect from because we have a legitimate interest in keeping the service working, stopping abuse and billing correctly. If you object to us holding your connection address on that basis, write to us and we will tell you what we hold and remove what we can. We keep payment records because the law requires it.

How long we keep it

Not forever, and not on a schedule invented to sound tidy. What actually happens:

• Your account: email address, hashed password or sign-in identifier, plan and renewal date, the dates you confirmed your age, and the account timeline: until you delete the account. Then it goes.
• The address you connect from: until account deletion, and only ever two of them: the one you signed up from and the most recent one. The recent one is overwritten as you connect, so this is not a history of where you have been.
• Usage metadata: which feature ran, which model, token counts and cost: as long as the account exists, because your allowance and your bill are worked out from it. Deleted with the account.
• The prompts: never written down at all. Our server passes them through.
• The answers: not written down either, except the reply to a memory job, kept for up to 24 hours so a retry is not billed twice, then deleted.
• At Anthropic: deleted from its systems within 30 days under its standard API policy, which lists limited exceptions for legal obligations and usage-policy enforcement.
• Payment records: invoices and the bookkeeping entries behind them for seven years after the end of the financial year they fall in, because Swedish bookkeeping law requires it. This is the one thing that survives account deletion, and the one thing we cannot delete on request.
• Everything on your own computer: for exactly as long as you keep it. Deleting your account does not touch your transcripts, recordings or notes, because we never had them.

Keeping it safe

The app talks to our server over TLS, and this website is served over TLS. Passwords, where you set one rather than signing in with Google or Discord, are stored salted and hashed, never in a form we could read back. Session audio is never uploaded. Prompts are never written to the account database, and answers only as the 24-hour replay copy described above; beyond that it holds account rows and usage counters and nothing else worth stealing.

Plainly: this is a one-person operation rather than a company with a security team, and we would rather say so than imply otherwise. If something does go wrong and a breach is likely to put your rights or freedoms at risk, we will email the people affected and notify IMY within 72 hours, as the GDPR requires.

The other people at your table

LoreMonkey transcribes a conversation other people are part of, and they have not agreed to anything with us. Two separate things follow from that, and it matters which is whose.

Telling your table is yours to do. Before you start capturing, tell the people at the table that the session is being transcribed, that AI features send extracts of it to us, and, if you have turned recording on, that the audio is being saved. In some places that is the law. Everywhere it is the decent thing to do, and it is the account holder's job rather than ours: we have no way to reach your players.

What we become responsible for, and when. While you are only transcribing, nothing about those people reaches us at all: the audio and the transcript stay on your computer. The moment you run an AI feature, a recent extract of the transcript, including the character names you have tagged people with or the Discord name of anyone you have not, is sent to our server and on to our model provider. From that point we are a controller of that extract as well as you, and everything else on this page applies to it.

Why we are allowed to handle it. For you, the account holder, the basis is our contract with you: you asked for the answer. For everyone else at the table there is no contract, so the basis is our legitimate interest in answering the request you made. We have weighed that against their privacy on the strength of three things that are true by design rather than by promise: the audio never leaves your PC, the prompt is never written to our database and the answer only as the brief replay copy above, and what does reach Anthropic is deleted there within 30 days.

If you are one of those people. Write to hello@loremonkey.com. You do not need an account, and you do not need the account holder's permission. We will tell you what we can find that relates to you, delete the usage metadata we can match to you, and ask the account holder to edit or delete the local files. The transcript and any recording are on their computer rather than ours, so that part only they can do. You can object to the processing described above, and you can complain to IMY or to the authority in the EU country you live in.

What you can ask us to do

You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete your account and everything attached to it. The copy and the deletion are both on the Account page in the app, under Your data, and happen at once: the copy is one plain JSON file saved beside your own campaign files, and deleting ends your subscription first, then removes the account. If you cannot sign in, or you are asking about someone else's account, email hello@loremonkey.com and we will deal with it within 30 days. Deleting your account does not touch the files on your own computer, because we never had them.

You can also object to processing we base on legitimate interests, ask us to restrict it, or ask for your data in a portable form. If you think we have handled your data badly, you can complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), or to the data protection authority in the EU country you live in.

Children

You must be at least 16 to hold a LoreMonkey account, and 18 to buy a plan or a credit pack. Sixteen is the highest age any EU country sets for a child to agree to this kind of processing on their own, so it is the one we use everywhere rather than a different rule per country. Creating an account asks you to confirm you are 16 or older, and the first purchase asks once whether you are 18; we keep the date you said so. We do not knowingly create accounts below it.

Plenty of tables include people younger than that, and transcribing your own game is not the problem, because that stays on your computer. What you should not do is run an AI feature in a way that sends a child's speech or name to us unless you have the right to do so, which for a child who is not yours generally means their parent agreeing. If a parent writes to us about a child at someone's table, we treat it exactly like any other request in the section above.

Changes

If this policy changes in a way that matters, we will say so in the app rather than quietly editing this page. The date at the top always reflects the current version.