SKY HOSTING / staff-conduct.md
Rev 2026.09.12 Active
Internal Governance Document

Staff Conduct & Activity Policy

Standards of professionalism, support activity, promotion, and account recovery for all SKY HOSTING staff.

Effective Aug 1, 2026 Last Updated Sep 12, 2026 Applies To All Staff Tiers Governing Body MK | PLAYZ Reading Time ~14 min Status Active
Document Information
Document Type

Internal Governance Policy

Department

Staff Management

Document Owner

MK | PLAYZ

Approval Status

Approved

Current Version

Version 2.4

Current Revision

Rev. 2026.09.12

Next Scheduled Review

February 2027

TOC

Table of Contents

§01

Purpose & Scope

This policy sets the standard of conduct, activity, and professionalism expected of every SKY HOSTING staff member — from Trial Staff through Admin — while on duty or acting in any staff capacity.

It supplements, and does not replace, the Staff Policy governing role grants and approvals. Where the two documents overlap, the stricter standard applies.

§02

Conduct in Staff-Only Areas

Staff-only channels are working spaces, not social ones. Meme culture and low-effort behavior are prohibited while on duty, regardless of tenure or role.

Excessive joking Low-effort messages Spam GIF chains Reaction spam "Brainrot" slang Unrelated memes Off-topic derailing

Exception

Casual conversation is permitted only in designated off-topic channels, and must never interfere with active support or moderation duties.

Staff represent SKY HOSTING at all times while in staff spaces. Tone, language, and behavior should reflect a company customers and applicants can trust.

§03

Support Activity Requirements

Activity is measured by meaningful contribution, not by presence or claim count.

5

Minimum daily activity

5 meaningful support tickets resolved or assisted per active day.

  • ✓A ticket counts only when staff provide a useful solution, troubleshooting step, or successful escalation.
  • ✕Claiming a ticket without helping does not count toward the minimum.
  • ✕Artificially inflating ticket counts is considered misconduct and is subject to the Staff Strike System (§14).
  • ✓Staff should prioritize quality over speed while still meeting the daily minimum whenever ticket volume allows.
  • ✓If fewer than five tickets are available during a shift, staff should assist with all available tickets instead — no penalty applies.
  • ✓Weekly requirements do not replace daily expectations — both standards apply.
§04

Weekly Staff Requirements

Staff members are expected to remain active every week. The figures below are minimum expectations, not targets — they exist to keep every position active and accountable, not to define success.

Role Minimum Staff Messages Minimum Support Tickets
Admin 20 per week 10 per week
Senior Moderator 15 per week 8 per week
Moderator 12 per week 6 per week
Senior Staff 10 per week 5 per week
Staff 7 per week 4 per week
Trial Staff 5 per week 3 per week
  • ✓Quality is always more important than quantity.
  • ✓Messages must be meaningful and related to staff work.
  • ✕Spam, one-word replies, and unnecessary chatting do not count.
  • ✓Ticket activity must involve actual assistance.
  • ✓If ticket volume is low, staff are only expected to help with available tickets.
  • ✕Repeated inactivity may result in a performance review.
§05

Professional Conduct Standards

  • ✓Be respectful, patient, and unbiased with every customer and applicant.
  • ✕Never argue with customers, regardless of how a conversation escalates.
  • ✕Never misuse staff permissions, immunities, or bypasses granted under the Staff Policy.
  • ✓Always follow internal procedures — improvisation around process is not permitted.
§06

Staff Moderation Guide

Moderation actions escalate by offense within each category. Some categories carry no escalation path and call for an immediate ban.

Advertising
✓First Offense

Warning

✕Second Offense

24 Hour Mute

✕Third Offense

Ban

Spam
✓First Offense

Warning

✕Second Offense

24 Hour Mute

✕Third Offense

Ban

Harassment / Toxic Behaviour
✓First Offense

Warning

✕Second Offense

10 Minute Mute

✕Third Offense

1 Hour Mute

✕Fourth Offense

24 Hour Mute

✕Fifth Offense

Ban

NSFW or Gore

Immediate Ban — no escalation path.

Doxxing

Immediate Ban — no escalation path.

Breaking Discord Terms of Service

Immediate Ban — no escalation path.

Use discretion

Severe or exceptional cases may require administrator approval before action is taken.

§07

Confidentiality

Staff must maintain confidentiality regarding customer information and internal staff discussions at all times. Information encountered in the course of duty is not to be shared outside its intended channel, discussed with unauthorized parties, or used for personal benefit.

