Data processing agreement (DPA) is a legally binding document. It’s signed between two key data processing actors under GDPR – the data controller and the data processor.
It regulates the details of data processing, such as the scope and purpose, as well as the relationship between those actors. In addition, it assigns certain obligations required by the new EU law.
Read more about this topic on the Piwik PRO blog: Check out the 7 elements every DPA should have.
Data processing agreement
-

What is PII, non-PII, and personal data? [UPDATED]
Personally identifiable information (PII) and personal data are two classifications of data that often confuse organizations that collect, store and analyze such data. Both terms cover common ground, classifying information that could reveal an individual’s identity directly or indirectly. PII is used in the US, but no specific legal document defines it. The legal system…
-

What is first-party data and how does it benefit your marketing strategy [Updated]
First-party data is information a company collects directly from its customers through owned channels like websites, apps, transactions, and customer interactions. Unlike third-party data purchased from external sources, first-party data comes straight from your audience, making it more accurate, privacy-compliant, and valuable for personalized marketing. According to Acquia’s 2024 CX Trends Report, 93% of marketers…
Other definitions
Recent posts from Piwik PRO blog
- What is PII, non-PII, and personal data? [UPDATED]
- What is first-party data and how does it benefit your marketing strategy [Updated]
- Digital marketing analytics: The beginner’s guide to data-driven marketing success [Updated]
- We’re introducing Piwik PRO MCP Beta – get answers from your data without building a single report
- Google is changing how GA4 and Google Ads share data: Here’s how it puts your compliance at risk
- HIPAA-compliant analytics for healthcare systems: How hospital marketing teams can measure what matters
- Privacy by design in practice: How “just enough” data beats “just in case” collection
- 4 ways to make your analytics HIPAA-compliant: Implementation guide