Skip to topic
    ← Back to course topics

    Ethical and legal — Edexcel GCSE Computer Science

    Ethical and legal explained

    Ethical and legal covers 3 specification points, including Understand ethical and legal issues associated… and Understand ethical and legal issues associated….

    Read the full explanation

    Open a point below for its explanation and revision guidance.

    5.2.1 understand ethical and legal issues associated with the collection and use of personal data (privacy, ownership, consent, misuse, data protection)

    Personal data is information relating to an identifiable living person (e.g. name, address, date of birth, online identifier). Collecting personal data raises ethical and legal responsibilities across five dimensions: Privacy (individuals expect confidentiality and protection against intrusive tracking); Ownership (questions over who controls, shares, or monetises stored records); Consent (clear, withdrawable agreement specifying the exact processing purpose); Misuse (preventing data loss, identity theft, unauthorized disclosure, or unapproved secondary use); and Data Protection (compliance with the Data Protection Act 2018 and UK GDPR, which legally require lawful, transparent, secure processing and uphold individual rights).

    5.2.2 understand ethical and legal issues associated with the use of artificial intelligence, machine learning and robotics (accountability, safety, algorithmic bias, legal liability)

    This topic examines ethical and legal issues when artificial intelligence, machine learning and robotics are used. Accountability asks who is answerable when a system causes harm: the developer who chose the training data and model, the organisation that deployed it, or the operator who used it. Safety concerns physical and psychological harm, especially where robots act in the real world or AI informs decisions about people; systems should be tested, monitored and have fail-safes. Algorithmic bias occurs when training data or design reflects existing unfairness, so the system produces discriminatory outcomes, for example a recruitment tool trained on past hiring that favoured one group. Legal liability asks who must compensate or face penalties under current law, which may not clearly assign responsibility when decisions emerge from a learned model rather than a direct instruction.

    5.2.3 understand methods of intellectual property protection for computer systems and software (copyright, patents, trademarks, licencing)

    Intellectual property (IP) law gives creators and businesses legal rights over what they make, including computer systems and software. Copyright protects the fixed expression of original work, such as source code, artwork, music and documentation; it arises automatically when the work is recorded and generally lasts many decades, so a programmer owns the code they write unless an employer or contract says otherwise. A patent protects a new, inventive technical process or device, for example a novel data-compression algorithm or hardware design, and must be applied for and granted before it can be enforced. A trademark protects brand identity: names, logos and slogans that distinguish a product, such as a software company's logo.

    Read the Ethical and legal study guideFull revision notes for Edexcel GCSE Computer Science

    Your focus

    1. Explain the ethical and legal issues of privacy, ownership, consent and misuse in the collection and use of personal data.
    2. Describe data protection duties under legislation such as the UK GDPR and the Data Protection Act 2018.
    3. Reach a balanced judgement on a scenario involving the collection and use of personal data.
    Show all 9 objectives
    1. Explain how accountability, safety, algorithmic bias and legal liability arise in a given use of AI, machine learning or robotics.
    2. Analyse a scenario to identify who may be accountable and how bias or safety failures could occur.
    3. Evaluate the ethical and legal challenges of assigning responsibility when decisions emerge from learned models or autonomous robots.
    4. Identify copyright, patents, trademarks and licencing as methods of intellectual property protection.
    5. Describe what each method protects and how it is obtained or granted.
    6. Select the most appropriate method for a given scenario involving computer systems or software.

    Ethical and legal exam tips

    Marking Points
    • Explains privacy as a person’s expectation of control over personal information, using an example such as covert location tracking.
    • Discusses ownership by distinguishing the individual the data describes from the organisation that stores and controls the copy.
    • Explains consent as informed, specific and withdrawable agreement to a stated purpose of collection.
    • Describes misuse such as unauthorised sharing, sale or repurposing of data and identifies a resulting harm such as identity theft or discrimination.
    • Outlines data protection duties under legislation such as the UK GDPR and the Data Protection Act 2018, including lawful basis, purpose limitation, security and retention.
    • Reaches a balanced ethical and legal judgement that weighs organisational benefit against individual rights and the consequences of breach.
    • Explains accountability by identifying the different parties (developer, deploying organisation, operator) and the difficulty of assigning responsibility when decisions emerge from a learned model.
    • Discusses safety in terms of physical and psychological harm, and the need for testing, monitoring and fail-safes, especially for robots acting in the real world.
    • Explains algorithmic bias as arising from training data or design that reflects existing unfairness, leading to discriminatory outcomes.
    • Discusses legal liability: who must compensate or face penalties, and the challenge that current law may not clearly assign responsibility for autonomous or learned behaviour.
    • Applies the issues to a realistic AI, machine learning or robotics scenario, showing how accountability, safety, bias and liability interact.
    • Copyright protects the fixed expression of original work such as source code, and arises automatically once the work is recorded.
    • A patent protects a new, inventive technical process or device and must be applied for and granted before it can be enforced.
    • A trademark protects brand identity such as a name, logo or slogan that distinguishes a product or company.
    • Licencing is the owner granting permission to use software under stated conditions, for example single-user, site or open-source licences.
    • The four methods are complementary and can be used together on the same product.
    Examiner Tips
    • 💡Address each named issue in turn — privacy, ownership, consent, misuse and data protection — so no clause is left uncovered.
    • 💡Support each point with a short scenario, such as a fitness app sharing heart-rate data with advertisers without specific consent.
    • 💡Finish with a balanced judgement that weighs the organisation’s legitimate need to collect data against the individual’s rights and the risk of harm.
    • 💡For extended answers, use a clear scenario and trace each issue (accountability, safety, bias, liability) through it, naming the parties involved.
    • 💡Define terms precisely: distinguish accountability (who answers for the system) from legal liability (who must compensate or face penalties under the law).
    • 💡When discussing bias, explain the mechanism (training data or design) and the effect (discriminatory outcomes), rather than just stating that bias exists.
    • 💡Read the scenario and identify exactly what is being protected: code, an invention, a brand or permission to use.
    • 💡Match each option to one method and check whether the method's defining feature (automatic, granted, brand identity, permission) fits.
    • 💡Eliminate options that describe a different method from the one the question asks about before choosing.
    Common Mistakes
    • Treating ethical and legal issues as identical: something can be legal yet still ethically questionable, such as aggressive data collection under a broad consent. Correction: address ethical concerns and legal duties as separate but related strands.
    • Assuming consent is permanent once given: consent must be specific to a purpose and can be withdrawn. Correction: state that consent is informed, purpose-limited and withdrawable.
    • Saying the individual legally owns the stored copy of their data: the organisation controls the stored copy, while the individual has rights over it. Correction: distinguish the person the data describes from the organisation holding the copy.
    • Ignoring the consequences of misuse: breaches cause real harm such as identity theft, fraud or discrimination. Correction: link each misuse to a concrete harm and to a legal duty breached.
    • Assuming AI is automatically objective because it is a machine; correction: machine learning can reproduce and amplify bias present in its training data or design choices.
    • Believing the developer is always solely responsible for any harm; correction: accountability may be shared among developer, deploying organisation and operator, and legal liability depends on the circumstances and applicable law.
    • Treating safety as only about physical injury; correction: safety also includes psychological harm and the consequences of biased or incorrect decisions about people.
    • Thinking that because a system is autonomous no one can be liable; correction: liability is decided by examining design, deployment, operation and the law, even if responsibility is difficult to assign.
    • Confusing copyright with patents: copyright protects the expression of a work automatically, whereas a patent protects an inventive technical process and must be applied for and granted.
    • Believing a trademark protects the code itself: a trademark protects brand identity such as a name or logo, not the underlying program.
    • Thinking that buying software transfers ownership of the IP: a licence grants permission to use the software under conditions, while ownership of the IP usually stays with the creator or company.