0.3.4.0 - Blacklist system, Ping/Uptime commands & fixes
This commit is contained in:
@@ -24,6 +24,7 @@ The Bot collects only the minimum data necessary to provide its intended functio
|
||||
The following data is written to a local SQLite database (`database.db`) and is retained across restarts:
|
||||
|
||||
1. Marriage records — the Valour user IDs of both partners and the timestamp the marriage was created
|
||||
2. Blacklist entries — the Valour user ID of each blacklisted user
|
||||
|
||||
### Information Never Stored
|
||||
|
||||
@@ -41,6 +42,7 @@ Temporarily held information is used exclusively to:
|
||||
2. Enable core bot functionality during the current session
|
||||
3. Track echo message pairs to support automatic cleanup when the original command message is deleted
|
||||
4. Operate the marriage system (tracking active marriages and pending proposals/divorces)
|
||||
5. Enforce the blacklist (preventing blacklisted users from using bot commands)
|
||||
|
||||
The Bot does not use any information for profiling, marketing, analytics, or tracking purposes.
|
||||
|
||||
@@ -48,7 +50,7 @@ The Bot does not use any information for profiling, marketing, analytics, or tra
|
||||
|
||||
## 3. Data Storage and Security
|
||||
|
||||
In-memory data is automatically cleared when the Bot restarts. Marriage records are written to a local SQLite database file (`database.db`) on the machine running the bot. No data is sent to any external storage or cloud service.
|
||||
In-memory data is automatically cleared when the Bot restarts. Marriage records and blacklist entries are written to a local SQLite database file (`database.db`) on the machine running the bot. No data is sent to any external storage or cloud service.
|
||||
|
||||
The Bot does not sell, rent, trade, or otherwise share any data with third parties.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user