Javelina/Javelina
2
0
Fork 0
Code Issues 20 Pull Requests Actions Projects 1 Releases Wiki Activity

GDPR-compatible data usage consent system #51

New Issue
Open
opened 2025-06-01 02:06:19 +03:00 by profitroll · 0 comments
profitroll commented 2025-06-01 02:06:19 +03:00
Owner
Copy Link
  • Users must explicitly give consent prior to usage of modules or integrations processing and/or storing data
  • Duration and terms of the consent must be displayed to the user prior to accepting it
  • Users must be able to withdraw any given consent at any time
  • Users must be able to export all their own data being stored by the bot
  • User must be able to purge all possible data from the bot
- Users must explicitly give consent prior to usage of modules or integrations processing and/or storing data - Duration and terms of the consent must be displayed to the user prior to accepting it - Users must be able to withdraw any given consent at any time - Users must be able to export all their own data being stored by the bot - User must be able to purge all possible data from the bot
profitroll added this to the v1.0.0 milestone 2025-06-01 02:06:19 +03:00
profitroll added the Kind/Feature
Priority
High
 labels 2025-06-01 02:06:19 +03:00
profitroll self-assigned this 2025-06-01 02:06:19 +03:00
profitroll added this to the Javelina project 2025-06-01 02:06:19 +03:00
profitroll referenced this issue from a commit 2025-06-01 02:06:32 +03:00
WIP: Added stubs for #51
profitroll added reference feature/data-control 2025-06-01 02:06:35 +03:00
profitroll moved this to To Do in Javelina on 2025-06-01 16:29:53 +03:00
profitroll moved this to In Progress in Javelina on 2025-06-01 16:29:59 +03:00
profitroll added spent time 1 hour 2025-06-01 16:30:15 +03:00
profitroll added spent time 30 minutes 2025-06-01 17:01:00 +03:00
profitroll added spent time 1 hour 2025-06-07 01:42:06 +03:00
profitroll added the Scope/Bot label 2025-06-07 17:05:43 +03:00
profitroll added spent time 1 hour 2025-07-22 00:21:01 +03:00
profitroll added spent time 2 hours 2025-07-23 22:55:58 +03:00
profitroll added spent time 1 hour 15 minutes 2025-07-24 01:40:31 +03:00
profitroll added spent time 1 hour 2025-07-24 23:26:58 +03:00
profitroll added spent time 45 minutes 2025-07-28 02:12:56 +03:00
Sign in to join this conversation.
feature/data-control
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Scope/API
Involves API
 Scope/Bot
Involves Discord bot
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label Kind/Feature
Priority
High
 Scope/Bot
Milestone
No items
No Milestone v1.0.0
Projects
Clear projects
No project Javelina
Assignees
Clear assignees
profitroll Renovate
No Assignees profitroll
1 Participants
Notifications
Total Time Spent: 8 hours 30 minutes
profitroll
8 hours 30 minutes
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Javelina/Javelina#51
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?