Privacy Erasure
The Privacy Erasure page holds support's three erasure tools. Each one erases personal data on a documented request (GDPR Art. 17): a channel's instruction, or a person's own request. Every erasure is final and writes an audit event (System scope) with the request reference and the reason.
Where to find it
Admin sidebar → Moderation → Privacy Erasure (/privacy-erasure). The menu item, the page and every tool on it need admin:privacy-erase.
Quick start
- Open Admin → Privacy Erasure and pick the tab that matches the request.
- Choose the Channel account (tools 1 and 3): search by account or owner name, or paste the account ID. The account's connected channels show under the search result so you can check you have the right channel.
- Fill in the person or the record, the Request reference (ticket or letter number, at most 200 characters) and the Reason (at most 500 characters); in tool 1 also Who initiated the erasure?
- Click the submit button. A confirmation dialog names the channel, the person or record, the reference, the reason and (tool 1) Initiated by, and lists what is Erased and what Stays.
- Confirm. The result shows the Case number (the first 8 characters of the case ID) and how many entries were erased per data type. New erasure clears the form.
- If removed content appeared on an indexed Lumio Stats page, request a search-engine refresh after the Lumio removal. For Google, use Remove Outdated Content ("Veraltete Inhalte entfernen") for the affected URL. Record the request with the case. Search results may keep the old snippet until the search engine processes it; Lumio cannot remove third-party archives.
The three tools
Person in one channel
Erases one person's data in one channel only — on that channel's instruction, or on a person's request that concerns this channel.
- Person: either a Platform account (platform + platform user ID — the ID, not the display name) or a Lumio user (Lumio user ID; erases the person under every platform account that user signs in with).
- Who initiated the erasure? (required, no preselection): The channel when the channel instructed it, or The person when the person asked for it. The choice is stored on the channel's erasure list: an entry the channel initiated can later be withdrawn on the channel's instruction; an entry the person asked for can never be withdrawn on the channel's instruction. The confirmation dialog repeats the choice.
- Erased: chat messages in the channel, the person's profile in the channel, moderator notes, moderation-log entries, AutoMod log entries and their allow/deny log rows, the bot-list entry, messages of the person still held for AutoMod review, and the person's name in the channel's past stream reports (places and counts stay).
- Afterwards: the person is on the channel's erasure list, so the channel's future stream reports leave them out. The channel owner receives a confirmation e-mail with the case number.
- Stays: events (follows, subs, donations), data in other channels, and Lumio Stats — use Person at Lumio only for those.
Person at Lumio only
Erases one person on Lumio's own surfaces. No channel's data is touched.
- Person: platform (Twitch, YouTube, Kick) + platform user ID; optionally the Login on Twitch and Kick, which also catches leaderboard entries saved under the login name. YouTube has no login name.
- Erased: the person on the public Lumio Stats leaderboard (an existing objection becomes an erasure, and future Lumio Stats leave them out) and, on YouTube only, the person in Lumio's member cache of every channel.
- Stays: all channel data — chat, notes, logs and stream reports belong to the channels.
Single record
Erases one entry in one channel, for example a single chat message the channel asked to remove. The person's other data stays and no erasure list is written.
| Record type | What you enter | What is erased |
|---|---|---|
| Chat message | Record ID + Sent at (your local time to the second, matched within ±1 second) | The message, and its text in the moderation log (the log row stays) |
| Moderator note | Record ID | The note |
| Moderation log entry | Record ID | The log entry |
| AutoMod log entry | Record ID | The AutoMod entry, its allow/deny log rows and a message still held for review |
| Bot list entry | Record ID | The bot-list entry |
| Person in a stream report | Stream ID (session ID) + platform + platform user ID (+ optional login) | The person's name in that report's top chatters, links, commands and keywords; places and counts stay |
A stream report can only be cleaned once it is final; until then the dialog says The stream report is not final yet. When the person did not appear in the report, the result says so and nothing changed.
Errors
Errors appear inside the confirmation dialog, so you can correct the form and try again:
- This account does not exist — the account ID is wrong.
- No such entry in this channel — the record ID does not belong to this channel, or it was already erased.
- The stream report is not final yet — retry once the stream has ended and its report is final.
- The request was rejected: … — a field failed the API's validation; the API's message is shown.
- The erasure failed — a retry is safe.
Permissions
| Action | Permission |
|---|---|
| See the menu item and the page, use all three tools | admin:privacy-erase |
| Search accounts by name in the account field | accounts:read (without it, paste the account ID) |
Dashboard entry requires admin:access. admin:privacy-erase is assigned only to system_admin.
API
The page calls the Next.js proxy routes /api/privacy-erasure/{channel,lumio,record}, which forward to GraphQL.
| UI action | GraphQL | REST |
|---|---|---|
| Person in one channel | eraseChatSubjectData | POST /v1/admin/privacy/chat/erase |
| Person at Lumio only | eraseChatSubjectAtLumio | POST /v1/admin/privacy/lumio/erase |
| Single record | eraseChatRecord | POST /v1/admin/privacy/records/erase |
Tips & gotchas
- IDs come from the request. The admin panel cannot search people or records across accounts; take the platform user ID, record ID or stream ID from the channel's instruction.
- Check the channel in the dialog. Tools 1 and 3 act on exactly one account; the dialog names its channel before anything is erased.
- Not on this page: erasing a YouTube member (
DELETE /v1/admin/privacy/youtube/member/{id}), withdrawing a channel erasure (admin:privacy-erase-withdraw) and objections are API-only. - After a Lumio Stats objection or erasure that removes content from an indexed channel or directory page, request the same search-engine refresh and record it with the case. Stream and channel-history pages carry
noindex, follow, but a search engine may still hold an older snippet until it refreshes. - Every erasure is listed in the Audit Log.