Commonly used definitions

GDPR defines an official set of definitions, which you can find on the official GDPR page.

Below you can find our short summary of the definitions used by STRM Privacy.


An input or output continuous collection of data.


Structure of the data that is sent to STRM Privacy. Also named serialization schema See schemas and contracts for details.

Event Contract

A contract, that contains which fields are Personally Identifiable Information (PII), which validations should be applied to events, etc. See schemas and contracts for details.

Consent level

The level of consent, given by the data owner (your customer), to use certain information (typically PII). This is used both in the events, as well as in the configuration of a decrypted output stream.


Data that is scrambled and cannot be read without the encryption key.


STRM Privacy component that sends batches of events to a Sink.

Personally Identifiable Information (PII)

Information that can be used to identify a person, directly (e.g. SSN, name) or indirectly (e.g. IP address), or belongs to an identifiable person (e.g. gender, interests).

Serialization Format

Currently, we support Avro Binary, Avro JSON and JSON serialized data. This defines the way that an event is converted to and from bytes, so that they can be transported and/or stored.


STRM Privacy component that connects to a file storage. Currently, AWS S3 and Google Cloud Storage buckets are supported.