> For the complete documentation index, see [llms.txt](https://guides.gresb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.gresb.com/sfdr-reporting-solution/getting-started/data-sharing-and-confidentiality.md).
# Data Sharing & Confidentiality
### Access to Submitted Data
Who can see my assessment response?
Data is submitted to GRESB through a secure online platform. It can only be seen by current GRESB staff and, to a more limited extent, authorized personnel from GRESB’s third-party validation provider, Sustainability Assurance Services (SAS).
### Access to Assessment Results
Who can see my assessment results?
Data collected through the SFDR Infrastructure Assessments is only disclosed to the participants themselves.
Participants can share data with their investors themselves outside of the GRESB portal by downloading their report as a PDF.
### Data Protection & Security
GDPR Compliance
GRESB is fully compliant with GDPR. The GRESB Privacy Statement can be found [here](https://www.gresb.com/nl-en/gresb-privacy-statement/). We also have specific internal policies, such as our Data Breach Policy and our Data Protection Policy, related to GDPR that we cannot share externally for security reasons. Please note that asset-level data does not fall under the incidence of GDPR because it does not contain any personal data.
Cybersecurity
GRESB’s data security measures and systems have been reviewed by an external expert and no issues were flagged. The GRESB website and the GRESB Portal are fully HTTPS/TLS encrypted. GRESB has strict and extensive policies on data security that cannot be shared externally for security reasons.
---
# 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://guides.gresb.com/sfdr-reporting-solution/getting-started/data-sharing-and-confidentiality.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.