Do I need to sign all of the modules?

Data Republic’s Legal Framework is comprised of the Data Republic Senate License and five modules. The Senate License is mandatory because it is a license to access and use our core Software as a Service (SaaS) platform, Senate. The Senate License sets out Data Republic’s standard terms; the rights and obligations of users (use case, time frame, users, confidential info) when using Senate. 

With the Senate License agreement in place, participants can then leverage the additional modules depending on the nature of the projects they wish to conduct on Senate. 

The additional modules fall into three categories:

1. The Common Legal Framework Modules for data exchange and analysis under a common legal framework managed by Data Republic:

  • Data Contributor Module
  • Data Developer Module
  •  Data Recipient Module

2. The Third Party Exchange Module which permits customers to apply their own legal frameworks to data exchange and analysis projects with third parties.
3. The Senate Matching Services Module for tokenization and matching services

For more information on how the separate modules function, see this help article.

Why aren’t all the data exchange terms (Common Legal Framework) I one big module instead of being split up?

There is a split between the modules to show the differences between the obligations of different types of users (i.e. The users making the data product would sign a different module to the participant who is contributing data to a project).Depending on your role in a particular project, some of the modules would not apply to you.

Can I use my legal agreement to define the terms of a project with another organization on Senate? 

 Yes, participants are able to use their existing legal arrangements for third party data sharing and exchange, by selecting the Third Party Exchange Module. 

The Third Party Exchange Module sets out that the multi-party exchange functionality will be made available to the Participant to conduct exchanges with third parties who may or may not be a licensed Data Republic Participant. These exchanges will be carried out on the Senate Platform, but will be governed according to the Participant’s own legal arrangement.

What is the purpose of End User License Agreements (EULAs)?

The EULA enables derived data products created via projects on Senate (for example aggregations, tools, maps, reports or scores) under the Common Legal Framework to be licensed to a non-participant. 

The EULA sets out the rights and obligations of the Data Custodian, data product developer and end-user when licensing or selling an approved data product.
 

Do we need to agree to the Senate Matching Module every time we conduct a matching project? 

No. The terms of the Senate Matching Module will apply to any tokenization and matching activities that you undertake using the Data Republic Senate Matching Services.

How much responsibility do I take if I bring on someone with a Guest Licence to Senate?

Guest Licenses enable participants to collaborate with trusted partners without those trusted partners being required to obtain a full Senate License from Data Republic. This can significantly help to accelerate outcomes from your Senate License.

We provide tools to help participants to determine the privileges granted to Guests, and therefore what they are permitted to do on the platform, however, Data Republic ultimately holds participants responsible for their guest’s activity within their ‘invited projects’.

As such, we recommend only provisioning Guest Licenses to organizations you know and trust.

When should we have a non-disclosure agreement with Data Republic?

We have a standard form Mutual Non-Disclosure Agreement (link here) which we can enter into with you if you would like to have detailed discussions before signing up to the Senate License agreement.

However, if you have a Senate License agreement with us, then there is no need, as comprehensive confidentiality provisions have already been agreed to.

Does Data Republic own my intellectual property (IP)?

No. Data Republic will never own your IP. 

Under the Common Legal Framework (the optional common legal framework for data exchange and analysis governed by Data Republic) we do have specific terms that can appear a bit like we do, but these terms apply in a very limited context and only to avoid complexity in multi-party data exchanges. 

Under the Common Legal Framework, the general approach is that all parties retain the intellectual property in whatever it is they bring to the platform (that could be in data sets, algorithms or other ways of combining and analyzing data).

When a data product is created, there is a compilation of multiple distinct forms of IP which have distinct ownership (data IP, developer IP etc.). 

In order to avoid a convoluted shared IP ownership situation, the default position in the Common Legal Framework is that each party will retain ownership in the distinct forms of IP from which the data product is comprised, and that Data Republic will own the IP in the data product as a compilation. Data Republic then licenses the data product to the data recipient. 

Data Republic’s ownership of the IP in the data product is limited to the extent that the owners of the background IP have licensed the IP comprised in the data product. In practical terms, this means that Data Republic can only use the data product as agreed to by the parties who own the underlying IP. 

If required, this default position can be amended in the Data License with the agreement of each of the relevant parties to the exchange.

Why can’t I have an explorer access to Senate?

Data Republic is concerned to meet the risk management and confidentiality requirements of its participants.We are considering whether a short-form agreement may be possible, along with functional privilege restrictions for an explorer role o the platform might be possible. In the interim our team are keen to assist you with demonstrations of the Senate system.

Did this answer your question?