Having your records erased (/cmd id)

You can also use this site’s form

Use Appeal a room restriction to choose “I think the room restriction was a mistake”, “Please erase my records” or “I want to report something about a host”. Appeals saying the room restriction was a mistake are read by the author and the Room Access Team members the author chooses; requests to erase records and reports about a host are read only by the author. Only the author decides whether to reply and whether to lift a room restriction. Include the date and time, room code, evidence number AEG-…, code from /cmd id and what happened as far as you know. You can send it without the numbers or codes. Use your in-game name, not your real name. Replies appear on the receipt page. Requests on this site are deleted 30 days after they are marked resolved. This is separate from how long game records stay on a host’s PC. You can still use Discord and email. Send report zips and evidence zips by email, rather than attaching them to this site’s form.

Steps

1. In a PocketRoles room, type /cmd id in the chat. You get “your code” (16 letters, e.g. BDZN XHNJ JSXD GZDG). In a registered room only you see it. In an unregistered room everyone sees it as “name: code”.
2. Send the code to the author: a ticket in the “🛡️｜異議申し立て” (appeals) channel of the “PocketRoles 役職部屋” Discord, or pocketroles.report+[email protected] (subject “erase my records”).
3. The author puts the code on the “erase list” of the signed definitions file. A host’s PC erases your records up to that day by itself the next time it gets the definitions file (when the game starts, and once a day while it runs). No host has to do anything.

Records are on each host’s PC; players have no way to view them (and the author can’t look into other hosts’ PCs either).

What goes

Your name, history (room codes where you were stopped, and so on) and evidence records. For an evidence record younger than 30 days, the name, room code, log lines and detection text go at once; the rest (hashes, detection numbers and so on) stays until its 30 days are up.

What stays

• A ban still in force: the minimum it needs to keep working (hash, level, end date) and that ban’s evidence records (for appeals).
• The minimum of the offence count (the PUID’s hash, count and dates): for a year after the last ban ends.
• Your code on the unban list: at least 180 days, and in the GitHub history.
• The lists a host writes by hand (Banlist.txt, VIP.txt, Moderator.txt, Admin.txt): the host decided them, so this request doesn’t change them.
• Your name inside other players’ evidence records (it stays as part of their record).
• Logs, report zips and copies of sent reports: they go after 30 days.
• The copies the author and the admins hold: nothing deletes them automatically yet. The author deletes them by hand and asks the admins to do the same. Names in the ban console’s operation record (audit.log) can’t be removed for now and stay.
• Records on a PC that runs a PocketRoles older than v0.5.5, or never starts PocketRoles again.

Good to know

• The code is not a password. Anyone who sees it can ask for the erase in your place (only what “What goes” lists goes, and a ban still in force keeps working). In an unregistered room everyone sees the code, so type it in a registered room if you can.
• The erase list is public on GitHub. It holds only codes and dates — no names, friend codes or PUIDs.
• The last letter of the code is there to catch typos.
• If you no longer join PocketRoles rooms, you can’t get a code. Then wait for the automatic deletion (30 days for logs and the like, 90 days for evidence records), or, if you only need the author’s copies gone, contact the author with your friend code.

Even if you do nothing, records on the PCs of hosts using PocketRoles v0.5.5 or later are deleted 30 days after they’re no longer needed (90 days for evidence records) (What stays on the host’s PC).