Privacy Policy

Translation This is a translation of our German privacy policy, provided for your convenience. The German version is the legally binding one; if the two texts differ, the German text prevails. You can read it at Datenschutzerklärung (German).

Last updated: 27 October 2026

This privacy policy explains how personal data is processed when you use the website fylgra.com, the Fylgra dashboard, the Discord bot “Fylgra” and connected services and modules.

Fylgra is an administration and community tool for Discord servers. Which personal data is processed within a Discord server or a connected service depends on which functions and modules the respective server or channel operator activates and how they are configured.

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) for the processing carried out by Fylgra is:

Controller Marcus Jung
c/o flexdienst – #22146
Kurt-Schumacher-Straße 74
67663 Kaiserslautern
Deutschland
fylgra@fylgra.com

No data protection officer has been appointed.

2. Responsibility for Discord servers and community modules

With Fylgra, a distinction must be made between what Fylgra processes and what the operator of a Discord server, a Twitch channel or a comparable community does with data themselves.

Fylgra is the controller in particular for:

Fylgra is also the controller for the processing carried out by the modules that a server or channel operator activates. These may include, for example:

Which modules are active on a server and how they are configured is decided by the respective server or channel operator. They are themselves responsible for what they do with the data – for example content that they publish via Fylgra in Discord or in a stream, or data that they take over from Fylgra and use in other ways.

3. Principles of data processing

Fylgra processes personal data only insofar as this is necessary for a specific purpose.

Personal data is not sold.

Fylgra does not use personal data for personalised advertising and does not pass it on to advertising networks for advertising purposes.

Particularly in community modules, Fylgra endeavours not to store message contents where mere activity data or metadata are sufficient for the function.

Which data a module actually processes depends on its function and on whether the respective server or channel operator has activated the module.

Optional modules that have not been activated do not, as a rule, collect any of the personal data intended for that module. Independently of activated modules, a count without any link to individuals runs on every server (section 14).

4. Sources of personal data

Depending on the function, Fylgra receives personal data:

Data of community members and participants may therefore be processed even though these persons do not have a Fylgra account themselves.

5. Hosting and server log files

Fylgra is operated on a rented virtual server of

Hosting netcup GmbH
Daimlerstraße 25
76185 Karlsruhe
Deutschland

in a data centre in Germany.

A data processing agreement pursuant to Art. 28 GDPR is in place with the hosting provider.

When the website is called up, the following data in particular may be processed in server log files:

The processing serves to deliver the website, technical security, error analysis and the detection and defence against attacks.

The legal basis is Art. 6(1)(f) GDPR. The legitimate interest lies in secure, stable and functioning operation of the service.

Server log files are stored for no more than 14 days.

6. Technical system and error logs

Fylgra keeps technical operational and error logs.

These may contain in particular:

This data serves secure operation, troubleshooting, the traceability of technical operations and the detection and investigation of misuse.

The legal basis is Art. 6(1)(f) GDPR.

System logs are, as a rule, stored for no more than twelve months. Shorter periods apply to certain particularly short-lived technical error messages.

7. Backups

Fylgra creates full backups of the databases daily and additionally before technical changes to the system.

These serve exclusively to be able to restore the service after a technical error.

The backups are held on the server used for Fylgra and are accessible only to the operator.

They are kept for no more than 14 days.

Data that has been deleted in the production system may therefore still be present in a backup for up to 14 days.

Evidence, reports and the test-mode data of moderation (section 15a) are not contained in any backup.

The stored messages and contents of the message log (section 15) are not part of the daily backups. They may be contained, in encrypted form, in backups made before maintenance work; we delete these after 14 days at the latest.

The legal basis is Art. 6(1)(f) GDPR.

8. Storage on your device

Fylgra does not use cookies for personalised advertising.

Session cookie

For signing in, the technically necessary cookie fylgra_session is used.

It contains a random session identifier and serves to keep you signed in and to prevent unauthorised actions in your name.

The cookie is stored for no more than seven days and may become invalid sooner after a longer period of inactivity.

It is technically necessary for the signed-in area.

It is stored pursuant to Section 25(2) no. 2 TDDDG.

Other technically necessary cookies

While you sign in via Discord, Fylgra sets a cookie with a random value for no more than 10 minutes, so that the sign-in can only be completed in the browser in which it was started.

If you choose a language, the cookie fylgra_lang remembers this choice for one year.

Neither cookie contains any personal content, and both are necessary for the function you have requested in each case (Section 25(2) no. 2 TDDDG).

If you expressly accept a referral from “Refer friends” (button “Accept referral and sign in with Discord”), Fylgra sets the cookie __Secure-fylgra_ref for no more than 30 days so that the referral can be assigned when you sign in; it is deleted after sign-in (section 11d). Merely opening a referral link sets no cookie. The cookie is necessary for the participation you have requested (Section 25(2) no. 2 TDDDG).

Local browser storage

Fylgra may store settings such as:

in the browser’s localStorage or sessionStorage.

Insofar as this data is stored exclusively locally in the browser and is not transmitted to Fylgra, it serves solely to implement the respective user setting.

9. Audience measurement on the website

Fylgra uses Umami for audience measurement.

The software is operated on our own server.

Measurement only takes place if you have consented beforehand.

This also applies to the pages of the help center (section 11e). The measurement does not record search terms you enter there.

The following may be processed in particular:

The IP address itself is not stored permanently. Page views that belong together are recognised via an irreversible checksum with a random value that changes daily; no cookies are set for the measurement. The measured values are kept permanently as statistics; once the respective day has passed, there is no longer any link to a person.

The legal basis is Art. 6(1)(a) GDPR and, insofar as information is stored on or accessed from your device, Section 25(1) TDDDG.

You can withdraw your consent at any time with effect for the future via the cookie settings.

10. Signing in with Discord

Signing in to Fylgra takes place via Discord OAuth2.

In the process, Fylgra may in particular receive and store:

The e-mail address of the Discord account is not needed and, as a rule, is not requested.

In order to determine which Discord servers you may manage, Fylgra may also temporarily retrieve:

The Discord access token used for signing in is stored in encrypted form and deleted no later than 14 days after the last sign-in, or when you sign out or the token becomes invalid.

The server list is cached only briefly.

To recognise whether an account is still in use, we store with your Discord ID the day you last used Fylgra while signed in – the date only, without a time, and only the most recent day, no history. We update it at most once a day. The legal basis is Art. 6(1)(b) GDPR (providing the user account) and Art. 6(1)(f) GDPR; our legitimate interest is to recognise unused accounts and to help customers get started.

The legal basis for signing in and providing the user account is Art. 6(1)(b) GDPR.

Security data such as the IP address or browser identifier may be processed on the basis of Art. 6(1)(f) GDPR.

11. Dashboard and change log

Changes to server or account settings may be stored in a change log.

The following may be processed in the process:

The log serves the traceability of administrative changes, security and the clarification of abusive or accidental changes.

The IP address is removed after 90 days.

We delete the remaining entries in a server's change log after 365 days. The server owner can set a shorter period of 30, 90 or 180 days in Fylgra; older entries are then deleted. How far back the log is visible in Fylgra also depends on the plan: on the free plan, entries from the last 90 days are currently visible. Older entries remain stored until the end of the period so that they become visible after switching to a plan with a longer view. If you don't want this, you can set a shorter period. Entries about a ticket are also part of that ticket's history and are kept for as long as the ticket history. At the latest, we delete all entries together with the remaining server data.

In Fylgra, a server's change log can be seen by the server owner, people with the "Manage Server" permission and people who are allowed to see the server's audit log in Discord. Entries about channels that someone isn't allowed to see in Discord are made unrecognisable for that person. Replies and status changes by Fylgra support appear there as "Fylgra support", without naming the person.

Export. Anyone allowed to see the change log in Fylgra can, on plans that include it, download the entries visible to them as a CSV file. The file contains the same information as the view, without IP addresses; it only contains entries from the Discord audit log if the person exporting is allowed to see them (the server owner or someone allowed to see the audit log in Discord). The change log records that, when and with which filters someone exported; we do not store a search term in the process. Whoever downloads the file, or the server, is responsible for its further use (section 2).

In addition, for changes to roles and channels made through Fylgra we store the complete state before and after the change, so that such changes can be undone later ("history"). This may include the Discord identifiers of individual members who have their own permissions in a channel. This history is deleted after 90 days for all plans, at the latest together with the remaining server data.

If a role is deleted through Fylgra, we additionally store in the history the Discord identifiers of the members who had this role at that time. They are only used to give the role back to these members on the same server if the deletion is undone. This list is deleted after 30 days for all plans, at the latest together with the remaining server data.

If someone changes a server's channels, categories, channel permissions or roles directly in Discord or through another bot, we also add this change to the history so that it can be undone later. As above, we store the state before and after, the time and the Discord identifier of the person or bot who made the change. Fylgra takes this identifier from the server's audit log at Discord; Fylgra only reads it if it has the "View Audit Log" permission on the server, and only evaluates entries about channels, roles and permissions for the history and, for the protection against mass deletions, entries about bans and removals (see below). Which entries Fylgra also adds to the change log is described in the next paragraph; Fylgra immediately discards all other entries transmitted by Discord without storing them. If a role is deleted in this way, we also store the Discord identifiers of the members who had it at that time, as described above. In Fylgra, only the server owner and members who are allowed to see the server's audit log in Discord can see who made a change. Messages and the assignment of roles to individual members are not part of the history. We delete the Discord identifier of the person who made the change after 45 days and the other information according to the periods above, in each case at the latest together with the remaining server data. The owner and the administrators of a server can switch this recording off.

As long as this recording is switched on, we also add entries from the server's audit log at Discord to the server's change log, so that it shows who changed what on the server. These are entries about roles being given to or taken from individual members, about bans and their removal, removals, timeouts and voice mutes and deafens, about nicknames that someone changes for another member, about channels, channel permissions and roles, about the server's settings including emojis, stickers, server events and AutoMod rules, about invites and about bots, apps and webhooks being added, changed or removed. We store the time, the type of change, the Discord identifier of the person or bot who made it, where applicable the Discord identifier of the member concerned, and the changed values, such as the name and identifier of a role. For bans and removals we also store the name of the member concerned, because they are no longer on the server afterwards, and for bans, their removal, removals and timeouts the reason the acting person gave in Discord. We do not store the code of invites, and never the address or access key of webhooks. Messages, threads and changes someone makes to their own nickname are not included; the next paragraph covers the message log. Changes made through Fylgra are already in the change log and are not stored twice. This includes roles that Fylgra itself gives to or takes from a member, for example through reaction roles or after the rules have been accepted; for this we store the time, the member's Discord identifier, the role and the module that triggered it. If a very large number of changes are made on one day, or a bot repeats the same change within a short time, above a fixed limit we only count them, without any reference to individuals. In Fylgra, the entries taken over from Discord's audit log can only be seen by the server owner and members who are allowed to see the server's audit log in Discord. The same periods apply as for the other entries in the change log; the identifiers of the acting and the affected person are kept for as long as the entry. Discord itself shows its audit log for 45 days; a longer look back helps to clear up incidents that are only noticed later. The legal basis is Art. 6(1)(f) GDPR; the legitimate interest is that owners and moderators of a server can trace changes and moderation actions and clear up misuse. The owner and the administrators of a server can switch this recording off together with the history.

