GribBot GribBot
Privacy

GribBot Privacy Policy

Effective date: 15 August 2026
Last updated: 15 August 2026
Related documents: GribBot Terms of Service · Discord Terms · Discord Privacy · Discord Guidelines

This Privacy Policy (the “Policy”) describes how personal data is processed when you use the Discord bot GribBot, the web control panel and related services of the Operator.

The Policy is prepared with regard to Federal Law No. 152-FZ of 27 July 2006 “On Personal Data”, the Civil Code of the Russian Federation, the Russian Federation Law of 7 February 1992 No. 2300-1 “On Consumer Protection”, and generally accepted international principles (including EU Regulation 2016/679 — GDPR — insofar as those rights apply to you where you live).

The Russian version is the primary legal text. This English translation is provided for convenience.

1. Personal data operator

OperatorAndrey Vasilyevich Bobryshov
ProjectGribBot
Address for requestsDonskoye, Russian Federation
Emailgribbot.sup@gmail.com
Bot requestsgribbot.ru/tickets · gribbot.sup@gmail.com
Discordandr1489
VKvk.ru/andr1489
Forumgrib-forum.ru/forums/gribbot-sup/
This pagegribbot.ru/privacy

The Operator processes personal data of:

  • GribBot license buyers (Discord server administrators);
  • members of Discord servers where the Bot is installed;
  • web panel users (sign-in via Discord OAuth);
  • people who submit a request through the form on this website.

Discord Inc. processes Discord platform user data under its own rules. The Operator does not control Discord.

The administration of a third-party Discord server that bought a license may also act as an operator for its own community. GribBot processes data that the Bot technically stores for its features to work.

2. What data is processed

Only data needed to run the Bot, panel, moderation, licensing and support requests is processed.

2.1. Discord identifiers

  • user, guild, channel, role and message IDs;
  • display name, avatar and server list — when signing into the web panel (OAuth scopes identify and guilds);
  • mentions and nicknames if they appear in punishment reasons, reports, appeals, staff notes, templates or website requests.

2.2. Moderation and safety

  • warnings: reason, moderator, date, duration;
  • punishments: mute, kick, ban, softban, unban, channel restriction, role removal;
  • cases, moderation log, audit;
  • reports (/report), evidence, review status;
  • appeals, request text, decision;
  • staff notes about a member.

2.3. Activity, levels and rewards

  • XP, level, message count, voice time, reactions;
  • points and reward records;
  • moderator activity;
  • level-reward settings.

2.4. Server settings and staff-created content

  • log channels, roles, auto-punishment thresholds, welcomes, self-roles;
  • auto-replies, tags, message templates, punishment reasons, command aliases;
  • temporary voice channel owners and access/ban lists in those channels.

2.5. Web panel, this website and technical data

  • panel session cookies (grib_session, up to 7 days) and short-lived OAuth cookies;
  • language and session cookies of this site (lang, gribbot_session);
  • website requests: Discord ID, topic, text, optional email and server ID, IP address to limit abuse;
  • web-server logs may include IP address, User-Agent and request time.

The Operator has access to the web panel of every server where the Bot is installed (super-admin mode). This is needed to issue a license, connect the Bot, provide technical support, diagnose failures, keep the service secure and investigate violations. The buyer’s server staff only see and configure their own server.

2.6. License purchase

Payment goes through Playerok. The Operator does not receive or store bank card numbers, e-wallet credentials or Playerok passwords.

The Operator may store: the buyer’s Playerok or Discord nick/ID, the fact of payment, order contents, access grant date, and deal correspondence.

Payment data is processed by Playerok under its own documents.

2.7. What the Operator does not collect on purpose

  • Discord passwords and DM contents (except notices the Bot itself sends);
  • full server chat history;
  • biometrics, passport data, the buyer’s TIN (unless you sent them in a request);
  • precise geolocation.

3. Purposes and legal bases

PurposeBasis (152-FZ, art. 6)
Providing a license, issuing the Bot, supporting the buyercontract (cl. 5 part 1)
Commands, moderation, roles, levels, panelcontract and/or consent (cl. 1, 5 part 1)
Handling website requestsconsent and handling the request
Security, abuse review, protection of rightslegitimate interest / legal duties
Responding to data-subject requestslaw (arts. 14, 20, 21 of 152-FZ)
Court or statutory requirementscl. 2 part 1 art. 6
Cross-border transfer to Discord and hostingconsent and necessity to perform the contract

Using the Bot, signing into the panel, submitting a request on this site or paying for a license while this Policy is available is treated as acceptance of its terms, unless the law requires another form of consent.

Data is not sold and not shared for advertising with third parties.

4. Where data is stored and cross-border transfer

  • The Bot’s main database is an SQLite file (data/bot.db) on the Operator’s server. The server is located in the Netherlands.
  • Requests from this website are stored on the hosting for gribbot.ru.
  • Moderation logs may be duplicated into Discord channels on your server.
  • Web-panel sessions are stored in the Bot process memory (cookies on the user’s device).
  • Discord processes data on its infrastructure (including outside the Russian Federation, including the USA).
  • Playerok processes deal data on its side.
  • The grib-forum.ru forum processes support posts under its own rules.

This is a cross-border transfer of personal data (art. 12 of 152-FZ). By using the Bot, panel, website or buying a license you agree to that transfer to the extent needed for the service to work.

The Operator takes reasonable security measures, but absolute network security cannot be guaranteed.

5. Retention

  • server data — while the Bot is installed and the license is active, plus a reasonable period to handle claims;
  • moderation records, cases, reports, appeals and website requests — until deleted by staff / the Operator or upon request, unless there is a legal ground to keep them;
  • panel cookies — up to 7 days or until sign-out;
  • technical logs — generally no longer than 30 days unless there is an incident;
  • deal data (payment fact, access grant) — for accounting, tax and consumer-claim periods (a reference point is up to 3 years).

Leaving a Discord server does not by itself delete Bot database records. A request to the Operator and/or the server administration is required.

If the Bot is removed from a server, that server’s data in the database may be deleted by the Operator. Messages in Discord channels remain until the server administration deletes them.

6. Data-subject rights

Under 152-FZ (and GDPR if it applies) you may:

  • learn whether your data is processed and obtain information about the processing;
  • request rectification, blocking or destruction if data is incomplete, outdated or processed unlawfully;
  • withdraw consent (this does not always stop processing if a contract or law still applies);
  • appeal the Operator’s actions to Roskomnadzor or a court.

How to send a request: via the request form, email gribbot.sup@gmail.com, or the forum support section. Include your Discord ID and the substance of the request. The Operator may ask you to confirm that the request comes from you.

Response time is within the limits set by 152-FZ (generally up to 10 business days, with a possible extension where the law allows).

Limits: data that must be kept by law, or that is needed to handle a dispute, security or license performance, cannot be deleted while those grounds remain.

Complaint to the Russian authority: Roskomnadzor.

7. Children

  • Discord is not intended for people under 13 (or a higher age in your country).
  • Buying a GribBot license is for people with full legal capacity, generally 18+, or with a legal guardian’s consent.
  • If it becomes known that a child’s data was collected in violation of the rules, write to the Operator for deletion.

8. Direct messages from the Bot

The Bot may send a DM about a punishment, reward or service notice if the server settings allow it. Closed DMs in Discord do not cancel the action and are not a Bot malfunction.

9. Changes to this Policy

The current version is always here: https://gribbot.ru/privacy

The Operator may announce material changes on the website or forum. Continued use of the Bot after a new version is published means you accept the changes, unless the law requires otherwise.

10. Contacts

GribBot · 15 August 2026