> For the complete documentation index, see [llms.txt](https://template.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://template.ishare.eu/business-and-organisational-building-blocks/legal-building-blocks/regulatory-compliance.md).

# Regulatory Compliance

Legal certainty is essential for building trust in any data space. According to the DSSC Blueprint 3.0, the Regulatory Compliance building block helps identify which legal frameworks, obligations, and regulatory triggers are relevant to the design, operation, and participation within a data space. It also helps clarify legal entitlements to data and provides practical guidance on how to apply legal frameworks, assign responsibilities, and remain compliant over time.

Each data space should establish clear procedures for:

<figure><img src="/files/3EXz5GaEUoowwKy1xrdY" alt=""><figcaption><p>Figure 14. Data Space Compliance Procedures.</p></figcaption></figure>

This should be assessed against a broader set of relevant EU, sectoral, and national legal frameworks, depending on the context of the data space. For example, see the relevant DSSC section on [Types of data](https://blueprint.dssc.eu/?pane=business\&business=types-of-data-data-as-a-trigger) that may trigger differernt legar requirements, and [domain-specific use cases](https://blueprint.dssc.eu/?pane=business\&business=examples-of-domain-specific-use-cases) that may introduce additional obligaitons.

{% hint style="info" %}
The complete DSSC description is available [here](https://blueprint.dssc.eu/?pane=business\&business=regulatory-compliance).
{% endhint %}

While compliance starts with awareness, it must be embedded into both governance and technology. The iSHARE Framework supports these activities through predefined legal provisions and trust-based mechanisms that help participants meet requirements such as GDPR, eIDAS, and sector-specific rules, without duplicating compliance work across the ecosystem. See more details here on the [Legal Context](https://framework.ishare.eu/detailed-descriptions/legal/legal-context).  In line with DSSC 3.0, compliance can also be supported through [LegalTech and RegTech](https://blueprint.dssc.eu/?pane=business\&business=regulatory-compliance#RegulatoryCompliance-3.4LegalTechandRegTechinthecontextofdataspaces) approaches, helping to enable auditability, policy enforcement, automation, and compliance by design.

{% hint style="info" %}
LegalTech refers to technology that supports legal processes, such as contract automation, licensing enforcement, and compliance monitoring, while RegTech refers to technology that supports regulatory compliance, for example, through identity verification, transaction monitoring, auditability, reporting, and policy management.
{% endhint %}

Data spaces may still need to customise legal interpretation for their domain and assess additional sector-specific or national requirements where relevant.

{% hint style="info" %}
Regulatory Compliance connects closely with other building blocks:

* **Intermediaries & Operators:** Some may be subject to the DGA, especially Chapter III rules.
* **Organisation Form & Governance Authority:** Business model and legal form must comply with national and EU laws.
* **Participation Management:** Onboarding and offboarding must follow data protection policies.
* **Contractual Framework:** Contracts need to cover legal requirements like data protection, IP, cybersecurity, and interoperability.
* **Provenance & Traceability:** Supports compliance with GDPR and access control requirements.
* **Identity & Attestation Management:** Participant verification must follow GDPR and eIDAS 2.0 rules.
* **Use Case Development:** Different use cases may be subject to sectoral or national regulations.
  {% endhint %}

{% hint style="warning" %}
The guiding questions can help in the co-creation process and in defining this building block, so please see the next section.&#x20;
{% endhint %}


---

# 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://template.ishare.eu/business-and-organisational-building-blocks/legal-building-blocks/regulatory-compliance.md?ask=<question>&goal=<endgoal>
```

`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.