Independently of this recording, on servers with the message log switched on (section 15) Fylgra also evaluates the entries in the server's audit log that concern the deletion of messages, as well as deletions of messages in the chosen channels, in order to determine who deleted someone else's message. Fylgra immediately discards all other entries about messages.

Log channels. The owner and the administrators of a server can have entries from the change log posted as short messages in one or more channels of the server and choose for each channel which kinds of entries appear there. A message may name the person who made a change as well as affected members, roles and channels, for example "Lisa received the role Souls". Everyone who can see the channel in Discord can read the message; the server decides which channel that is. Fylgra does not post messages there about channels that not all readers of the log channel are allowed to see or about tickets. Messages about events and from areas reserved for administrators are only posted in channels that only the owner and administrators can read. Fylgra posts entries from Discord's audit log there together with the person who acted only if all readers of the log channel are allowed to see that audit log in Discord too, or if someone who is allowed to see it has expressly switched this on for the channel. Otherwise, changes to members' roles, nicknames, channels, roles, emojis and stickers appear without the acting person and without any reason given, and all other entries from Discord's audit log do not appear at all. So that messages don't appear twice and can be grouped and edited later, we store for 14 days which entry was reported in which message and in which channel, for a message with message content at least until we have removed the content. Messages about deleted or edited messages can contain their content if the owner has switched this on; Fylgra removes this content again after 7 days (section 15, "Message log"). The posted messages are held by Discord and remain there until someone on the server deletes them; the server is responsible for them (section 2).

Security notices (Watchdog). Fylgra automatically checks new change-log entries for security-relevant changes – whether they were made directly in Discord or through Fylgra – such as a newly added bot or webhook, a role with the "Administrator" permission being given to someone, far-reaching permissions for a role or for all members (@everyone), a changed invite address or a lowered verification level of the server. For this check Fylgra also reads the current permissions of the roles concerned or of the new bot from Discord; none of this is stored. Fylgra marks such entries in the change log as a security notice; we keep the mark for as long as the entry. If switched on (on by default; only the owner can change this), Fylgra also sends the server owner a direct message naming the change and the person who made it – not for changes the owner made themselves, and not while an incident of the protection against mass deletions is running on the server. To avoid too many messages, Fylgra remembers for at most 24 hours which notices it has already sent. Fylgra does not take any action against people.

Weekly summary. On request (off by default; the owner and the administrators can set it up), Fylgra summarises once a week how many entries of which kind there were in the server's change log, compared with the week before, and lists the week's security notices – as a direct message to the owner or in a log channel. In a log channel, Fylgra only counts what could also appear there as a report under the rules for log channels. The summary names no people and contains no ranking of people. So that it isn't sent twice, we store the week of the last summary.

For the rules, we also store an earlier revision of the settings each time they are saved or published, so that it can be restored later. This includes the time and the Discord identifier of the person who saved or published them; who agreed to the rules is not included. These revisions are deleted after 90 days for all plans, at the latest together with the remaining server data.

If someone creates a backup of a server – manually, automatically, before a restore or after a detected mass deletion – we store the server's structure: categories, channels, roles, their permissions and order, and the server settings. This also includes the settings of the Fylgra modules on that server, such as the texts and settings of the rules, the welcome post and role panels; information about who agreed, took part or created something is not included. If the texts themselves mention people, these mentions remain. This may include the Discord identifiers of individual members who have their own permissions in a channel. We also store which members have which role (their Discord identifiers), as well as the time and the Discord identifier of the person who created the backup; messages are not included. The role assignments are only used to give members their roles back when restoring on the same server, and are deleted from the backup after 30 days. We keep the rest of the content until the backup is deleted. If the module can no longer be used on the server, for example because the plan ends, its backups are deleted after 90 days, at the latest together with the remaining server data.

If a server uses the "Backups & Templates" module with protection against mass deletions, Fylgra also evaluates these changes automatically: if an unusually large number of channels or roles are deleted or members are banned or removed within a short time – directly in Discord or through Fylgra –, Fylgra reports this as an incident in the dashboard and in the server's alert channel and sends the server owner a direct message. For this purpose, Fylgra counts the deletions as well as bans and removals per person for no more than ten minutes; for this count Fylgra only keeps the audit log entry, not the identifier of the banned or removed member; what of this appears in the change log is described in the paragraph above. In addition, Fylgra counts the number of deletions per server for up to one hour, without any reference to individuals. Neither the incident nor the message in the alert channel nor the direct message names the person who deleted something; who it was is only shown in the history (see above). On request, Fylgra saves the server's state before the incident as a backup so that it can be restored; the paragraph on backups applies, and we delete this backup after 30 days. Fylgra does not take any action against people – it does not remove anyone's roles or permissions and does not ban anyone.

The legal basis is Art. 6(1)(f) GDPR.

Profile pictures and server icons from Discord

The dashboard shows members’ profile pictures and server icons by having your browser load them directly from Discord (cdn.discordapp.com) – for example in the member list, in the user menu and in the list of the most active members in Community Pulse. Fylgra does not store these images and does not route these requests through its own servers. As with any request for a web page, Discord receives your IP address and technical information about your browser (sections 23 and 24). The legal basis is Art. 6(1)(f) GDPR; the legitimate interest is to show people and servers recognisably in the dashboard without storing their images ourselves.

News and notices in the dashboard

In the dashboard we show news about Fylgra, for example about new modules or planned maintenance – as a notice bar or as a window after you sign in. Which news you see can depend on the plan of a server, whether you own a server, which modules are installed on your servers and since when you have been using Fylgra. We make this selection anew each time from data we already hold; we do not create a profile for it.

So that a news item does not keep reappearing, we store per news item, linked to your Discord ID, when you first saw it, how often and in which sign-in session it was last shown to you as a window, whether you hid or confirmed it and whether you used its button. This makes “don’t show again” apply on all your devices. We only evaluate this information in aggregate, for example how many people saw a news item; we do not evaluate individual persons. We delete this information together with the news item, at the latest 12 months after it ends, and together with your sign-in data. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to inform you about changes to Fylgra without bothering you with repetitions.

Embedded YouTube videos

News items in the dashboard and articles in the help center (section 11e) can contain a YouTube video. At first we only show a preview area; no data is transferred to YouTube. Only when you click “Load video” does your browser load the video in the privacy-enhanced mode from youtube-nocookie.com. Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) then receives, among other things, your IP address and the address of the page; Google may also transfer data to the USA (section 24). The legal basis for loading the video is your consent given by the click (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). Google’s privacy policy also applies. If JavaScript is turned off in your browser, the help center shows a link to YouTube instead of the preview area; only if you follow it do you open YouTube’s website, and Google’s privacy policy applies.

11a. Fylgra account, plans and change of owner

Every server on which Fylgra is used belongs to the Fylgra account of its Discord owner. For the account, we store the owner’s Discord identifier, the plan and its history, redeemed keys, exceptions granted by the operator and a change log of the account.

Anyone with a Fylgra account can save the structure of a server on which they are the owner or an administrator and, optionally, the settings of its Fylgra modules as their own server template in their account – including a server that belongs to another Fylgra account. A server template contains categories, channels and roles with their names, settings, channel topics and permissions, optionally the settings of Fylgra modules (such as the texts of the rules, the welcome post and role panels), plus the template’s title and description. Members, role assignments, Discord identifiers of individual people and information about who created, agreed to or took part in something in a module are not part of it; we remove mentions of people, roles or channels from names, channel topics and module texts, and links to Discord messages, channels and invites from module texts, when saving. This is also possible from an existing backup of a server from which Fylgra has been removed, as long as its data is still retained – in that case only for the holder of the Fylgra account the server belongs to. If a template is taken over or applied from a Discord template link, Fylgra retrieves it from Discord via our servers. We only keep the categories, channels and roles described above plus the template’s name, description and code – no details about the person who created it on Discord and no identifier of the server it comes from. Server templates are kept until the account holder deletes them. If their plan no longer includes them, we delete them after 90 days, at the latest together with the Fylgra account. When a template is applied to a server, we keep a copy of it with that server for up to 30 days.

If the owner of a server changes on Discord while Fylgra is on the server, we assign the server to the Fylgra account of the new owner; if they do not have one yet, we create it. The data stored for the server – including data of members – is retained and from then on belongs to that account. The plan of the previous account stays with that account. If the previous account is restricted because of a breach (section 21), we only reassign the server once the restriction has ended.

The legal basis is Art. 6(1)(b) GDPR (user agreement) and, for data of members, Art. 6(1)(f) GDPR; the legitimate interest lies in continuing a server without loss of data.

11b. Paid plans and payment via Stripe

Paid plans such as Fylgra Pro are sold and billed via Stripe (Stripe Payments Europe, Limited, Ireland, with the payment service Link). Stripe acts as the merchant and, under its own responsibility, collects in particular the e-mail address, name, billing address and payment details for the purchase, payment, invoice and taxes. Stripe sends receipts, invoices and notices about the subscription in its own name; on your bank statement the charge appears as LINK.COM*. Stripe’s privacy policy applies to this processing.

Fylgra stores only the Stripe customer identifier for the Fylgra account, the status and billing periods of the subscription, a trial period, refunds and disputes only as an event (without the amount), the time and version of a waiver of the right of withdrawal, whether the Terms of Service were accepted during checkout, and the identifiers of the messages that Stripe sends us about a subscription. We do not store names, addresses, payment methods or amounts. If the operator blocks purchases for an account, we store the time, the person acting and an internal reason; the operator can also see how often an account has already withdrawn from a contract.

Purchase through Discord

Fylgra Pro can also be bought as a subscription directly in Discord. In that case the seller is Discord (Discord Netherlands BV or Discord Inc.). Discord processes the data needed for the purchase, payment, invoice, taxes, cancellation and refunds under its own responsibility; the Discord Privacy Policy applies.

For such a purchase, Discord only tells us the Discord user ID of the buyer, the product purchased, the start and end of the term and whether the subscription has been cancelled. We store this information with the Fylgra account in order to set the plan. If the person does not yet own a server with Fylgra, we first store it without an account and assign it as soon as an account exists. We neither receive nor store names, e-mail addresses, payment methods or amounts. We delete ended purchases after twelve months.

The legal basis is Art. 6(1)(b) GDPR (contract for the plan) and, insofar as retention obligations exist, Art. 6(1)(c) GDPR.

