Last updated: August 31, 2026
Zarka is a Discord application (“the bot”) operated by an individual developer (“we”, “us”). This policy explains exactly what data the bot collects, why, how long it is kept, and how to have it removed.
Contact: beanjuice@humanfirsttechnologies.com
Zarka stores two things: moderation warnings issued by server moderators, and Path of Exile 2 build links that users choose to save. Nothing else is written to disk. Message content is read only to detect commands and is not stored.
Discord requires applications to request explicit permission for certain kinds of data. Zarka requests two:
Message Content. Required because the bot responds to text commands
prefixed with !. Every message in a channel the bot can see is examined in
memory to determine whether it begins with that prefix. If it does not, it is
discarded immediately. If it does, the command runs and the message is discarded
once the response is sent.
Server Members. Required to greet new members when they join, to grant and remove opt-in roles through reactions, and to apply moderation roles.
Zarka does not request the Presence intent and does not receive information about whether you are online, idle, or what you are playing.
Message content is never written to disk, logged, or transmitted to any third
party. The only exception is where your own command explicitly saves something —
for example the URL and title you supply to !setbuild, described below.
The Discord library the bot is built on keeps a small rolling cache of recent messages in memory to support Discord’s own features. That cache is volatile, is evicted automatically, and is lost whenever the bot restarts.
When a server moderator issues a warning with !warn, the bot records:
| Field | Description |
|---|---|
| Discord user ID | The numeric ID of the warned user |
| Reason | Free text written by the moderator, or “No reason given” |
| Moderator username | The Discord username of the moderator who issued it |
Why: so moderators can review a user’s history with !warnings, and so
warning counts stay accurate across bot restarts.
Retention: kept indefinitely until cleared. A moderator can erase a user’s
entire warning history with !clearwarnings. Users may also request erasure by
contacting us at the address above.
Note: the reason field is written by a moderator and may quote or describe something the user said.
When a user saves a build with !setbuild or !addbuild, the bot records:
| Field | Description |
|---|---|
| Server ID | The numeric ID of the Discord server |
| Discord user ID | The numeric ID of the user who saved the build |
| Display name | The user’s display name in that server, refreshed on each save |
| Build URL | The link the user supplied |
| Title | A title the user supplied, or one read from the linked page |
| Timestamp | When the build was saved |
Why: so users can list and share their own builds with !mybuilds,
!currentbuild, and !allbuilds.
Retention: kept until the user deletes it. Users can remove a single build
with !delbuild <number> or all of their builds with !clearbuild. These
commands are self-service — no moderator involvement is needed.
Zarka has no website, sets no cookies, and runs no advertising.
When a moderator uses a moderation command, Zarka posts a summary — the action, the moderator’s name, the target’s name, and the reason if one was given — as a message in a private log channel inside the Discord server.
These messages are stored by Discord, not by us, and are governed by Discord’s Privacy Policy. Server administrators control who can see that channel and can delete its contents at any time.
The service records basic operational messages — startup, which components loaded, and errors — to a system log on the machine it runs on. These logs are used for debugging, contain no message content, and are automatically deleted after two weeks.
We do not sell, share, rent, or transfer any stored data to third parties.
Zarka does make outbound requests to public websites in the course of its features — for example to read the title of a build link a user has submitted, to look up a wiki article, or to fetch public game news and free-game listings. These requests carry no personal data. Where a request results from a link a user chose to submit, that link is sent to the site it points at, which is an unavoidable consequence of following it.
Stored data lives in files on infrastructure operated and controlled by the developer. It is not publicly accessible and is not hosted with a third-party cloud database provider.
Depending on where you live, you may have rights over your personal data under the GDPR, the UK GDPR, the CCPA, or similar laws — including the right to know what is held about you, to obtain a copy, to correct it, and to have it erased.
To exercise any of these, either:
!clearbuild, !delbuild), orWe will respond within 30 days. There is no charge.
Because Zarka identifies users only by Discord user ID, we may need you to tell us your Discord user ID in order to locate your data.
Discord requires all users to be at least 13 years old, or older where local law sets a higher minimum. Zarka is not directed at children and we do not knowingly store data belonging to anyone below Discord’s minimum age. If you believe we have, contact us and it will be deleted.
Access to stored data is limited to the developer. No system is perfectly secure, and we cannot guarantee absolute security, but the data held is limited to what is listed above and contains no credentials, payment information, or real-world identifiers.
If this policy changes materially, the updated version will be published here with a new “Last updated” date and announced in the server where the bot operates. Continued use of the bot after a change constitutes acceptance of it.
beanjuice@humanfirsttechnologies.com
You may also ask in the support channel of the Discord server where Zarka operates, which is open to anyone who joins.