Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Adhese acts as a processor of data under the GDPR in the EU. Adhese does Adhese does not decide what possible Personally Identifiable Information (PII) is collected and what it is used for, but our platform can and does process PII in certain implementations. The controllers of the data that flows through the system must have consent have consent to use any PII. To use PII, a consent flag will have to be passed with each Adhese request to enable the PII use of PII and the possibility to set any cookies.

...

Adhese account owners can add the tl parameter to a request in in any kind of implementation to define whether or not PII can be used for their application of Adhese.

...

  1. Every Adhese implementation is an instance of the platform , running its own database , and using its own set of domains to face the public. This means no data can be shared between two Adhese instances. Implementations can run on the first domain, making sure cookies stay within the context they were set , and for which consent was given.
  2. Even when consent is given, Adhese does not log any PII even when consent is given, so users will never be identifiable in any log files.
  3. If consent for a unique identifier for one day is given, that cookie ID will be logged as a hash with sufficient collision to make sure ensure the original cookie ID can never be identified. The ID is used for reporting unique browsers over one day.

...