11c. E-mails and cancellation form

We send e-mails about the contract, the trial period and cancellation – for example confirmations and the reminder before a trial period ends – via IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, Germany, as a processor. The recipient is the address stored with Stripe or the address given in the cancellation form. For the salutation, we read the name stored with Stripe; we do not store it ourselves.

Via the public cancellation form at fylgra.com/kuendigen, we process the information provided there (e-mail address, server ID, Discord name, requested date and reason) and match the e-mail address against the one stored with Stripe in order to assign it. We send a confirmation of receipt to the address given. To protect against misuse, we count requests per e-mail address and per IP network; for this, we only store values hashed with a secret key, which expire after no more than two hours or two days respectively. The legal basis for this is Art. 6(1)(f) GDPR.

The legal basis is Art. 6(1)(b) and (c) GDPR (performance of the contract, Section 312k BGB (German Civil Code)).

11d. Refer friends

With “Refer friends” you can recommend Fylgra to others. For valid referrals, you both get a week of Fylgra Pro (Terms section 10a). For this we process the following data. While the programme is in test mode, only test accounts enabled by the operator can refer or be referred.

Referral link. If you create a referral link, we store the link’s code, the time and how often it has been accepted, together with your Discord ID. From then on, and for as long as your link is active, we also store once a day a hash of your IP network, created with a secret key. This happens when you create the link and every time you sign in (for the purpose, see “Checks for misuse”).

Opening a referral link. When you open a referral link (fylgra.com/r/…), Fylgra shows a page on which you can accept the referral. Opening the link alone stores nothing and sets no cookie; as with every visit to the website, the request, including the code, only appears in the server log files (section 5).

Accepting a referral. Only when you click “Accept referral and sign in with Discord” do we store one entry per link, IP network and day with the number of acceptances. We do not store the IP address in clear text, only as a hash of the network: for IPv4 the full address, for IPv6 the first 64 bits. The hash is created with a secret key. This is pseudonymisation, not anonymisation: with the key, it would be possible to check whether an entry belongs to a particular IP address. Only Fylgra knows the key. We do not store browser identifiers or device characteristics.

Cookie. With the same click, Fylgra sets the cookie __Secure-fylgra_ref so that the referral can be assigned when you sign in. It contains a value that only refers to the entry for this acceptance, and it is only sent to the addresses used for signing in and for referral links. It is valid for 30 days and is deleted after a successful sign-in. An existing cookie is not overwritten; the first accepted referral counts. Without your click, Fylgra does not set this cookie. It is stored pursuant to Section 25(2) no. 2 TDDDG because it is necessary for the participation in the referral that you have expressly requested.

Assignment when you sign in. If you then sign in with Discord in this browser, we check whether you are new to Fylgra: you had never signed in before accepting, and no Fylgra account existed in your name before accepting. An account that is only created afterwards, because you add Fylgra to a server before signing in, does not count against this. Only if you are new do we store a referral with:

If you are not new, we do not store a referral, and the entry for the acceptance is only marked as “no effect”.

What the referrer sees. For each referral, the referrer only sees a sequential number (“Person 3”), the date of sign-in, the status – for example “waiting”, “still being reviewed”, “valid” or “expired” – and, where applicable, the date by which the requirements must be met or the review completed. They do not see the referred person’s name, Discord ID, servers or activity. Because they know whom they gave their link to, they may still be able to link a referral to a person. This information is therefore pseudonymous, not anonymous. The referred person never sees who referred them. Only they themselves see the status of their own requirements. In the operator panel, the operator sees both people with display name, account and server in order to review referrals.

Checking the requirements. Every night, Fylgra automatically checks whether a referral is valid, using data that is available anyway:

Checks for misuse. A week of Pro is meant to reward genuinely new servers, not second accounts. Once the requirements are met, Fylgra therefore checks the referral once automatically for signs of misuse:

No single sign leads to a rejection. If something stands out, the referral is “reviewed” and the operator decides personally. Only the operator sees the data checked and the results; customers are not shown a reason. If the operator does not decide within 30 days, the referral expires (Terms section 10a(11)). We do not use the server list that Discord transmits when you sign in (section 10) for this purpose.

Crediting. If a referral is valid, we store one credit each with the Fylgra accounts of those involved, with the time, status (saved up, redeemed, expired, withdrawn), expiry date and, where applicable, the reason why it has not yet been redeemed. A saved-up credit expires 12 calendar months after it was credited. This period is suspended while a paid subscription is running, while the account is restricted or while redemption fails for reasons outside your control (for example because your plan has no end date or is higher, or a plan change is scheduled); after the programme has ended, it is suspended for as long as redemption is not possible for any reason. If a purchase without a trial or a purchase in Discord replaces a running week, we credit the remaining full days as a new credit. With the referred person’s account we also store a marker that the one-time week has been granted. With the server’s ID we store a marker that it has already led to a reward. If a server moves to another Fylgra account (section 11a), the account marker is carried over there. Decisions by the operator (approval, rejection, withdrawal, blocking a link) are stored with the time, the person acting and the reason.

Retention period.

Legal bases.

You can object to processing based on point (f) (section 27). Without the misuse check, however, we cannot reward a referral.

11e. Help center

You can read the help center at fylgra.com/en/help and fylgra.com/hilfe without signing in. When you open it, we process the same data as for any page of this website (section 5).

The search in the help center runs entirely in your browser: the page loads a directory of the articles from our server once, and your search terms do not leave your device. Only if the page’s search script cannot be loaded does your browser send the search term to our server as part of the address; it then appears in the server log files (section 5).

So that we can show you the way to the dashboard instead of “Sign in”, the page asks our server whether you are signed in. Your browser sends the session cookie along if one exists (section 8). If you are signed in, this updates the day you last used Fylgra (section 10). Beyond that, we store nothing about this request apart from the server log files.

If you choose a light or dark appearance, your browser stores this choice locally (section 8). Videos in articles only load after you click (section 11, “Embedded YouTube videos”).

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is to provide help with Fylgra freely and without passing anything on to third parties.

12. General processing by the Discord bot

If Fylgra is installed on a Discord server, the bot processes the data that is necessary for technical operation and for the activated functions.

This may include in particular:

Discord transmits to the bot the messages in the channels visible to it, including their content. Fylgra does not ask for the Discord permission “Administrator” when it is invited; the server’s channel permissions then determine which channels the bot can see. If Fylgra has the “Administrator” permission on a server, because Fylgra was invited with it before 22 October 2026 or because the server granted it to the bot later, these are all channels of the server, including staff-only channels. Normal message contents are not stored permanently merely because Fylgra is installed on a server; if a server switches on the message log, Fylgra stores messages in the chosen channels in encrypted form for 7 days (section 15). At a server’s request, Fylgra also fetches older messages once via Discord’s interface in order to count them for Community Pulse after the fact; here, too, the content is discarded immediately (section 13, ‘Loading past messages’).

Message contents are only analysed or stored if this is necessary for a module expressly intended for that purpose, for example for tickets or for moderation, which checks messages in memory against the server’s rules (section 15a). Depending on the activated modules, the bot sends members direct messages, for example a welcome, a notice before it removes someone from the server for not confirming the rules, a message if a role could not be assigned, a warning, its revocation, the lifting of a timeout or the decision on an appeal by a server’s moderation (section 15a), or a message to the person who started loading past messages for Community Pulse once it has finished (can be switched off). It also sends a server's owner security notices, notices from moderation about a detected raid or a paused bot trap (section 15a) and the weekly summary of the change log (can be switched off, section 11).

Welcome when Fylgra is added: When Fylgra is added to a server, the bot reads the server’s audit log once to see who added it and sends that person a welcome direct message pointing to the dashboard. If the person cannot be determined this way, the message goes to the server owner. If the direct message cannot be delivered, for example because direct messages are blocked, or the person has recently received, or was due to receive, such a welcome, Fylgra instead posts a short message without naming anyone in the server’s system channel, provided Fylgra may write there; everyone who can see the channel can read it. We do not store in plain form who added Fylgra; this information is used to send the message. So that the welcome is not repeated every time Fylgra is added again and does not reach the same person more than once, Fylgra remembers for 7 days that the server has been welcomed and, for the recipient of the direct message, only a pseudonymised value of their Discord ID (a hash formed with a secret key); after that, both are deleted. We also store, for the server, when a welcome message was last attempted and with what result – delivered as a direct message, in the system channel, or not at all because neither was possible. We do not store who received it. We replace this with the next welcome message and delete it together with the server's other data. There is no welcome on servers and for accounts that are restricted because of a breach (section 21). The legal basis is Art. 6(1)(f) GDPR; the legitimate interest lies in pointing the person who uses Fylgra to its setup and help.

Getting started and dashboard use (operational evaluation). To help new servers get started and to see where something is stuck, our internal operator panel shows for each server whether Fylgra is still on the server and how long it was there, whether and how the welcome message was delivered, whether and when the server owner first signed in to Fylgra, whether the setup assistant was completed, whether and when a module was first set up, and whether the bot was used in Discord in the last 30 days (as a count, section 14). For this we store, for the server, the day the server owner last used this server's dashboard and the day another person with access last did – the date only, without a time, and without recording which team member it was. The panel also shows the day the owner last used Fylgra (section 10). We also count, per server and day, how often Fylgra showed an administrator the hint that a module can be switched on in the dashboard (each person at most once a day), and how often someone came to the dashboard through a link in a message from the bot (such as the welcome message or /help). These links carry a short addition that only names the origin (for example ?quelle=begruessung); the dashboard reports it once and then removes it from the address. So that nobody is counted twice, we remember until midnight (Coordinated Universal Time) that a person has already been counted on this server that day; afterwards only the number is stored, without any person. We also count, until midnight and per person, how many servers they have reported that day, and stop after a fixed number – so nobody can burden our systems with made-up servers. The panel does not show names or IDs of people. Only the operator sees this information; it never leads to any automatic action. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to provide Fylgra reliably, to help customers get started and to improve the product. If a server has objected to the evaluation of its usage figures (section 14), we count neither the names of commands nor hints or entries via links from the bot for it, and the panel does not show for it whether and how the bot was used in Discord. Hints and entries by the operator's staff are never counted.

The legal basis is Art. 6(1)(b) GDPR towards the server operator who uses Fylgra, and Art. 6(1)(f) GDPR for data of members; the legitimate interest lies in providing the functions requested by the server operator on their server.

The Discord privacy policy, over which we have no influence, applies to the processing of your data within Discord.

13. Community module and member-related activity analysis

If a server operator activates a community, activity or statistics module, Fylgra may record the use of the server on a per-member basis.

Depending on the respective configuration, the following data in particular may be processed:

Insofar as only the count of a message is needed for a statistic, the content of the message is not stored.

