liz/PluralKit
liz/PluralKit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Explicitly state information privacy in the privacy policy

Browse Source
This commit is contained in:
Ske 2020-01-23 22:14:32 +01:00
parent b4439ba872
commit 4922181fe1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/4-privacy-policy.md
View File

@ -10,7 +10,6 @@ description: I'm not a lawyer. I don't want to write a 50 page document no one w
I'm not a lawyer. I don't want to write a 50 page document no one wants to (or can) read. In short: I'm not a lawyer. I don't want to write a 50 page document no one wants to (or can) read. In short:
This is the data PluralKit collects indefinitely: This is the data PluralKit collects indefinitely:
* Information *you give the bot* (eg. system/member profiles, switch history, linked accounts, etc) * Information *you give the bot* (eg. system/member profiles, switch history, linked accounts, etc)
* Metadata about proxied messages (sender account ID, sender system/member, timestamp) * Metadata about proxied messages (sender account ID, sender system/member, timestamp)
* Aggregate anonymous usage metrics (eg. gateway events received/second, messages proxied/second, commands executed/second) * Aggregate anonymous usage metrics (eg. gateway events received/second, messages proxied/second, commands executed/second)
@ -25,9 +24,10 @@ This is the data PluralKit does *not* collect:
* Information added *and deleted* between nightly backups * Information added *and deleted* between nightly backups
* Information about messages that *aren't* proxied through PluralKit * Information about messages that *aren't* proxied through PluralKit
System and member information (names, member lists, descriptions, etc) are public by default, and can be looked up by anyone given a system/member ID or an account ID. This can be changed using the [privacy settings](/guide#privacy).
You can export your system information using the `pk;export` command. This does not include message metadata (as the file would be huge). If there's demand for a command to export that, [let me know on GitHub](https://github.com/xSke/PluralKit/issues). You can export your system information using the `pk;export` command. This does not include message metadata (as the file would be huge). If there's demand for a command to export that, [let me know on GitHub](https://github.com/xSke/PluralKit/issues).
You can delete your information using `pk;delete`. This will delete all system information and associated members, switches, and messages. This will not delete your information from the database backups. Contact me if you want that wiped, too. You can delete your information using `pk;delete`. This will delete all system information and associated members, switches, and messages. This will not delete your information from the database backups. Contact me if you want that wiped, too.
The bot is [open-source](https://github.com/xSke/PluralKit). While I can't *prove* this is the code that's running on the production server... The bot is [open-source](https://github.com/xSke/PluralKit). While I can't *prove* this is the code that's running on the production server... it is, promise.
it is, promise.