✨ Add purge event for age assurance data for compliance#4709
Merged
Conversation
gcwill70
requested changes
Mar 4, 2026
| await this.db.db | ||
| .deleteFrom('moderation_event') | ||
| .where('subjectDid', '=', subjectDid) | ||
| .where('action', '=', 'tools.ozone.moderation.defs#ageAssuranceEvent') |
Contributor
There was a problem hiding this comment.
should we also delete tools.ozone.moderation.defs#ageAssuranceOverrideEvent?
Contributor
Author
There was a problem hiding this comment.
the override event is not user generated and does not contain any user info so i'm inclined to keep those.
| ) | ||
|
|
||
| if (isAgeAssurancePurgeEvent(event)) { | ||
| await this.purgeAgeAssuranceEvents(subjectInfo.subjectDid) |
Contributor
There was a problem hiding this comment.
Should the purge happen after the moderation_event insert in case it fails?
Contributor
Author
There was a problem hiding this comment.
I believe that's what we're doing here, the event insert happens above this line.
estrattonbailey
approved these changes
Mar 9, 2026
Member
estrattonbailey
left a comment
estrattonbailey
left a comment
There was a problem hiding this comment.
LGTM from my limited knowledge of this codebase 👍
gcwill70
reviewed
Mar 12, 2026
Contributor
gcwill70
left a comment
gcwill70
left a comment
There was a problem hiding this comment.
Left some comments to consider
estrattonbailey
added a commit
to bluesky-social/indigo
that referenced
this pull request
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For compliance reasons, we need to be able to purge all AA related data upon user request. This PR introduces a purge event for AA data which deletes the user generated AA events from ozone db. The intent is for other microservices to do the same upon receiving this new purge event.