> 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/who-owns-our-second-lives-virtual-clones-and-the-right-to-your-identity.md). # Who Owns Our Second Lives: Virtual Clones and the Right to Your Identity This paper discusses different aspects and issues that arise when this identity corresponds to and overlaps with the identity of actual humans. ## Overview **Authors:** Thommy Eriksson **Publication Date:** 1 November 2021 **Link:** **Keywords:** Identity in VR, digital identity, ethics in XR, AR, digital rights, bodyright, user consent, digital avatars, immersive technology and ethics, data sovereignty **Type:** Peer-Reviewed Journals/White Papers ## Summary This paper discusses different aspects and issues that arise when this identity corresponds to and overlaps with the identity of actual humans. These actual humans can be alive, or they can be deceased, and both represent challenging ethical issues. The arguments will mostly concern identities in VR since that is where researchers and developers have the most experience and empirical data. However, most of the argument should be applicable to augmented reality applications as well. The paper suggests a few means of handling the ethical concerns, most importantly a “bodyright”. If this is implemented it can work in a similar way to copyright, but controlling how others can use a user’s identity, both mental and physical. --- # 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/who-owns-our-second-lives-virtual-clones-and-the-right-to-your-identity.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.