murm/mrmBot-Matrix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update PRIVACY.md

Browse source
This commit is contained in:
Essem 2021-10-05 16:47:43 -05:00
parent 636161ad99
commit d54e4e0117
No known key found for this signature in database
GPG key ID: 7D497397CC3A2A8C
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
PRIVACY.md
View file

@ -1,5 +1,7 @@
# esmBot and Privacy
First things first: esmBot does not collect IP addresses, emails, or any other personal/private info. This info is not accessible via Discord's API [except for emails](https://discordapp.com/developers/docs/resources/user#user-object), which require the email OAuth2 scope to access. esmBot does not use OAuth2 to link to a user account, therefore it does not have access to this info.
First things first: **esmBot does not and is incapable of collecting IP addresses, emails, or any other sensitive personal/private info.** This info is not accessible via Discord's API [except for emails](https://discord.com/developers/docs/resources/user#user-object), which require the email OAuth2 scope to access. esmBot does not use OAuth2 to link to a user account, therefore it does not have access to this info.
Whenever a command is run using esmBot, a command count number is increased. **This counter is completely anonymous and is used only for statistical purposes.** Users can check this info at any time using the count and help commands.
esmBot uses the following user-related info:
+ User IDs (needed for many reasons such as the tag commands and replying to users)
@ -9,18 +11,17 @@ esmBot uses the following user-related info:
+ Permissions (for checking if a user has perms to run some commands)
+ Whether the user is a bot (needed to prevent other bots from running commands)
Out of these, **only user IDs are stored in the database**, and they are used for checking the owner of a tag as well as storing a user's warnings.
![Tags section in the database](https://projectlounge.pw/pictures/tags.png)
Out of these, **only user IDs are stored in the database**, and they are used only for checking the owner of a tag.
esmBot uses the following guild-related info:
+ Guild IDs (for guild-specific settings)
+ Guild channel IDs (for getting where to send a message, storing disabled channels)
+ List of members (for getting permissions and obtaining user objects by ID)
+ Guild names (for embeds)
+ Icons (embeds)
Out of these, **only guild IDs are stored in the database** for configuration info and storing warns, disabled channels, prefixes, and tags.
Out of these, **only guild and channel IDs are stored in the database** for configuration info and storing disabled channels/commands, prefixes, and tags.
The stored info is stored in the database forever; however, I do intend to change this in the future. If you want this data removed, you can DM me on Discord (Essem#9261) or email me at [data@essem.space](mailto:data@essem.space).
The stored info is stored in the database forever; however, I do intend to change this in the future. If you want this data removed on the main instance, you can DM me on Discord (Essem#9261) or email me at [data@essem.space](mailto:data@essem.space).
Hopefully this document is clear enough to help understand what esmBot does and doesn't use. If you have any further questions, please contact me via the [esmBot Support](https://projectlounge.pw/support) server.