Skip to content

Latest commit

 

History

History
41 lines (30 loc) · 6.24 KB

PRIVACY.md

File metadata and controls

41 lines (30 loc) · 6.24 KB
Raw

Group Up's Privacy Policy

Information relating to Discord Interactions

Public Bot Information

Publicly available versions of Group Up#1305 (Discord ID: 847256159123013722) (herein referred to as The Bot or Bot) do not automatically track or collect user information via Discord.

Upon inviting The Bot to a user's guild, The Bot sends the guild name, Discord Guild ID, and current count of guild members to Burn_E99#1062 (herein referred to as The Developer) via a private Discord Guild. The guild name, Discord Guild ID, and current count of guild members are only used to roughly gage how popular The Bot is and to determine if The Bot's hosting solution needs to be improved. These pieces of information will never be sold or shared with anyone.

The Bot reads every message that it is allowed to, meaning if The Bot is allowed to see a channel in a guild, it reads every new message sent in said channel. This is for the automated cleanup of designated Event Channels.

The Bot does not read any user messages sent in the past, but does read its own past messages. This is to limit the amount of data that The Bot needs to store outside of Discord, giving users better control of their own data.

  • Messages that do not begin with The Bot's command prefix are not saved or stored anywhere. Messages that do not begin with The Bot's command prefix that are sent outside of a designated Event Channel are ignored and not processed.
  • Slash Commands sent to The Bot do not automatically log user data, and most commands to not log any data. The commands that log data are the report command (in Discord, this command is known as /report [message]), the Event Channel setup command (known as /setup), and the Create New Event command (known as /create-event or the Create New Event button).
    • The report command only stores the text placed within the message that is directly after the command (herein referred to as The Report Text). This command is entirely optional, meaning users never need to run this command under normal usage of The Bot. This command is only intended to be used to report roll commands that did not output what was expected. This command will accept any value for The Report Text, thus it is up to the user to remove any sensitive information before sending the command. The Report Text is stored in a private Discord Guild in a channel that only The Developer can see. The Report Text is solely used to improve The Bot, either by providing a feature suggestions or alerting The Developer to bugs that need patched.
    • The Event Channel setup command only stores Discord IDs. The setup command will always store the Discord Channel ID and Discord Guild ID from where it was run.
      • If the Event Channel setup command was run with the with-manager-role option, the submitted Discord Role ID and Discord Channel ID for the desired Manager Role and Log Channel will also be stored.
    • The Create New Event command stores the following data for every event that is created:
      • The Discord Message ID, Discord Channel ID, and Discord Guild ID of the event that the user created. These IDs are stored so that The Bot can locate the event for future use, including but not limited to: editing or deleting the event, and notifying the members of the event.
      • The Discord User ID of the creator. This ID is stored so that The Bot knows who created the event to control who can edit or delete the event. This ID is also used when The Bot fails to find an event so that the event creator is aware that The Bot was unable to notify the event members.
      • The full Date and Time of the event. The Date and Time of the event are stored so that The Bot can send notifications to members of events when the event starts.
    • If a Custom Activity is created during the Create New Event command, the following additional data is stored:
      • The Activity Title, Subtitle, and Max Members entered by the event creator. These are stored so that The Developer can determine if a new activity preset is necessary to improve user experience while using The Bot.
      • The Discord Guild ID that the Custom Activity was created in. This ID is stored so that The Bot can delete the Custom Activity from its database if The Bot is removed from the Guild.

All commands contribute to a global counter to track the number of times a command is used. These counters do not keep track of where commands were run, only counting the number of times the command has been called. These counters have no way of being tracked back to the individual commands run by the users.

If the Discord interaction is not explicitly mentioned above, it does not collect any data at all.

Private Bot Information

Privately hosted versions of Group Up (in other words, bots running Group Up's source code, but not running under the publicly available Bot, Group Up#1305) (herein referred to as Rehosts or Rehost) may exist. The Developer is not responsible for Rehosts, thus Rehosts of The Bot are not recommended to be used.

All policies described in Public Bot Information apply to Rehosts.

Due to the nature of open source code, Rehosts may not use the same codebase that is available in this repository. The Developer does not moderate what other developers do to this codebase. This means that if you are not using the publicly available Bot and instead using a Rehost, this Rehost could collect any information it desires.

Deleting Your Data

Event Deletion

If you wish to remove all data that The Bot has on your Guild, simply remove The Bot from your Guild. Upon removal, The Bot deletes all data on Event Channel, all data on Events created in the Guild, and all Custom Activities created in the Guild.

User Data Deletion

If you would like to ensure that all of your submitted reports are removed from The Bot's private development server, please contact The Developer via Discord (by sending a direct message to Burn_E99#1062) or via email (ean@milligan.dev) with a message along the lines of "Please remove all of my submitted reports from your development server.". Submitted reports are deleted from the server as they are processed, which happens roughly once a week, but this can be accelerated if requested.