Community Guidelines

Last updated: 3 days ago

Community Guidelines

Last updated: June 2026

Applies to: Mobieus.io Support, forums, comments, direct messages, member profiles, uploads, reactions, polls, events, courses, knowledge articles, support areas, and any other interactive community features.

These Community Guidelines explain how members, moderators, administrators, contributors, and visitors are expected to behave on Mobieus.io Support. They work together with our Terms of Service, Privacy Policy, and any forum-specific rules.

By using Mobieus.io Support, you agree to follow these Guidelines. Violations may result in content removal, warnings, temporary restrictions, suspension, or permanent bans.

The Short Version

Be useful. Be accurate. Be civil.

  • Treat people with respect.
  • Disagree with ideas, not people.
  • Stay on topic.
  • Do not spam, harass, threaten, impersonate, or deceive.
  • Do not post illegal, exploitative, or harmful content.
  • Respect privacy, confidentiality, and intellectual property.
  • Use responsible disclosure for security issues.
  • Follow moderator instructions.
  • Report problems instead of escalating them.

1. Community Purpose

Mobieus.io Support exists to help members:

  • Ask and answer questions.
  • Report bugs.
  • Request features.
  • Share knowledge.
  • Improve documentation.
  • Discuss platform usage.
  • Support safe, productive, and constructive community participation.

This is a support and knowledge-sharing community, not a place for abuse, harassment, spam, illegal conduct, or bad-faith disruption.

2. Scope

These Guidelines apply to all public and private areas of Mobieus.io Support, including:

  • Forum threads and replies.
  • Bug reports.
  • Feature requests.
  • Help requests.
  • Knowledge articles.
  • Editorial suggestions.
  • Member profiles.
  • Usernames, avatars, bios, and signatures.
  • Direct messages and modmail.
  • Uploaded files, images, code, logs, screenshots, and attachments.
  • Events, polls, comments, reactions, and leaderboard activity.
  • Moderator and administrator interactions.

Private messages are not exempt from these Guidelines.

3. Account Responsibility

You are responsible for activity on your account.

Do not:

  • Share your account with others.
  • Use another person's account.
  • Create duplicate accounts to evade restrictions.
  • Use throwaway accounts to harass, spam, manipulate voting, or avoid moderation.
  • Misrepresent your identity, role, employer, affiliation, or authority.
  • Attempt to access restricted areas without permission.

If you believe your account has been compromised, contact support immediately.

4. Respectful Conduct

Members must communicate respectfully.

Allowed:

  • Firm disagreement.
  • Technical criticism.
  • Good-faith debate.
  • Asking for clarification.
  • Correcting inaccurate information.
  • Challenging an idea, proposal, or implementation.

Not allowed:

  • Personal attacks.
  • Insults, slurs, or demeaning language.
  • Harassment or intimidation.
  • Threats.
  • Mocking someone's identity, ability, background, language, or experience level.
  • Sustained hostility across threads or messages.
  • Encouraging others to attack or isolate a member.

Critique the work, claim, code, decision, or idea. Do not attack the person.

5. Harassment and Abuse

Harassment is prohibited.

This includes:

  • Repeated unwanted contact.
  • Following a user across threads to provoke them.
  • Sending hostile direct messages.
  • Contacting someone after they have asked you to stop.
  • Coordinated pile-ons.
  • Targeted ridicule.
  • Sexual harassment.
  • Threatening harm.
  • Encouraging self-harm.
  • Publishing or threatening to publish private information.
  • Using alternate accounts to continue unwanted contact.

A single severe incident may be treated as harassment.

6. Privacy and Confidentiality

Respect personal, private, confidential, and sensitive information.

Do not post or share:

  • Home addresses.
  • Personal phone numbers.
  • Private email addresses.
  • Government IDs.
  • Financial information.
  • Authentication tokens.
  • API keys.
  • Passwords.
  • Session cookies.
  • Private messages, DMs, emails, or screenshots without consent.
  • Internal business information without authorization.
  • Customer data.
  • Employee data.
  • Logs containing sensitive information.
  • Personal photos or identifying details without permission.

