MODULE 1 Flashcards
Foundational Principles of Privacy in Technology
Nissenbaum’s Contextual Integrity
Ties adequate protection for privacy to norms of specific contetexts, demanding that information gathering and dissemination be appropriate to that context and obey the governing norms of distribution within it. This viewpoint presents a challenge to IT professionals: how to identify relevant norms and preserve norms when they introduce new or changing technology? Helen Nissenbaum’s framework of contextual integrity ties privacy expectations to context-dependent norms of information flow. Information collection, processing and transmission practices that are in accordance with those norms are likely to be perceived as acceptable, whereas practices that do not follow those norms are perceived as privacy violations because they violate contextual integrity.
Solove’s Taxanomy
A work by Daniel Solve and attempts to order the different harms that may arise from infringements in privacy. The taxonomy is split into four categories: 1) Information Collection, 2) Information Processing, 3) Dissemination of Information, and 4) Invasion.
Calo’s Harms Dimensions
Objective harms are measurable and observable, wherein a person’s privacy has been violated and a direct harm is known to exist. Subjective harms exist without an observable or measurable harm, but where an expectation of harm exists.
Westin’s Four States of Privacy
The states include:
Solitude: The individual stands by themselves, separate from the group and remains free from the observations of others.
Intimacy: The individual is part of a small unit; information sharing and the rules of secrecy are negotiated with members of the unit.
anonymity: While the individual is in public, they still maintain freedom from identification and surveillance.
reserve: While the individual is in a large group, they maintain the ability to withold communication or disengage from others to create a psychological barrier agains t unwanted intrusion.
Fair Information Practice Principles (FIPPs)
Published in 1977 by the U.S. Federal Trade Commission (FTC) and provides guidance to businesses in the United States. FIPPs is a collection of widely accepted principles that agencies use when evaluating information systems, processes, programs, and activities that affect individual privacy. FIPPs are not a requirements; rather, they are principles that should be applied by each agency according to the agency’s particular mission and privacy program requirements.
Collection Limitation Principle
FIPPS Principle: There should be limits to the collection of personal data and any such data should be obtained by lawful and fair means and where appropriate, with the knowledge or consent of the data subject.
Data Quality Principle
FIPPS Principle: Personal data should be relevant to the purposes for which they are to be used, and, to the extent necessary for those purposes, should be accurate, complete and kept up-to-date.
Pupose Specification Principle
FIPPS Principle: The purposes for which personal data are collected should be specified not later than at the time of data collection and the subsequent use should be limited to the fulfillment of those purposes or such others as are not incompatible with those purposes and as are specified on each occasion of change of purpose.
Use Limitation Principle
FIPPS Principle: Personal data should not be disclosed, made available or otherwise used for purposes other than those specified, except: (a) with the consent of the data subject; or (b) by the authority of law.
Security Safegaurd Principle
FIPPS Principle: Personal data should be protected by reasonable security safeguards against such risks as loss or unauthorized access, destruction, use, modification or disclosure of data
Openness Principles—There should be a general policy of openness about developments, practices and policies with respect to personal data. Means should be readily available of establishing the existence and nature of personal data, and the main purposes of their use, as well as the identity and usual residence of the data controller.
Individual Participation Principle
FIPPS Principle: Focuses on giving people control over their personal information. In simple terms, it means that individuals should have the right to know what information is being collected about them, access that data, and correct it if it’s wrong.
Example:
Let’s say a company collects your personal information to create an account for their services. According to this principle, you should be able to:
See what data they have – You can ask the company what information they’ve collected about you.
Update or correct it – If your name or contact information is wrong, you should be able to request corrections.
Challenge or delete the data – If the information is incorrect or you no longer want the company to hold it, you should be able to request that they remove or update it.
This principle ensures transparency and empowers individuals to have some control over their personal data.
Accountability Principle
FIPPS Principle: Means that organizations are responsible for protecting your personal information and must take steps to ensure it is handled properly. If something goes wrong—like a data breach or misuse of your data—they are held accountable for fixing the problem and must follow through with consequences or corrective actions.
Active Collection
Data Collected directly from the subject
Passive Collection
Collection occurs without requiring any action from the participant.
First Party Collection
Providing personal information directly to data collector
Repurposing
Previously collected data used for a different purpose
Surveillance
Collect data through observed behaviors like online searchesor websites
Third Party
When companies or organizations that you don’t directly interact with gather information about you. These third parties often collect data from other websites, apps, or services you’re using, without you directly giving it to them.
Explicit Consent
Requires the user to take an action, such as selecting an option to allow the collection of information that the application provider want to use to impove services and functionality.