Privacy Policy

1.Controller

The controller for the processing described here is the following person. They run DualMod as a private individual (no company) from Switzerland:

Anil Erdal
E-mail: dualmod.support@gmail.com

For all data protection requests you can reach us by e-mail to dualmod.support@gmail.com or through our support server on Discord.

2.Scope

This policy applies to the DualMod Discord bot, the dashboard at dualmodverify.com and the Roblox verification pages. The operators of the Discord servers where the bot is used are responsible for their own use of it (see “Data entered by server staff”).

3.What we process and why

GDPR legal bases are given in brackets. Under the Swiss FADP, processing is permitted as long as it is proportionate, purpose-bound and transparent.

• Account verification: your Discord user ID, Roblox user ID and Roblox username. Login runs through Roblox OAuth; we never see your password. Purpose: linking the accounts and assigning roles and nicknames. (Art. 6(1)(b) GDPR – providing the service you ask for)
• Dashboard login: your Discord user ID, username, avatar and the list of servers you manage (via Discord OAuth), kept in a session cookie. (Art. 6(1)(b) GDPR)
• Reports: the reporter (Discord and Roblox name), the reported player, the reason, the proof and the status. If the server uses the cross-report system, the report is shown to the moderators of every server that has it enabled; otherwise only to the moderators of the server where it was made. Every report is also sent to the DualMod report feed. Purpose: safety and moderation of Roblox communities. (Art. 6(1)(f) GDPR – legitimate interests)
• Suggestions and bug reports: your Discord ID and username, the text you write, attachments, your votes and the staff response. (Art. 6(1)(b) and (f) GDPR)
• Player files (optional, per server): if a server turns this on, its moderators can keep internal records about a Roblox player: bans and unbans, warnings, notes and related reports, with the moderator and the date. A player file is only visible to authorised staff of that server. Other servers can at most see a number of cross-report reports, never notes or warnings. A warning can be sent to the linked Discord account by direct message. (Art. 6(1)(f) GDPR)
• Role rewards: which roles the bot granted you for Roblox badges, game passes or group ranks. (Art. 6(1)(b) GDPR)
• Ban-evasion protection: when you verify, we compare your Roblox account with Discord accounts linked to it earlier. If a linked account is banned on that server, your account is banned automatically. You can ask for a human review (see “Your rights”). (Art. 6(1)(f) GDPR – protecting the community from abuse)
• Alternate-account detection (Alt Detection, optional, per server): if a server turns this on, we rate how likely your account is an alternate account when you verify and when you join (a risk score from 0 to 100). We use publicly visible Roblox data (for example account age, number of friends, badges, groups, earlier usernames), the age and avatar of your Discord account and data of that server (banned players, similar usernames, friendships with banned players, several Discord accounts on one Roblox account, reports through DualMod). The result is a hint for the moderators, not a verdict; they decide. Nobody is banned automatically. Depending on the server’s setting, a very high score can lead to quarantine (verified role removed) or a kick. You can ask for a human review (see “Your rights”). We store the Roblox ID, username, risk score and the reasons per server. (Art. 6(1)(f) GDPR – legitimate interest in protecting the community from abuse)
• Server settings: settings entered by server administrators. Roblox API keys are stored encrypted. (Art. 6(1)(b) and (f) GDPR)
• Technical data: when you open our web pages, the web server briefly processes technical data such as your IP address to deliver the page and to defend against abuse. We do not build profiles from it. (Art. 6(1)(f) GDPR)

We do not sell your data and do not use it for advertising or tracking.

4.Data entered by server staff

Content that a server team enters into player files, reports or settings is the responsibility of that team for its own server. DualMod only provides the technical function and acts on behalf of the respective server in that respect. If you have a question about such an entry, please contact the team of the server concerned first.

5.Providing data is voluntary

Using DualMod is voluntary. Without the verification data above, however, we cannot link your accounts or give you roles.

6.Recipients

• Discord Inc. and Roblox Corporation for the login and to run the bot (each is a controller in its own right).
• Hosting: Bot-Hosting.net operates the servers DualMod runs on, on our behalf.
• DNS: Cloudflare, for resolving our domain name.
• Moderation teams of the Discord servers where you use the bot, and the DualMod review team for forwarded reports.
• Authorities only where we are legally required to.

7.Transfers abroad

Our server at Bot-Hosting.net is located in Germany, so within the EU. Some other recipients, in particular Discord and Roblox, are located in the United States. Our hosting provider may also use sub-processors outside the EU. Where required, transfers rely on an adequacy decision (for example the Data Privacy Framework) or on standard contractual clauses.

8.How long we keep data

• Account link and account data: until you ask us to delete it or the purpose no longer applies.
• Session cookie: 7 days, or until you log out.
• Reports, suggestions and bug reports: until they are deleted or the purpose no longer applies.
• Player file entries: deleted automatically after the period the server chose (90 days up to 2 years, or until deleted manually). Server staff can remove them at any time.
• Alt Detection results: deleted automatically after 90 days. The “marked safe” list stays until a moderator removes it.
• Technical data and logs: only as long as needed for operation and security.

Statutory retention duties remain reserved.

9.Cookies and external content

We set only one strictly necessary cookie (dualmod_session) that keeps you logged in to the dashboard (HttpOnly, SameSite=Lax, Secure, 7 days). No consent is needed for it (section 25(2) TDDDG). We use no analytics, advertising or tracking cookies.

We serve our fonts from our own server and do not call Google Fonts. Server icons and avatars are loaded by your browser from the Discord CDN (cdn.discordapp.com) and game images from Roblox (roblox.com); these providers receive your IP address in the process. The link to our hosting partner Bot-Hosting.net only transfers data after you click it.

10.Security

The connection to the website is encrypted with HTTPS. Roblox API keys are stored encrypted and access to data is limited to what is necessary. No system on the internet can be completely secure, however.

11.Your rights

Under the FADP and the GDPR you have the right of access, rectification, erasure, restriction of processing, data portability and objection to processing based on legitimate interests. You can withdraw any consent at any time with effect for the future. For automated decisions (ban-evasion protection and, if a server enables it, automatic quarantine or kick by Alt Detection) you can also ask for a review by a human and state your point of view.

To exercise your rights, write to us by e-mail to dualmod.support@gmail.com or through our support server on Discord. We usually reply within 30 days. We may ask for proof of identity.

12.Complaints

You can lodge a complaint with a data protection authority. In Switzerland this is the Federal Data Protection and Information Commissioner (FDPIC). If you live in the EU, you can contact the authority in your country (list of authorities). In Germany these are the data protection authorities of the federal states.

13.Children and teenagers

DualMod requires a Discord and a Roblox account. We do not knowingly process data of people below the minimum age of those platforms. If you believe this has happened, contact us and we will delete the data.

14.Changes

We update this policy when the service or the law changes. The version published here applies.