Fylgra may automatically create personal activity statistics from this data. These include, for example, analyses of

This processing may constitute profiling within the meaning of Art. 4(4) GDPR.

Display of personal statistics and charts

Fylgra may create personal statistics and charts from the stored activity data.

A member can, for example, call up an analysis of their own activity via a Discord command.

Among other things, this may show:

Personal activity statistics are shown to normal server members exclusively for their own data.

Other members cannot use this function to call up the personal activity data of another member.

Purpose

The purpose of the module is in particular:

The legal basis is Art. 6(1)(f) GDPR. The legitimate interest lies in enabling the server operator to manage their community and enabling members to gain insight into their own activity. In the balancing of interests, we take into account that no message contents are analysed, that normal members only see their own values, that leaderboards and lists of members who have gone quiet, come back or become more active are only visible to the server’s administrators and to those they allow, that every member can object to the count themselves at any time and that the data is stored only for a limited period (section 25). Keeping the Discord identifier and three times from the analysis of newcomers (joining, leaving, first activity) longer than the other entries after someone leaves a server serves to show the server operator how many newcomers of a period stayed. We take into account that no figures per day or channel are included, that the analysis only shows counts and only to people allowed to see the server’s analysis (administrators and anyone they give the “View” permission), that with very small groups it may still be possible to tell whether a particular person agreed to the rules after joining, wrote (in any counted channel, including one the viewer cannot see themselves) or left the server again, and that an objection deletes this data immediately – while you are on the server with /pulse tracking, afterwards by email to fylgra@fylgra.com (section 27). You can object to this analysis under Art. 21 GDPR (section 27).

Fylgra does not use member-related activity profiles for advertising.

No content analysis

Fylgra does not analyse the content of normal messages in order to determine a member’s interests, political opinions, state of health, religion, sexual orientation or comparable personal characteristics.

Insofar as the community module only needs to establish that a message was sent in a certain channel, the actual message content is not stored permanently.

Depending on the name and purpose of a channel, the mere assignment of an activity to certain channels may nevertheless allow conclusions to be drawn about personal interests or other characteristics.

Administrators of a server, and people they have given the “Change settings” permission, can therefore specify in the Community Pulse settings how individual channels and whole categories are counted; a category also applies to channels created in it later (such as tickets), and a channel's own setting takes precedence over that of its category. “Don’t count”: the channel is no longer counted at all – neither per member nor in the total without any link to individuals (section 14) – and numbers collected up to then are no longer shown anywhere. “Count separately”: the channel is only counted without any link to individuals and does not appear in the server’s totals but as a separate area that only the server’s owner and administrators can see. If a channel – on its own or through its category – is set so that it is no longer counted normally, the stored entries of individual members for that channel are deleted immediately; if a channel is moved in Discord into a category set this way, they are deleted by the following night at the latest. “Don’t count” continues to apply even if Community Pulse is switched off or removed from the server and only ends when the server’s data is deleted (section 25); “count separately” applies as long as Community Pulse is set up. They should use this particularly for sensitive or especially personal areas.

Community Pulse: messages and voice time per member, channel and day

If an administrator of a server has activated the “Community Pulse” module, Fylgra counts on that server, for each member, how many messages they wrote in a channel on a given day and how many minutes they spent in a voice channel on a given day. For each entry, the following is stored: the Discord identifier of the server and of the member, the channel, the date (Coordinated Universal Time) and the two counts. Message contents, attachments and the time of individual messages are not stored. Voice time is determined every five minutes by recording who is currently in a voice channel; it is therefore only accurate to about five minutes. In Community Pulse, the server’s AFK channel – the channel for members who are away – counts neither as voice time nor as being in a voice channel. Bots, webhooks and system messages are not counted, and messages in threads – private ones included – count towards the parent channel. Counting takes place in all channels the bot can see; if the server invited Fylgra with administrator permissions, these are all channels, including staff-only channels. A channel’s numbers are, however, only shown to people who can see that channel in Discord themselves. The totals, daily trends and times of day of the server as a whole, on the other hand, include all counted channels, including staff-only ones; they are never named there, neither in channel lists nor on image cards. Anyone who does not want this for certain channels sets them or their category to “count separately” or “don’t count”. Channels set to “don’t count” or “count separately” (see above) are not counted per member and are not included in the times of first and last activity either.

Ongoing counting begins once an administrator of the server activates the module. It pauses while the module is switched off or paused. For the period before activation, the server can have the figures loaded once from its message history (see ‘Loading past messages’ directly below).

Community Pulse: loading past messages

The owner of the server and people who have the “Administrator” or “Manage Server” permission there in Discord – if the owner has set in Fylgra that only they may manage modules, only the owner – can decide once that Fylgra catches up on the count for the period before activation from the server’s message history – either for the last 90 days or back to the start of the month twelve months ago (just over a year). The shorter option can be extended to the longer one once. To do so, Fylgra fetches older messages from the channels and threads the bot is allowed to read via Discord’s interface. Discord delivers them including their content. Fylgra only uses who wrote a message (Discord identifier), when, in which channel and what kind of message it is; everything else – text, attachments, mentions, replies – Fylgra discards immediately, without storing or logging it. This produces the same entries as ongoing counting: the number of messages per member, channel and day (above) and the figures without any link to individuals (section 14). Voice time, joins and departures cannot be loaded retroactively. For this, Fylgra stores per server the progress per channel and thread without any link to individuals, and the Discord identifier of the person who started it until the message about its completion, for at most 90 days; the start is recorded in the server’s change log (section 11).

Not loaded per member are: messages from bots and webhooks and system messages; members who have objected via /pulse tracking; after an objection has been revoked, only messages from that point on; members who have left the server, and messages from an earlier membership (before the latest join) – these messages only count towards the totals without any link to individuals (section 14); the time during which Community Pulse was switched off or paused on the server after the ongoing per-member count had started (on 27 September 2026 at the earliest). For the time before that, Fylgra reads the whole chosen period, including days on which Community Pulse was switched off back then. Channels and categories set to “count separately” or “don’t count” are treated as they are set at the time of loading, also for the past. Fylgra can no longer see deleted messages and channels; they are missing. Loading may move the time of the first message in the analysis of newcomers to an earlier date. Milestones include loaded messages; anything already exceeded as a result is not celebrated retroactively.

What this means for you as a member: Fylgra does not collect these figures from you but from the server’s message history. Fylgra does not announce the loading on the server separately; we inform you about it with this section (Art. 14 GDPR). You could not object to the counting of these older messages beforehand – you can do so at any time with /pulse tracking: the objection also deletes the loaded entries about you immediately, and any later loading leaves you out. The legal basis is Art. 6(1)(f) GDPR. The legitimate interest lies in server operators and members seeing how the community has developed, not only from activation onwards. In the balancing of interests, we take into account that these messages were written before Fylgra counted on the server, some before Fylgra was invited; on the other side, only counts are stored and no content, at most just over a year is loaded and the same retention periods apply, only the owner and people with “Administrator” or “Manage Server” can start the loading, the channel settings apply, a channel’s figures are only visible to those who can see the channel themselves, and an objection deletes everything about you immediately. You can also object under Art. 21 GDPR (section 27).

The purpose is to show members their own activity, to make the use of individual channels comprehensible to the server operator, and to show the most active members of a period – but only to the server’s administrators and to people they have given a dedicated permission for this (“See top members”). Only channels that the viewing person can see in Discord themselves are taken into account. For this list, Fylgra looks up the display name and the address of the profile picture of the members considered for the ranking (those shown and a few just behind them) through its Discord bot and caches them for at most eleven minutes; they are not stored permanently. If a member objects (below), their cached details and the server’s cached rankings are deleted immediately. The profile picture itself is loaded by the viewing person’s browser directly from Discord (section 11). The legal basis is Art. 6(1)(f) GDPR (see above).

Members who have gone quiet or come back: Community Pulse shows how many of the members present have neither written a message nor been in a voice channel for 30, 60 or 90 days, and how many became active again within a chosen period after a break of at least 14 days without activity; these numbers are visible to everyone allowed to see the server’s analysis (administrators and anyone they give the “View” permission) – a number of returning members below five, however, only as “under 5”, except for people who may also see the list of these members. To the server’s administrators and to people with the “See top members” permission, Fylgra also shows a list of these members with display name, profile picture and the day of their last activity (last message or time in a voice channel), or the day since which their activity has been recorded (after rejoining: the day they rejoined), and a list of members who have come back with display name, profile picture, the day they came back and the number of days without activity before that. Members who have never written or spoken during this time are shown separately from those who were active before. It is based on the data described above – the time of the last activity, the number of messages and the voice time per day, including where they were loaded from the history; nothing is newly collected or stored for it. All counted channels of the server are taken into account, including ones the viewing person cannot see themselves; the lists do not show which channel it was, nor any time of day, count or Discord identifier. Fylgra looks up display name and profile picture through its Discord bot as for the leaderboard and caches them for at most eleven minutes (see above). Members who have objected (below), who have left the server, and bots never appear. Fylgra notifies nobody and takes no action from the lists. The purpose is to show the server operator who in their community is not (or no longer) taking part and who has come back, so that they can involve these members (again) themselves. The legal basis is Art. 6(1)(f) GDPR. In the balancing of interests, we take into account that only administrators and people they expressly allow see the names, that only a day or a number of days is shown and nothing is newly collected, that the lists are not published and that an objection via /pulse tracking removes you from them immediately; on the other hand, such lists may prompt someone to contact individual members or remove them from the server. You can also object to this under Art. 21 GDPR (section 27).

Members who have become more active (“More active lately”): Community Pulse also shows how many members were active – wrote a message or were in a voice channel – on clearly more days within a chosen period than in the previous period of the same length. Only members who were still on the server at the end of the period are counted. This number is visible to everyone allowed to see the server’s analysis (administrators and anyone they give the “View” permission) – a number below five, however, only as “under 5”, except for people who may also see the list of these members. To the server’s administrators and to people with the “See top members” permission, Fylgra also shows a list of up to ten of these members with display name, profile picture and the number of days with activity in the chosen period and in the period before; the list is ordered by the increase but shows no ranking position. Only members who were already members during the whole earlier period, were recorded without interruption and were active there on at least one day are considered. It is based on the entries per day (above, including loaded ones) and the times of joining and leaving; nothing is newly collected or stored for it. All counted channels of the server are taken into account, including ones the viewing person cannot see themselves; the list does not show which channel it was, nor any time of day, number of messages, voice time or Discord identifier. Fylgra looks up the display name and profile picture of the members considered (those shown and a few behind them) through its Discord bot as for the leaderboard and caches them for at most eleven minutes (see above). Members who have objected (below), who have left the server, and bots do not appear in the list. Fylgra shows members who were active less often than before neither as a list nor as a number. Fylgra notifies nobody and takes no action from the list. The purpose is to show the server operator who is taking a bigger part in their community, so that they can notice and appreciate it. The legal basis is Art. 6(1)(f) GDPR. In the balancing of interests, we take into account that only administrators and people they expressly allow see the names, that only an increase and only two numbers of days are shown, that nothing is newly collected, that the list is not published and that an objection via /pulse tracking removes you from it and from the number immediately; on the other hand, a comparison of two periods shows more about the behaviour of individual members than a single number, and on very small servers the number may allow conclusions about individual people. You can also object to this under Art. 21 GDPR (section 27).

