Skip to main content

2IX

2IX.org

Trust and Safety

Trust and safety baseline

Keep volunteer matching useful, fair, and private enough to protect people.

The safest default is civic, nonprofit, school, public agency, community, and open-source work with clear outcomes. For-profit unpaid roles are not a default posting category.

Report a concern
Read safety model
Privacy policy

Volunteer

Control visibility

Use public, limited, or private profile visibility depending on comfort level and the role.

Organization

Publish responsibly

Post only work with support, consent-aware screening, and enough context to evaluate the role.

Moderator

Report concerns

Flag unsafe postings, misleading records, privacy exposure, or exploitative requests.

  • Eligible publishers: nonprofits, schools, civic groups, public agencies, mutual-aid/community initiatives, and open-source projects.
  • For-profit unpaid roles: not allowed by default; any CSR or community-service exception needs explicit review and separate rules.
  • Privacy: public records should not expose secrets, credentials, government IDs, exact home addresses, or unnecessary personal data.
  • Screening: background checks and clearances are role-specific, consent-based, and delegated to qualified providers.
  • Moderation: reporting, review, limits for unverified accounts, and audit trails are part of the product, not later polish.

Trust model

What 2IX does and does not publish

Safety is a product feature. The public site should expose enough context to evaluate work while keeping sensitive personal, screening, and internal project details out of public view.

Public-safe information

Cause areas, skills, broad availability, public links, organization type, verification state, deliverables, acceptance criteria, and public screening notes can help users decide what to do next.

  • Use broad locations unless exact site details are necessary.
  • Use public artifact links only.
  • Use text badges so status is not color-only.

Private or restricted information

Private emails, phone numbers, exact home addresses, credentials, raw background checks, government IDs, private files, and unreviewed internal notes should not be public browsing content.

  • Applications are private records.
  • Reports are private moderation records.
  • Screening belongs in consent-based provider workflows.

Reporting closes the loop

Every opportunity and organization surface includes a concern path. Reports capture reason, details, reporter context when provided, and the referenced entity for moderator review.

  • Privacy leak
  • Misleading scope
  • Safety or eligibility issue

Key terms

Unverified
The organization can be visible, but users should read the post carefully and stewards may apply limits.
Pending review
The organization has supplied enough signal for review but is not fully verified yet.

Verified organizations should receive more publishing reach and lower friction. Unverified records should face review, lower outbound limits, and clearer warnings.

Report a concern

Use this for safety, privacy, accuracy, eligibility, or suspicious-content concerns. Reports are private moderation records.

Optional, but helpful for follow-up.