Latest Post:

What is GDPR?

Definition

The GDPR sets requirements for processing personal data, including a lawful basis, transparency, security and individual rights. Its reach depends on the organisation and activity: it applies to processing in the context of an EU establishment, and certain activities involving people in the EU by organisations based elsewhere.

Responsibilities depend on whether an organisation acts as a controller or processor. Hosting in the EU alone does not establish compliance; contracts, access, retention and international transfers also matter.

Why it matters

Routine analysis can include personal data even when a report is about business performance. Customer records, employee activity and identifiers that can be linked back to individuals all deserve attention. Understanding what the analysis actually needs can help you avoid bringing unnecessary detail into another system.

Start with the purpose of the work and follow the data through its lifecycle:

  • Identify the fields needed for the question and who can access them.
  • Review the controller and processor roles and the relevant agreements.
  • Understand retention, deletion, exports and connected providers.

These checks help make the product assessment specific to your organisation’s use, instead of treating a vendor’s broad compliance statement as the whole answer.