Confidential information includes but is not limited to:

Customer information Billing information Internal discussions Investigation records Administrative decisions Staff reports Server infrastructure Panel credentials Internal documentation

Unauthorized disclosure

Unauthorized disclosure of confidential information may result in immediate removal from the staff team.

Ticket logs, investigation records, and recovery application data are retained for a period of 90 days from the date of closure or final action. Data may be retained longer if required for ongoing investigations or legal obligations.

§08

Definitions

Terms used throughout this policy carry the specific meanings defined below.

Staff Member

Any user holding an official SKY HOSTING staff role.

Support Ticket

Any customer or internal support request requiring staff assistance.

Meaningful Contribution

A response that genuinely assists, resolves, investigates, or escalates a support request.

Performance Review

A scheduled evaluation of staff activity, professionalism, contribution, and compliance.

Recovery Code

A unique verification code issued to confirm a staff member's identity during account recovery.

Strike

A formal disciplinary record issued after violating company policy.

§09

Conflict of Interest

Staff members must remain impartial while performing their duties.

The following are prohibited:

  • ✕Favoring friends or acquaintances.
  • ✕Giving unfair advantages.
  • ✕Leaking confidential information.
  • ✕Accepting gifts, payments, or favors in exchange for staff actions.
  • ✕Making decisions for personal benefit.

Violations are subject to disciplinary action under the Staff Strike System (§14), and severe violations may result in immediate removal.

§10

Staff Promotion Path

Progression through the staff track is earned, not assigned. Every member follows the same path from entry to the highest attainable staff position.

Entry Trial Staff Starting staff tier
Tier 2 Staff Confirmed staff member
Tier 3 Senior Staff Promoted on merit
Tier 4 Moderator Promoted on merit
Tier 5 Senior Moderator Promoted on merit
Ceiling Admin Highest staff tier
  • ✓All accepted applicants begin as Trial Staff.
  • ✓Promotions are earned through activity, professionalism, support quality, and policy compliance.
  • ✓Admin is the highest staff position.
  • ✕Owner and Co-Owner are ownership roles and cannot be earned through promotion.
§11

Staff Appointment Term

Not a permanent appointment

Staff positions are not permanent. Every staff member undergoes a periodic performance review, occurring every 3–6 months. Reviews are conducted by an Administrator or above.

Cycle Every 3–6 Months
Event Performance Review

Possible outcomes of each review:

✓Retained

Position continues unchanged.

✓Promoted

Advanced along the promotion path.

✕Demoted

Moved back a tier.

✕Removed

Staff role revoked entirely.

Reviews are based on activity, professionalism, contribution, and adherence to company policies. This ensures every position remains active and accountable, similar to performance reviews in any professional organization.

§12

Staff Role Ceiling

Admin is the highest role attainable through the staff track. No staff member progresses beyond it — Owner and Co-Owner are ownership positions held by the founding partners and are not part of the staff promotion path defined in this policy.

§13

Emergency & Account Recovery

If a staff member loses access to their Discord account, or their account is compromised, lost, or otherwise inaccessible, the following recovery procedure applies. This is the only recognized path back to a staff role — access is never restored informally.

01

A Recovery Code must already exist

A Recovery Code is issued to a staff member and sent by DM. It is personal and confidential — tied to the individual, not to any single account. Save it somewhere secure before it's ever needed.

02

Open the Recovery Verify Panel and click "Verify Now"

Recovery is self-service through the #recovery-apply channel's Staff Account Recovery panel. Clicking Verify Now opens a short application form asking for your Discord username, Discord ID, recovery code, and last staff position.

03

Submit within the time window

Once the form opens, you have a limited window to fill it out and submit. Missing the window applies a short cooldown before you can try again. (Exact timings are intentionally not published here.)

04

Review

A valid, unused code creates a pending recovery application posted for staff review. An authorized reviewer will Apply (grant the role) or Deny the application.

Failed Attempts
✕Repeated failures

Escalating lockout.

✕Continued failures

Removed from the server.

Exact thresholds are intentionally not published here, to prevent guessing attempts from being calibrated around them. Staff administering recovery can find the real numbers in the internal staff-only reference.

Before you start

Only proceed if you actually hold a valid recovery code. If you don't have one, open a support ticket instead — guessing burns your attempts. A staff member without a working code should contact an Administrator directly rather than repeatedly guessing.

Security note

