> For the complete documentation index, see [llms.txt](https://docs.meeco.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meeco.me/concepts/secure-data-storage.md). # Secure Data Storage Both users and enterprises store a significant amount of data online, including personally identifiable information (PII), sensitive corporate data and customer information. More often than not, this data is not appropriately protected. A secure data storage solution is designed to protect the data from unauthorised access or use, while ensuring that data is available when needed. Here are some features that a secure data storage should have: * **Encryption**: Data is encrypted both in transit and at rest to ensure that even if it is intercepted or stolen, it cannot be read or used by unauthorised parties. * **Access Control**: Access to data is restricted to authorised parties. * **Logging and Auditing**: The storage solution maintains a log of all events related to the data, and provides audit logs to authorised users. * **Compliance with Standards and Regulation**: The storage solution complies with relevant data protection regulations, such as the General Data Protection Regulation (GDPR). It also follows best practices for security and data protection, such as those outlines by the National Institute of Standards and Technology (NIST). * **Data Integrity**: When exchanging data with other parties, it is essential to conserve integrity to ensure that the data remains accurate and unchanged throughout the transmission process. ## Meeco’s Secure Storage Solution Meeco has developed the Vault as part of our Secure Value Exchange (SVX) platform, a flexible secure data storage option that provides end-to-end encryption on all data types. It also includes encrypted peer-to peer-sharing with granular control over Shares. Via the use of the Vault APIs, our secure data technology can be embedded in new and existing applications such as digital wallets, mobile apps, web portals or back-up services. By default, users and organisations are authenticated via an OIDC provider. For details, see our [Vault](/other-products/vault.md) information page. --- # 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://docs.meeco.me/concepts/secure-data-storage.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.