Community Guidelines

1. Make requests useful

Keep each request focused on one product idea, explain the problem it would solve, and use clear, constructive language.

Do not include passwords, contact details, account information, private health information, or other sensitive information. Approved requests are visible to other signed-in users.

2. What is not allowed

You may not submit or promote content that:

• is unlawful, threatening, harassing, hateful, discriminatory, or intended to target or shame another person or group;
• is sexually explicit, graphically violent, or encourages physical harm;
• reveals another person’s personal, confidential, or sensitive information;
• infringes intellectual-property or other third-party rights;
• is spam, advertising, malware, deliberately misleading, or unrelated to improving PUMPD; or
• uses automation, multiple accounts, or coordinated manipulation to distort voting or reporting.

3. Protect your privacy

Your account identity and contact details are not shown with a feature request, but the request text itself is shared with the signed-in PUMPD community if it is approved. Do not use a request to share information you want to keep private.

Staff can review the account associated with a request when needed for moderation, safety, or support. Reports, author blocks, and internal moderation notes are not shown publicly.

4. Review and moderation

New requests are private while awaiting review. We may edit a request for clarity, correct its category, reject it, hide it after publication, or merge it into a substantially similar request. We will not intentionally change the meaning of an accepted request.

Duplicate ideas are not misconduct. We may merge them so votes and updates have one clear home.

We may temporarily or permanently restrict access to feature-board participation when an account repeatedly or seriously violates these guidelines.

5. Votes and roadmap states

Each account may cast one vote per request. A vote is a signal of interest, not a purchase, promise, or entitlement.

• Open — available for community voting and consideration.
• In Review — being evaluated; no decision or delivery commitment has been made.
• Planned — something we intend to pursue, but scope and timing may change.
• Not Planned — not currently moving forward.
• Complete — released or otherwise delivered.

Votes, rankings, labels, and roadmap states are informational and non-binding. They may change as product, safety, technical, or business needs change.

6. Reports and blocks

Use the in-app report action when a request may violate these guidelines. Reports should be made in good faith and include only the information needed for us to review the concern.

You can block a request author to hide that contributor’s requests from your own board. Blocking does not notify the author or decide whether their content violates these guidelines.

7. Enforcement and contact

Enforcement depends on context, severity, and history. Actions may include rejecting or hiding content, merging duplicates, restricting feature-board participation, or taking account action under our Terms.

If you believe we made a mistake, or if you have a safety or privacy concern, contact us at support@getpumpd.com.

8. Changes to these guidelines

We may update these guidelines as the feature request board evolves. When we do, we will revise the “Last updated” date above and provide additional notice when appropriate.