Missing GDPR end_user_data_statement in 3 new cogs (affiliates, ghostwipe, imagevault) #9

New issue

Open

opened 2026-08-03 04:13:10 -04:00 by everestmcarthur · 0 comments

everestmcarthur commented

2026-08-03 04:13:10 -04:00

(Migrated from github.com)

Summary

The three cogs added on 2026-07-28 (affiliates, ghostwipe, imagevault) are missing the end_user_data_statement field in their info.json. Every other cog in this repo has one (added in #6 for GDPR compliance across all 10 cogs).

This is more than a formality for two of these cogs — both actively persist end-user content to disk:

ghostwipe/ghostwipe.py:163-178 — stores message.content and attachment metadata for each purged message in a per-guild history config entry.
imagevault/imagevault.py:159,177,186 — stores message content (truncated) and re-hosts image attachments in a vault channel, indexed via _store_entry.
affiliates/ — stores Discord user IDs for POJ/affiliate-board/DM-affiliates management (lower risk, but still user data).

Fix

Add an end_user_data_statement to each of the three info.json files, following the pattern used elsewhere in the repo, e.g. (dashboard/info.json):

"end_user_data_statement": "This cog stores Discord user IDs for authentication sessions and blacklist management. No message content is stored."

For ghostwipe and imagevault the statement should explicitly mention that message content/attachments are persisted to disk.

Affected files

affiliates/info.json
ghostwipe/info.json
imagevault/info.json

## Summary The three cogs added on 2026-07-28 (`affiliates`, `ghostwipe`, `imagevault`) are missing the `end_user_data_statement` field in their `info.json`. Every other cog in this repo has one (added in #6 for GDPR compliance across all 10 cogs). This is more than a formality for two of these cogs — both actively persist end-user content to disk: - **ghostwipe/ghostwipe.py:163-178** — stores `message.content` and attachment metadata for each purged message in a per-guild `history` config entry. - **imagevault/imagevault.py:159,177,186** — stores message content (truncated) and re-hosts image attachments in a vault channel, indexed via `_store_entry`. - **affiliates/** — stores Discord user IDs for POJ/affiliate-board/DM-affiliates management (lower risk, but still user data). ## Fix Add an `end_user_data_statement` to each of the three `info.json` files, following the pattern used elsewhere in the repo, e.g. (dashboard/info.json): ``` "end_user_data_statement": "This cog stores Discord user IDs for authentication sessions and blacklist management. No message content is stored." ``` For `ghostwipe` and `imagevault` the statement should explicitly mention that message content/attachments are persisted to disk. ## Affected files - `affiliates/info.json` - `ghostwipe/info.json` - `imagevault/info.json`