When sharing logs, screenshots, configuration files, or bug reports, redact sensitive information first.

Examples of information to redact:

  • Access tokens.
  • IP addresses, unless technically necessary.
  • Email addresses.
  • Customer names.
  • Hostnames.
  • Secret keys.
  • License keys.
  • Account IDs.
  • Billing information.
  • Internal URLs.
  • Security findings not ready for disclosure.

7. Intellectual Property

Respect the work of others.

Do not:

  • Upload copyrighted material you do not have permission to share.
  • Copy articles, guides, code, images, or documentation without attribution.
  • Present someone else's work as your own.
  • Remove license notices from code or documentation.
  • Share proprietary source code unless authorized.
  • Upload pirated software, cracks, keygens, or unauthorized copies.

You may share brief excerpts, links, commentary, and properly attributed references where permitted by law and license terms.

If you believe your work has been posted without permission, use the reporting process or contact the moderation team.

8. Accuracy and Good-Faith Participation

Members should make a reasonable effort to be accurate, clear, and helpful.

Do:

  • Explain what you tried.
  • Include relevant context.
  • Mark speculation as speculation.
  • Correct your post if you discover an error.
  • Link to authoritative sources when possible.
  • Use descriptive titles.
  • Keep bug reports reproducible.
  • Separate facts from opinions.

Do not:

  • Knowingly post false information.
  • Fabricate sources.
  • Mislead users about capabilities, risks, pricing, security, or availability.
  • Present guesses as confirmed facts.
  • Abuse AI-generated content to flood the site.
  • Post low-effort replies that do not help the discussion.

9. Staying on Topic

Each area of Mobieus.io Support has a purpose.

Post in the correct area:

  • Use Help for how-to questions.
  • Use Bug Reports for reproducible defects.
  • Use Feature Requests for proposed improvements.
  • Use General Discussions for broader community discussion.
  • Use security-related areas only for appropriate security topics.

Do not:

  • Hijack threads.
  • Repeatedly repost the same issue.
  • Cross-post identical content across multiple forums.
  • Convert support threads into unrelated debates.
  • Bump old threads without adding useful information.
  • Use misleading titles.

If your reply introduces a new topic, start a new thread.

10. Bug Reports

Bug reports should help others reproduce, diagnose, and resolve the issue.

Useful bug reports include:

  • Clear summary.
  • Steps to reproduce.
  • Expected behavior.
  • Actual behavior.
  • Browser, device, OS, or environment details.
  • Screenshots or logs, when safe to share.
  • Whether the issue is intermittent or consistent.
  • Any workaround discovered.

Do not include secrets, private data, or customer information in bug reports.

11. Feature Requests

Feature requests should be constructive and specific.

Good feature requests explain:

  • The problem being solved.
  • The affected user or workflow.
  • Why existing functionality is insufficient.
  • A proposed solution.
  • Alternatives considered.
  • Potential risks or tradeoffs.

Do not attack the team or other members because a feature does not exist or is not prioritized.

12. Security Issues and Responsible Disclosure

Security discussions must be handled responsibly.

Allowed:

  • General security questions.
  • Defensive configuration guidance.
  • Secure coding discussions.
  • Responsible vulnerability reports.
  • Sanitized logs.
  • High-level descriptions of risks.
  • Reproduction steps shared privately with authorized staff when appropriate.

Not allowed:

  • Exploit code targeting real systems without authorization.
  • Instructions for compromising accounts, bypassing access controls, or stealing data.
  • Public disclosure of active vulnerabilities before the team has had a reasonable chance to investigate.
  • Posting secrets, tokens, credentials, private keys, session cookies, or live exploit details.
  • Social engineering attempts.
  • Credential phishing.
  • Malware, ransomware, spyware, botnet, or persistence instructions.
  • Requests to attack, scan, disrupt, or evade monitoring on systems you do not own or administer.

If you find a vulnerability, report it through the appropriate security or escalation channel. Include enough detail for verification, but avoid exposing other users or production systems.

13. Logs, Screenshots, and Attachments

