Skip to content


1. What is PIISA?

PIISA stands for a Personally Identifiable Information Standard Architecture. This open source and interoperableframework creates a standard designed to allow seamless interoperability between various PII processing frameworks.

2. Rationale

Our mission statement stems from these facts:

  • Proper PII management is hard, and has many facets.

  • There are solutions available for PII processing, both open source and commercial

  • We might want to combine several solutions to achieve better results, or to adapt to specific use cases

  • However there is no practical way of achieving such combination, or of customizing solutions

Our approach has been let's define an architecture that decomposes the PII problem into blocks, and let's define interfaces between those blocks

Therefore the PIISA specification, and its reference implementation, tries to follow the approach of independent components that pass data between them to compose a full solution

3. Specification

Click here for the latest specification document.

4. Usage

We are developing a reference software of this specification, delivered as a set of Python packages that implement each block in the architecture. Check the libraries and an introductory usage document to find out how it has been structured and how to use it.

5. Who are we

We are a team of privacy enthusiasts who are interested in improving PII management across multiple domains. Read our blog posts.

Current contributors to this codebase:

6. Contributing

We are happy to accept contributions from anyone interested in shaping out PIISA. To contribute:

  • Make sure you have a GitHub account.
  • Check if a Github issue already exists. If not, create one.
  • Clearly describe the issue.
  • Fork the repository on GitHub.
  • If your contribution contains code, please make sure you have unit tests added.
  • Optional but recommended: Run flake8 and black on your code prior to publishing your pull request.
  • Run all tests locally before publishing your pull request.
  • Push your changes to a topic branch in your fork of the repository.
  • Submit a pull request to the repository.

7. License