> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/privacy-and-policy/voices-of-vr-1091-ieee-xr-ethics-the-erosion-of-privacy-and-anonymity/privacy-and-ethical-considerations-for-extended-reality-settings-on-tech-ethics.md). # Privacy and Ethical Considerations for Extended Reality Settings - On Tech Ethics Discusses privacy and other ethical considerations for extended reality settings. ## Overview **Authors:** CITI Program **Publication Date:** 1 December 2024 **Link:** **Keywords:** VRISE, accessability, XR, VR, AR, privacy concerns, data collection, marketing in VR, algorythmic bias **Type:** Video ## Summary Discusses privacy and other ethical considerations for extended reality settings. Our guest is Mihaela Popescu who is a Professor of Digital Media in the Department of Communication Studies at California State University, San Bernardino (CSUSB) and the Faculty Director of CSUSB's Extended Reality for Learning Lab (xREAL). She holds a Ph.D. in Communication from the University of Pennsylvania. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://library.xrguild.org/privacy-and-policy/voices-of-vr-1091-ieee-xr-ethics-the-erosion-of-privacy-and-anonymity/privacy-and-ethical-considerations-for-extended-reality-settings-on-tech-ethics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.