Uploads must be safe, relevant, and lawful.

Before uploading:

  • Remove passwords, tokens, and secrets.
  • Blur or crop private information.
  • Confirm you have permission to share the file.
  • Avoid uploading customer, employee, or confidential business data.
  • Use the smallest relevant excerpt.
  • Explain why the attachment is needed.

Do not upload:

  • Malware.
  • Exploit kits.
  • Pirated software.
  • Private keys.
  • Credential dumps.
  • Sensitive personal information.
  • Nonconsensual images.
  • Copyrighted works you cannot legally share.
  • Files intended to harass, deceive, or disrupt others.

Moderators may remove attachments that create privacy, legal, security, or safety risks.

14. Spam, Self-Promotion, and Commercial Activity

Do not use Mobieus.io Support primarily for promotion.

Not allowed:

  • Repetitive promotional posts.
  • Unsolicited advertising.
  • Referral farming.
  • Affiliate-link spam.
  • Fake testimonials.
  • Lead generation disguised as support.
  • Posting solely to drive traffic elsewhere.
  • Automated promotional messages.
  • Mass direct messages.
  • SEO manipulation.
  • Giveaway scams.
  • Cryptocurrency, investment, or financial scams.

Limited self-promotion may be allowed when:

  • It is directly relevant.
  • It answers the question.
  • Your relationship is disclosed.
  • The post provides value beyond the link.
  • The forum rules allow it.

Affiliate links must be clearly disclosed. Pure affiliate posts may be removed.

15. Impersonation and Misrepresentation

Do not impersonate:

  • Other members.
  • Moderators.
  • Administrators.
  • Mobieus.io staff.
  • Public figures.
  • Companies.
  • Support representatives.
  • Vendors.
  • Security researchers.
  • Law enforcement or government entities.

Do not use names, avatars, signatures, or bios that create confusion about who you are or what authority you have.

Parody or fan accounts must be clearly labeled and must not mislead users.

16. Prohibited Content

The following content is prohibited:

  • Threats of violence.
  • Incitement to violence.
  • Terrorist or extremist recruitment or praise.
  • Child sexual abuse material or sexualization of minors.
  • Nonconsensual intimate imagery.
  • Sexual exploitation.
  • Human trafficking.
  • Doxxing.
  • Malware or credential theft.
  • Phishing.
  • Fraud.
  • Scams.
  • Illegal marketplace activity.
  • Instructions for evading law enforcement.
  • Content that facilitates real-world harm.
  • Gratuitous violence.
  • Pornographic content.
  • Hate-based harassment.
  • Encouragement of self-harm.

Content involving minors, exploitation, credible threats, or serious illegal activity may be reported to appropriate authorities.

17. Adult, Graphic, and Sensitive Content

Mobieus.io Support is a general-audience community.

Do not post:

  • Pornography.
  • Sexually explicit images.
  • Gratuitous gore.
  • Shock content.
  • Graphic violence intended to disturb others.
  • Exploitative or nonconsensual content.

Limited discussion of mature, sensitive, or difficult topics may be allowed when:

  • It is relevant to the forum.
  • It is not graphic or exploitative.
  • It is clearly labeled.
  • It does not target, harass, or endanger others.

Moderators may remove sensitive content even if it was not posted maliciously.

18. Hate, Discrimination, and Dehumanization

Do not attack people based on protected or personal characteristics.

This includes attacks related to:

  • Race.
  • Ethnicity.
  • National origin.
  • Religion.
  • Sex.
  • Gender identity.
  • Sexual orientation.
  • Disability.
  • Age.
  • Veteran status.
  • Caste.
  • Immigration status.
  • Serious medical condition.

Not allowed:

  • Slurs.
  • Dehumanizing language.
  • Calls for exclusion, segregation, or violence.
  • Mocking identity or disability.
  • Using stereotypes to harass or demean.

Good-faith discussion of policy, history, or social issues must remain respectful and relevant.

19. Automation, Bots, Scraping, and Platform Abuse

Do not abuse the platform or interfere with normal operation.

