# Legal

The iSHARE Trust Framework is underpinned by legal agreements to which all participants (both Adhering Parties and Certified Parties) need to adhere. This section contains the relevant legal aspects of the Framework:

| Title                                     | Agreement with version                                                    |
| ----------------------------------------- | ------------------------------------------------------------------------- |
| Terms of Use                              | [Terms-Of-Use](#terms-of-use-1) (05-03-2025)                              |
| Accession Agreement for Adhering Parties  | [Adhering-Parties-Accession-Agreement](#adhering-parties) (05-03-2025)    |
| Accession Agreement for Certified Parties | [Certified-Parties-Accession-Agreement](#certifying-parties) (05-03-2025) |

### Legal Context

This section clarifies which rules and regulations may apply to Framework's participants, and provides information and formats that participants can use to improve their understanding. This section does not aim to be all-encompassing in the sense that it covers all the rules and regulations applicable to the participants, it aims to provide useful information to the Trust Framework's participants. Please note that depending on an organisation's context and specific focus, different rules and regulations might apply, both stemming from national and international law, which might not be mentioned in this section.

### Terms of Use

The Terms of Use are an appendix to and integral part of the Accession Agreement. The Terms of Use further define the rights and obligations of the various roles within the iSHARE Trust Framework. The Terms of Use provide a uniform set of rules for both the participants and the Scheme Owner, thereby fostering a level playing field between all parties involved.

The Terms of Use are drafted in such a way that data can be exchanged by participants even if they have no other contractual arrangement in place. In that case, the default requirements as set forth in the Terms of Use govern their legal relationship. This includes the (license) conditions that apply to the exchange of data. But the Terms of Use leave room for participants to derogate from or further detail the provisions of the Terms of Use on a bilateral basis. However, there will be certain requirements that participants should comply with at any time, and from which they will not be able to deviate. These are the requirements that deal with the proper functioning of the iSHARE Trust Framework, such as each party's responsibility to safeguard the security of its IT-systems (articles 3.5 and 4.1).

#### Furthermore, the Terms of Use include a number of annexes, amongst which the pre-defined conditions of exchange, the iSHARE Trust Framework and the standards and specifications. <a href="#terms-of-use" id="terms-of-use"></a>

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-2efd0536987df9b8eee0129750290b11114ee249%2FTerms%20of%20Use.pdf?alt=media>" %}
Terms of Use
{% endfile %}

### Accession Agreement

#### **Adhering Parties**

The main contract between the participant and the iSHARE Scheme Owner. This main contract refers to the terms of use, including all specifications, to which all participants must abide. After signing this Accession Agreement, an organisation becomes a participant of the data space/iSHARE network as an Adhering Party.

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-f668082d34c6fcfd68bb52e397e965b6d95a400d%2FAccession%20Agreement%20for%20Adhering%20Parties.pdf?alt=media>" %}
Accession Agreement for Adhering Parties
{% endfile %}

#### **Certified Parties**

The main contract between the participant and the iSHARE Scheme Owner. This main contract refers to the terms of use, including all specifications, to which all participants must abide. After signing this Accession Agreement, an organisation becomes a participant of the data space/iSHARE network as a Certified Party.

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-fb7e18c5b25287b9b611c43641cd6c4d3e2b2fa8%2FAccession%20Agreement%20for%20Certified%20Parties.pdf?alt=media>" %}
Accession Agreement for Certified Parties
{% endfile %}

***

### Previous Versions for Agreements

#### Adhering Parties *(*&#x76;ersion 13-02-2023)

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-2dbe5e279a8527578485d3f64404fdfb613c3ebb%2F717750290.pdf?alt=media>" %}

#### Certified Parties *(*&#x76;ersion 13-02-2023)

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-03c14bd7f8610e30f8012965740af81d2ecbff7b%2F2773778436.pdf?alt=media>" %}

#### Adhering Parties (version 18-09-2020)

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-2dbe5e279a8527578485d3f64404fdfb613c3ebb%2F717750290.pdf?alt=media>" %}

#### Certified Parties (version 18-09-2020)

{% file src="<https://3919494753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzzhDvZUvcb2VsHvLXh89%2Fuploads%2Fgit-blob-2dbe5e279a8527578485d3f64404fdfb613c3ebb%2F717750290.pdf?alt=media>" %}


---

# 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://framework.ishare.eu/version-2.2/detailed-descriptions/legal.md?ask=<question>
```

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.