Analyses without names: From the same data, Community Pulse also shows counts and shares that do not name individual members: how many members were active in a period – that is, wrote at least one message or were in a voice channel –, per day and per week, and what share of the members that is; how many of them were active on a few, on several or on many days of the period; how many of them only wrote, were only in a voice channel, or both; for newcomers, after how many days half of them write for the first time and how many write on at least two days in their first week; how many members were active in a channel; and short notes that follow from these numbers and from the numbers of members who have gone quiet or come back (above), such as that more members are active in a channel than in the previous period. Only members who were still on the server at the end of the respective period are counted; the figures on newcomers – like the analysis of newcomers – also include those who have left the server again, as long as their entries per day are still stored. Bots and members who have objected (below) are not included. These numbers are visible to everyone allowed to see the server’s analysis (administrators and anyone they give the “View” permission); they cover all counted channels of the server; the number of active members of a channel is only shown to people who can see that channel themselves. They are based on the entries per day (above, including loaded ones) and the times of joining and leaving; nothing is newly collected or stored for this. The purpose is to show the server operator how many people actually carry their community and how that develops – regardless of how many messages individual members write. The legal basis is Art. 6(1)(f) GDPR. In the balancing of interests, we take into account that no names are shown, nothing is newly collected and an objection via /pulse tracking removes you from all of these numbers immediately; on the other hand, on very small servers or in very small groups a count may allow conclusions about individual people – for example if only one member came back after a break. You can also object to this under Art. 21 GDPR (section 27).

Image cards in Discord: With the Discord commands /pulse me, /pulse channel and /pulse server (in the German Discord app: ich, kanal, server), Fylgra creates an image from these numbers that at first only the person using the command can see. The personal card shows your own numbers, counted in channels you can see, and, where applicable, your place among the most active members; channel and server cards are only available to administrators and people with the “View” permission, and the display names of the most active members appear on them only with the “See top members” permission. With the “Share in channel” button, the person using the command can post the card in the channel where they used it; Fylgra posts it there with a note saying who shared it, and everyone who can see the channel can read it. The shared version only names channels that everyone in that channel can see, and your own numbers on it are counted only in such channels; the totals on a server card include all counted channels of the server, as everywhere (see above); it only contains display names of the most active members if an administrator has explicitly switched this on for the server (default: off). A shared personal card shows the sharing person’s display name and numbers. Members who have objected (below) do not appear on any card. Fylgra creates the images on its own server; channel and server cards are cached for at most two minutes, and this cache is cleared for the server immediately after an objection. A shared card is an ordinary Discord message: it remains until it is deleted – by the person who shared it or by someone with the permissions to do so. The legal basis is Art. 6(1)(f) GDPR (see above); sharing happens at the request of the sharing person.

Automatic posts: Administrators of a server, and people with the “Change settings” permission, can have Fylgra regularly post a weekly or monthly recap in a channel of their choice and celebrate the server’s milestones. A recap consists of the same server card as when sharing (see above: channel lists only with channels everyone in that channel can see, totals across all counted channels, display names of the most active members only if this has been expressly switched on) and a short text with the totals for the period. Server milestones are round member counts (people only, no bots), round numbers of messages on the server since counting began, and the anniversary of the server’s founding; they do not name individual members. Milestones of individual members only exist if administrators or people with the “Change settings” permission expressly switch them on for the server (default: off): Fylgra then names in that channel, once a day, members who have reached a round number of messages on the server (from 1000, counted as above since counting began for that member, only in channels counted normally – that is, all channels set to “count”, including ones not everyone in the post’s channel can see; anyone who does not want this for certain channels, such as staff-only ones, sets them to “count separately” or “don’t count”) or who have been on the server for one, two or more years that day (based on the join date Discord provides). They are named as a mention, which Discord displays with the current display name without notifying the member, together with the number or years reached. Members who have objected (below), members who have left the server and bots are never named. So that nothing is celebrated twice, Fylgra stores for each milestone reached its kind, value, for members their Discord identifier, and the channel and message of the post; in addition, per server, the values last checked (without any link to individuals). If a member objects, their milestones are deleted immediately and Fylgra removes their name from previous milestone posts (the message is rewritten without them or, if nothing else is in it, deleted), as far as Fylgra can match the post and still edit it in the channel; without access to the channel, Fylgra keeps trying for about a week. The posts are ordinary Discord messages that everyone who can see the channel can read; they remain until they are deleted. The legal basis is Art. 6(1)(f) GDPR. The legitimate interest lies in enabling the server operator to look back on and recognise their community; in the balancing of interests we take into account that individual members are only named on the server’s express decision, that no content and no leaderboards are published, that nobody is notified and that every member can object at any time via /pulse tracking.

The entries are stored per day for 13 months, counted from the day of the message, and deleted thereafter – loaded entries included, so their oldest days are deleted again shortly after loading. If a member leaves the server, their entries are deleted 90 days afterwards. The Discord identifier and the times of joining, leaving and first activity from the analysis of newcomers remain stored for 13 months after leaving; one whole calendar month is deleted at a time once all of it is older (at most just over 14 months). The time of the last activity is deleted 90 days after leaving, like the entries. Only this way does the analysis of newcomers for a period also count those who have left the server again. It shows counts, not names; with very small groups – for example a self-selected period of one day with a single join – conclusions about individual people are nevertheless possible. If an administrator switches the module off or removes it from the server, counting ends; the stored data is not deleted immediately as a result, so that switching it off or removing it by mistake does not cost any data. It remains stored until the periods stated; the times of joining and of first and last activity from the analysis of newcomers are then deleted 13 months after the last recording on the server. With /pulse tracking you can have your data deleted immediately at any time during this period as well (below). If Fylgra is removed from the server, section 25 applies.

Objection via command: With the Discord command /pulse tracking (in the German Discord app: /pulse erfassung) you can see whether you are counted on the respective server and object at any time – even while the module is suspended or switched off on the server. If it has been removed from the server, this works as long as data about you is still stored there; otherwise the command only shows that nothing is counted there – if you have left the server, you object by email to fylgra@fylgra.com (section 27). After a confirmation, all of the module’s data about you on that server is deleted immediately: your entries from the count and the times of joining and of first and last activity from the analysis of newcomers. This also applies to entries loaded from the message history. From then on you are no longer recorded there, not even by a later loading, do not appear in any leaderboard, any list of members who have gone quiet, come back or become more active, or any milestone, and are not counted in any of the analyses without names; your milestones are deleted and your name is removed from previous milestone posts (see above). So that this remains the case, Fylgra stores the objection itself (Discord identifier of the server and of the member, time) for as long as it applies – even if you leave the server. With the same command (“Count again”) you revoke it; counting then resumes from that point, deleted data does not come back. So that a later loading does not bring back anything from before, Fylgra stores the time of the revocation (Discord identifier of the server and of the member) for 13 months. Fylgra also uses this time as the start of recording for this member, for example as the day since which their activity has been recorded (list of members who have gone quiet). The server operator is not shown who has objected. Independently of this, you can contact us at any time in accordance with section 27.

14. Aggregated server and usage statistics

Independently of member-related analyses, Fylgra may process aggregated usage values of a server.

These may include, for example:

Aggregated server statistics are not intended to show detailed personal data of individual members.

Insofar as this data no longer allows individual members to be identified, it is processed as aggregated statistics.

This count runs on every server, regardless of which modules are activated. No user identifiers and no message contents are stored in the process. For commands we only store the name of the command as Fylgra offers it – never what someone entered with it. Counting takes place in the channels the bot can see – with administrator permissions, in all channels of the server, including staff-only ones (section 12). Channels that should not be included can be set to “don’t count” in Community Pulse (section 13). A server’s AFK channel is not included in voice time. If a server has its message history loaded in Community Pulse (section 13), Fylgra adds these figures for the period before as well, including the time before Fylgra was invited; messages from members who have since left the server are included too – likewise without user identifiers.

For messages and voice time, Fylgra additionally counts these values per channel and hour (Coordinated Universal Time) in order to show at which times of day a server is active. Here, too, no user identifiers and no message contents are stored. The hourly values are kept as long as the daily values: 13 months, with a whole calendar month deleted at a time once all of it is older than that (at most just over 14 months). When loading past messages, hourly values are created for the same period as the daily values. Channels that an administrator has set to “don’t count” in Community Pulse (section 13) are not counted here either. So that a category setting also applies to channels deleted in the meantime (such as closed tickets), Fylgra remembers for each counted channel the category it was last in. Fylgra also remembers the last known name of each counted channel, so that the server’s owners and administrators can still identify the figures of a channel that has since been deleted; only they see this name. Both without user identifiers, for as long as the daily figures.

Fylgra may use such statistics for technical operation, product improvement, capacity planning and error detection. As the operator, we can also tell from them whether the use of a server drops noticeably – for example because something is not working as expected. Only the operator sees this analysis, and it never leads automatically to any measure.

The legal basis is Art. 6(1)(f) GDPR. You can object to the analysis for your server at any time (section 27); the server is then excluded from it.

15. Tickets and other content modules

In modules whose function is precisely to store content, message contents may also be processed.

In the Tickets module, the following may be stored, for example:

The actual files sent via Discord generally remain with Discord, unless they are expressly stored additionally by Fylgra.

Other modules may store content such as the following:

Which data is processed depends on the activated module.

Monitoring modules (for example for Proxmox, Proxmox Backup Server or AMP) store the addresses and encrypted access credentials of the operator’s systems that the operator has entered, their measured values for 30 days and incident reports. These may contain user names of those systems, for example for tasks or backups.

The legal basis is Art. 6(1)(f) GDPR; the legitimate interest lies in providing the functions set up by the server operator – for example the handling of a ticket by their team.

Message log

A server's owner can switch on a message log for individual channels on plans that include it; it is off by default. When a message is deleted or edited, Discord does not tell Fylgra what it said before. To make deleted and edited messages traceable, Fylgra therefore stores every new message from members in these channels and, if chosen, in their public threads: the text, the Discord identifiers of author, channel and message, the time, the name, size and type of attached files, the names of stickers, whether a poll was included, and the number of embedded previews. The files themselves, messages from bots and webhooks, private threads and ticket channels are not included. We store this information encrypted and delete it 7 days after the message was sent or last edited. A server stores no more than 50 000 messages a day; beyond that, Fylgra stores nothing more until the end of the day.

