Privacy Policy

The short version

• Bonki does not read your messages unless your server turns that on. Message logging is off by default. A server’s administrators can switch it on so that deleted and edited messages can be shown to moderators, and when they do, message text is kept for a few days and then deleted automatically. Ticket transcripts work differently and are described below. Both are set out in full under What is stored about members.
• It never asks for your email address. The sign-in scope is identify, guilds and applications.commands.permissions.update, nothing else.
• Nothing is sold, rented or shared for advertising. There are no analytics scripts, no advertising pixels and no third-party trackers on this site.
• Modules that are off store nothing. Every module starts disabled.

Who is responsible for your data

For the dashboard and your sign-in, the data controller is the operator of getbonki.com, an individual based in Australia, contactable through the Bonki support server.

For data about members of a server, the server’s administrators are the controller and Bonki is a processor acting on their instructions. They chose which modules to enable. If you are a member of a server and want your data removed, you can ask either them or us, see Your rights below.

What is stored when you sign in to the dashboard

• Your Discord user ID, username, global display name and avatar hash.
• The list of servers you are in and your permissions in them, so the dashboard can show you only the ones you administer.
• Your Discord access and refresh tokens, encrypted at rest with AES-256-GCM. These let the dashboard act for you without asking you to sign in again every hour.
• A session record with an expiry, so a session can be revoked immediately rather than remaining valid until it expires.

No email address, because the email scope is not requested. No password, because there is no password. Discord does the authenticating.

What is stored about a server

The server’s ID, name, icon hash, owner ID, approximate member count, locale and timezone, plus the configuration of whichever modules are enabled and an audit record of who changed what setting and when.

What is stored about members, module by module

Only for modules the server has enabled. If a module is off, none of this exists.

• Levelling, your XP, level, a count of messages sent, your cached username and nickname, and when you last earned XP. No message text. Messages are counted, not read.
• Moderation, a case record for each warning, note, timeout, kick or ban: your user ID and tag at the time, the moderator’s, the reason given, any evidence links the moderator attached, when it expires, and whether the notification DM reached you.
• Tickets, who opened it, who claimed it, who took part, the subject and closing reason, and an HTML transcript. The transcript does contain message text, for up to the last 2,000 messages in the ticket channel. It is read back from Discord when the ticket closes, not recorded as you type. It includes display names, timestamps and the filenames (not contents) of attachments. Server staff can read it from the dashboard.
• Suggestions, your user ID, the text of your suggestion, your votes, and any staff note or decision.
• Polls, your user ID and which option you chose. An “anonymous” poll hides your choice from other members; it is still stored so the same person cannot vote twice, and a server administrator with database access could see it.
• Events, your RSVP, waitlist position, cached nickname, whether you checked in, and, if you set one with /timezone, your timezone.
• Giveaways, that you entered, how many entries you hold, your cached nickname, and whether you won.
• Reminders, the text of the reminder you asked for and when to send it.
• Roles, which roles you held when you left, if sticky roles are on, so they can be restored if you come back.
• Dynamic voice, that you own a temporary channel, deleted when the channel is.
• Logging, the events the server chose to log, written to a channel in that server. What is kept in Bonki’s own database is the configuration, not a second copy of the log.
• Message logging - off unless your server’s administrators enable it. When it is on, Bonki keeps a copy of the text of messages sent in that server so that a deletion or an edit can show what actually changed. Without it, a moderation log can only say thatsomething was deleted, which is of little use to anyone.
  
  What is kept: the message text, who sent it, which channel, when, and the filenames of any attachments. Not the attachments themselves, and not images, audio or video.
  
  What is never kept: anything from a channel, category or member the server has added to its ignore lists, and anything posted by a bot.
  
  How long: the server chooses, up to a maximum of 30 days, and 7 days by default. Every stored message is given an expiry when it is written and is deleted automatically once it passes, whether or not anyone asks. A message that is deleted or purged has its stored copy removed as soon as the log entry has been written.

Server logs

The web server keeps standard access logs containing IP addresses, timestamps, requested URLs and user-agent strings. These are used to diagnose faults and spot abuse. They are not joined to your Discord account and are not used to build a profile of you.

Cookies

One cookie: the session cookie that keeps you signed in. It is strictly necessary for the dashboard to work and is not used for tracking. There is no analytics cookie and no advertising cookie, so there is no consent banner to click through.

Who else sees it

• Discord, the platform Bonki runs on. Your use of Discord is governed by Discord’s Privacy Policy.
• Cloudflare, all traffic to getbonki.com passes through Cloudflare, which sees your IP address and provides connection security and DDoS protection.
• Your server’s administrators, anyone with Manage Server can see that server’s configuration, moderation cases and ticket transcripts.

That is the entire list. No data broker, no advertising network, no analytics provider, no AI training.

Where it is kept

On hardware operated by the operator in Australia, reached through an outbound-only Cloudflare Tunnel with no inbound ports open. The database is not reachable from the internet. OAuth tokens are encrypted at rest. Backups are kept on the same machine and are covered by this policy.

Cloudflare operates globally, so request routing may pass through servers outside Australia.

How long it is kept

Data is kept while it is being used for the purpose it was collected for:

• While Bonki is in the server, configuration and module data are kept so the features keep working.
• After Bonki is removed, collection stops immediately. The stored configuration is kept for 30 days so you can re-add Bonki without setting everything up again, then deleted automatically along with everything attached to it: levels, events, tickets, moderation cases and any uploaded images. You can ask for it sooner.
• Your sign-in, a session ends after 15 minutes of inactivity, and the cookie is discarded when you close your browser, whichever happens first. Signing out deletes it immediately.
• Our own audit log of who changed which setting, kept for 365 days and then deleted automatically.
• Stored message text, deleted automatically after the period that server chose, 7 days by default and never more than 30. This is the one kind of data here that deletes itself on a timer rather than on request, because it is also the most sensitive.
• Moderation cases, kept until the server deletes them, because a moderation history that disappears is not a moderation history.

You can ask for anything to be deleted at any time, and it will be actioned within 30 days. See below.

Your rights

You can ask for:

• a copy of what is stored about you;
• a correction, if something is wrong;
• deletion, of your dashboard account, of your data in a particular server, or of everything;
• a machine-readable export, and for processing to stop where it is based on legitimate interests.

Ask in the Bonki support server. Requests are answered within 30 days. You will be asked to prove the Discord account is yours, because otherwise anyone could delete anyone else’s data.

Some deletions have a limit worth knowing about. A moderation case names two people; deleting it on the request of one removes the server’s record of a decision affecting the other. Where that applies, the server’s administrators are consulted first, and where the law requires deletion it happens regardless.

If you are unhappy with how a request was handled, you can complain to the Office of the Australian Information Commissioner. If you are in the UK or the EEA, you may complain to your own supervisory authority instead.

Children

Bonki is not directed at children. Discord requires users to be at least 13, and older in some countries. Nothing is knowingly collected from anyone below their country’s minimum age; if you believe a child has been recorded, say so in the support server and it will be deleted.

Security

OAuth tokens are encrypted with AES-256-GCM. The database has no published ports and is on an internal network no internet-facing container shares. Every dashboard request re-checks your permissions against Discord rather than trusting the session. Sessions are stored in the database so they can be revoked instantly.

No system is perfectly secure. If a breach affects you and is likely to cause serious harm, you will be told, and the Office of the Australian Information Commissioner notified where the Notifiable Data Breaches scheme requires it.

Changes

If this policy changes in a way that affects what is collected or who sees it, it will be announced in the support server before taking effect, and the date at the top of this page will change.