Privacy
What we hold, and why
Lore Spawner is in closed alpha. This page says plainly what we keep about you, what it is for, who else ever sees it, and how to take it with you or have it deleted.
Effective date: 21 September 2026
Controller: Kaperkunde
KVK number: 42061326
Address: Prof. E.M. Meijerslaan 1, Amstelveen, The Netherlands
Privacy/GDPR requests: privacy@kaperkun.de
Support: privacy@kaperkun.de
Lore Spawner is in closed alpha. This notice says plainly what we keep about you, what it is for, who else ever sees it, and how to take it with you or have it deleted.
It sits on top of the Kaperkunde Privacy Policy, which is the company-wide document and covers your rights, how to complain, international transfers, security, and the promises that hold across everything Kaperkunde runs. This notice adds what is particular to Lore Spawner. It never takes away anything the company policy gives you.
Who you are dealing with
Lore Spawner is built and run by Kaperkunde, the independent software business of Kevin Lohman, registered in the Netherlands (KVK 42061326), at Prof. E.M. Meijerslaan 1, Amstelveen. Kaperkunde is the data controller for everything described here under the General Data Protection Regulation.
Anything on this page, and any request about your data, goes to privacy@kaperkun.de. A person reads it. That address is also where support requests go.
What we hold
- Your account. The email address you signed up with, a display name if you set one, and your password — stored hashed, so nobody at Kaperkunde can read it. Sign-in sessions, email verification and password reset records sit alongside it.
- What you create. The worlds, places, characters, events and writing you put into Lore Spawner, and who contributed what. This is the substance of the service and is kept until you remove it or close your account.
- Who you are playing with. Invitations you send or accept, and which characters have been handed to whom.
- Notification settings, and what has been sent to you. The notifications the app has written for you, how far you have read, and how you want to be told about each kind of thing.
- Devices you turn notifications on in. If you say yes to notifications in a browser, we keep the address that browser's push service issued us and the keys that encrypt a message to it. There is one such record per browser, and forgetting a device deletes it.
- Whether you are here. A single timestamp of when you last did something in the app, so we can stay quiet rather than mail you about something you are watching happen. It is overwritten, not accumulated: there is no history of your visits.
- What you have said to the AI. If this campfire has a language model and you talk to it about one of your worlds, the conversation is kept so you can come back to it. Unlike an event, it was never written to be read by anybody else, and nobody else can: it is yours and the model's.
- What the AI has cost. A line per call saying who it was for, which world it was about, what kind of work it was, and how many tokens it took. It is a meter, so that a runaway agent is visible and can be capped; it holds nothing of what was written.
- Ordinary server logs. Requests to the site, with IP address and timestamp, kept briefly so we can fix things that break and stop people abusing the service.
That is the whole list. There is no analytics, no advertising, no tracking pixel and no profiling of you anywhere in Lore Spawner. The only cookies we set are the ones that keep you signed in, which is why you have never been asked to dismiss a cookie banner here.
If somebody invites you
Inviting a friend means giving us their email address so we can send them one invitation. We use it for that and nothing else, we do not add it to any list, and if they decline — or never answer — the invitation can be taken back, which deletes the address with it.
If you got an invitation from us and had never heard of Lore Spawner, that is where your address came from, and privacy@kaperkun.de will remove it on request.
Why we hold it
Your account, your worlds and the people you play with are there because we cannot run the service you asked for without them — that is the contract between us. Notification settings and device records are there because you asked to be told about something. The logs, and the fact of whether you are currently here, rest on our legitimate interest in keeping the service up, secure, and quiet when it should be.
We email you about your account (verification, password resets, sign-in links) and, while Lore Spawner is in closed testing, to tell you when there is room for you — which is the thing you signed up to be told.
How long
| What | How long |
|---|---|
| Your account, and everything you have made | Until you delete it or ask us to |
| Server logs | 30 days |
| Notifications the app has written for you | As long as the account — they are the record of what we told you, and the list in the app is where you read it |
| A conversation with the AI about a world | Until you delete the conversation or the world, or close your account |
| The record of what the AI has cost | As long as the account. It is the meter the spending cap is read from, so it outlives the world it was spent on |
| A device you turned notifications on in | Until you forget that device, or its push service tells us the browser is gone |
| An invitation you sent | Until it is accepted, declined, or taken back |
Everything else goes when the account does.
Who else ever sees it
We do not sell your data, share it, rent it, give it away, or hand it to advertisers, data brokers or AI training sets.
One processor. Lore Spawner runs on servers rented from Hetzner, in the European Union. Everything else the service is made of — the database, the API, the mail server — is Kaperkunde's own software running on those servers. No analytics service, no content delivery network, no mail provider, and none of your data leaves the EU.
Push services, if you turn notifications on. A notification to a browser has to travel through whoever made that browser — Google, Apple or Mozilla. They relay a message encrypted to keys only your own browser holds, so what they pass on they cannot read. Turning notifications off, or forgetting the device, ends that.
The full list, and what each one is for, is in the Lore Spawner subprocessor list. If it ever has to change, that list and this page will say so, and who they are, before it does.
The exception every service has to name: if we are ever legally required to hand something over, we will, and we will tell you unless we are forbidden to.
The AI, and what it is told
There are two different AIs here and they hold different things.
The AI at the fire is a language model this campfire can be pointed at, which can play or tell a character you have handed to it and can talk with you about a world. It is off unless the campfire has been given a model to use. When it runs, what it is sent is the part of the world it is acting in — the events, the places, the characters, and what you have said to it — and that goes to whoever serves that model. Where that is not a model Kaperkunde runs itself, that provider is a processor and is named in the subprocessor list, which is the honest place to look before you turn it on.
An assistant you connect yourself is the other: an outside app you allow over OAuth, which then acts as you within the limits you set when you allow it. It reads what you can read, and it writes only where you have ticked a box saying it may. The connection is a token held by that app, not a copy of your password, and you can take it back at any time from the AI page in your account. What that app does with what it reads is between you and whoever makes it — it is your assistant, not ours.
Kaperkunde does not train anything on your worlds, your conversations or your writing, and neither AI changes that.
What you make is yours
You keep every right you have in the worlds, characters and writing you create on Lore Spawner. Signing up gives us no ownership of it and no licence to sell it or publish it elsewhere. We store it and show it so the app can work — to you, and to the people you are building the world with — and that is the whole of it.
Taking it with you, or taking it down
Every world you own can be exported from the app itself, at any time, as one file you can keep and put back. That is the fastest way to have a copy of your work, and it needs nobody's help. It is also how Kaperkunde's company-wide export promise is kept here — see §4.1 of the Privacy Policy.
For the rest — your account and everything attached to it — email privacy@kaperkun.de and we will send you a machine-readable copy, or delete it, whichever you ask for. Either way you hear back within 30 days, and normally a great deal sooner than that.
Deleting an account removes it and the work attached to it. Where your writing is woven into a world other people are still playing in, we will talk it through with you before anything goes, so we take out what is yours without collapsing someone else's story.
Your rights, and who to complain to
These are the same across everything Kaperkunde runs and are set out in §9 and §10 of the Privacy Policy: access, correction, erasure, restriction, objection, portability, withdrawing consent, and a complaint to the Dutch Autoriteit Persoonsgegevens if we get it wrong. We will not make you jump through hoops for any of it.
You need to be 16 or over to use Lore Spawner, as §11 of the Privacy Policy sets out for all our services.
While we are still in alpha
Lore Spawner is unfinished software, offered as it is, and we cannot promise it will not lose your work. Export anything you would be sorry to lose. If we ever need to reset the test data, everyone signed up hears about it first.
Changes to this notice
This notice grows as Lore Spawner does, and it will be a longer document before Lore Spawner opens to the public. If anything here changes in a way that matters to you, we will tell you rather than quietly editing the page.
The terms of use say what we each agree to.