> 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/ethical-responsibility/extended-reality-xr-and-the-erosion-of-anonymity-and-privacy.md). # Extended Reality (XR) and the Erosion of Anonymity and Privacy This paper highlights some of the key capabilities that XR adoption will unlock – around augmented intelligence, personal and distributed surveillance, and augmented perception – and considers the pri ## Overview **Authors:** Dr. Mark McGill **Publication Date:** 1 November 2021 **Link:** **Keywords:** XR, augmented intelligence, augmented perception, privacy implications, user privacy, ethics in XR, consent in XR, informed consent, security and surveillance **Type:** Peer-Reviewed Journals/White Papers ## Summary This paper highlights some of the key capabilities that XR adoption will unlock – around augmented intelligence, personal and distributed surveillance, and augmented perception – and considers the privacy implications XR has for users, bystanders, and society more broadly. The paper then reflects on the growing need to understand, anticipate, and protect against the capacity for XR to both consensually and non-consensually infringe upon the user and bystander privacy. --- # 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/ethical-responsibility/extended-reality-xr-and-the-erosion-of-anonymity-and-privacy.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.