Skip to main content

Tokens

Tokens are authentication credentials that the Portal generates for you to use with INCERT, the backend pseudonymisation system. Think of them like temporary passwords that authorise INCERT to process your data according to your project's configuration.

When the Portal generates a token, you receive an authentication credential that:

  • Authorises your requests to INCERT for pseudonymisation operations.
  • Contains your project's configuration (reversibility, treatment, output format).
  • Expires after a set period for security, depending on your project's retention settings.
  • Doesn't contain your actual data—it's just an authorisation key.
  • Single-use—each token authorises one request; generate as many tokens as you need for multiple requests.

You use tokens by including them in API requests when sending data to INCERT for processing. The Portal manages token generation; INCERT handles the actual pseudonymisation.

Token types​

The Portal supports three token types for different pseudonymisation scenarios. This diagram illustrates how they relate to your data transformation journey:

Pseudonymisation token​

Pseudonymisation tokens authorise INCERT to convert your original data (personal identifiers) into pseudonyms. This token allows you to:

  • Authorise INCERT to convert personal identifiers (names, IDs, etc.) into pseudonyms
  • Enable collaboration without sharing tokens — each collaborating organisation generates their own token independently for their own requests
  • Re-use the same pseudonymisation configuration across requests, as defined in your project settings

When to use: Use this token whenever you need to pseudonymise data. If you are collaborating with other organisations, each party generates their own token — there is no need to share tokens between organisations.

Reverse token​

Reverse tokens allow you to convert pseudonymised data back to original identifiers, if your project is configured as "Reversible" and within the retention period. Reverse tokens:

  • Take pseudonymised values and returns the original data
  • Only work if your project is configured as "Reversible"
  • Require proper permissions and during the retention periodz

When to use: Use this token for data verification, quality checks, and audit processes when you have a legitimate need to access original identifiers. This must be done before the retention period expires.

Secondary token​

Secondary tokens allow you to re-pseudonymise data that has already been pseudonymised. This is useful for adding an extra layer of protection when sharing data with third parties. Secondary tokens:

  • Creates a second layer of pseudonymisation
  • Prevent recipients from accessing the original identifiers
  • Can be reversed to reveal the first-level pseudonyms, but not the original data

When to use: Use this token when sharing with third-party organizations who shouldn't have access to source identifiers, or when you need additional privacy protection to prevent correlation between datasets.