How Civcampus is governed
Published rules that apply to students, moderators, verified organizations, university responders, and everyone on the platform.
The purpose of Civcampus is to help campus communities identify issues, document concerns, support constructive advocacy, and track outcomes. Civcampus is not a place for harassment, personal attacks, defamation, doxxing, threats, or targeting individuals.
Every moderation action must follow Civcampus rules. Moderators are required to protect privacy, apply rules consistently, document their decisions, and avoid conflicts of interest — and moderation actions are logged so users can understand what happened and why.
Civcampus is designed to be accountable to students while giving universities a clear, professional, and safe way to understand student concerns.
Who does what
Students create the record, responders answer the record, moderators protect the record, admins maintain the system, and verified group officers organize advocacy — but no one quietly controls the record.
Everyone starts as a Member; elevated roles are granted by an admin — never self-assigned. Verified Group Officer is derived from leading a verified organization, and is scoped to that group.
Verified students who report issues, add their voice, follow updates, and support advocacy.
Verified campus offices or representatives who can post official public responses — but cannot edit, delete, or moderate student posts.
Authorized representatives of a verified student organization who manage their group page, sponsor campaigns, and collect consent-based support. Scoped to their own group.
Trained students who review posts, protect privacy, verify groups, and act on takedown requests under published rules.
Platform stewards who manage campus setup, roles, security, and escalated safety or legal issues — with every action logged.
| Capability | Member | Responder | Group Officer | Moderator | Admin |
|---|---|---|---|---|---|
| Post issues | ✓ | ✓ | ✓ | ✓ | ✓ |
| Add their voice | ✓ | ✓ | ✓ | ✓ | ✓ |
| Follow issues | ✓ | ✓ | ✓ | ✓ | ✓ |
| Comment / submit updates | ✓ | ✓ | ✓ | ✓ | ✓ |
| Sign petitions as self | ✓ | ✓ | ✓ | ✓ | ✓ |
| Apply to start a group | ✓ | ✓ | ✓ | ✓ | ✓ |
| Sign on behalf of a verified group | — | — | ✓ | — | ✓ |
| Manage a verified group page | — | — | ✓ | — | ✓ |
| Create campaigns/petitions for a group | — | — | ✓ | — | ✓ |
| Post official university response | — | ✓ | — | — | ✓ |
| Review pending posts | — | — | — | ✓ | ✓ |
| Approve / reject posts | — | — | — | ✓ | ✓ |
| Redact unsafe identifying details | — | — | — | ✓ | ✓ |
| Verify groups & organizations | — | — | — | ✓ | ✓ |
| Review takedown requests | — | — | — | ✓ | ✓ |
| Decide appeals | — | — | — | ✓ | ✓ |
| Access limited identity for safety (logged) | — | — | — | ✓ | ✓ |
| Manage campus settings & themes | — | — | — | — | ✓ |
| Assign roles | — | — | — | — | ✓ |
| Secretly edit / delete a student post | — | — | — | — | — |
- 01
What Civcampus allows
Civcampus allows good-faith reports, updates, campaigns, petitions, letters, and initiatives that focus on campus issues.
Allowed content may include- campus facility problems
- accessibility barriers
- safety concerns
- dining, housing, transportation, or service issues
- communication problems
- policy concerns
- recurring student experience problems
- campaign updates
- petitions or sign-on letters
- verified student organization advocacy
- evidence related to a campus issue
- 02
What Civcampus does not allow
Civcampus does not allow content that creates safety, privacy, legal, or harassment risks.
Not allowed- naming or identifying a person in an accusation
- targeting a student, professor, staff member, administrator, or bystander
- personal attacks, insults, or name-calling
- harassment or bullying
- threats or encouragement of harm
- doxxing or private personal information
- student ID numbers, private emails, phone numbers, addresses, or medical details
- photos of people used to accuse, shame, or expose them
- unsupported allegations against a specific person
- spam, impersonation, or fraudulent activity
- content that belongs in an emergency, police, Title IX, HR, conduct, or official reporting channel
A post may be held for review even if it does not include a name, if it contains enough detail to identify a person. Civcampus is for documenting campus issues — not exposing individuals.
- 03
How posts are reviewed
Some posts may appear immediately if they pass safety checks. Posts that trigger a content rule are held as Pending Review and hidden from the public feed until a moderator reviews them.
A moderator may- approve the post
- reject the post
- request edits from the author
- redact identifying details
- mark the post as duplicate
- link it to an existing issue
- escalate it for safety review
- lock comments or updates
- remove evidence that violates privacy rules
Every moderation decision must include a reason. If a post is rejected, the author is notified and shown the reason. Depending on the seriousness of the violation, a user may receive a warning, temporary posting limit, temporary suspension, or permanent removal.
- 04
What moderators must follow
Moderators must follow Civcampus’s published rules. They may not moderate based on personal opinion, disagreement, popularity, politics, friendship, campus position, or pressure from any outside party.
Moderators must- apply rules consistently
- protect student privacy
- avoid conflicts of interest
- give clear reasons for decisions
- document moderation actions
- avoid unnecessary access to private account information
- recuse themselves from cases where they are personally involved
- escalate serious safety, legal, or privacy concerns
- follow Civcampus data and privacy policies
Moderators may not- remove posts because they are embarrassing to the university
- approve posts that identify or target individuals
- use private user information for personal reasons
- browse anonymous account identities without a safety reason
- moderate issues involving their own organization, department, campaign, or personal dispute
- retaliate against users
- secretly change public records
- 05
What moderators can see
Civcampus lets students post publicly under a display name or hide their name from the public. Authorized moderators may access limited account information behind a pseudonymous or anonymous post only when necessary to enforce safety rules, investigate abuse, review a takedown request, or respond to a serious policy violation.
Moderator access to private account information is logged. Moderators cannot use private account information for curiosity, retaliation, personal disputes, or routine browsing. Misuse of moderator access can result in removal from the moderation team and loss of platform access.
- 06
Student moderators, university moderators, or both?
Student moderators keep Civcampus student-centered — students are more likely to trust a platform that is not controlled by administration. But universities are more willing to participate when there is a clear role for official campus responders.
University responders can- post official updates
- acknowledge an issue
- provide resource links
- request clarification
- mark that a department is reviewing an issue
- submit a takedown request
- propose a resolution
- respond publicly to a campaign or petition
University responders cannot- delete student posts
- edit student posts
- reveal anonymous identities
- approve or reject student reports
- silently remove records
- access private supporter data without consent
The best model: student moderators + university responder accounts. University administrators are not ordinary moderators and cannot remove or edit student posts. Instead, universities get a separate role — University Responder.
- 07
What university administration cannot do
University administrators do not have direct edit or delete access to student posts.
Universities may submit a takedown request if they believe a post violates Civcampus rules, contains private information, creates a safety risk, identifies an individual, or includes legally sensitive content. Takedown requests are reviewed under the same published rules as all others. If action is taken, Civcampus records the action and reason in the moderation log.
Civcampus is not designed to block universities from responding. It is designed to prevent quiet or unexplained changes to student records.
- 08
Takedown requests
Anyone may submit a takedown request if they believe a post violates Civcampus rules.
Takedown requests may be submitted for- personal identifying information
- doxxing
- harassment
- threats
- defamation risk
- private or sensitive information
- mistaken identity
- safety concerns
- duplicate or fraudulent posts
- copyrighted or unauthorized material
- evidence that exposes bystanders
Possible outcomes (reviewed within a 72-hour target)- no action
- redaction of identifying details
- evidence removed
- post hidden pending review
- post rejected
- post removed
- post locked
- user warned or suspended
- issue merged with another record
Each outcome is logged with a reason.
File a takedown request → - 09
Rejected posts and appeals
If a post is rejected, the author receives a notice explaining which rule was violated. Authors may appeal a rejection. Appeals are reviewed by a second moderator who was not involved in the original decision.
Appeal outcomes may include- original decision upheld
- post approved
- post approved after edits
- post returned to author for revision
- post permanently rejected
Repeated or serious violations may result in temporary or permanent account restrictions.
- 10
Public moderation log
Civcampus maintains a public moderation log to increase transparency. It does not show private user identities, private evidence, student emails, internal notes, or details that could identify someone.
The public log may show- action taken
- general reason
- date and time
- content type
- campus
- whether the action was appealed
- appeal outcome
Example entries- · Post held for review — identifying details included
- · Evidence removed — bystander faces visible
- · Post approved after edits — personal names removed
- · Takedown request denied — no rule violation found
- · Post removed — harassment / personal targeting
- · Appeal approved — post restored with redactions
Live log
last 1 actionsDate Action Target Reason By 8/7/2026 approve issue #6C60E9 — Jhonyadmin - 11
Verified organizations and advocacy content
Verified student organizations may create pages, campaigns, petitions, letters, initiatives, and sign-on requests. Organizations must follow the same rules as all users.
Verified organizations may not- impersonate another group
- sign on behalf of a group without authorization
- publish private supporter information without consent
- target individuals
- use Civcampus to harass, shame, or defame others
- misuse supporter records
Organization sign-ons must be made by authorized representatives. Civcampus may require officer approval, annual verification, or additional review before a group’s name appears on an initiative. Supporter lists are consent-based; private supporters are counted but not individually named.
- 12
Why universities can work with Civcampus
Civcampus is designed to support a healthier feedback loop between students and campus leaders.
Universities may benefit because Civcampus can help- identify recurring student concerns
- organize scattered feedback into clearer patterns
- reduce misinformation by creating structured public records
- give departments a place to post updates
- show progress over time
- support student trust through transparent rules
- separate constructive issue reporting from harassment or personal attacks
- route emergencies and protected matters to official resources
Civcampus does not replace official university reporting systems — it complements them by helping students document non-emergency concerns, organize advocacy, and track visible outcomes. The goal is not to embarrass universities; it is to make issues easier to understand, respond to, and resolve.
Civcampus is an independent, student-run platform and is not owned, operated, or endorsed by any university or university system. For emergencies call 911 or campus police; for crisis support call or text 988; use official campus channels for Title IX and other protected matters.