Recovery Codes are personal and confidential. Never share your code with anyone — including other staff or anyone claiming to be staff — outside the official Verify Now flow. A code you believe has been shared or leaked should be reported immediately to MK | PLAYZ.

§14

Staff Strike System

Strikes accumulate across a staff member's tenure and progress toward removal. Each stage is documented against the staff member's record.

Strike One
Verbal Warning

Minor policy violation.

Strike Two
Written Warning

Official warning recorded internally.

Strike Three
Demotion

Demote the staff member one role lower.

Strike Four
Final Warning

Final opportunity before removal.

Strike Five
Removed

Permanent removal from the staff team.

Immediate removal

Serious violations including permission abuse, leaking confidential information, account compromise through negligence, malicious behaviour, or abuse of staff powers may result in immediate removal without following the normal strike progression.

Strike Expiration

Strikes remain active for ninety (90) days.

After ninety days of continued good conduct, management may remove one strike at its discretion.

Serious misconduct, abuse of permissions, security breaches, or confidentiality violations do not expire automatically.

Staff members may contest a strike within 48 hours of issuance, before it is finalized on their record. This is separate from the post-removal appeal process in §17.

For Trial Staff members who do not have a lower tier to demote to, Strike Three instead serves as a Final Warning, and Strike Four results in immediate removal.

§15

Staff Leave & Inactivity

Staff members who cannot remain active should notify management in advance whenever possible.

Examples include:

  • ✓School or examinations.
  • ✓Vacation.
  • ✓Medical reasons.
  • ✓Family emergencies.

Approved leave

Approved leave does not count as inactivity and will not negatively affect performance reviews.

§16

Staff Resignation

Staff members wishing to leave the team should:

  • ✓Notify an Administrator.
  • ✓Return any staff-only resources if applicable.
  • ✓Complete outstanding responsibilities whenever possible.
  • ✓Staff permissions will then be removed.

Former staff members may reapply in the future unless removed for misconduct.

§17

Appeals

Staff members who are demoted or removed may submit one formal appeal.

Appeals must
  • ✓Be truthful.
  • ✓Include supporting evidence where applicable.
  • ✓Be respectful.

Management will review each appeal individually. Management decisions after appeal are final.

§18

Acknowledgement

By accepting any SKY HOSTING staff position, you acknowledge that you have read, understood, and agree to comply with this Staff Conduct & Activity Policy and all future revisions.

Failure to comply with these policies may result in warnings, strikes, suspension, demotion, or permanent removal from the staff team.

§19

Revision History

This document is the single governing Staff Conduct & Activity Policy for SKY HOSTING. It is revised in place — changes are logged here rather than issued as separate documents.

Version Information
Current Version

2.4

Current Revision

2026.09.12

Previous Revision

2026.08.25

Next Planned Review

February 2027

Rev. 2026.09.12 — Policy Expansion & §13 Security Hardening
Published September 12, 2026
CURRENT
  • ✓Removed exact Recovery Verify Panel timing and failed-attempt thresholds from the public §13 text, to prevent the numbers being used to calibrate a guessing attempt. Real thresholds now live in an internal staff-only reference.
  • ✓Added §27 Conduct Outside Sky Hosting.
  • ✓Added §28 Staff-to-Staff Grievances.
  • ✓Added §29 Staff Account & Device Security.
  • ✓Added §30 Customer Data Handling.
  • ✓Added §31 Owner Unavailability.
  • ✓Added §32 Availability Expectations.
  • ✓Added §33 Anti-Bribery for Support & Refund Staff.
Rev. 2026.08.25 — Extended Recovery Submission Window
Published August 25, 2026
  • ✓Extended the Recovery Verify Panel submission window from 60 seconds to 5 minutes, and the timeout cooldown from 60 seconds to 2 minutes, to reduce false lockouts from rushed submissions.
Rev. 2026.08.25 — Account Recovery Process Update
Published August 25, 2026
  • ✓Rewrote §13 Emergency & Account Recovery to reflect the live Recovery Verify Panel process: a pre-issued Recovery Code, the Verify Now button in #recovery-apply, a 60-second submission window, a 60-second cooldown on timeout, and staff Apply/Deny review.
  • ✓Documented the 3-in-a-row / 9-lifetime failed attempt thresholds (24-hour lockout, then removal from the server).
  • ✓Replaced the previous ticket + direct message recovery procedure, which no longer reflects how recovery is processed.
