Legal Guides

Trackerdetect Legal Guide describes:

  1. the legal duties (GDPR, ePD etc) site owners have when Trackers are on site owners’ sites, and
  2. actions site owners can take to comply with such legal duties.

GDPR Consent Guide provides a general introduction to how controllers (site and app owners) can meet the GDPR requirements for:

  1. the Consent Request,
  2. the Consent Dialogue,
  3. who provides the Consent Request, and
  4. when to provide the Consent Request.

We will soon publish special guides for the following:

  1. ePrivacy Directive and ePrivacy Regulation.
  2. the obligation to demonstrate consent for single controllers and joint controllers.
  3. the Consent Event Record and DPA inspection of Consent Event Record.
  4. representation of consent requests by icons, flowcharts, stickmen etc.
  5. accessible information for low-visioned and no-visioned.
  6. where to provide consent requests (Privacy Settings Dashboard with user account, in context where data are collected, pop-up nudging, for cookies, on each URL, etc).
  7. Consent Dialogue design and architecture (privacy by design, GDPR Art 25) with UX/UI requirements and best in class design.
  8. When and how to refresh consent.
  9. Consent Analytics.
  10. Signalling Consent Events.
  11. Consent Receipts.
  12. Where/how users exercise their rights, including Subject Access Request to see Consent Event History, Withdraw consent, Object to direct marketing, Object to legitimate interest, Notify Notify 3rd parties of users’ request to rectify or erase data or restrict processing, etc.
  13. Signatu technology for Opt-out of Legitimate Interest.

GDPR Privacy Policy Guide

GDPR Privacy Policy Guide provides a general introduction to how controllers (site and app owners) can meet GDPR Articles 13 and 14 requirements with regard to:

  1. which information (content) must be provided to data subjects (end users), and
  2. how information (quality, understandability and accessibility) must be provided to data subjects (end users).

We name the document in which this required information is provided a “Privacy Policy”.