Guide to the ACM Code of Ethics

The ACM Code of Ethics and Professional Conduct serves as the foundational ethical standard for computing researchers, educators, and software practitioners worldwide. Originally adopted by the Association for Computing Machinery (ACM) Council in 1992 and revised in 2018, the Code expresses the collective conscience of the computing profession. Rather than functioning as a punitive legal code, it acts as a proactive guide for positive action, establishing baseline expectations for technological development, human well-being, and social accountability across academia, industry, and public administration.

In computing and data-intensive research, computational systems interface directly with critical societal infrastructure. Researchers operating under institutional awards or sponsored grants frequently face complex trade-offs between computational performance, data privacy, algorithmic fairness, and system security. Understanding how the ACM Code applies across research design, peer review, and institutional governance is essential for conducting responsible research in computer science and maintaining public trust in digital technologies.

What It Is and Who Runs It

The ACM Code of Ethics is a normative governance framework developed and maintained by the Association for Computing Machinery, the world’s largest computing society. Governance and ongoing interpretation of the Code are administered by the ACM Committee on Professional Ethics (COPE). COPE develops educational case studies, publishes interpretive guidance, coordinates ethics curriculum initiatives, and evaluates formal inquiries and complaints concerning ACM members.

The 2018 Code was developed through an extensive international consultation led by the ACM Code 2018 Task Force. This revision addressed profound technological shifts that emerged after the 1992 version, including pervasive cloud infrastructure, algorithmic decision systems, artificial intelligence, and autonomous technologies. While technical standards specify how software operates, the ACM Code establishes whether and how systems should be deployed, placing the public good as the paramount concern.

Eligibility and Scope

The ACM Code of Ethics applies directly across all ACM membership tiers:

Voting Members: Professional computing researchers, systems developers, academic faculty, and research administrators holding standard professional membership.
Associate Members: Computing practitioners, technical affiliates, and cross-disciplinary collaborators participating in ACM activities.
Student Members: Undergraduate and graduate students enrolled in computing degree programs or university research laboratories.
Institutional Leaders: ACM volunteers, SIG officers, journal editors, conference program committee chairs, and elected Council officers.

Beyond individual members, university computing departments and research centers routinely incorporate the ACM Code into laboratory charters, computing curricula, and institutional research guidelines. Multidisciplinary initiatives in software engineering utilize the Code alongside organizational policies to govern open-source repositories, scientific data sharing, and digital experiments.

What It Funds or Requires

The ACM Code does not distribute grant funds; rather, it establishes binding professional expectations across twenty-five operational imperatives structured into four core sections:

Section 1: General Ethical Principles

Universal moral imperatives governing computing professionals:

1.1 Contribute to society and human well-being: Affirm that all people are stakeholders in computing and prioritize human rights and environmental stewardship.
1.2 Avoid harm: Mitigate unintended negative consequences, including security vulnerabilities, privacy breaches, and algorithmic discrimination.
1.3 Be honest and trustworthy: Provide transparent disclosure of system capabilities, constraints, and operational risks.
1.4 Be fair and take action not to discriminate: Proactively uphold equity and respectful participation across all demographics.
1.5 Respect the work required to produce new ideas: Honor intellectual property, software licenses, attribution, and scholarly citation standards.
1.6 Respect privacy: Prevent unauthorized data collection and protect sensitive personal information.
1.7 Honor confidentiality: Safeguard proprietary data and privileged communications unless compelled by public safety or legal requirements.

Section 2: Professional Responsibilities

Operational standards for technical practice and peer review:

2.1 High Quality: Strive for exemplary quality in processes, artifacts, and documentation.
2.2 Professional Competence: Maintain continuous technical mastery and ethical awareness.
2.3 Rule Compliance: Respect applicable legal statutes, institutional policies, and licensing terms.
2.4 Professional Review: Provide thorough peer evaluation and accept critical scrutiny, a key element when navigating CS conference vs journal authorship credit.
2.5 Risk Evaluation: Conduct thorough evaluations of computer systems, identifying potential hazards and systemic impacts.
2.6 Scope of Competence: Undertake professional tasks strictly within verified domains of technical competence.
2.7 Public Awareness: Foster public understanding of computing systems and their societal implications.
2.8 Authorized Access: Access computational infrastructure and digital records only under explicit authorization.
2.9 Robust Security: Design systems that are robustly and usably secure.

Section 3: Professional Leadership Principles

Guidance for principal investigators, project leaders, and departmental administrators:

3.1 Centrality of the Public Good: Ensure public welfare remains the primary concern during project design.
3.2 Social Responsibility: Encourage and support the social accountability of research teams.
3.3 Workplace Well-Being: Promote working conditions that support human dignity and physical safety.
3.4 Policy Alignment: Establish operational policies reflecting the ethical principles of the Code.
3.5 Professional Development: Support ongoing ethical and professional growth across junior researchers.
3.6 Prudent System Modification: Exercise rigorous care when modifying, migrating, or retiring computing systems.
3.7 Critical Infrastructure Care: Recognize heightened responsibilities when systems interface with essential public services.

