Community safety should feel like a visible operating rule, not a hidden moderation afterthought.
DeadArk exists to help people find belonging. These boundaries protect people, locality, honest participation, and system integrity across the unified app and focused community surfaces. This conduct framework applies across the network.
Calm, readable policy pages inside the same system.
These pages should feel authoritative without dropping out of the DeadArk design language. The goal is clarity, not spectacle: stronger rhythm, stronger hierarchy, and direct explanation.
Respect people
Do not harass, threaten, degrade, dehumanize, or target people. Disagreement is allowed. Abuse is not.
Do not manipulate
Do not exploit fear, outrage, group pressure, false urgency, coordinated behavior, or deceptive context to control others.
Be honest
Do not knowingly spread false information, impersonate others, or hide material context. Say when you are uncertain.
Protect locality
Do not expose precise locations, stalk, intimidate, or use local discovery to endanger someone. Respect boundaries in online and in-person interactions.
Use influence responsibly
People, communities, businesses, projects, publications, institutions, moderators, and the DeadArk team follow the same conduct expectations.
Protect the service
Do not exploit bugs, abuse automation, manipulate visibility, evade safeguards, or interfere with system integrity.
Repair harm
Intent does not erase impact. If your actions cause harm, stop, correct what you can, and cooperate with safety measures.
Trust pages should still route people into the right DeadArk context.
These pages are not isolated legal dead ends. They should explain the rule or safeguard clearly, then point people toward the correct surface for access, security, recovery, or broader system understanding.
DeadArk App
Use the app for the wider identity and participation context that these conduct rules are meant to protect.
Route here when the issue involves account state, reporting, or participation across the broader network
Communities
Use the community surface when questions of belonging, moderation, or local boundaries need a more focused social context.
Route here when conduct questions are tied to community continuity and shared local participation
Terms
Use the terms page for the wider access, content, and service rules that frame this conduct layer.
Route here when the question is about service structure or participation rights beyond behavior alone
Enforcement should aim at protection, not theatrical punishment.
Violations may result in content limits, feature limits, invitation limits, temporary pauses, or removal when necessary to protect people or the service. The point is to preserve a trustworthy environment, especially where locality and continuity make harm more consequential.
Help should stay available in context.
Questions about rules should be answerable from the current context: the active community, the relevant interaction, the user’s role, and the wider system policy. People should not have to guess whether the rule changes when they move between surfaces.
Even trust and policy flows should make sense relative to the wider app, the user's active identity, and the focused surface they came from.