Safety
Protect the account, the work, and the people involved.
Marketplace safeguards reduce risk, but they do not replace careful judgment. Stop and report anything that asks you to bypass a recorded workflow.
Account safety
- Use a unique password and never share a sign-in session or verification link.
- Confirm the address and purpose before following links. Many support will not ask for your password or a one-time code.
- Report unexpected account changes, messages, or payout details promptly.
Payment and payout safety
- Keep listing payments, funded rewards, refunds, and disputes in their recorded Many workflow.
- Never pay an applicant to apply, send a “verification payment,” buy gift cards, or move money for another user.
- A browser redirect or screenshot is not proof of payment. Many relies on a verified provider event.
- Review the destination summary before requesting a payout. Full destination values are encrypted and are not shown in admin tables.
Safe product testing
- Use staging accounts and test data whenever a client can provide them.
- Stay inside the written scope. Do not perform load, denial-of-service, credential, social-engineering, or destructive testing unless a separate authorized program explicitly permits it.
- Remove secrets, personal data, authentication tokens, and unrelated user information from screenshots and recordings.
- If you encounter live personal data or a serious vulnerability, stop the test, preserve only the minimum evidence, and notify the client privately.
Files and links
Treat every attachment as untrusted. Many permits a narrow set of file types and validates basic signatures, but basic validation is not a malware scan. Keep endpoint protection current and do not open unexpected files.
Immediate danger or illegal content
Do not use Many for emergency services. If someone faces immediate danger, contact the appropriate local emergency authority. Preserve relevant records and then report the matter to Many.
Conduct expectations are in the community guidelines.