Privacy Policy

1The short version

Nekonomy is an economy bot for Discord. To work, it needs to know who played and where — and that is very nearly all it keeps.

This policy covers the bot on Discord and the dashboard at nekonomy.xyz. It complements the Terms of Service.

2What we do not collect

To be clear up front, Nekonomy does not collect or store:

• Message content, attachments, images or audio — except the forms chat conversation (see Server forms)
• Direct messages (DMs) between users
• Usernames, nicknames, avatars or banners
• E-mail, phone number, address or identity documents
• IP addresses of bot users
• Credit card or payment data
• Browsing history or advertising data

3Data we collect

Discord identifiers

Public numbers assigned by Discord that the bot receives when processing a command:

• User ID — to tie your progress to your account;
• Server ID — because each server has its own economy and settings;
• Channel ID — to know where to reply, and for rules that limit commands to certain channels;
• Role ID — for permissions, role rewards and profession role syncing;
• Message ID — so the same reaction is not counted twice (temporary, in memory) and, in the forms chat, to link each message to its counterpart in the ticket channel.

Game data

Created by your own actions inside the bot, spread across roughly a hundred tables. In summary:

Forms chat

When a form has its conversation enabled, the messages between the submitter and the server's staff are stored: the text (encrypted), who wrote it (the Discord ID of the staff member), the time, and whether it was edited or deleted in the channel. For images sent by staff in the channel we keep only the attachment's name, type and identifier — the image itself stays on Discord. Internal staff notes (starting with //) are never shown to the submitter.

Technical logs

Operational logs holding identifiers, command name and timestamp, used to diagnose failures and investigate abuse. Administrative audit records (for example, who granted or removed currency) are kept so the server itself can hold its moderators accountable.

4Purpose and retention

Every piece of data exists for a reason, and lives as long as that reason does.

Basis for processing: performing the service you requested by using a command, and the legitimate interest in keeping the service secure and free of fraud.

5Privileged intents

Discord classifies some access as privileged and reviews it individually. This section describes exactly what Nekonomy does with it.

Message Content — optional

The bot requests this intent only when it is enabled in its configuration. When active, message text is used for:

1. Forms chat. What staff write in a form's ticket channel reaches the submitter's page. This is the only text that is stored, encrypted (see Server forms).
2. Prefix commands. The bot accepts commands such as s!profile. The text is read to recognise the command and then discarded.
3. Typed replies in menus. Some menus ask you to type a quantity, a name or a channel. The reply is read and discarded.
4. Server custom commands. The message is compared with the triggers the server's administrators configured, and discarded.
5. Activity counter. For the weekly “send messages” mission, only the length is checked (a guard against spam) and a number tied to your ID is incremented.

When the intent is not active, Discord only delivers to the bot the content of messages that mention it; the features above are limited to that, and slash commands (/) keep working normally.

Server Members — not requested

The bot does not request the members intent and receives no join or leave events. Role income uses the member list Discord already provides to the bot, in memory only, to know who holds the role at payout time; that list is never stored.

Presence — not used

The bot does not read anyone's status, activity or presence.

Reactions

For the “react to messages” mission, the bot receives reaction events and keeps the user + message pair in memory only so the same reaction is not counted twice. That pair lives in process memory, is capped in size, and disappears when the bot restarts. Only a numeric counter reaches the database.

6Dashboard and sign-in

The dashboard at nekonomy.xyz uses Discord OAuth2 with the identify and guilds scopes — the minimum needed to know who you are and which servers you can administer. The bot is invited with bot and applications.commands.

• The session lives in a signed cookie, with SameSite=Lax and, in production, restricted to HTTPS. Valid for up to 7 days.
• The cookie holds: your ID, username, avatar identifier, the Discord access token and an anti-CSRF token. Your server list is cached temporarily in the session.
• The access token is used only to confirm your identity and your servers with Discord. It is not written to the database.
• Signing out ends the session. You can also revoke the application under Discord Settings → Authorised Apps.
• This has nothing to do with the bot's panels inside Discord. Screens such as /farm or /coop stay clickable in the conversation and depend on no session: each button carries what it needs in its own identifier, and the state is read from the database at the moment of the click. That is why they keep working even after the bot restarts.

Server forms

A server's administrators can create forms in the dashboard (reports, support, applications and others) and share links to them. Each form belongs to the server that created it, and whoever configures it decides what to ask.

• Media is stored in the server's Google Drive. Images and videos sent through a form are saved to a folder in the Google Drive account the server's administrators connected, not on Nekonomy's servers. Nekonomy's access to that account is limited to the files it created itself (the drive.file scope).
• Who can see it. Answers and media are visible only to the staff the server authorized in the dashboard.
• How long it is kept. Each server sets its own retention: submissions and media are deleted after the chosen period, or kept until someone deletes them. Files from a submission that was never completed are deleted automatically within 7 days.
• The Google Drive authorization is stored encrypted in the database and is never shown in the dashboard.
• Chat with staff. If the form has its conversation enabled, the submitter and the staff exchange messages through the page and the ticket channel. The text is stored encrypted in Nekonomy's database, visible to the submitter (except internal notes) and to authorised staff, and is deleted with the submission when the form's retention expires.
• Ticket transcript. If the server picks a transcript channel, when a ticket is closed the bot posts there a file with the display names and the text of the ticket channel's messages. That file lives on Discord, in the server's channel; it is not stored in Nekonomy's database.

7Payments

Where premium features are enabled, payment is processed by Stripe, entirely within its environment.

• Nekonomy never receives, sees or stores card numbers, CVV or banking data;
• We store only the subscription identifier, its state (active, cancelled, expired) and a record of the events received, in order to grant or end benefits;
• Stripe's handling of data follows its own privacy policy.

8Third parties and sub-processors

We do not sell, rent or share data for marketing. Data passes only through the services the bot needs in order to exist:

We may disclose data where required by law, by court order, or to protect the rights, safety and integrity of the service and its users.

9Security

• The forms chat text is stored encrypted in the database (Fernet: AES-128-CBC with HMAC-SHA256), with the key kept outside the code, like form links and the Google Drive authorization;
• Encrypted connections to Discord, to the dashboard and to the database;
• Secrets (bot token, database credentials, Stripe keys) live in environment variables, outside the source code;
• Parameterised queries, and currency operations inside atomic transactions so a balance is not lost midway through a failure;
• Anti-CSRF protection and rate limiting on the dashboard;
• Administrative dashboard access restricted by role, with an audit trail.

10Your rights and deletion

At any time you may:

• Access — request a copy of the data linked to your ID;
• Correct — ask for incorrect information to be fixed;
• Delete — ask for your data to be removed;
• Restrict — stop using the bot and revoke the application's access.

How to request deletion

1. Send a request to kaicho1520@gmail.com with the subject “Data deletion”;
2. Include your Discord user ID (enable Developer Mode in Discord, right-click your name and choose “Copy ID”);
3. If the request concerns a specific server, include the server ID as well.

We confirm ownership before deleting — otherwise anyone could erase someone else's progress. Requests are handled within 30 days.

When a server removes the bot

That server's data stops being used. An administrator may request deletion of the server's data through the same channel, providing the server ID.

11Minors

The service is not intended for people below the minimum age required by Discord's Terms (13 years in most countries, and higher where local law requires it).

We do not knowingly collect data from anyone below that age. If we learn that this has happened, the data will be removed. Guardians may request removal at the contact address.

12International transfer

The bot, the dashboard and the database run on servers that may be located in countries other than yours. By using the service, you acknowledge that the data described here may be processed outside your country of residence, with security measures equivalent to those described in this policy.

13Changes

This policy may be updated when the service changes, when new Discord requirements arise, or where the law requires it. The last updated date appears at the top of the page, and material changes will be announced through the official channels.

If a change significantly broadens the data collected, it will be highlighted before it takes effect.

14Contact

Questions about privacy, access requests or deletion requests:

• E-mail: kaicho1520@gmail.com
• Website: nekonomy.xyz

Data controller: the Nekonomy maintainers. Response time: within 30 days.