Not allowed:

  • Unauthorized bots.
  • Spam automation.
  • Credential stuffing.
  • Scraping that violates site rules or user privacy.
  • Load testing without permission.
  • Attempting to bypass rate limits.
  • Exploiting bugs for advantage.
  • Manipulating votes, reactions, views, achievements, badges, leaderboards, or referrals.
  • Creating accounts in bulk.
  • Circumventing bans or suspensions.
  • Testing security controls outside authorized channels.

Report platform abuse through the appropriate support or moderation channel.

20. AI-Generated Content

AI-assisted content is allowed when it is useful, accurate, and properly reviewed.

When using AI tools:

  • Review content before posting.
  • Verify technical claims.
  • Do not post fabricated citations.
  • Do not flood the site with low-value generated posts.
  • Do not represent AI-generated work as personal expertise if that would mislead readers.
  • Do not use AI to harass, impersonate, deceive, or manipulate others.
  • Do not upload private or confidential community content into external AI tools unless you have permission.

Moderators may remove AI-generated content that is inaccurate, repetitive, unsafe, or disruptive.

21. Moderator Authority

Moderators help keep the community safe, organized, and useful.

Moderators may:

  • Edit titles for clarity.
  • Move threads.
  • Merge duplicate discussions.
  • Remove posts or attachments.
  • Lock threads.
  • Pin important content.
  • Issue reminders or warnings.
  • Mute users.
  • Suspend users.
  • Ban users.
  • Restrict access to specific forums.
  • Escalate severe issues to administrators.

Moderator decisions should be followed even if you disagree. Public arguments about moderation may be removed. Use modmail or the appeal process instead.

22. Administrator Authority

Administrators may take broader action to protect the site, users, data, infrastructure, and community.

Administrators may:

  • Remove content.
  • Restrict accounts.
  • Disable features.
  • Lock forums.
  • Preserve evidence of abuse.
  • Investigate platform misuse.
  • Respond to legal, privacy, or security concerns.
  • Update rules and policies.
  • Take emergency action without prior notice.

Administrators may also act on behavior that technically avoids a written rule but clearly violates the purpose of these Guidelines.

23. Reporting Problems

Report content or behavior when you see:

  • Harassment.
  • Spam.
  • Threats.
  • Doxxing.
  • Security issues.
  • Privacy exposure.
  • Illegal content.
  • Impersonation.
  • Copyright concerns.
  • Repeated off-topic disruption.
  • Abuse of platform features.

Do not retaliate, dogpile, or continue an argument. Report the issue and move on.

Reports are reviewed by moderators or administrators. Submitting a report does not guarantee a specific outcome.

24. False or Abusive Reports

The report system exists to protect the community.

Do not:

  • File knowingly false reports.
  • Use reports to harass another member.
  • Mass-report content because you disagree with it.
  • Encourage others to weaponize reporting.
  • Repeatedly report the same issue after a decision has been made.

Abuse of the reporting process may result in moderation action.

25. Enforcement

Enforcement depends on severity, context, history, and risk.

Possible actions include:

  1. No action — The content does not violate the Guidelines.
  2. Informal reminder — A moderator asks the member to adjust behavior.
  3. Content edit — A moderator edits a title, removes sensitive data, or fixes formatting.
  4. Content removal — A post, reply, upload, profile field, or message is removed.
  5. Thread action — A thread may be moved, merged, closed, hidden, or locked.
  6. Warning — The member receives a formal notice.
  7. Feature restriction — The member may lose access to posting, messaging, uploads, reactions, or specific forums.
  8. Temporary suspension — The account may be restricted for a defined period.
  9. Permanent ban — The account may be removed from the community.
  10. Emergency action — Severe threats, exploitation, abuse, security incidents, or illegal content may result in immediate removal, account restriction, preservation of evidence, and escalation.

We may not always explain every enforcement detail, especially when doing so would expose reporters, private information, security controls, or abuse-prevention methods.

26. Appeals

If you believe a moderation action was made in error, use the appeal process or contact the moderation team through the appropriate channel.

