Skip to main content

Data Sharing & Governance

AquaCloud is all about creating value by applying industry data. By sharing industry data, AquaCloud can save months of work trying to access and compile data for projects and trials, increasing the time for developing findings and new solutions.

As a non-profit organisation, our mission is to support the aquaculture industry by providing high-quality data and insights. While we are committed to open collaboration, we reserve the right to charge for datasets to ensure the sustainability of our operations, maintain data quality, and continue delivering valuable services to the industry.

AquaCloud Governance - The Rules of Engagement

All applications for data are vetted by a steering committee of fish farmers.  They work
with us in AquaCloud to ensure that data is used to create value through insights
and new services and that the value applies to the industry.  Last, the steering committee
is an extra security to ensure all data sharing follows the well-defined data sharing governance. 
 

The Do's and Dont's

At AquaCloud, our operations are guided by a governance framework that outlines how we collaborate with our partners—the fish farmers along the Norwegian coast who contribute their data to our database. This framework not only governs our business-to-business interactions but also dictates how we share data with our users.

The partner agreement establishes the terms of our cooperation, detailing our obligations, data ownership, and the licenses we hold to explore commercial uses of the data. As a non-profit entity, AquaCloud directs any commercial revenue back into maintaining the organisation and enhancing our services to our partners.

Our governance framework also specifies the parameters for data sharing. We are committed to complying with Norwegian and international laws regarding insider information and market manipulation, as well as adhering to GDPR regulations. These laws and regulations are our firm boundaries.

Stake i skvalpesjø_BH-juster (1)
Compliance iStock-1245954506-justert (1)

Now, let’s explore how we can share data and the criteria we use to evaluate its sensitivity.

When assessing data sensitivity, we consider factors such as the identification of individual companies, the granularity of the data, and its recency. The more identifiable the company is, the more restricted the access becomes; this restriction increases with greater granularity and the recency of the data.

We apply three levels of sensitivity: Private, Restricted, and Open. In all cases, our team is here to assist you in formulating your data requests and understanding the limitations of our datasets. We prioritize quality assurance by ensuring that all data requests are reviewed by our steering group, which consists of representatives from the fish farming community. They evaluate each request to ensure that it aligns with our governance guidelines for data sharing.

Three Levels of Sensitivity

It's important to note that all access categories are subject
to commercial terms, and specific user terms apply.
wave_blue

Private

In the first level of access, Private, only the data owner, the fish farmer, can approve both the recipient and the specific dataset being shared.

Permitted recipients:
Data owner
Legal entities approved by the Data owner

Terms: 
AquaCloud Cooperation Agreement or License Agreement/Commercial Terms.
Dataset-specific terms as applicable

 

wave_blue

Restricted

In the second level, Restricted, only the data owner, the fish farmer, can approve the recipient and the specific dataset being shared. AquaCloud can approve the recipient.

Permitted recipients:
AquaCloud Partners
Legal entities approved by AquaCloud

Terms: 
AquaCloud Cooperation Agreement
or License Agreement
Dataset-specific terms as applicable

 

wave_blue

Open

In the third category, Open, we typically release data upon request.

Permitted recipients:
Any legal entry

Terms:
AquaCloud License Agreement only

How We Work

We work closely with our partners to facilitate these processes.
 
Now, let's clarify these access categories further with examples to illustrate how
sensitivity, data recency and aggregation affect data sharing.
How we work example 2

Example 1: Current Inventory Data

Imagine you request data showing the current inventory—specifically, biomass, numbers, and average weight—at the cage level. This represents the finest granularity, meaning the data is highly detailed and the farmer is easily identifiable.

  • Initially, this request would be classified as Private, indicating highly restricted access. The application process for this data would follow our strictest protocols.

Now, consider the same request, but for data that is more than 12 months old.

  • In this scenario, the sensitivity level shifts from Private to Restricted. While AquaCloud can approve the recipient, the final decision regarding whether the data will be shared still rests with the data owners regarding whether the data will be shared.

Now, consider the initial request, but for data that is aggregated up to PO level

  • In this scenario, the initial sensitivity level is Restricted and shifts to Open after 12 months. While AquaCloud can approve the recipient, the final decision remains with the data owners regarding whether the data will be shared.
  • The level of aggregation and the age of the data will contribute strongly towards release.
How we work example 1

Example 2: Lice Count Data

Now let’s look at a request for lice counts per cage.

  • This request would initially be categorised as Restricted, meaning access is limited. The data owners have the final say on whether the information can be shared. AquaCloud will vet the recipient in this case.

If you were to make the same request but for data that is more than 30 days old, the sensitivity level would change.

  • Here, the classification would shift from Restricted to Open. Again, while AquaCloud can vet the recipient, the data owners retain the authority to decide if the data will be made available.

Now, consider the initial request, but for data that is aggregated up to PO level

  • Here, the classification is Open, and data recency doesn't count. Again, while AquaCloud can vet the recipient, the data owners retain the authority to decide if the data will be made available.

These examples illustrate how the granularity and currency of data influence its sensitivity and the corresponding access levels in our governance framework.

When we share data, we focus on using industrial data to generate valuable insights for fish farmers. We ensure that every step is conducted in accordance with established guidelines and best practices. This commitment to transparency and integrity helps us maximise the benefits for our partners while adhering to legal and ethical standards.

 

Bjørgolfur Havardson

Björgolfur Havardsson

Senior Business Developer

Contact Us

Get in touch to discuss data!