Privacy Policy

Last updated 11 Oct 2026.

This policy explains what personal data buncol stores, why, who can see it, how long it is kept and what your rights are. In short: we collect only what the site needs to work, we do not sell anything, we show no ads and we use no analytics or trackers.

1. Who is responsible

buncol is run by LLMpeeters, who is the controller of your personal data under the General Data Protection Regulation (GDPR) and similar laws. Contact: info@llmpeeters.com.

2. What we collect and why

Your account

E-mail address - to send you login codes and identify your account. An account record is created as soon as you ask for a login code, even if you never use the code.
Username - the name other people see. You choose it, and you can change it in your account settings.
Settings - whether your profile is private (the default) or public, and whether you want e-mail backups.
Account details - when the account was created and last changed, whether you have logged in at least once, and your site role if you are a moderator or administrator.
Login security - the one-time login code we sent you, the number of wrong codes entered and, after three wrong codes within an hour, the time until login is unlocked again (24 hours). One login session per browser you log in on: how you logged in, the browser and system it reported (such as "Firefox on Android"), when it started and was last used, and until when it lasts. Its cookie holds a random value, of which we keep only a hash. How long logins last and what a login with limited access may do, as you set it in the login settings. For each browser you trust: the name you gave it, when you trusted it and last used it, a hash of the random value in its cookie, and the settings you gave it. If you set a password: a hash of it (never the password itself), when you set it, what made it easy to guess, where it works and when using it is e-mailed to you, and the number of wrong passwords since the last right one. For each network address, the number of wrong passwords in the last hour, kept only as a keyed hash of the address. For each passkey you add: its id, its public key (the private key never leaves your device), the name you gave it, when you added and last used it, its signature counter and whether your device syncs it; and a random id for your account that your passkeys carry instead of your e-mail address. A server-side session for short messages shown on the next page, and the one-time challenge while you add or use a passkey.

What you create

Projects - name, introduction, description and settings.
Writing - epics, stories, notes and snippets, including text you import.
World builder - objects, pins, scenes and locations, and the images and 3D models you upload.
Forum - threads and posts, with their author and time.

Uploaded files are stored exactly as you upload them. Photos often contain hidden metadata (EXIF), such as the camera model, the date and sometimes the GPS location where the photo was taken. We keep that metadata, and the original file name, as part of the file. Remove it before uploading if you do not want it stored.

Project membership and the audit log

Membership - which projects you belong to, your role in each, whether you were invited, asked to join or were banned from a project, who invited you and the message sent with an invite or request.
Audit log - every project keeps an automatic log of changes: who made the change (your account and the username you had at the time), what was created, changed, deleted or restored, its title or name at the time (for a snippet, which has no title, its first words; for a forum post, the title of its thread), and the names of the fields that changed. The log never stores what a change was, and never the text of a forum post. When site moderators hide or show content again, the log records that without naming them.

Moderation

Reports you file - the reported item, a link to it, a short snapshot of it taken at the moment you reported it (so the evidence survives later edits), the reason and your explanation.
Reports about you or your content - the same information, and how they were handled.
Moderation actions - warnings, hidden content, suspensions and bans, with the reason shown to you, an internal note for moderators, who took the action and when it ends or was reversed. Your account records whether it is suspended or banned.
Appeals - your appeal message and the moderator's response.

E-mail

Login codes - a six-digit code, valid for 2 minutes, each time you log in.
Weekly backup (optional, off by default) - if you turn it on, we e-mail you a file with the writing of the projects you own. Each backup has a one-click unsubscribe link, which works with a token that is valid for a month.

We send no newsletters or marketing e-mail.

Technical data

Cookies - only the ones needed to log in; see the Cookie Policy.
Keeping you logged in - while you are logged in, your browser checks in with the server every 10 minutes so your session does not run out while you work. This sends no data besides the request itself.
Server logs - when an error happens, the server logs details of the request so we can fix it. These can include the page address (which during login contains your e-mail address) and your account identifier. The web server may also keep ordinary access logs with IP addresses, browser type, the pages requested and the time.

3. Legal bases

Providing the service you signed up for (GDPR article 6(1)(b)): your account, logging in, storing and showing your projects, writing, world and forum content, project membership, and the backups you turn on.
Our legitimate interests (article 6(1)(f)): keeping the site and accounts secure (login limits, logs), keeping the community safe (reports, moderation and the moderation log), letting project owners see who changed what (audit log) and fixing errors. You can object to these, see section 7.
Legal obligations (article 6(1)(c)): for example handling reports of illegal content and answering lawful requests from authorities.

4. Who can see what