If such a message is deleted or edited, Fylgra adds this to the change log (section 11): who wrote the message, in which channel, when, how many characters it had before and after and – where Discord records it in the server's audit log and the attribution is unambiguous – who deleted someone else's message. For this we store the content before and after in encrypted form for 7 days from the deletion or edit and delete the remaining details of the entry after 30 days. In Fylgra, the content can only be seen by the owner, administrators and people who are allowed to see the change log and have the "Manage Messages" permission in the affected channel in Discord; every view is recorded in the change log. The owner can also have Fylgra include this content in the messages it posts to a log channel (section 11): the text shortened, attached files and stickers only by their name. This only happens if everyone who can see the log channel – including other bots – has the "Manage Messages" permission in the affected channel in Discord, or if only the owner and administrators can read it. Fylgra removes the content from the message again after 7 days, earlier as soon as we delete it or the display is switched off, and if not all readers have this permission any more, usually within 20 minutes. Fylgra does not remove copies readers made before, such as screenshots. As long as the content is in the message, it is held by Discord. If Fylgra can no longer edit the message, for example because Fylgra was removed from the server or lost the permission to do so, the content remains there until someone on the server deletes the message; the server alone is then responsible for it (section 2). Reading in the log channel is not recorded individually; the change log shows who switched this display on or off. At the owner's request, Fylgra posts a notice in the chosen channels that the message log is switched on.

If the owner switches the message log off, deselects a channel, the plan no longer includes it or the server gets a new owner, storage stops immediately; we delete stored content within one hour and remove it from messages in log channels within the same period. The stored messages and contents are not part of the daily backups; backups made before maintenance work may contain them in encrypted form for up to 14 days (section 7). Fylgra uses them only for this feature and in particular not to train AI models. You can request the deletion of your stored messages at any time (section 27); we then also remove them from messages in log channels.

The purpose is moderating the server, for example to trace deleted insults, threats or spam. The legal basis is Art. 6(1)(f) GDPR; the legitimate interest lies in effective moderation of the server and in providing the feature requested by the owner. You can object to the processing on grounds relating to your particular situation (section 27).

15a. Moderation

If a server has activated the “Moderation” module and switched on at least one rule, Fylgra checks every new and every edited message from members in the channels the bot can see. Messages are checked against the rules the server has set, such as banned words, insults, links, mass mentions, capital letters, emojis or repeated messages. The check happens in memory only. Fylgra does not store messages that match no rule. To detect messages that repeat or follow each other quickly (only if the server has a rule against spam, constant capitals or emoji floods over time), Fylgra keeps in memory, for about eleven minutes at most (a time window of up to ten minutes plus the cleanup cycle), who wrote in which channel and when, together with a non-reversible checksum of the text and a few counts (such as the number of capital letters); a restart of the bot clears all of it. The exceptions set in the rule are exempt, and so are always the owner and the administrators of the server.

If a message matches a rule, Fylgra can, depending on the server’s settings, delete it, send the member a warning by direct message, show a short notice in the channel and inform the server’s team in a log channel. Members with the Discord permission “Timeout Members” can also warn members themselves (command /warn) and revoke warnings; if such a warning triggers an automatic consequence, Fylgra carries it out only if the person who warned has the matching Discord permission themselves (timeout, kick or ban), otherwise it stays recorded as “waiting”. For each warning we store: the Discord IDs of server, member, channel and message, the member’s display name at that time, the rule that matched or, for a manual warning, the ID of the person who warned, the reason, the time, which consequences were carried out and whether the direct message was delivered, and for a revocation also its time, person and reason.

If the server has switched it on, Fylgra also stores evidence for a warning issued by a rule: the text of the message (at most 2 000 characters), the name, size and type of attached files and the names of stickers, but not the files themselves. We store evidence encrypted and exclude it from our backups. Only people allowed to see the server’s records can view it, and only for channels they can see in Discord themselves (for threads, the parent channel); evidence from private threads and from channels deleted since is visible only to the owner and administrators. Every view is noted in the change log. Reports in log channels never contain the message text. If the server has also switched on the message log (section 15), it records a message deleted by moderation like any other deleted message, regardless of whether moderation stores evidence.

Records and visibility. A member’s warnings and penalties form their record. Only people who may “Timeout Members” on the server, or whom the server has given the permission, can see it. Everyone else with access to the module sees totals without names. Warnings, revocations and consequences also appear in the server’s change log; there too, names and reasons are shown only to people who may “Timeout Members” (and to the owner and administrators), other readers of the change log only see that a warning happened, not whom it concerns – not even through search and filters. The change log deletes these entries after its own period (set by the server, 365 days unless changed). The warned member learns by direct message the rule, the reason, their current count and what comes next; the name of the person who warned them is not included. The server can set the wording of these direct messages, of the notice in the channel and of the texts in the bot trap channel itself. Fylgra then only inserts the details mentioned where the server’s text provides for them.

Automatic consequences. The server decides after how many warnings a consequence follows automatically: a timeout, removal from the server or a ban. Fylgra carries out this consequence on the server’s behalf and stores its type, duration, cause, time and whether it succeeded (see section 22).

Retention. A warning counts for as long as the server has set: 30 days unless changed, at most 365 days. After that we delete it together with its evidence. We delete evidence earlier, after the period the server chooses: 30 days unless changed, at most 90 days; “don’t store” is available. The other details of the warning remain until it expires. Entries for automatic consequences are deleted with the warning that triggered them. A ban stays recorded as long as it exists on the server, for one year at most. If a member leaves the server, their record is kept until the periods end, so that warnings cannot be reset by leaving and rejoining. For overviews, Fylgra counts matches, warnings and consequences per day, rule and channel without personal reference and deletes these counts after 400 days. Deletion happens within about 10 minutes of the period ending, at the latest together with the server’s other data.

Block instantly via Discord. For some rules (words, insults, links, mass mentions) the server can choose to have Discord not show the message at all. For this, Fylgra creates rules in Discord’s own AutoMod on the server: the rule’s word lists or patterns, including Fylgra’s built-in list of insults, and the exempt roles and channels. These rules are stored by Discord and can be viewed there by people with the Discord permission “Manage Server”. When Discord blocks a message, Discord informs Fylgra, including the message text. Fylgra treats this as a match under this section (warning and, where applicable, evidence with the same retention period). Notifications about Discord AutoMod rules that Fylgra did not create are discarded immediately without being stored. If a server removes the module, Fylgra deletes the Discord rules it created. If the server removes Fylgra itself instead, Fylgra can no longer delete them; they remain at Discord until the server deletes them.

Reports by members. Members can report a message to the server’s team through the Discord menu “Report to mods” if the server allows it. Fylgra then stores who reported it, whose message was reported, in which channel, a reference to the message, the optional note, how often the same message was reported, and whether the team has resolved the report. If the server stores evidence, Fylgra also stores the text of the reported message, encrypted and with the same retention period as evidence. The team sees the report in the mod channel (without the message text, but with the reporting person’s note) and in the record, including the name of the reporting person, so that misuse of reporting can be recognized. Fylgra does not tell the reported person who reported them; if they are part of the team themselves, they can see the report in the mod channel. Reports are deleted after the same period as warnings (30 days unless the server changes it, at most 365 days); the hand-over to the mod channel stays with Fylgra for at most one day. To limit misuse, Fylgra remembers for at most one day which messages a member has already reported and how many reports they have sent (identifiers only, no content).

Warning from the message menu. If the team warns a member through the Discord menu “Warn” on a message, Fylgra attaches that message to the warning as evidence if the server stores evidence (retention and visibility as above).

Test mode. A rule can first just observe: it doesn’t warn or delete. So that the server can check what the rule would have caught, Fylgra stores for each match only the time, the channel and the match – the word, phrase or link, for other rules a number such as the share of capital letters or the emoji, and for Fylgra’s built-in list of insults only the note “built-in list” –, not who wrote the message and not the rest of the text. This is deleted after 7 days, at most 50 per rule. Evidence, reports and this data are not part of any backup. The test field on the website, where the team types an example message, stores nothing.

Raid protection. If the server turns on raid protection, Fylgra counts how many members join within a short time – only as a number, without storing who joined; the numbers stay in temporary storage for at most two minutes. If Fylgra detects a raid (an unusual burst of joins), Fylgra can temporarily raise the server’s verification level, pause invites and temporarily time out new members, depending on the server’s settings. Only during a detected raid does Fylgra store who joined during that time (Discord ID, join time and whether the team banned the account through this list), so that the team can review and ban these accounts. This list is deleted 24 hours after the raid ends at the latest, earlier when the next raid is detected. For the raid itself, Fylgra stores the start, the end, the number of joins and the measures taken and deletes this after 400 days. People only appear there if someone from the team turns protection on by hand or bans accounts from the list: the change log then shows who did it, as for any other change. Fylgra informs the server owner about a detected raid by direct message and the team in the mod channel.

Bot trap. The server can set up a channel as a trap for spam bots, where nobody is supposed to post. Anyone who posts there (except the server’s team) is treated like a warning by a rule: Fylgra stores a warning, with evidence if the server stores evidence, and removes the account from the server (with a ban, depending on the setting) together with its messages from the last hour, the last 6 hours or the last 24 hours. Members who have been on the server for a longer time (the server sets how long, at least one day) are timed out for one hour instead, and their messages from the last hour are deleted. Accounts that post in the trap don’t get a direct message. If an unusual number of accounts post in the trap within a short time, Fylgra pauses it – it then only observes, as in test mode – and notifies the owner by direct message and the team in the mod channel, without naming anyone.

Appeals. If the server has switched it on, a warned member can appeal through a button in the warning direct message while the server’s period runs (7 days unless changed, at most 30 days). Fylgra creates a ticket in the server’s ticket module for this (section 15). It contains the member’s explanation, the rule, the reason, the channel and the warning count, but not the text of the warned message and not the name of the person who warned; only people with access to the records see those. The ticket is visible to the member and to the roles the server has set for this ticket type. The rule, reason and status of the warning are therefore visible to everyone who handles tickets of this type – even without access to the records. It is kept like any ticket, so also beyond the end of the warning. For the warning, Fylgra stores that and when an appeal was made, the ticket, the outcome, who decided and a reason in case of rejection; we delete these details together with the warning. The member learns the outcome by direct message. If the appeal is accepted, Fylgra revokes the warning and lifts a timeout it triggered. Fylgra counts clicks on the button for one minute per member (identifier only) to limit misuse.

“New on the server”. A rule can apply only to members who joined the server recently or whose Discord account is still young. For this, Fylgra reads the join date and the account age (from the Discord ID) when checking a message and stores neither.

