01 Data that is not stored
- Message contents. The text of your messages is never written to the database.
- Copies of deleted messages. If a filter deletes a message, only "whose message was deleted and why" is written to the event log; the message text is not.
- ID documents, date of birth, address, phone number. The bot never asks for these. The registration system only collects the fields the server chooses, and the registration flow warns you about this.
- Direct message contents. What you write during a registration conversation is only used for the relevant field; the conversation as a whole is not stored.
- Login details and passwords. Sakbot never asks for a password; panel login uses Fluxer OAuth.
02 Data that is stored
| Data | Why | When it is created |
|---|---|---|
| Member ID, display name | To link records and points to the right person | While the activity or registration system is enabled in the server |
| Activity points, message count, time of last points | To calculate levels and leaderboards | When you earn points while the activity system is enabled |
| SHA-256 hashes of your last five scored messages | To prevent earning points by repeating the same message | When you earn points |
| Registration details (in-game nick, name, age) | To run the server's registration system | When you register; only the fields enabled by the server |
| ID of the staff member who registered you and registration status | To track who performed the registration | During registration |
| Invite records (who invited whom) | For the invite leaderboard and invite points | When you join the server while invite tracking is enabled |
| Warning and suggestion records | For moderation history and tracking suggestions | When you receive a warning or send a suggestion |
| Event records (logs) | For the administrator's audit log | Member join/leave, auto role, message deleted by a filter |
This data arrives automatically through Fluxer. The bot only processes the events delivered to it; it does not collect data about you from any other source.
03 Where and how long data is kept
- Data is kept in the database of the server that runs the bot; it is not sent to any third-party analytics or advertising service.
- Data is not used for advertising, is not sold and is not shared for marketing.
- There is no automatic deletion. The bot does not delete a server's data on its own; it remains until the server administrator deletes it or the bot is removed from the server.
- The operator takes regular backups. Backups contain the same data and are subject to the same privacy rules.
04 Your rights
!mydata— Sends you a summary of the data the bot holds about you by DM.!deletemydata— Deletes your registration details (in-game nick, name, age). Your roles do not change. To confirm, type the command again followed byCONFIRM.- For other data (activity points, warning records), you can contact the server administrator or the support address below.
Note: Deleting your registration details does not change your roles. If you want to leave
the server completely, talk to the server administrator; when the bot is removed from a server, that
server's data can be deleted by the operator.
05 For server administrators
- While the registration system is off, the bot collects no personal information from your members.
- Only enable the registration fields you really need; do not ask for ID documents or dates of birth.
- You can view and delete stored details in the panel. Let members know that their details are stored.
- Activity and invite tracking are off by default; when you enable them, we recommend informing your members.
06 Contact
For privacy questions, data deletion requests and other matters, use the support server: fluxer.gg/KhiSEjJV
This page is an informational text and is not legal advice. The data protection laws of your country may impose additional obligations; review it for your own situation before relying on it. This is an English translation of the Turkish privacy notice.