MokoConsulting/MokoSuiteClient
0
0
Fork 0
Code Issues 99 Pull Requests Releases 3 Wiki Activity

feat(privacy): lifecycle hooks for cross-extension data wipe #232

New Issue
Open
opened 2026-06-21 20:30:06 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-21 20:30:06 +00:00
Owner
Copy Link
Copy Source

Summary

When a user account is deleted or anonymized, trigger hooks so all MokoSuite extensions can wipe their user data too.

  • Dispatch onMokoSuiteUserDataWipe Joomla event with user ID and wipe type (anonymize/delete)
  • Each MokoSuite extension listens and cleans its own tables
  • MokoSuiteClient: wipe tickets, consent log, WAF log entries for that user
  • MokoSuiteBackup: wipe user-specific backup profiles
  • Log all wipe actions in the audit trail
  • Integrate with Joomla's built-in onUserAfterDelete event

Reference

GDPR Article 17 — right to erasure must apply across all data stores.

## Summary When a user account is deleted or anonymized, trigger hooks so all MokoSuite extensions can wipe their user data too. - Dispatch `onMokoSuiteUserDataWipe` Joomla event with user ID and wipe type (anonymize/delete) - Each MokoSuite extension listens and cleans its own tables - MokoSuiteClient: wipe tickets, consent log, WAF log entries for that user - MokoSuiteBackup: wipe user-specific backup profiles - Log all wipe actions in the audit trail - Integrate with Joomla's built-in `onUserAfterDelete` event ## Reference GDPR Article 17 — right to erasure must apply across all data stores.
jmiller commented 2026-06-21 20:30:11 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/232-feat-privacy-lifecycle-hooks-for-cross-e

git fetch origin
git checkout feature/232-feat-privacy-lifecycle-hooks-for-cross-e
Branch created: [`feature/232-feat-privacy-lifecycle-hooks-for-cross-e`](https://git.mokoconsulting.tech/MokoConsulting/MokoSuiteClient/src/branch/feature/232-feat-privacy-lifecycle-hooks-for-cross-e) ```bash git fetch origin git checkout feature/232-feat-privacy-lifecycle-hooks-for-cross-e ```
Sign in to join this conversation.
Labels
Clear labels
architecture
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 bug
build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 duplicate
enhancement
generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 invalid
javascript
JavaScript code changes
 joomla
Joomla extension or component
 major-release
Major version release (breaking changes)
 minor-release
Minor version release (XX.YY.00)
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 needs-testing
Requires manual or automated testing
 patch-release
Patch version release (XX.YY.ZZ)
 php
PHP code changes
 priority: critical
priority: high
priority: low
priority: medium
push-failure
File push failure requiring attention
 python
Python code changes
 question
regression
Regression from a previous working state
 release-candidate
Release candidate build
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 standards-violation
Standards compliance failure
 status: blocked
status: in-progress
status: needs-review
status: on-hold
Temporarily on hold
 status: pending
Pending action or decision
 status: wontfix
This will not be worked on
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 test-failure
Automated test failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: release
Release preparation or tracking
 type: test
Test suite additions or changes
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-branch
Version branch related
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteClient#232
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?