The legal basis is Art. 6(1)(f) GDPR. The legitimate interest is enabling the server to provide a safe and respectful environment and to protect it from spam, harassment and raids. In weighing interests we take into account that messages without a match are not stored, that evidence is stored encrypted, briefly and only if the server wants it, that only the server’s team sees records, and that every warning can be revoked by hand.

16. Welcome and joining functions

If welcome or joining functions are activated, the following may be processed in particular:

Depending on the server’s settings, Fylgra greets new members in the channel and sends them a direct message whose content is determined by the server.

Certain data may be cached briefly in order to prevent duplicate greetings or mass messages.

For this purpose, the Discord identifier of a newly joined person may be stored for up to 24 hours.

If a greeting is only to take place after agreement to the rules, the identifier may be stored together with the time of joining until the person agrees or leaves the server, for no more than seven days.

Fylgra records who has agreed to a server’s rules, with their Discord identifier, the version, the time and whether the agreement was given by click or taken over from existing members when the rules were set up (retention period: section 25). This agreement log is visible in the dashboard to the people allowed to view the rules there (the owner, administrators and anyone they give the “View” permission) – with the person’s display name, where available, and whether they are still on the server; Fylgra looks up both when the log is opened and does not store them for this purpose.

The legal basis is Art. 6(1)(f) GDPR; the legitimate interest lies in the server being able to receive new members, point them to its rules and demonstrate who has agreed to the rules, and in preventing repeated and mass messages.

17. Linked accounts

Users can voluntarily link external accounts to Fylgra.

These include in particular:

When an account is linked, the following may be stored in particular:

Linking is voluntary.

The legal basis is, as a rule, Art. 6(1)(a) GDPR or Art. 6(1)(b) GDPR, insofar as the link is necessary for the expressly requested function.

The link can be undone at any time.

18. Google and YouTube API services

Fylgra uses the YouTube API Services. If you link a YouTube account, Fylgra uses the permission “View your YouTube account” (read-only) to read the identifier and name of your channel in order to show the link in your profile. We will describe functions that use this link here before they start. Access and refresh tokens are stored in encrypted form and deleted when the link is undone.

The use and transfer of information that Fylgra receives via Google API interfaces takes place in accordance with the Google API Services User Data Policy, including the Limited Use requirements contained therein.

In particular, this means: data from Google services is used exclusively to provide the functions you have visibly requested. It is not used for advertising, not sold, not passed on to third parties and not analysed to create user profiles. No human review takes place, unless you have expressly consented, it is necessary to resolve a security incident, or it is required by law.

When you use these functions, the YouTube Terms of Service and the Google Privacy Policy apply. In addition to doing so in your profile, you can also revoke Fylgra’s access in the permissions of your Google account.

19. Twitch functions and giveaways

Server or channel operators can use Fylgra for Twitch functions.

In the process, personal data of Twitch users who do not have a Fylgra account themselves may also be processed.

Giveaways

In a giveaway run via Fylgra, the following may be processed in particular:

Message contents are not stored permanently if the respective function only requires that a message or a keyword was sent.

Fylgra does not disclose a person’s weighting, number of entries or chance of winning to anyone, not even to the organiser.

Entry via chat activity

If a person can take part through activity in the Twitch chat, Fylgra may, during the period relevant to the giveaway, store or cache on which days a Twitch identifier was active in the chat.

This information serves exclusively to determine participation or a weighting specified by the organiser.

Objection: Anyone who does not want to take part automatically via chat activity can object to this at any time (Art. 21 GDPR) by writing !giveaway-aus (or !giveaway-off) in the channel’s chat. From then on, we no longer note any chat activity of that person on this channel. We store the objection with the Twitch identifier, the channel and the time for as long as it applies; it can be withdrawn with !giveaway-an (or !giveaway-on). An objection is also possible by e-mail to fylgra@fylgra.com.

Draw

A draw is carried out automatically according to the rules set by the organiser.

In the process, a random result may be generated taking into account the weighting that has been set.

Data may be stored about people who are drawn so that the draw remains traceable.

Winners’ names may be displayed in the Twitch chat or in a stream overlay used by the organiser.

The organiser decides whether and how such a publication takes place.

Overlay and stream

If an organiser activates an overlay for their streaming software, the following data in particular may appear publicly in the stream:

A stream may be recorded by the organiser or by third-party platforms.

Fylgra cannot subsequently fully retrieve content that has already been published or recorded.

Legal basis

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in providing the organiser with this tool without being able to obtain consent in advance from every participating person. For entry via chat activity, we take into account that the recording is limited to the duration of a giveaway, covers only the Twitch identifier per day, is kept for a short time only and can be ended at any time with a chat command. The organiser of every giveaway is the owner of the Twitch channel (section 8 of the Terms of Service); they are expected to inform their viewers about automatic participation. If they authorise other members as helpers, we store their Discord identifier, name and level until the organiser withdraws the authorisation.

20. Feedback and support

When you contact us or use the feedback function, the following may be processed:

The data serves exclusively to handle the request, troubleshooting and support. Reports from the feedback function are additionally transferred to an internal Discord channel of the operator. Depending on the server’s settings, shared reports can also be seen by other authorised persons on that server.

The legal basis is Art. 6(1)(b) or (f) GDPR.

Feedback reports remain stored until the data of the associated server is deleted at Fylgra; the copy in the internal Discord channel remains until the operator deletes it there. Requests by e-mail are, as a rule, deleted once they have been dealt with, no later than after twelve months, unless longer retention is necessary.

21. Misuse, breaches and restrictions

In the event of a breach of the Terms of Service or of misuse, data may be processed in order to restrict a server or an account (section 6 of the Terms of Service).

This may include:

The statement of reasons is seen only by the owner of the affected account; they also receive a short direct message via Discord. Everyone else, including in Discord, only sees the sentence “Fylgra is restricted on this server. The server owner has been informed.” The internal note is seen only by the operator. If an affected server belongs to someone else on Discord, that person also receives a direct message without details.

The legal basis is Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR.

The legitimate interest lies in protecting Fylgra, other users and third parties against misuse and in being able to trace breaches.

You can send an appeal against a restriction by e-mail to fylgra@fylgra.com; it is independent of your rights under the GDPR (section 27).

22. Profiling and automated decisions

Certain community functions may automatically calculate personal activity values.

These may include, for example:

This may constitute profiling within the meaning of Art. 4(4) GDPR.

The analysis serves, as a rule, to show the respective member their own activity and, where applicable, to create aggregated statistics about the general use of a server.

Personal activity profiles of other members are not shown to normal members.

Fylgra does not use such activity profiles on its own initiative to take a decision regarding a member that is based solely on automated processing and produces legal effects or similarly significantly affects them.

The detection of mass deletions (section 11) does not assess people or make decisions about them; it only reports what happened on the server.

The getting-started overview in the operator panel (section 12) does not assess people and makes no decisions; it only shows which steps have taken place on a server.

For “Refer friends”, Fylgra automatically checks whether the requirements are met and whether there are signs of misuse (section 11d). A rejection is not made automatically by Fylgra but by the operator after a personal review. A referral expires automatically only if its requirements are not met in time or the review is not completed within 30 days.

With moderation (section 15a), Fylgra automatically checks messages against rules set by the server and automatically carries out the consequences the server has set, up to removal from the server or a ban. Likewise, the bot trap automatically removes anyone who posts in its channel, and raid protection automatically changes server settings when an unusual number of members join. Rules, thresholds and consequences are decided by the server alone; Fylgra does not assess anyone beyond these rules. Every warning and every consequence is visible to the server’s team and can be revoked by it or lifted in Discord. Please contact the server’s team for this. An accepted appeal automatically lifts a timeout it triggered.

In giveaways, the selection of a winner may take place automatically. The entry conditions and rules of the giveaway are set by the respective organiser.

23. Recipients of personal data

Depending on the respective function, personal data may be transmitted to or processed for the following recipients:

RecipientPurposePlace of establishment
netcup GmbHHosting and server operation (processor)Germany
IONOS SESending contract and cancellation e-mails (processor)Germany
Discord Netherlands BV / Discord Inc.Discord sign-in, bot functions, communication via Discord, forwarding of feedback to an internal channel and delivery of profile pictures and server icons in the dashboard (section 11), and sale of Fylgra Pro through Discord under its own responsibility (section 11b)Netherlands / USA
Stripe Payments Europe, Limited / Stripe, Inc.Sale and billing of paid plans (own responsibility)Ireland / USA
Twitch Interactive, Inc.Twitch links, Twitch chat and Twitch functionsUSA
Google LLC / Google Ireland LimitedYouTube and Google API functions; embedded videos in news only after your click (section 11)USA / Ireland

In addition, depending on the respective function, personal data may be accessible to the respective server or channel operator, administrators or other expressly authorised persons, insofar as this is necessary for the corresponding administrative function.

If a server owner has switched this on, the content of deleted or edited messages can be visible to the readers of a log channel who may manage messages in the affected channel (section 15).

Personal activity statistics of the community module are, as a rule, shown to normal server members only for their own person.

Other normal server members do not gain access to the personal activity data of another member via this function.

In Twitch giveaways, the names or display names of a winner and – in the animation of a draw – of other participants may be displayed publicly in the Twitch chat or stream in accordance with the configuration chosen by the organiser.

24. Transfers to third countries

When Discord, Twitch, Google, Stripe or comparable external services are used, personal data may be processed outside the European Economic Area.

Insofar as a recipient in the USA is certified under the EU-US Data Privacy Framework, a transfer may be based on the corresponding adequacy decision of the European Commission.

Insofar as no adequacy decision applies, appropriate safeguards pursuant to Art. 46 GDPR are used where necessary, in particular standard contractual clauses.

25. Retention period

As a rule, Fylgra stores personal data only for as long as it is needed for the respective purpose.

The following periods apply in particular:

