> For the complete documentation index, see [llms.txt](https://frameworks.greendealdata.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frameworks.greendealdata.eu/governnace-frameworks/gdds-rulebook/conformity-framework-and-governance-enforcement/3.-suspension-revocation-and-voluntary-withdrawal.md).

# 3. Suspension, Revocation & Voluntary Withdrawal

This part corresponds to Stage 5 of the participation lifecycle: it defines how participation ends, whether involuntarily, as the outcome of enforcement, or voluntarily, at the participant's own initiative. In all cases, the objective is a controlled exit that protects the trust and continuity of the data space. 

## 3.1 Involuntary measures 

* Suspension is the temporary deactivation of a participant’s credentials while a non-compliance is being rectified. The Participant Registry status is updated accordingly and restored once the issue is resolved. 
* Revocation / exclusion is permanent. The participation agreement is terminated (its status set to obsolete in the Participant Registry), credentials are permanently deactivated, and a network-wide notice is issued for information purposes. 
* Re-admission bar — an excluded party may not re-apply for admission for a defined period. 

{% hint style="warning" %}
*Note: (partially resolved, Session 10): A potential 12-month re-admission bar following exclusion was discussed (consistent with the iSHARE default) but not formally confirmed. The group affirmed that the purpose of involuntary measures is to preserve ecosystem trust and prevent further damage, not to punish participants. To confirm: (a) the re-admission bar period; and (b) the decision-and-execution split — proposed that the compliance authority decides and the GDDS Operator executes the registry and credential changes, pending confirmation of the compliance authority’s identity.* 
{% endhint %}

On suspension or revocation, the handling of the participant’s published datasets, active data-sharing relationships, and any data already shared under a usage policy is governed by the [Data Sovereignty & Technical Governance](/governnace-frameworks/gdds-rulebook/data-sovereignty-and-technical-governance.md) section and the applicable agreements. Counterparties are notified so that dependent transactions can be wound down in an orderly way. 

{% hint style="warning" %}
*Note (open, action assigned Session 10): The legal and technical feasibility of asset handling during suspension or exclusion is to be analysed (action: WP4). In particular, under the Data Act a copy of the exchanged data may need to be left with the data consumer upon termination of a commercial relationship; this specific obligation is to be verified (action: WP4) and reflected here and in the Legal Framework.* 
{% endhint %}

***

## 3.2 Voluntary withdrawal and downgrade 

A participant may choose to leave the data space, or a Certified Participant may step down to Adhering status (a downgrade) rather than leaving entirely. The process is designed to minimise disruption to other participants. 

Notice periods: one month for Adhering Participants; six months for Certified Participants (based on the iSHARE Trust Framework). 

Procedure: 

1. The withdrawing party formally notifies the governance body of its intention to withdraw (or downgrade) and submits a withdrawal plan. 
2. The governance body acknowledges the intention within 5 working days and confirms the effective date. 
3. The withdrawing party notifies the counterparties it has interacted with and winds down its participation in cooperation with the governance body. 
4. The Participant Registry records the completed withdrawal and updates the status list entry for each affected credential. 

{% hint style="warning" %}
*Note: To confirm the owner and required contents of the withdrawal-plan template, and which obligations survive exit (for example, in respect of data already shared under a usage policy).* 
{% endhint %}