Community
Effective and last updated: 17 July 2026
Describe a genuine workflow or process problem, the people affected, the current steps, and what a useful result would achieve. Use a clear title and the most relevant category. Do not fabricate demand, submit vague promotion, or disguise an advertisement as a problem.
Vote only from your own account and because you genuinely want the problem solved. Do not buy, trade, coordinate, automate, or manipulate votes. If an adequate solution already exists, identify it accurately and disclose any relationship you have with it.
Discuss ideas and work without attacking people. Harassment, threats, hate, sexual exploitation, targeted humiliation, doxxing, and discriminatory abuse are prohibited. Criticism should be specific, relevant, and directed at improving the problem or solution.
Do not post personal data, private communications, credentials, customer records, trade secrets, or confidential employer information without proper authorization. Use fictional or de-identified examples where context is needed.
Submit only content and solutions you have the right to share. Credit relevant sources and comply with software, content, open-source, and data licenses. Do not misrepresent copied work as your own.
Do not distribute malware, exploit the service, probe accounts or systems without authorization, evade restrictions, scrape at disruptive scale, or publish instructions primarily intended to enable abuse. Responsible security reports should be sent privately to support@upsolve.co.
Every problem and solution must comply with the Humanity Pledge. UpSolve may decline content where foreseeable harm cannot be responsibly mitigated.
Depending on severity, history, and context, UpSolve may issue a warning, reduce visibility, remove content, reverse platform decisions, restrict features, or suspend or terminate an account. Serious safety or legal concerns may be reported to appropriate authorities where required or justified.
Report suspected guideline violations to support@upsolve.co. Include the relevant URL, a concise explanation, and supporting context. Do not use reports to retaliate against legitimate disagreement.