Rev. 2026.08.24 — Policy Expansion & Staff Requirements Update
Published August 24, 2026
  • ✓Corrected §04 weekly staff requirements and promotion-path roles.
  • ✓Added §20 Substance & Illegal Activity References.
  • ✓Added §21 Infrastructure Integrity.
  • ✓Added §22 Ticket Response Time with a 6-hour initial response requirement.
  • ✓Added §23 Multi-Account / Alt Account Disclosure.
  • ✓Added §24 Refund & Dispute Handling.
  • ✓Added §25 Server Access Logging.
  • ✓Added §26 Off-boarding Checklist.
  • ✓Removed the rejected Ownership & Title Claims section.
Rev. 2026.08.06 — Staff Promotion Path Restructure
Published August 6, 2026
  • ✓Removed the Community entry tier from the Staff Promotion Path.
  • ✓Restructured the promotion path to: Trial Staff → Staff → Senior Staff → Moderator → Senior Moderator → Admin.
  • ✓Updated Admin as the highest staff position attainable through promotion.
Rev. 2026.08.02 — Weekly Requirements & Staff Strike System
Published August 2, 2026
  • ✓Added Weekly Staff Requirements.
  • ✓Added Staff Moderation Guide.
  • ✓Added Staff Strike System.
  • ✓Added inactivity expectations.
  • ✓Clarified ticket quality requirements.
  • ✓Clarified moderation procedures.
  • ✓Added progressive strike enforcement.
  • ✓Improved internal staff governance.
Rev. 2026.08.01 — Initial Release
Published August 1, 2026
  • ✓Published the first official Staff Conduct & Activity Policy.
  • ✓Established professional conduct standards for all staff tiers.
  • ✓Prohibited excessive joking, spam, GIF chains, reaction spam, unrelated memes, and other low-effort behavior in staff-only channels while on duty.
  • ✓Introduced minimum daily support activity expectations based on meaningful ticket contributions.
  • ✓Defined professional conduct and confidentiality requirements.
  • ✓Introduced the Staff Promotion Path — Community → Moderator → Administrator → Official Manager.
  • ✓Introduced the Staff Appointment Term, establishing periodic 3–6 month performance reviews.
  • ✓Established Official Manager as the highest position within the staff promotion path.
  • ✓Introduced the Staff Account Recovery procedure, including Recovery Codes for identity verification.
  • ✓Defined a progressive enforcement system — verbal reminders, written warnings, temporary suspensions, and removal for repeated or severe violations.
  • ✓Confirmed that acceptance of any staff role constitutes acceptance of this policy and future revisions.

Future revisions will continue to be documented within this section to maintain a complete change history.

§20

Substance & Illegal Activity References

Staff must not discuss, joke about, promote, or ask others about illegal substances, drug use, or other illegal activity in any staff or company space, regardless of intent or tone.

Violations are treated as harassment/toxic behavior under §06, with a minimum first-offense written warning. This is considered a formal written warning and is logged as Strike Two under the Staff Strike System (§14).

Zero tolerance

This prohibition applies to all staff spaces, including private channels and direct messages where the context is related to staff duties or company business.

§21

Infrastructure Integrity

SKY HOSTING will only use legitimately purchased or obtained infrastructure, including VPSs, servers, licenses, software, and credentials.

Staff must never source, recommend, or knowingly use stolen, carded, fraudulently obtained, or otherwise illegitimate infrastructure or credentials for company services.

Any staff member who becomes aware of such activity must report it to MK | PLAYZ immediately.

Immediate removal

Violation results in immediate removal with no escalation path.

This immediate removal action operates outside the standard Staff Strike System defined in §14.

§22

Ticket Response Time

Support tickets must receive an initial staff response within 6 hours.

If no staff member is available to respond, the ticket should be flagged in #staff-chat for coverage.

Coverage expectation

All staff are responsible for monitoring #staff-chat for flagged tickets and stepping in when available.

§23

Multi-Account / Alt Account Disclosure

Staff must disclose any alternate Discord accounts they use, especially if those accounts interact with the server or community, including:

  • ✓Customers
  • ✓Support tickets
  • ✓Purchases
  • ✓Reviews
  • ✓Vouches

If a staff member is found operating an undisclosed alt account within the community — including using it to pose as a customer, inflate reviews, or interact with their own tickets — all accounts and roles/privileges tied to that person are immediately suspended and terminated, and the staff member is permanently banned from the community.

No escalation path

This applies regardless of tenure or role and has no escalation path.

This immediate removal action operates outside the standard Staff Strike System defined in §14.

§24

Refund & Dispute Handling

