1. Respect Everyone
Treat members, clients, developers, partners, and staff with basic respect at all times.
Harassment, hate speech, bullying, personal attacks, slurs, threats, targeted drama, and doxxing are not allowed.
Debates are allowed only when they stay civil and do not disturb support or development work.
Do not mock people for skill level, age, accent, language, device, region, budget, or project experience.
2. Keep the Server Clean
Use the correct channels for support, development discussion, project posts, media, bug reports, and general chat.
Do not spam, flood, mass ping, chain message, advertise without permission, or intentionally derail conversations.
Avoid excessive caps, repeated emojis, low-effort messages, and content that makes channels hard to use.
Staff may move, delete, or archive messages that are posted in the wrong place or make channels harder to use.
3. Support Rules
When asking for help, explain the issue clearly and include screenshots, errors, steps already tried, and relevant project details.
Do not ping developers or management repeatedly. Staff will respond when available.
Do not open fake tickets, troll support, abuse staff time, or demand instant work.
One ticket should cover one issue or project unless staff asks you to combine related topics.
4. Project & Client Conduct
Be clear about requirements, deadlines, budget, platform access, and permissions before work begins.
Do not leak private project files, client data, internal discussions, paid assets, source code, or unreleased plans.
Chargebacks, scams, impersonation, fake proof, and dishonest client behavior can result in blacklisting.
Scope changes, rushed deadlines, missing assets, or late requirements may delay work or require a new agreement.
5. Developer, Tester & Staff Safety
Developers must not request unnecessary admin permissions, tokens, passwords, billing access, or private credentials.
Testers must only use test access for assigned quality checks and must report bugs without leaking private builds, credentials, or unreleased content.
Staff must not abuse moderation tools, leak logs, alter access without approval, raid servers, or make unsafe permission changes.
All staff, developers, and testers must follow the principle of least privilege: only use the access needed for the assigned task.
Any security concern, suspicious link, leaked token, or unsafe permission setup should be reported to management immediately.
6. Content Restrictions
NSFW content, illegal content, malware, token grabbers, phishing links, scams, self-harm encouragement, extremist content, and malicious scripts are forbidden.
Do not share pirated paid assets, cracked software, stolen designs, leaked source code, or content you do not have rights to use.
Files, links, and attachments may be removed if they create a safety, legal, or platform risk.
Do not post content designed to bypass Discord, Roblox, GitHub, hosting, payment, or API platform rules.
7. Advertising & Partnerships
Advertising is only allowed in approved channels or with staff permission.
Partnership requests must be honest, relevant, and safe for the Saphix community.
Invite farming, DM advertising, fake giveaways, and misleading promotions are not allowed.
Partner communities may be removed if they become unsafe, inactive, misleading, or harmful to Saphix members.
8. Account and Identity Rules
Do not impersonate Saphix staff, developers, partners, clients, bots, or other community members.
Use of alternate accounts to bypass punishments, manipulate giveaways, evade blocks, or hide misconduct is not allowed.
Names, avatars, statuses, and profiles may be moderated if they are hateful, explicit, misleading, scam-related, or designed to cause confusion.
9. Privacy and Confidentiality
Do not share private messages, tickets, invoices, project details, logs, screenshots, or staff discussions without permission.
Do not pressure members, clients, or staff to reveal personal information, credentials, private accounts, addresses, payment details, or unrelated identity information.
Support evidence should be shared only with authorized staff and only when it is needed to resolve the issue.
10. Payments and Trading
All paid work, commissions, middleman activity, sponsorships, and trades must be handled honestly and with clear terms.
Fake receipts, refund abuse, chargeback threats, stolen payment methods, and misleading proof of ownership are prohibited.
Saphix staff may refuse to mediate deals that were made outside approved channels or without enough evidence.
11. Platform Compliance
Members must follow Discord Terms, Roblox Terms, GitHub rules, hosting provider rules, payment processor rules, and any other platform policies connected to a project.
Do not ask Saphix developers or staff to build systems for raids, spam, account theft, token collection, exploit distribution, bypassing bans, or platform abuse.
Projects that create legal, safety, or platform risk may be refused or removed without notice.
12. Enforcement
Staff may warn, mute, timeout, kick, ban, blacklist, remove content, revoke access, or deny service depending on severity.
Severe abuse, scams, raids, leaks, threats, phishing, or security issues may lead to immediate permanent removal.
Appeals may be allowed, but staff decisions are final when community safety or project security is involved.
Rules may be enforced based on intent, impact, past behavior, and risk even if an exact situation is not listed here.
13. Staff Chain of Command
CEO and COO decisions are final for executive matters, staff access, policy interpretation, and high-risk situations.
Development issues should move through Tester, Trial Developer, Junior Developer, Developer, Senior Developer, and Head Developer when escalation is needed.
Discord moderation issues should move through Trial Discord Moderator, Discord Moderator, Senior Discord Moderator, and Head Discord Moderator when escalation is needed.
Do not contradict another staff action publicly. If something seems wrong, move it to staff channels or executive review.