# Our Manifesto Personal biometric data is currently collected and stored by individual wearable manufacturers. As a consequence, data is only analysed with algorithms developed in house, and data from different devices do not have the ability to be integrated during analysis. This stifles innovation and limits user insights. Personal biometric data is often sold to third parties and affiliates, with no way for users to provide detailed permissions on such commercialisation, or be rewarded for this. Personal data is at risk of being exposed through data breaches due to centralised storage. LYNX is building the ability to combine data from multiple wearables (including traditional trackers; biosensors; and neurotech) to give users advanced insights into individual health, wellbeing and performance. Data privacy and ownership of data will be enabled through the use of decentralised technologies. Our team of engineers, scientists, and ethicists are building a future where all human wearable data will be owned and governed by individual users; and unbound from centralised silos. **Our North Star** 1. Users can gain cutting-edge mind-body insights through the holistic analysis of data from multiple devices. 2. Users can choose from a personalised marketplace of third parties to interact with (including specialist AI providers) for amplified insights, participation in scientific research, and tokenised rewards. 3. No third party will ever see or own your identifiable biometric wearable data again. Create and own your digital clone with LYNX. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.lynx.phas3.io/our-manifesto.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.