Sign in

Integrating with Ü


These are the URLs to our two main applications:

Authentication & Permission dialogues

Environment URL

Developer Self Service

Environment URL

Setting up your client and project structure

The first step to get started with your integration is to get access to our Developer Self Service application. During the implementation phase of your application you should use our sandbox environment. Once your implementation is complete and tested you must configure your project for using our production environment

You will need to onboard yourself as a user of our Developer Self Service:

Environment URL

Self-service is a very powerful tool that could potentially make the logins for all your company clients stop working so always be very selective in whom and how many people should gain access to the self-service system for your application. The Developer Self Service application uses Ü itself for authenticating your project’s administrators.

Once you have gained access to the Developer Self Service, you may create clients and projects for your application.

Configuring privacy settings for your application

The privacy services APIs are centred around the concept of Projects. A project needs to define some basic privacy related metadata, such as your service name and other configuration. All our privacy APIs require a project.

This documentation describes the APIs needed to configure the privacy settings for your project and also how to keep your application backends synchronised with Ü for user data and privacy requests:

Authenticating users to your application

Ü login helps your customer connect your service in a simple and convenient way. You can find the current developer documentation here:

Authentication flows

Your customers will see different authentication flows, depending on the level of assurance chosen by you. These authentication flows you can choose are illustrated below:

Privacy configuration

Your application’s privacy configuration is a registry of

  • data processing purposes
  • data objects affected by these purposes
  • first and third parties connected to these purposes (recipients, processors and controllers of data)
  • retention applied to each purpose
  • and what legal ground each purpose has

The purpose of creating this configuration is threefold:

  • creating compliant dialogues with end users during consent gathering
  • show the data processing purposes for your service on the privacy management portal (allowing for revoke/give consent, objection of legitimate interest purposes and for transparency requirements by GDPR)
  • for your service to comply with GDPR, the registry will function as a record of processing activities (art.30)

Permission flows

Based on your privacy configuration we will create and trigger compliant permission dialogues with end users during consent gathering during onboarding or contextually when you choose to trigger them. The configuration also shows the data processing purposes for your service during onboarding and on the privacy management portal (allowing for revoke/give consent, objection of legitimate interest purposes and for transparency requirements by GDPR)

Permission flow prototype:

Ü self service portal for end users

When a profile is created, users can access the Ü application/portal to manage their profile and privacy preferences. In the portal’s privacy section, users can see all the services they have a relationship with, the information about the data they collect and why and user journeys for exercising their GDPR individual rights like give/revoke consent given, object to data processing and trigger requests to personal data stored by each service. Ü will notify your service when your customers make changes of their profile or permission to share their personal data.

Interactive prototype: