> For the complete documentation index, see [llms.txt](https://docs.humandataincome.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humandataincome.com/datamask/application/data-requests.md). # Data requests ### **Types of Data Requests**

* **Data Read Request:** This occurs when a website or service wants to read information from your Data Wallet. Datamask allows you to see exactly what data is being requested before you decide to approve or decline the request. * **Data Write Request:** This happens when a website or service wants to write or store information in your Data Wallet. Similar to read requests, you can review the details before deciding to accept or decline. ### **Access Authorizations**

Datamask keeps a detailed record of all access authorizations you have granted. You can easily review, manage, and revoke access as needed. Each authorization is time-bound and fully transparent, ensuring that your data is shared only with those you trust, and only for as long as you allow. ### **Data Transaction History**

Transparency is key in managing your data. Datamask provides a comprehensive transaction history, allowing you to review all data interactions, including what was shared, with whom, and when. This feature ensures that you have complete visibility over your data's journey, maintaining full control at all times. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.humandataincome.com/datamask/application/data-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.