# An overview of privacy on the Unblock Request Ticket System/Case analysis and process workflow

​Case analysis
Case 1: Anonymous user blocked by IP Address
Condition: An anonymous Wikipedia editor edits with the IP address is blocked for vandalism. They create a ticket on the Unblock Ticket Request System. When prompted to identify an account, they do not because they do not have one; they are editing anonymously. User is informed that clicking submit will agree to the privacy policy.
Action: UTRS system records the user’s IP Address and useragent automatically. The user must volunteer an email address to facilitate communication. The appeal is set to "NEW" status.
Visibility: The user’s IP Address is visible to all UTRS users. The email address is not visibility in its entirety, however the domain (after the @ symbol) is visible. Useragent data is only visible to checkusers.
Workflow: UTRS users will first reserve the appeal to their account. This will prevent duplicate effort and duplicate responses to the user. Tool users will not be able to email the blockee unless they hold a reservation on an appeal. UTRS user will then review the appeal request. The tool user will review the IP’s contributions on Wikipedia and any unblock template on the IP talk page.
If the tool user requires more information from the IP Address, they will use a drop-down menu to select from a list of response templates, or a blank template, to send the user an email. Email is transmitted by the UTRS system using a noreply-unblock@toolserver.org email address. The IP’s email address will never be available to the tool user. The appeal is set to “AWAITING_USER” status. The IP will receive the email at their identified email address. The email will contain a link to a reply form where the user can enter a response. Once a response is entered, the appeal is set to "AWAITING_REVIEWER" status.
The tool user can review the response in the comments window as a highlighted comment. If the user feels there may be a case of abuse or sockpuppetry, they may forward the appeal to a checkuser by clicking the checkuser button. This will drop the user’s reservation on the appeal and set the appeal’s status to "AWAITING_CHECKUSER".
If there are no concerns and the tool user decides to unblock, they can use the IP Address to unblock the anonymous account on Wikipedia. They can then send an unblocked template email response to the user and the appeal will be set to close. If the tool user decides not to unblock, they may close the appeal and send an email, or not send an email, explaining the rationale to the user. Alternatively, if the
Case 2: Named Account blocked by IP Address
Condition: A named account is blocked by IP address either because they are in a rangeblock or because of an autoblock. They identify an account when creating an appeal. User is informed that clicking submit will agree to the privacy policy.
Action: UTRS system records the user’s IP Address and useragent automatically. The user must volunteer an email address to facilitate communication. The appeal is set to "NEW" status.
Visibility: The users IP address and useragent data are only available to checkusers and developers. Email address is visible by domain only.
Workflow: The tool user will review the account similarly to Case 1. The user will review the named account’s contributions instead of IP Address contributions because they do not have access to view the IP Address. Often times, Wikipedia users are unaware that there can be blocks on IP Addresses or accounts. The tool user will check for a block on the account. If one is not found, they will check for an autoblock.
If an autoblock is found, they will review the merits of the case and close the appeal. If an autoblock is not found, the tool user will click the checkuser button to forward the appeal to a checkuser. A checkuser will view the IP Address on the UTRS tool, and then check for cases of sockpuppetry, rangeblocks, or IP blocks.
If one is found, the checkuser will review the appeal and determine an outcome. They will close the appeal. However, if it is determine that the account or IP is abusing the UTRS system, they will click the tool admin button to forward the appeal to a tool admin to ban the account, email, or IP from the UTRS system.
Case 3: Named account is blocked
Condition: A named account is blocked. They identify an account when creating an appeal. User is informed that clicking submit will agree to the privacy policy.
Action: UTRS system records the user’s IP Address and useragent automatically. The user must volunteer an email address to facilitate communication. The appeal is set to "NEW" status.
Visibility: The users IP address and useragent data are only available to checkusers and developers. Email address is visible by domain only.
Case 4: IP Address is blocked as a sock puppet
Condition: A user with a named account does not reveal their account name instead opting to be identified by IP Address. They create a ticket on the Unblock Ticket Request System. When prompted to identify an account, they do not despite actually owning an account. User is informed that clicking submit will agree to the privacy policy.
Action: UTRS system records the user’s IP Address and useragent automatically. The user must volunteer an email address to facilitate communication. The appeal is set to "NEW" status.
Visibility: The user’s IP Address is visible to all UTRS users. The email address is not visibility in its entirety, however the domain (after the @ symbol) is visible. Useragent data is only visible to checkusers.
Workflow: Similar to case 2. If the tool user feels there may be more information, they can request the information from the user. The user will be given the opportunity to reveal their account name. If the tool user feels the appeal is deceptive or there are signs of sockpuppetry, they can forward the appeal to a checkuser.