Service Guidelines

How requests should be handled

These guidelines keep project requests clear, safer to deliver, and easier for staff to review.

Every serious request should explain the platform, desired outcome, features, references, deadlines, and access needed before work begins.

Support, reports, appeals, bug reports, and project updates should stay in the correct channels or tickets so work stays traceable.

Never send tokens, passwords, billing access, or private credentials unless leadership confirms the exact need and destination.

Revisions should match the original scope. New systems, major redesigns, or rushed timeline changes may require a new agreement.

Developers and testers should verify important changes before public rollout, especially bots, dashboards, permissions, and moderation tools.

Saphix Development will not build scams, spam systems, token grabbers, raid tools, evasion tools, malware, or platform-abuse systems.