Players & cooldown status
This list only shows anonymous account codes. No names, emails, phone numbers or conversations appear on this screen, not even at the highest level of access. Reading identifying data needs a business reason that is written to the access log and a second person to confirm it.
Cooldown is a safety control, not an operational setting
The seven-day break models a self-exclusion period, and it is one of the three things this product exists to protect. A valid cooldown cannot be cancelled or shortened, including by a system administrator, so this page exposes no early-release action or request.
A suspected assignment error goes through the separate incident workflow. That workflow corrects the faulty source event and records the evidence; it never shortens a valid cooldown. Extending a cooldown or suspending an account still takes two people, a written reason and notice to the account holder.
| Account code | Status | Cooldown until | Run | Registered | Available actions |
|---|---|---|---|---|---|
| U-10188 | Cooldown | 29/07/2026 · 2 days left | #2 (ended) | 14/04/2026 | Cannot be shortened |
| U-10241 | Cooldown | 31/07/2026 · 4 days left | #3 (ended) | 02/05/2026 | Cannot be shortened |
| U-10307 | Cooldown | 02/08/2026 · 6 days left | #1 (ended) | 21/05/2026 | Cannot be shortened |
| U-10052 | Active | — | #4 (day 9) | 03/03/2026 | |
| U-10412 | Active | — | #1 (day 3) | 18/06/2026 | |
| U-10466 | Suspended | — | — | 07/07/2026 | The account holder was told the reason and how to appeal (required for every suspension) |
Cooldown countdowns are calculated from a server timestamp, not from the device clock.
Recent two-person account-control decisions
The proposer cannot approve the same request. That constraint sits in the data layer, not in the button.
Data export and deletion requests
Open the queue| Account | Type | Due | Action |
|---|---|---|---|
| U-10188 | Export my data | 31/07 | Work this request |
| U-10412 | Delete account | 04/08 | Work this request |
| U-10466 | Delete account | 09/08 | Work this request |
Deleting an account does not delete the safety control audit records or the de-identified token ledger. Those are audit evidence and hold no identifying data. A running cooldown is not ended by a deletion either: the countdown is held against a de-identified marker that outlives the account.
Not available here: any way to grant tokens · any way to change the odds for one account · any way to restore a lost Family asset · any AI companion transcript (the outbound companion stores none in tibbi). If one of those four ever turns up in a build, treat it as a release blocker, not a new feature.