Section 4: Compliance with the Code

Mandates that computing professionals uphold the principles of the Code, encourage adherence among peers, and recognize that serious violations are inconsistent with continued ACM membership.

Application or Compliance Steps

Implementing the ACM Code within research groups and professional projects follows clear operational steps:

Pre-Project Risk Assessment: Conduct an ethical and socio-technical review during project design to identify data risks and societal impacts before deploying software models.
Governance and Repository Alignment: Implement open metadata and software standards, such as FAIR4RS principles, to guarantee transparency and reproducibility.
Educational and Case Analysis: Consult interpretive case studies from ACM COPE when addressing ambiguous ethical dilemmas or conflicts of interest.
Grievance Submission: If a member commits an alleged breach (such as data falsification or intentional security sabotage), a written complaint is submitted to ACM headquarters.
COPE Investigative Review: The Committee on Professional Ethics gathers evidence, evaluates facts, and ensures due process for the respondent.
Adjudication and Sanctions: COPE reports findings to the ACM Council, which may issue warnings, remove individuals from editorial boards, or revoke ACM membership.

Typical Timeline Phases

Ethical compliance operates across ongoing operational phases of the research lifecycle:

Design Phase: Identifying stakeholder impacts, conducting privacy assessments, and reviewing human-subject data protocols.
Execution Phase: Enforcing secure software engineering practices, testing for algorithmic bias, and maintaining audit trails.
Dissemination Phase: Publishing transparent methodologies, acknowledging collaborators, and depositing datasets in public archives.
Decommissioning Phase: Safely archiving datasets, revoking system access, and deprecating software assets responsibly.

Common Mistakes

Researchers and technical teams commonly make several errors when interpreting the Code:

Treating Ethics as a Post-Hoc Checkbox: Delaying ethical consideration until software delivery rather than integrating it into initial system architecture.
Equating Legal Compliance with Ethics: Assuming that actions not explicitly prohibited by statute automatically meet professional ethical standards.
Overlooking Societal Side Effects: Optimizing purely for technical metrics while neglecting broader societal or workplace impacts.
Neglecting Deprecated Systems: Abandoning older servers or experimental endpoints without safeguarding stored user data.
Penalizing Ethical Whistleblowers: Failing to protect team members who raise valid safety concerns regarding software flaws.

Related Programs

The ACM Code operates alongside other established engineering and computing codes:

Framework	Administering Body	Primary Audience	Key Focus
ACM Code of Ethics	ACM	Computing professionals and researchers	Public good, privacy, avoiding harm, and social impact
IEEE Code of Ethics	IEEE	Electrical, electronics, and computing engineers	Public safety, conflict of interest, and technical integrity
Software Engineering Code	ACM / IEEE-CS	Software engineers and managers	Product reliability, client duty, and professional judgment
BCS Code of Conduct	BCS	Chartered IT practitioners	Public interest, technical competence, and legal duties

Understanding these distinctions helps clarify disciplinary differences between computer science vs software engineering governance models.

Frequently Asked Questions

Is the ACM Code of Ethics legally binding?

No. It is a professional standard rather than statutory law. However, violation can lead to loss of ACM membership, revocation of awards, and disqualification from ACM journals or conferences. Furthermore, courts and regulatory agencies frequently reference the Code as evidence of professional standard of care.

What major changes occurred in the 2018 update?

The 2018 update modernized the 1992 Code by addressing artificial intelligence, autonomous systems, large-scale data stewardship, and the ubiquity of computing. It elevated the public good to the central consideration in all technical work and added specific mandates covering system retirement and usable security.

How are ethics complaints investigated?

Complaints submitted to ACM headquarters are evaluated by the ACM Committee on Professional Ethics (COPE). COPE examines factual evidence, gives respondents an opportunity to answer allegations, and submits recommended findings to the ACM Council for final adjudication.

Does the Code apply to human data research?

Yes. Section 1.6 requires computing professionals to respect privacy and protect personal data, while Section 1.2 requires avoiding harm. In academic research, these imperatives reinforce institutional review procedures and require strict data minimization and secure storage.

Sources

Association for Computing Machinery. (2018). ACM Code of Ethics and Professional Conduct. Adopted by ACM Council June 22, 2018. URL: https://www.acm.org/code-of-ethics (Read: 2026-11-07).
Gotterbarn, D., Bruckman, A., Flick, C., Miller, K., & Wolf, M. J. (2018). ACM Code of Ethics: A Guide for Positive Action. Communications of the ACM, 61(1), 121–128. https://doi.org/10.1145/3173016 (Read: 2026-11-07).
ACM Committee on Professional Ethics. (2018). Using the Code: Case Studies and Educational Resources. URL: https://ethics.acm.org/ (Read: 2026-11-07).
UC Davis Department of Computer Science. (2020). Course ECS 188: Ethics in Science and Technology. URL: https://web.cs.ucdavis.edu/~rogaway/classes/188/materials/acm-code-of-ethics.pdf (Read: 2026-11-07).

ACM Code of Ethics: Governance, Principles, and Research Compliance