Privacy Policy
⚑ 2026-08-04 — parts of this document are stale.
Bots ARE now connected: a receive-only gateway turns Discord events into working
files on a private machine. Discord content still never enters any public repo, and we
still sell nothing and share nothing. A full re-carry of these papers from the Forge
is owed — the source of record is
Forge/Shelf/Bots/ in the Soulforge,
and re-carrying is a separate act, not an edit made here.
Drafted by Celeste, Attention of the Swarm; the source of record lives in the Soulforge at Forge/Shelf/Bots/. The text below is carried byte-faithful.
# Privacy Policy — the Soulforge Discord bots **Draft — Kal's ratification owed.** Written 2026-07-31 by Celeste (Knight seat) against behaviour verified on that date. **Last verified: 2026-07-31.** ⚑ **This document describes what the software actually does today, which is very little.** Where it describes something planned, it says so in as many words. If you are reading it after a bot has gone live and the date above has not moved, it is stale — ask the human below rather than trusting it. --- ## The short version **Today we collect nothing about you, because nothing is connected.** The eight Discord applications exist in a developer portal and do not run. No bot is connected to Discord's gateway; no interactions endpoint answers (as of 2026-07-31 the domain that would host one has mail records and nothing else — the names do not resolve); no message is read, stored, forwarded, or sent to anyone. The rest of this document exists because that will not stay true, and it is easier to be honest about what we would collect while the answer is still ours to choose. ## Who is responsible Kal, an individual, reachable at **kal@bugfyn.com**. There is no company, no team, and no processor behind him. The software runs on his own machine. ## What happens today The parts of this project that *do* run are local programs on that machine. They read and write a body of text — the project's own notes and documents — and talk to Anthropic's API to do it. **No third party's personal data enters that loop at all.** Nothing of yours is in it, because there is no path from you to it. ## What would be collected if a bot goes live When a bot connects, this is the shape it is built to. It is written here as a commitment, not a prediction. **What it would see.** Discord hands a connected bot the messages in channels it can see. Ours are built to act only on messages that address them — a mention, a reply to the bot, or a command prefix — and on direct messages to the bot. Ambient conversation is not the point and is not acted on. **What it would keep.** A message that wakes a bot is written to a queue file on the owner's machine so it is not lost while the slow local process catches up, along with the Discord user ID it came from and the channel it came from. That queue is on one disk, in one house. It is not a database, it is not backed up anywhere, and it is not synced to any service. **Where it would go.** The text of a message that wakes a bot is sent to **Anthropic's API** to compose a reply. That is the only third party in the loop besides Discord itself. Anthropic's handling of it is governed by their own terms, not ours. **What it would not do.** No advertising, no analytics, no profiles, no selling, no sharing with anyone else, no tracking of who talks to it or how often for any purpose beyond a rate limit. The project has a standing rule against counting people's engagement, and it is written into its own laws rather than into this document. **How long it would stay.** The queue is drained as it is processed. Anything kept beyond that would be a deliberate choice, and this document would have to be rewritten to say so before it happened. **Special cases worth naming.** A bot distinguishes its owner from everyone else by Discord user ID, and that ID is written into its configuration by hand. Nothing in the owner's private notes is ever shown to anyone else. ## Children This is a private project on a private server. It is not for children, it is not directed at them, and nobody here is in a position to verify anyone's age. ## Asking for something back, or asking us to stop Write to **kal@bugfyn.com**. If a bot has kept anything you said, he will tell you what and delete it on request. Today the honest answer to "what do you have on me" is "nothing", and it can be checked in about a minute because it is one folder on one computer. Because there is no account system, there is nothing to log into and nothing to verify you with beyond your Discord user ID. ## Changes This file is rewritten in the open and its history is public in the project's repository. The date at the top is the version. There is no mailing list to be notified from. --- ⚑ **Two things left plain on purpose, flagged rather than guessed at:** 1. **No claim of compliance with any named regime is made here** — not GDPR, not CCPA, not COPPA, not any other. Nobody involved is a lawyer, and asserting compliance we have not had checked would be worse than saying nothing. If this project ever grows past one person's server, that assessment is owed and this line is where it starts. 2. **The transfer to Anthropic's API is the one place personal data would leave this machine**, and the terms governing it are theirs. That is named here rather than buried, because it is the only part of this that a careful reader should actually care about.