Back to all glossary articles

Privacy by design

Privacy by design means that privacy must be the primary principle in designing and developing software, and should be assured by the way organizations operate. It has to be taken into consideration from the beginning of every project and throughout its entire lifecycle.

The concept was initially defined by Ann Cavoukian for systems engineering and has since been widely adopted by various organizations, becoming an obligation under GDPR . According to the Regulation, you need to incorporate safeguards into data processing from the initial phases of design of processing operations, both at the technical and organizational levels.

More about privacy by design on the Piwik PRO blog:

Privacy by design under the GDPR

  • first party data

    First-party analytics without consent: Your Digital Omnibus compliance guide

    The Digital Omnibus is the European Commission’s simplification initiative to modernize the EU’s digital rulebook and reduce consent fatigue. The framework would enable first-party analytics without consent when specific criteria are met, ending years of uncertainty about the use of legitimate interest for web statistics.

  • University website personalization: First-party data strategies for student recruitment and retention

    University websites receive millions of visits annually from diverse audiences – prospective students, admitted students weighing their options, current undergraduates, graduate students, parents, alumni, and faculty. Yet most institutions serve identical content to all these visitors, missing critical opportunities to engage each audience with relevant information.

Other definitions

Recent posts from Piwik PRO blog