DataRetention period
Server log filesno more than 14 days
System logsas a rule, no more than twelve months
Technical error messages of individual modulesno more than 7 days after the last error
Session datano more than seven days or until you sign out
Discord access tokenuntil you sign out, until it becomes invalid, or no later than 14 days after the last sign-in
Cached Discord server listas a rule, no more than five minutes
Welcome when Fylgra is added: markers for the server and the recipient (section 12)7 days
Sign-in data (Discord identifier, user name and display name, profile picture)until you request its deletion
Day you last used Fylgra (section 10)only the most recent day; until you request deletion of your sign-in data
Day the server's dashboard was last used by the owner or the team; time and result of the last welcome attempt (section 12)only the most recent value; until the server's data is deleted
IP addresses in the change log90 days
Change log of a server365 days or the shorter period set by the owner (30, 90 or 180 days); entries about tickets as long as the ticket history; at the latest together with the server’s data
Entries from the Discord audit log in the change log, including identifiers of the acting and affected personas for the change log
Log channels: which entry was reported in which message14 days
Security-notice mark (Watchdog)as long as the change-log entry
Marker against duplicate security direct messagesat most 24 hours
Watchdog and weekly summary settings, including the Discord ID of the person who last changed them; week of the last weekly summaryuntil the server's data is deleted
Message log: stored messages (encrypted, section 15)7 days after sending or last edit; within one hour when switched off; not in daily backups
Message log: content of deleted or edited messages (encrypted)7 days after deletion or edit; within one hour when switched off; not in daily backups
Message log: content in messages of a log channel (held by Discord)7 days after the deletion or edit; earlier when switched off (within one hour) or when not all readers may manage messages any more
Message log: change-log entries without content (including viewing a content)30 days
Moderation: warnings, consequences and reports (section 15a)the server’s period (30 days unless changed, at most 365 days); a ban as long as it exists, at most one year
Moderation: evidence (message text, encrypted)the server’s period (30 days unless changed, at most 90 days); not in backups
Moderation: matches in test mode (time, channel, match)7 days, at most 50 per rule; not in backups
Moderation: markers against repeated reports and hand-over to the mod channelat most one day
Moderation: who joined during a detected raiduntil 24 hours after the raid ends
Moderation: raid details without personal reference and daily counts400 days
Moderation: appealswith the warning; the ticket like ticket histories
Server structure history (state before/after, through Fylgra and directly in Discord)90 days, at the latest together with the server's data
Discord identifier of the person who made a change directly in Discord, in the history45 days
Members of deleted roles in the history and role assignments in backups30 days
Fylgra account with plan and plan historyas long as a server belongs to it or a paid plan is running; thereafter no earlier than 30 days after the end of the plan or, if there never was one, at the latest in the following night
Own server templatesuntil the account holder deletes them; 90 days after the plan no longer includes them, at the latest together with the Fylgra account
Payment data at Fylgra (Stripe customer identifier, subscription status)together with the Fylgra account; identifiers of Stripe messages 90 days
Information from the cancellation formuntil 12 months after the matter has been concluded
Read status of dashboard news (seen, hidden, confirmed, button used; section 11)until the news item is deleted, at the latest 12 months after it ends; together with your sign-in data
Linked accountsuntil the link is undone
Ticket historiesas long as the server’s data exists at Fylgra; individual tickets cannot currently be deleted
Feedback reportsuntil the data of the associated server is deleted
Consents to the server rulesuntil the server’s data is deleted, also after leaving the server
Requests by e-mailuntil dealt with, as a rule no more than twelve months
Restrictions for breachesuntil the server or account is deleted, thereafter as a restriction note for a further 12 months
Note of an early deletion on request3 years from the end of the year of deletion (Art. 6(1)(c) GDPR)
Notes and logs of interventions by the operator (removal of the bot, plan and key management)12 months
Values from audience measurementpermanently as statistics, without any link to a person once the day has passed
Count per server without any link to individuals (section 14)daily values 13 months from the day counted or the day of the loaded message, thereafter monthly totals; until the server’s data is deleted
Count per server, channel and hour without any link to individuals (section 14)13 months from the hour counted or the hour of the loaded message, deleted one whole calendar month at a time (at most just over 14 months); no monthly totals; until the server’s data is deleted
Last seen category and last known name per counted channel, without user identifiers (section 14)13 months after the last count in the channel; until the server’s data is deleted
Counts per command, “hint shown” and “entry via a link from the bot” per server and day (sections 12, 14)like the server's other usage figures; until the server's data is deleted
Marker against double counting (Discord ID, server ID) and check counter per person (Discord ID, a number)until midnight (Coordinated Universal Time) of that day
Community Pulse: cached channel and server cards (section 13)at most two minutes; deleted immediately after an objection
Community Pulse: Discord identifier and times of joining, leaving, first and last activity per member (analysis of newcomers, section 13)while the member is on the server; after leaving, the time of the last activity 90 days, the other details 13 months, deleted one whole calendar month at a time (at most just over 14 months); 13 months after the last recording if Community Pulse is switched off or removed; deleted immediately after an objection
Community Pulse: messages and voice time per member, channel and day (section 13)13 months from the day of the message, loaded entries included, also after the module has been switched off or removed; after leaving the server 90 days; deleted immediately after an objection via /pulse tracking
Community Pulse: milestones of individual members (section 13)posted ones: while the member is on the server and up to 90 days after leaving, or up to 13 months after Community Pulse was switched off or removed on the server – only this way can Fylgra remove the name from the post after an objection; unposted ones at most 400 days and only while the person is being counted; deleted immediately after an objection or after the name has been removed
Community Pulse: records of automatic posts (section 13)400 days
Objection via /pulse trackingfor as long as it applies, even after leaving the server; the time of a revocation 13 months; in each case until the server’s data is deleted
Community Pulse: status of loading past messages (section 13)progress per channel and thread without any link to individuals: until the server’s data is deleted; Discord identifier of the person who started it: until the message about its completion, at most 90 days
Refer friends: acceptances of referral links and hashes of the IP network (section 11d)30 days
Refer friends: results of the misuse check (numbers only)90 days after the referral is concluded
Refer friends: referrals and decisions on themuntil the end of the calendar year following their conclusion
Refer friends: creditsuntil the Fylgra account is deleted; saved up for no more than 12 calendar months, the period is suspended in the cases listed in section 11d
Refer friends: blocked referral link12 months after the Fylgra account ceased to exist, but not before no referral is linked to it
Refer friends: marker for the server IDno fixed period, also after the server’s data has been deleted (section 11d)
Backupsno more than 14 days; daily backups without the contents of the message log

Community activity data

Detailed personal data of the community module is stored only for as long as it is necessary for the statistics activated by the server operator.

For member-related activity data, a rolling maximum retention period of 13 months generally applies.

This may include in particular:

Older data may subsequently be retained exclusively in aggregated form, provided that individual members can no longer be identified from it.

If a member leaves the server, their personal community activity data is deleted after 90 days, the Discord identifier and the times of joining, leaving and first activity after 13 months (one whole calendar month at a time, at most just over 14 months; section 13), unless other legally permissible processing or retention is required.

If the community module is switched off or removed from the server, the further collection of the activity data intended for this module ends. Data already stored is not deleted immediately as a result, but after the periods stated, the times of joining and of first and last activity 13 months after the last recording on the server. With /pulse tracking they can be deleted immediately at any time (section 13).

Twitch giveaways

Entry data of a completed or cancelled giveaway is, as a rule, deleted no later than after 30 days.

Data of people who were drawn may be stored in personal form for up to 90 days after the draw as proof that the giveaway was carried out properly, and anonymised or deleted thereafter.

While Fylgra has restricted the server because of a violation – including through the Fylgra account it belongs to (section 21) – this data is not deleted or anonymised, so that no evidence is lost; Fylgra usually catches up on this in the night after the restriction ends.

Short-term notes on chat activity are deleted after the end of the giveaway or after the period required for entry has expired.

An objection to entry via chat activity remains stored for as long as it applies.

Removing Fylgra from a server

If Fylgra is removed from a Discord server, the data stored for this server may initially be retained so that an accidental removal can be undone.

No earlier than 30 days after the removal, usually in the night after this period has expired, the server’s data is deleted automatically, including the data of its members. If a paid plan is running for the associated Fylgra account, this period is suspended for all of the server’s data and only begins when the plan ends.

Earlier deletion can be requested, unless statutory or contractual reasons prevent it.

This does not apply to the “Refer friends” markers for the server ID (section 11d).

The data disappears from backups no later than a further 14 days later.

26. Provision of personal data

Certain data is required in order to be able to use Fylgra.

In particular, a Discord account is required for the signed-in area.

Without the data required for signing in with Discord, the dashboard cannot be used.

For a paid plan, the information that Stripe requires for purchase and payment is necessary.

Voluntary account links with Twitch, YouTube or other services are only necessary if a function is to be used that requires this link.

As a rule, community members do not have to create their own Fylgra account.

However, the use of individual Discord servers and their functions may result in personal data being processed via Fylgra.

27. Rights of data subjects

Subject to the statutory requirements, data subjects have in particular the following rights:

Consent that has been given can be withdrawn at any time with effect for the future.

An objection to processing based on Art. 6(1)(f) GDPR can be made on grounds relating to the particular situation of the data subject. This applies, for example, to the analysis of your server’s usage figures (section 14) – please tell us which server this concerns – or to the member-related activity analysis (section 13). For the Community Pulse count there is additionally the Discord command /pulse tracking (section 13), which takes effect immediately – even while the module is suspended. For entry into giveaways via chat activity, there is additionally the chat command from section 19.

Early deletion of a server’s data: If Fylgra has been removed from a server, the owner of the associated Fylgra account can request that we delete this server’s data before the period set out in section 25 has expired – even while a plan is running. We keep a note of the deletion with the server identifier, time and reason, so that we can prove that we complied with the request (Art. 6(1)(c) in conjunction with Art. 5(2) GDPR).

Requests can be sent informally to fylgra@fylgra.com.

28. Rights regarding data of a Discord server or Twitch channel

Even if your data is processed via a Discord server or Twitch channel of another operator, you can assert your rights directly against Fylgra.

Insofar as an operator uses data further themselves – for example content published in Discord – you can additionally contact them.

When making a request, please state, where possible, which Discord server, Twitch channel and which Discord or Twitch account it concerns, so that the data concerned can be clearly identified.

29. Information for community members

Discord members, Twitch viewers or other persons may be affected by processing without having a Fylgra account themselves.

Fylgra provides the information about this processing in this privacy policy.

Server and channel operators should additionally inform their members or participants which modules they use – in particular if modules process personal activity data, ticket contents, rule agreements, giveaway data, warnings and moderation rules or comparable information.

30. Right to lodge a complaint

Under Art. 77 GDPR, data subjects have the right to lodge a complaint with a data protection supervisory authority.

The authority responsible for the operator of Fylgra is in particular:

Supervisory authority Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz
Hintere Bleiche 34
55116 Mainz
Deutschland
poststelle@datenschutz.rlp.de

A complaint can also be lodged with another competent data protection supervisory authority, in particular at the place of habitual residence, place of work or place of the alleged infringement.

31. New and changed modules

Fylgra is continuously being developed further.

New or extended modules may enable additional processing of personal data.

Insofar as a new or extended module remains within the types of data, purposes and processing operations already described in this privacy policy, the respective information applies accordingly.

This may concern in particular functions that:

If, on the other hand, a new module leads to a new purpose of processing, substantially new categories of data, new recipients or a significantly changed use of personal data, this privacy policy will be amended before the corresponding processing begins.

Information about which data is processed for the function in question may additionally be provided in the dashboard or within the respective module.

32. Changes to this privacy policy

This privacy policy is amended when Fylgra, the services used or the legal requirements change.

The current version is available at fylgra.com/datenschutz (English translation: fylgra.com/en/privacy).

The date of the last change is given at the beginning of this privacy policy.