This glossary defines common terms that you might see as you're working in Projects on Data Republic, or throughout our Help Centre.
Have you come across a term that we haven't defined and you want to know what it means? Send us a note using the chat bubble on the bottom right of your screen or by emailing support@datarepublic.com.
Term | Definition |
Common Legal Framework / "CLF" | The Data Republic Common Legal Framework (CLF) is a balanced and functional framework for multi-party data sharing. |
Contributor Node | Containerised software package used as part of Privacy-Preserving Matching to deidentify PII within your own IT environment. |
Data Asset | Each discrete category or collection of data submitted into the Data Republic Databases by a User, and includes any data updates, data incorporated into Data Products, and any corrections to or re-ordering, cleansing or transformation of such data. |
Data Contributor | Organisation or individual who is contributing data to the Platform |
Data License | Data Licenses are project specific terms that determine who has access, to what data, for how long and for what purpose. |
Data Product | Means any combinations, compilations, integrations, models or analyses of data created or derived on the Data Republic Platform from, or using, Participant Data and/or other data contained in the Data Republic Databases in accordance with the Data Product Policy and each applicable Term Sheet or Approved Data Licence. Data Products include, but are not limited to: |
Data Product Development Environment | The environment to which Data Developer will be granted access in order to create a Data Product. |
Data Republic Licensee / “Participant” | Customer who executed Data Republic Software Agreement |
Data Republic Platform | The system and application stack upon and within which the Data Republic Databases and Projects are hosted and the Data Republic environment which is made available to Participants to contribute, receive and develop Data Assets and/or Data Products according to the legal framework set out in the Data Republic Common Legal Framework and/or in accordance with a Non-CLF Collaboration. |
Privacy-Preserving Matching Network | A patented proprietary distributed network developed by Data Republic for secure, privacy preserving, data matching - whose technology components (Contributor Node, Matching Node, Aggregator Node) are to be licensed and configured under Participant’s Annual Enterprise Agreement. |
End User License Agreement / "EULA" | EULA can be used to protect the interests of data owners, to the extent that their intellectual property still exists within a data product sold to a non-Data Republic Participant |
Guest | Organisation who has signed the Guest Participation Agreement. May include a Data Contributor, other Data Republic Licensee, or third party to Licensee organisation |
Matcher Node | Matcher Node is a component of the Data Republic Matching network that stores hashed splices of PII during the tokenization process. This means that no one Matcher Node can contain an entire hashed field value for PII |
Personally Identifiable Information/ "PII"/"Personal Data" | Any information relating to an identified or identifiable natural person. Such information may include but is not limited to an individual’s name, identification number, biometric data and certain online identifiers |
Privacy-Preserving Matching | Privacy-Preserving Matching is Data Republic’s patented feature for matching datasets without exposing personally identifiable information (PII). |
Project | A Sandbox Project, Data Project, or simply ‘Project’ is a designated area wherein one or many organisations can collaborate on data. A Project can consist of many data contributor organisations and many data consumer organisations. |
Sandbox | A Sandbox is a restricted environment for the sharing of data between Participant and its Guests. A Sandbox environment can consist of one or more Workspaces (Sandbox VMs), a Sandbox database, and other services such as the shared Project Drive. Only Participant approved data is allowed into the Sandbox, and Participant approval is required for any files to be extracted from the Sandbox. Approvals are managed according to the terms of the Project Data License. |
User | A User or Active User is a user account that has Data Republic Platform credentials and is assigned to a Project under the People tab. (the user had to sign in at least once into the Data Republic Platform). |