Only Owner or Co-Owner may approve refunds or resolve payment disputes.

All other staff members must escalate refund or payment-dispute requests rather than promising or approving refunds themselves.

Escalation required

Unauthorized approval of refunds or disputes may result in disciplinary action.

§25

Server Access Logging

Any staff member granted access to the panel, VPS, bot, or other company infrastructure must have that access tied to their real staff account.

The following are prohibited:

  • ✕Shared logins
  • ✕Generic "admin" credentials used by multiple people
  • ✕Shared staff credentials
  • ✕Unattributed infrastructure access

Audit requirement

Every action taken on company infrastructure must be attributable to a specific staff member. Sharing logins or enabling unattributed access is treated as a security violation and results in immediate removal, with no escalation path.

This immediate removal action operates outside the standard Staff Strike System defined in §14.

§26

Off-boarding Checklist

Whenever a staff member leaves the company, whether through resignation or removal, a defined off-boarding process must be followed.

The checklist must be completed within 24 hours of departure and include:

  • ✓Revoke Discord roles
  • ✓Revoke panel access
  • ✓Revoke VPS/infrastructure access
  • ✓Revoke bot permissions
  • ✓Remove the staff member from private staff channels

Completion required

Off-boarding must be verified by an Administrator and logged internally.

§27

Conduct Outside Sky Hosting

Staff status is not transferable to other communities or platforms. Staff must not represent themselves as acting on behalf of SKY HOSTING in other Discord servers, on social media, or in DMs unless explicitly authorized to do so for a specific task.

Staff must not use their SKY HOSTING staff position to build personal reputation, audience, or leverage off the SKY HOSTING brand, and must not speak as an official representative of the company outside approved channels.

Why this matters

SKY HOSTING has previously dealt with impersonation and scam-server incidents. Unauthorized off-platform claims of staff status create the same risk directed at our own brand.

§28

Staff-to-Staff Grievances

The Appeals process (§17) covers a staff member appealing their own demotion or removal. This section covers a different case: a staff member with a concern about another staff member's conduct toward them.

  • ✓Raise the concern privately with an Administrator rather than in any staff-wide channel.
  • ✓Grievances are handled confidentially and are not treated as public moderation matters.
  • ✓Retaliation against a staff member for raising a good-faith grievance is itself a policy violation.
§29

Staff Account & Device Security

Staff hold access to panel tools, ticket data, and in some cases infrastructure credentials. Basic account hygiene is mandatory, not optional.

  • ✓Two-factor authentication is required on the Discord account used for staff duties.
  • ✕Do not share a device that is logged into staff tools with anyone else.
  • ✓Report a lost, stolen, or compromised device or account to an Administrator immediately.

Delay has a cost

A delayed report on a compromised staff account gives an attacker more time with real access. Report first, explain later.

§30

Customer Data Handling

Confidentiality (§07) covers what information is confidential. This section covers how customer data is specifically handled in practice.

  • ✕Customer payment details are never copied, screenshotted, or stored outside official systems.
  • ✓On account deletion or refund, customer data is handled per SKY HOSTING's published Privacy Policy, not staff discretion.
  • ✕Customer data is never used for any purpose beyond the support or billing task it was provided for.
§31

Owner Unavailability

SKY HOSTING's systems include an automated safeguard for extended Owner inactivity. Staff should understand what it does without needing the exact technical thresholds.

If the Owner is unreachable for an extended period, system safeguards escalate automatically — starting with quiet check-in reminders and, if inactivity continues long enough, tightening server security and treating unverified "I'm the Owner" claims in tickets with added scrutiny.

Staff do not need to take any special action when this happens — the safeguard resolves itself once the Owner checks in. Staff should simply continue following normal escalation and verification procedures already in this policy.

§32

Availability Expectations

Weekly and daily activity minimums (§03, §04) are not the same as an expectation of constant availability.

Staff are not expected to respond outside reasonable hours. Approved leave (§15) and normal rest are protected and will never count against a staff member in a performance review.

§33

Anti-Bribery for Support & Refund Staff

Conflict of Interest (§09) already prohibits accepting gifts or favors for staff actions. This section makes the support/refund context explicit given the financial risk involved.

Staff must never accept payment, discounts, gifts, or favors from a customer in exchange for any support action — including bypassing normal queue order, exaggerating an issue's severity to justify a refund, or influencing a decision reserved for Owner/Co-Owner under §24.

Zero tolerance

This applies regardless of the amount involved and is treated the same as any other Conflict of Interest violation under §14.