Re-Verification

Nitice Snippet: -reverify

Use when:

• A specific incident, report, or moderation review raises age concerns

• Age eligibility needs to be reconfirmed due to context or irregularities

• Staff discretion determines verification is necessary

Notes:

• No explicit under-18 statement is required

• This is the most neutral and flexible reverify type

Notice Snippet: -reverify statement

Use when:

• A member states, implies, jokes about, or suggests being under 18

• Age-related comments contradict adult eligibility

• References to being a minor, in school, “not 18 yet,” etc.

Notes:

• Intent does not matter (jokes still qualify)

• This is a high-confidence trigger

• Immediate re-verification is required

Notice Snippet: -reverify partner

Use when:

• A member was previously verified through a partner or cross-server system

• The member later selects an Under 18 or minor-coded role

• Any conflict appears between partner verification and in-server indicators

Notes:

• Partner verification is overridden

• In-house verification is mandatory

• No partner verification is accepted in this scenario

Notice Snippet: -reverify inhouse

Use when:

• A member has already completed Masquerade’s in-house age verification

• The member later selects an Under 18 or equivalent role

Notes:

• This represents a serious trust breach or account misuse

• Still requires re-verification for documentation and recordkeeping

• Highest-severity re-verification scenario short of immediate ban

Notice Snippet: -reverify conflict

Use when:

• Age information differs across messages, profiles, or tickets

• A member updates details that introduce ambiguity

• No explicit under-18 statement exists, but consistency is broken

Notes:

• Useful when Type 1 feels too vague

• Helps document why re-verification was required

Age re-verification is a compliance action and must be handled consistently.

Once a concern is identified, staff should follow the steps below without deviation.

• Any staff member who notices a potential age concern should immediately escalate it to Admins.

• Do not confront or question the member directly in public channels.

• Do not attempt to resolve the concern independently.

Admins are responsible for all age re-verification actions.

Once an Admin determines that re-verification is required:

1. Open an Admin Outreach (Tier 2) ticket using the /new command

2. Add the member in question to the ticket

3. Unverify the member immediately (/staff verification)

4. Send the appropriate re-verification notice snippet

5. Tag the member and provide a clear 48-hour deadline

   • Use a formatted timestamp when possible

6. Disable ticket auto-close so the ticket remains open (/ticket autoclose action:Toggle)

7. Open a private notes thread using /ticket notes for admin discussion

At this stage, the outreach ticket serves notification and tracking only.

Admins must clearly state the following in the outreach ticket:

• Age re-verification is required

• Verification must be completed through the Age Verification system

• Do not submit verification materials in the outreach ticket

• The deadline to complete verification is 48 hours

• Failure to complete verification results in a permanent ban with no appeal

No debate, negotiation, or alternative arrangements are permitted.

• All re-verification must be completed in-house

• Partner or cross-verification options are not accepted once re-verification is requested

• Only valid government-issued ID submitted through the Age Verification system may be used

Once the 48-hour window expires, the outcome is final:

• Verification completed successfully → Member may be re-verified through normal procedures.

• No response, refusal, or failure to verify → Permanent ban (no appeal).

• Confirmation of underage status → Immediate permanent ban (no appeal).

Admins must document the final outcome in the outreach ticket before closing. The notes thread will not be transcribed. 

• Do not debate age eligibility with members.

• Do not accept explanations, screenshots, or documents outside the proper system.

• Do not delay action once re-verification is triggered.

• Do not promise appeals, exceptions, or second chances.

All communication should remain factual, calm, and policy-based.

Age re-verification protects Masquerade, protects staff, and protects members.

When in doubt — reverify and escalate.