Make Bug Reports Useful.
Keep the Community Better.

1. Our Community

Bugged.cc works best when everyone contributes in good faith. Whether you're reporting a broken button, testing a new product, maintaining a project, or helping someone reproduce an issue, your contribution should make the software and the community better.

We value:

• Accuracy
• Respect
• Transparency
• Constructive feedback
• Responsible disclosure
• Useful information
• Collaboration

2. Before You Report a Bug

Search First

Before creating a new report:

• Search existing bugs.
• Check whether the issue has already been reported.
• If you find an existing report, add useful information instead of creating a duplicate.

Make Sure It's Actually a Bug

Consider:

• Is the behavior unexpected?
• Can you reproduce it?
• Is there enough information for someone else to understand the problem?

3. Write a Useful Bug Report

Include whenever possible:

4. Good vs Bad Reports

5. Don't Include Sensitive Information

Never post:

• Passwords
• API keys
• Access tokens
• Private keys
• Credit/debit card information
• Authentication cookies
• Personal identification documents
• Private customer information
• Confidential company information
• Database credentials

6. Security Vulnerabilities

Don't publicly expose sensitive security issues

Security vulnerabilities can be different from ordinary bugs. Do not publicly post:

• Active exploit details
• Credentials
• Private data
• Authentication bypass details that expose real accounts
• Database dumps
• Secrets
• Malware

Responsible reporting

If a project provides a private security reporting channel, use that channel instead of publishing sensitive details publicly.

Don't exploit a vulnerability

Do not access, modify, download, destroy, or disclose data that does not belong to you.

7. Respect Other People

Bugged.cc is for technical discussion, not personal attacks.

8. No Spam

Don't use Bugged.cc for:

• Unsolicited advertising
• Repeated promotional posts
• Referral spam
• SEO spam
• Fake bug reports
• Automated content flooding
• Irrelevant links

9. Don't Fabricate Bugs

Report what you actually observed.

Do not:

• Invent bugs
• Fake screenshots
• Manipulate evidence
• Misrepresent results
• Deliberately submit false reports
• Create reports to damage a company or project

If you're unsure whether something is a bug: Say that you're unsure and explain what you observed.

10. Duplicate Reports

Duplicate reports make issue tracking harder.

Before submitting:

Search → Compare → Report

If the issue already exists:

Add additional reproduction steps, screenshots, affected versions, or other useful information to the existing report.

11. One Issue Per Report

Whenever practical: One report = One issue

Instead of:

“Login, dashboard, payments, and email are broken.”

Create separate reports if they are independent problems.

This makes tracking and resolution easier.

12. Keep Titles Clear

13. Comments & Discussions

Comments should add value.

14. Voting / Reactions

If Bugged.cc supports voting or reactions:

Use votes to indicate that you are experiencing or supporting an issue—not as a replacement for useful technical information.

Don't manipulate votes using:

• Multiple accounts
• Bots
• Coordinated fake activity
• Purchased engagement

15. Company & Project Owners

Companies and project maintainers also have responsibilities.

When reviewing reports:

• Don't attack the reporter.
• Ask for missing information.
• Mark duplicates appropriately.
• Explain when something cannot be reproduced.
• Keep statuses accurate.
• Don't delete legitimate criticism simply because it is negative.
• Don't expose private reporter information.

Recommended responses:

16. Don't Abuse Bug Status

Statuses should represent the actual state of an issue.

Reported → Confirmed → In Progress → Fixed → Verified → Closed

Other possible statuses:

• Duplicate
• Invalid
• Cannot Reproduce
• Won't Fix
• By Design

17. Responsible Disclosure

Security researchers

If you discover a vulnerability:

• Avoid unnecessary access to data.
• Don't disrupt the service.
• Don't delete or modify other users' information.
• Collect only the minimum evidence needed.
• Use the project's private security channel when available.
• Give the affected party reasonable opportunity to investigate.
• Don't publish sensitive information irresponsibly.

18. Content We Don't Allow

Bugged.cc may remove content that includes:

19. Moderation

How Moderation Works

Bugged.cc may review content and accounts to maintain platform safety, prevent abuse, and enforce these guidelines.

Possible actions:

• Warning
• Content removal
• Report limitation
• Comment restriction
• Temporary suspension
• Account suspension
• Account termination

The action taken may depend on the nature, severity, frequency, and context of the violation.

20. Reporting Abuse

See Something That Violates These Guidelines?

Users should be able to report:

• Spam
• Harassment
• Fake bug reports
• Privacy violations
• Security issues
• Impersonation
• Malicious content
• Other guideline violations

Report button → Select reason → Add details → Submit

21. Appeals

Think We Made a Mistake?

If your content or account was restricted and you believe the action was incorrect, you may contact Bugged.cc to request a review.

Include:

• Username
• Report/comment URL
• What happened
• Why you believe the action was incorrect
• Relevant context

22. Automated Tools & Bots

Automation

Automated tools must interact with Bugged.cc responsibly and within applicable rate limits.

Don't:

• Spam reports
• Create fake accounts
• Manipulate votes
• Scrape restricted data
• Circumvent platform limits
• Overload the service

23. AI-Generated Content

AI-Assisted Content

AI tools may be used to help draft or organize bug reports, but users remain responsible for the accuracy and content of anything they submit.

Don't submit AI-generated reports that:

• Invent bugs
• Fabricate evidence
• Misrepresent testing
• Spam projects
• Automatically flood the platform

24. Accessibility & Inclusion

Everyone Is Welcome

Bugged.cc aims to provide a respectful environment where people with different levels of technical experience can participate.

Beginners are welcome.

You don't need to be a developer to report a bug.

25. Guidelines vs Terms

These Community Guidelines explain how we expect people to use Bugged.cc and interact with others.

Our Terms of Service contain the legal terms governing your use of the platform.

26. Changes to Guidelines

Guideline Updates

These guidelines may change as Bugged.cc grows and new types of abuse or community needs emerge.

Last Updated: September 2026