Appeals should include:

  • Your username.
  • The action you are appealing.
  • Why you believe the action was incorrect.
  • Any relevant context.
  • A clear commitment to follow the Guidelines going forward, when applicable.

Do not:

  • Submit repeated frivolous appeals.
  • Harass moderators.
  • Create new accounts to evade restrictions.
  • Argue moderation decisions across unrelated threads.
  • Encourage others to pressure moderators.

One clear appeal is more effective than repeated hostile messages.

27. Special Rules for Support Requests

When asking for help:

  • Use a descriptive title.
  • Explain the problem clearly.
  • Include relevant environment details.
  • Describe what you already tried.
  • Share screenshots or logs only after redacting sensitive data.
  • Be patient with volunteers, members, moderators, and staff.
  • Mark solutions when available.
  • Follow up with the fix so others can learn.

When answering support requests:

  • Be accurate.
  • Be constructive.
  • Ask clarifying questions when needed.
  • Avoid sarcasm toward beginners.
  • Do not shame users for not knowing something.
  • Do not recommend unsafe workarounds without warning.
  • Identify assumptions.
  • Correct outdated or risky advice.

28. Special Rules for Courses and Learning Areas

In course-related areas:

  • Do not post answer keys unless explicitly allowed.
  • Do not help others cheat.
  • Do not request someone else's completed work.
  • Do not misrepresent course completion or achievement.
  • Do not upload copyrighted course material unless authorized.
  • Keep feedback constructive.
  • Respect different levels of experience.

Helping someone understand a concept is allowed. Doing the work for them in a way that violates course rules is not.

29. Member Profiles, Avatars, and Signatures

Profiles, avatars, bios, and signatures must follow the same rules as posts.

Do not use profile content to:

  • Harass.
  • Impersonate.
  • Promote scams.
  • Display explicit content.
  • Share private information.
  • Evade moderation.
  • Attack another member.
  • Mislead users about your role or authority.
  • Insert spam links.

Moderators may edit or remove profile content that violates these Guidelines.

30. Marketplace, Promotions, and External Links

Where marketplace or promotional activity is permitted, additional rules may apply.

External links may be removed when they:

  • Are unsafe.
  • Are deceptive.
  • Are irrelevant.
  • Contain malware.
  • Lead to phishing.
  • Hide affiliate or referral relationships.
  • Bypass community rules.
  • Require unnecessary personal information.
  • Create legal, security, or privacy risk.

Members are responsible for links they post.

31. Legal Requests and Law Enforcement

Mobieus.io Support may respond to valid legal requests according to applicable law and internal procedures.

Do not post legal demands, subpoenas, takedown threats, or law-enforcement requests as forum drama. Use the appropriate contact channel.

The community is not a substitute for legal advice.

32. Medical, Legal, Financial, and Safety Advice

Members may discuss general information, but Mobieus.io Support is not a professional advisory service.

Do not present yourself as a licensed professional unless you are authorized and your profile or post makes the limits of your advice clear.

For high-risk matters:

  • Encourage users to consult qualified professionals.
  • Avoid definitive instructions beyond your competence.
  • Do not pressure users into risky decisions.
  • Do not exploit vulnerable users.

33. Emergencies and Immediate Harm

Mobieus.io Support is not an emergency service.

If someone appears to be in immediate danger, contact local emergency services or an appropriate crisis resource. Moderators may remove content or escalate concerns when necessary to reduce harm.

34. Changes to These Guidelines

These Guidelines may be updated as the community, platform, risks, or legal requirements change.

When practical, significant updates may be announced or dated. Continued use of Mobieus.io Support after changes means you agree to follow the updated Guidelines.

35. Final Standard

No written policy can cover every scenario.

When deciding whether content or behavior is acceptable, moderators and administrators may consider:

  • Intent.
  • Impact.
  • Safety risk.
  • Legal risk.
  • Privacy risk.
  • Pattern of behavior.
  • Prior warnings.
  • Community disruption.
  • Whether the conduct supports or harms the purpose of Mobieus.io Support.

Use good judgment. Help keep the community useful, safe, and respectful.