Project content. A project's writing and world are visible to its owner and to members whose role allows it. Uploaded images and models are only served to people with access to the project's world.
Forums. Each project chooses who can read its forum: only members, any logged-in user, or everyone, including visitors who are not logged in (and therefore search engines). Check a forum's setting before you post.
Your name. Your username is shown with your forum posts and threads, in the member lists of projects you belong to, in invitations and in project audit logs. People invite you by your exact username, never by your e-mail address. Without a username, a placeholder is shown in its place; your e-mail address is never shown to other users.
Your profile. Profiles are private by default. Public profiles can appear in the list of users that logged-in users can browse.
Audit log. Visible to the project owner, to members whose role includes viewing the audit log, and to site moderators. Each reader sees the title or name of an entry only where they may open what it is about.
Site moderators and administrators can see reports, the reported content, account details such as your e-mail address and moderation history, and the content and audit log of any project, so they can review reports in context. They use this access only to handle reports and enforce the rules.
The operator has technical access to everything stored on the server, as anyone running a website does, and uses it only to run and fix the site.

We do not tell the person you report who reported them.

5. Service providers and sharing

We use two kinds of service providers, who process data only on our instructions:

A hosting provider, which runs the server where the database, uploaded files and logs are stored.
An e-mail delivery provider, which delivers login codes and backups and so receives your e-mail address and the content of those e-mails.

Your browser does not contact any other company when you use buncol: all scripts, styles and icons are served from our own domain, and there are no external fonts, embeds, analytics or advertising scripts.

If a provider processes data outside the European Economic Area, we only use it with the safeguards the GDPR requires. We do not sell or rent personal data, we do not use it for advertising or profiling, and no decisions about you are made by automated means alone. We only disclose data to others when the law requires it.

6. How long we keep it

Login codes expire after 2 minutes and are deleted shortly after.
The login cookie lasts 4 hours at most. Login sessions are deleted when you log out, or when the time you chose in the login settings has passed since you last used the site (30 days unless you changed it). Trusted browsers are kept until you forget them, or 400 days after they were last used. Counts of wrong passwords per network address are deleted an hour after the first. Passkeys are kept until you remove them. Sessions end when you close the browser and are then cleaned up on the server.
Unsubscribe tokens for the backup e-mail are valid for one month.
Your account is kept until you delete it under Your account, or ask us to (see section 7). Accounts that were created by requesting a login code but never used are not removed automatically yet; ask us if you want one removed.
Deleted content. When you delete writing, objects, scenes, locations or forum sections they are kept for 3 days so you can restore them, and are then removed permanently by a clean-up job (a forum section with all its threads and posts). A forum thread deleted by a forum moderator is removed at once with all its posts. A forum post its author deletes is only hidden: the project's forum moderators and the site moderators can still read it, so ask us if you want it erased. Roles and memberships are removed at once. A project marked for deletion is not yet removed from the database automatically; e-mail us if you want a project and everything in it erased. Deleting your account erases the projects you own at once.
Audit log entries are kept for as long as the project exists, also after the account that made a change is deleted.
Moderation records (reports, snapshots, actions, appeals) are kept for as long as they are needed to enforce the rules, handle appeals and deal with repeated abuse, also after the content or account concerned is deleted.
Server logs are kept for a limited time for troubleshooting and security.

Copies of deleted data can remain in server backups until those backups are replaced.

7. Your rights

You have the right to:

access the personal data we hold about you and get a copy of it;
correct data that is wrong;
delete your data and account;
export your data in a machine-readable format (data portability);
restrict or object to processing based on our legitimate interests;
complain to a data protection authority, for example the one where you live.

You can change your username, profile privacy and backup setting yourself in your account settings, and delete your account under Your account. For everything else - including changing your e-mail address and a full copy of your data - e-mail info@llmpeeters.com from the address you log in with, so we know the request is yours. We answer within one month.

Deleting your account. Under Your account, choose Delete your account: the page lists what goes, and you confirm by typing your e-mail address, after a fresh login code. It happens at once and cannot be undone. We delete:

your account, your login codes and "stay logged in" tokens;
every project you own, with everything in it, including what other members added there. If you would rather hand a project over to another member, e-mail us before you delete your account;
your memberships, invites, requests and bans in other projects;
the text of your forum posts in other people's projects. The posts show as deleted by their author, so the conversation around them still reads. A thread you started where nobody else posted is deleted; one with replies keeps its title.

Writing and world items you added to other people's projects stay there, as part of those projects. Where your account was named, the site shows "Deleted user" instead. Audit log entries keep the username you had at the time, and moderation records are kept as described in section 6, no longer linked to an account. While your account is suspended or banned you cannot delete it yourself: e-mail us from the address you log in with and we delete it for you, in the same way.

Exporting. Besides asking us, you can turn on the weekly e-mail backup of your writing, export locations as JSON and download objects as GLB files from the world builder.

8. Security

There are no passwords to leak: you log in with short-lived one-time codes, and repeated wrong codes lock the login. Login cookies cannot be read by scripts on the page, and uploaded files are only served to people with access to the project. No system is perfectly secure, so please do not store anything on buncol that would cause serious harm if it got out.

9. Children

buncol is not meant for children. You must be at least 16 to have an account. If we learn that an account belongs to someone younger, we delete it. If you think a child has given us personal data, please e-mail us.

10. Changes to this policy

We update this policy when the site changes how it uses personal data. The date at the top shows the latest version, and important changes are announced on the site before they take effect.

11. Contact

For any privacy question or request: info@llmpeeters.com.