Cserebogár
Privacy Policy
Csereprogram | Hungarian cross-community safety and alliance since 2017
| Policy details | Information |
|---|---|
| Effective date | [11.09.2026] |
| Operator / controller | [Viktor Hu] |
| Postal address | [2890 Tata, Nagykert s 31.] |
| Privacy, support and appeals | [csereprogram@kanicorp.com] |
| Public policy address | [csereprogram.kanicorp.com/privacy.html] |
1. Who we are
Cserebogár serves Csereprogram, an established Hungarian cross-community Discord association founded in 2017. Participating server owners and moderators work together to reduce scams, spam and abuse through coordinated moderation, raid cleanup and a reviewed community directory. Participation is voluntary for server owners. We are independent, not an official Discord partnership or endorsement.
The operator above is responsible for the bot's central processing. Partner owners administer their own servers. Participation does not waive a member's privacy rights.
2. What we process and where it stays
We obtain necessary information from Discord's API, accessible messages and member events, commands, authorized staff decisions and user-initiated support.
| Information | How we handle it |
|---|---|
| Server messages and attachment information | Processed in memory for moderation and requested cleanup. We do not save API-obtained message content, excerpts, extracted message links or attachment content outside Discord, including in databases, files, diagnostics or backups. |
| Off-platform moderation records | Only the affected user's Discord ID, the action date/time and the sanction. No copied message text or free-text evidence. |
| Operational configuration | Necessary server, channel and role identifiers, partner invitations, moderation settings and local/global exemptions. These are separate from message evidence. |
| Incident evidence on Discord | A limited excerpt and necessary case context, such as the relevant account, action, reason, moderator and time, may be posted to restricted staff channels for review. No general chat archive is created. |
| Support conversations | User-initiated DMs are relayed to restricted Discord staff channels after a forwarding notice. Staff use recent context only to handle that request. Discord conversations are not exported to email. |
| Membership information | Used for join checks, sanction reconciliation, maintained spam-account checks and case-specific staff investigations. No persistent general member roster or membership-tracking history is kept. |
/smartremove is limited to the invoking server and channels the requesting moderator can access and moderate. /mutualservers is restricted to authorized staff handling a relevant network moderation case. Direct privacy/support emails contain the information the sender voluntarily supplies; they are separate from API-obtained Discord message content.
3. Purposes and moderation
We use data for the owner-enabled directory, scam prevention, network moderation, incident investigations, raid cleanup, support, appeals and privacy requests.
Configured rule matches can automatically remove a message or trigger a warning or ban. Only unexpired warnings count: a second warning within the rolling 90-day window triggers a network kick; a third triggers a network ban. Existing active bans are enforced when an account joins a participating server, subject to local and global exemptions. Warnings expire after 90 days. Expiry of warnings or historical evidence does not itself lift a separately active ban.
Staff review flagged incidents daily, can correct or reverse mistakes, and provide human review through the contact above. We do not sell personal data, use it for targeted advertising, build behavioral profiles, or send message content to AI providers or use it to train models.
For the central service, our legal basis is legitimate interests in protecting participating communities, operating their requested directory and moderation service, and responding to support and review requests, subject to necessity and balancing against users' rights. Processing required by law relies on the relevant legal obligation. Server enrollment is not blanket consent from every member.
4. Who can access information
Authorized application staff access information only for their duties. Local moderators receive results relevant to their own authorized server work, not unrestricted central support histories or unrelated evidence. Shared sanctions identify the affected account in the participating servers where enforcement occurs. We do not publish the central ban register or supply an external ban-list feed.
Discord processes on-platform messages and moderation actions under its own policies. Our operational service providers and their processing countries are: Hungary.
5. Retention and deletion
| Category | Maximum retention or review rule |
|---|---|
| Ordinary message content and routine membership checks | Transient processing only; no persistent ordinary-chat archive or general member roster. |
| Incident evidence and bot-controlled moderation reports on Discord | Up to 90 days from collection for investigation, daily staff review and appeals. |
| Warnings and historical action records, on or off Discord | Up to 90 days from creation. Expired warnings no longer count toward escalation. |
| Bot-controlled Discord support copies | Up to 30 days from receipt. New replies do not extend the expiry of older messages. |
| Content-free diagnostic logs | Up to 30 days from creation. |
| Minimum active-ban record | Only while necessary to enforce an active sanction; reviewed at least every 90 days and deleted when revoked, no longer necessary or subject to a deletion obligation. |
| Current partner configuration and exemptions | Only while needed for participation or an applicable exemption; reviewed at least every 90 days and deleted when no longer needed. |
| Direct email support, appeal and privacy correspondence | While the request is being handled, then up to 30 days after closure, unless retention is required by law. |
The 90-day window supports incident review and repeat-violation checks within the warning period. An ongoing ban retains only its minimal status record, not expired evidence or warnings. We delete data earlier when no longer necessary or required by a deletion obligation. Review, copying and restoration do not restart retention.
Expiry and deletion cover our database, files, applicable backups and bot-controlled Discord copies. Backups do not extend retention or restore deleted records. We promptly handle API-data deletion requests, except where retention is required by law; active bans are not automatically exempt.
Deleting our copies does not erase original messages, native moderation records or audit trails independently controlled by Discord or a server operator. We do not use independent copies to reconstruct deleted bot records.
6. Security
The server storage holding the bot's records is encrypted, with access restricted to authorized operators. Credentials are protected. Discord evidence and support channels use restricted staff permissions. Diagnostics do not contain message text, excerpts or extracted message links.
7. Your choices and rights
Email [csereprogram@kanicorp.com] or use /privacy to request access, correction, deletion, restriction, objection, portability where applicable, or human review. The email route remains available after leaving or being banned. We verify identity proportionately, never ask for passwords or tokens, and respond promptly within applicable legal deadlines.
Individual members cannot disable essential moderation in an enabled channel. An enforcement exemption is not a privacy opt-out. Support is voluntary. Privacy requests and moderation appeals are handled separately; privacy rights do not depend on the issuing moderator approving an unban.
You may complain to your competent data-protection authority, including Hungary's National Authority for Data Protection and Freedom of Information (NAIH). We update the effective date when this notice changes. Questions or concerns: [csereprogram@kanicorp.com].