Refusal without penalty
You can restrict processing, opt out of algorithmic matching, withdraw sensitive matching consent, decline contact, or delete your account without losing basic access to public knowledge.
Loading...
Loading...
Governance surface
This page names the refusal, challenge, and accountability paths that hold the platform to its charter while fuller community governance is still being built.
Product decisions must respect dignity, consent, reciprocity, commons stewardship, plural knowledge, and honest incompleteness. Admin tools and recommendation systems are implementation details, not exceptions to that floor.
You can restrict processing, opt out of algorithmic matching, withdraw sensitive matching consent, decline contact, or delete your account without losing basic access to public knowledge.
If a recommendation, moderation action, label, or governance decision feels wrong, use feedback or contact support and describe the affected page, decision, and harm. The team must name the reason and review path rather than silently close the issue.
Admin-only controls are for safety, legal, and operational continuity. Route disabling, moderation, and data access should be documented and contestable when they affect a user or community.
Current V1 controls are broad. Some fine-grained label, temporal, lineage, and more-than-human controls remain planned work and must be described as such until they are shipped.
The permanent charter-holding body, amendment thresholds, and public refusal register still need community design. Until then, this surface is the minimum user-facing accountability layer.
The short governed commitments that anchor participation, consent, refusal, amendment, and stewardship.
What Changemappers will not trade away under funder, partner, acquisition, or use-case pressure.
A plain route for correcting harm, incompleteness, or governance drift without knowing internal process language.
A visible account of current platform limits across traditions, languages, work contexts, users, and product gaps.
The safety and exit process required before federation or remote-instance features are enabled.
The initial public roster for role transparency until a formal governance-role data model exists.
Traditional Knowledge and Biocultural labels are protocol/context labels beside legal licensing.
Default turnover and successor-mentoring expectations for governance roles.