Installation Overview

In order for customer systems to work with ALIAS, both the DPO and System Developers/IT team must provide ALIAS with information about the company, its users, and the types of data they are managing as well as where it is stored. This information may be provided to ALIAS through dedicated User Interfaces used by the DPOs and Developers or via our APIs.

We will note throughout the Configuration Guide whose responsibility it is to handle a particular configuration task, be it the DPO (indicated with the scales ⚖️ emoji) or the Dev group (indicated with the wrench 🔧 emoji)

Once this initial information is provided, developers will be able to add support to their applications via various integration points.

Configuration Requirements

ALIAS itself does not store or have access to a company’s Personal Data. Instead, as a part of setting up an integration, references are defined that correspond to a data subject (Identities) as well as potentially sensitive information about where individual pieces of Personal Data that pertain to that data subject are stored (Selectors).

Therefore it will be necessary for your organization to store information provided by ALIAS locally in a database or similar repository so you can match ALIAS identifiers to your instances of Personal Data and the various aspects of locations where that data is stored (mediums, addresses and determinants).

The details of these location tables are described in the section ALIAS Local Framework Set Up