Skip to content

Conversation

@Aras14HD
Copy link
Collaborator

@Aras14HD Aras14HD commented Jan 13, 2026

In preparation for when we make the discord bot public, to fulfill the requirements for verification as fast as possible (when we get close to the limit of servers).

This is currently just a rough draft

@tolik518
Copy link
Owner

tolik518 commented Jan 13, 2026

I've also prepared and invite URL for the bot.
https://discord.com/oauth2/authorize?client_id=1425936019559153847&permissions=274877975552&integration_type=0&scope=bot

It runs on the same server as the reddit factorion and the url should always be valid, but it's currently deployed by hand.

Edit: I'll carefully read over the draft some time later

@tolik518
Copy link
Owner

tolik518 commented Jan 27, 2026

Some thoughts:

The message content is not stored if the server is configured correctly.

This sounds dangerous - it sounds like we're saying we don't know if the message content is stored. I'll look into the logs, but I think we never store the message content.

In any case, "Message content is never stored permanently" would sound more mild and is true as logs are cleared every now and then (I'll need to look the exact timings up and/or configure them).

Thinking about that, we probably would need to define a Data Retention for logs (DSGVO).
I would like to store Influx points "permanently" though.

Also because of DSGVO I will need to provide an email and/or discord name for users to make a Data Deletion Request. In such a request I would simply anonymize the username of the user

"Some statistics may be shared with the public"
I would add "anonymized" here, since the discord room/server ids are more secret as the subreddits, as far as I understand.

In the end I think we should say something along the lines that the data is "never sold" and is just aggregated for debugging and statistics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants