Data Space Governance Framework

Sheetgo Data Space

Effective date: Feb 10, 2026
Last update: Feb 10, 2026

1. Purpose and vision

The Sheetgo Data Space is a data space designed to enable organisations from different sectors to share and use data in a secure, controlled, and interoperable manner, generating economic and operational value through collaboration.

The Data Space has a cross-sectoral vocation, open to companies of different sizes and fields of activity, and is aligned with the European Data Strategy and with best practices promoted by the Data Spaces Support Centre (DSSC) and the Data Spaces Association.

Its objective is to offer a platform that is:

  • trustworthy and transparent,
  • technologically open,
  • easy to adopt,
  • and prepared to scale across multiple sectors and use cases.

2. Fundamental principles

2.1 Data sovereignty

Each participant retains ownership and control of its data at all times.

2.2 Trust and responsibility

Trust is based on clear rules, defined roles, and responsibilities assumed by all participants.

2.3 Technological neutrality

The Data Space is agnostic with respect to technologies and providers, avoiding any form of dependency or exclusivity.

2.4 Interoperability

Interoperability is promoted through European standards and reference frameworks.

2.5 Scalability and sustainability

The governance model is designed to grow in a progressive and orderly manner.

3. Roles within the Data Space

3.1 Data Space Operator

Sheetgo acts as the Data Space Operator and is responsible for:

(i) the technical operation of the platform;
(ii) execution of onboarding processes;
(iii) implementation of technical and security controls;
(iv) maintenance of the data and services catalogue;
(v) execution of the decisions adopted by the Data Space Governance Body.

The Operator does not acquire ownership rights over the shared data nor does it unilaterally determine the governance rules of the Data Space.

3.2 Data Space Governance Body

The Data Space has a Governance Body, named the Data Space Governance Committee, responsible for ensuring the proper application, evolution, and compliance of the common governance framework of the Data Space.

3.2.1 Functions

The Committee is responsible, among other functions, for:

  • approving and amending the Governance Framework and the Rulebook;
  • defining the general criteria for participant admission;
  • resolving structural or recurrent conflicts;
  • deciding on the suspension or exclusion of participants in the applicable cases;
  • approving the incorporation of sector-specific rules through annexes;
  • supervising alignment of the Data Space with European reference frameworks (including GAIA-X).

3.2.2 Composition

The Committee shall initially be composed of five (5) members:

  • two representatives of the Data Space Operator,
  • two independent members,
  • one representative of the participant community of the Data Space.

3.2.3 Functional independence

The Committee acts with functional independence from the Operator, adopting its decisions in accordance with objective, transparent, and documented criteria.

3.2.4 Governance evolution

The governance structure may evolve as the Data Space grows, including changes to its composition or transformation into an independent governance entity, without prejudice to the continuity of the common governance framework.

3.3 Participants

Participants may act as data providers, data consumers, or both, depending on their role.

3.4 Technical service providers

Technical services may be provided by the Operator, by third parties, or by providers freely chosen by the participants.

4. Functional separation and neutrality

The Data Space clearly distinguishes between:

  • governance, and
  • the provision of technical services.

Governance decisions are adopted independently of any commercial or technical relationship.

5. Operator’s technological and operational capabilities

The design and operation of the Data Space are supported by the Operator’s technological experience in:

  • data flow automation,
  • integration of heterogeneous data sources,
  • process traceability and control,
  • operation in scalable cloud environments,
  • application of security and compliance best practices.

These capabilities inform the design of the Data Space without imposing specific technologies on participants.

6. Cross-sectoral Data Space and sectoral domains

The Sheetgo Data Space operates as a single, cross-sectoral Data Space with a single governance framework and a common set of rules applicable to all participants.

On this common basis, the Data Space may enable sectoral domains or usage communities oriented towards specific sectors, concrete use cases, or homogeneous data types.

These sectoral domains:

  • do not constitute independent data spaces;
  • do not have a separate legal personality;
  • do not require separate adhesion agreements;
  • fully inherit the Governance Framework and Rulebook of the Data Space.

Where necessary, a sectoral domain may incorporate additional specific rules through sectoral annexes, which must always be subordinated to and consistent with the general Rulebook.

This approach enables:

  • coherent governance,
  • sector-specific specialisation,
  • scaling of the Data Space without fragmentation.

Sectoral domains or usage communities are consultative in nature and do not constitute governance bodies. Any additional sectoral rule must be approved by the Data Space Governance Body and incorporated through the corresponding Sectoral Annex.

7. Onboarding and participation

Participation is formalised through an Adhesion Agreement, which confirms acceptance of this Governance Framework and the Data Space’s rules.

8. Trust and compliance framework

The Data Space operates within a shared trust framework that includes identity validation, basic traceability mechanisms, and clear expectations regarding regulatory compliance.

9. Evolution of the Data Space

The governance model may evolve to adapt to the growth of the Data Space, while always preserving the principles defined in this document.