Defining Processing Activities in the RoPA, Explained Simply

When you start creating the record of processing activities (RoPA), most people face the question of "how" right at the first task, defining processing activities. In this post, we explain in simple terms what a processing activity is and how you can find out which processing activities exist in your company.

Table of contents

What is a processing activity and why do I have to document these activities?

A processing activity is a self-contained one-off or recurring activity in which personal data is processed manually or automatically. The GDPR requires that a company must know in which processes personal data is processed. This information and the associated details are the basis for information obligations (privacy policy) towards the data subject. In the case of services where you process personal data for another company, these processing activities are also part of the processor agreement.

How do I create a list of processing activities?

To get started, you need to define the processes in which personal data is processed. The best approach is to go through your business processes and your value chain and create a RoPA entry for each self-contained area where personal data is processed. Important: a very common mistake is using tool names as RoPA entries, e.g., "Outlook emails" or "Customer data in Excel". Avoid tool-centered names and use names such as "Customer communication" or "Management of customer data" instead. The tools are then a building block within the RoPA entry. Another tip: if you offer services (e.g., employee coaching), this service offering would be its own RoPA entry. If the service varies greatly from customer to customer, it makes sense to create a separate RoPA entry for each customer (e.g., "Individual employee coaching for customer X").

 

As an alternative or a complement to the method described above, based on defining the business processes and the value chain, you can also try to identify relevant processing activities by following the data flow. Here you try to trace the "path" of the data through the company: where data from customers and employees is collected, where it is then needed (processed) and stored, and when it is no longer needed. Based on this overview, you can map the data flow into self-contained processing steps and thus into RoPA entries, and you will already have content for the RoPA entries. Here is an example based on an online shop, where the numbered headings represent the RoPA entries:

Customer registration

  • Data collection: Customers register in the online store and enter their name, address, e-mail address and, if applicable, telephone number.
  • Processing: The data is used to create a customer account, order processing, shipping and invoicing.
  • Storage: Customer data is stored in the online store's customer database.
  • Forwarding: To shipping service providers to deliver the order and, if necessary, to payment service providers to process the payment.
  • Deletion: Customers can have their account deleted, which removes their data from the database.

Order process

  • Data collection: When an order is placed, the article, quantity, delivery address and payment information are recorded.
  • Processing: The data is used for order processing, invoicing and shipping.
  • Storage: Order data is stored in the online store's order database.
  • Forwarding: To shipping service providers to deliver the order and, if necessary, to payment service providers to process the payment.
  • Deletion: Order data will be deleted after expiry of the statutory retention periods.

Payment processing

  • Data collection: Credit card information or other payment data is collected during payment.
  • Processing: The data is used for payment processing.
  • Storage: Payment data is not stored by the online store itself, but is processed directly by the payment service provider.
  • Forwarding: To the payment service provider for processing the payment.
  • Deletion: Payment data will be deleted after the payment has been processed.

Website use

  • Data collection: When you visit the website, data such as IP address, browser type, operating system and pages visited are collected.
  • Processing: The data is used to analyze user behavior, improve the website and personalized advertising.
  • Storage: The data is stored in log files and possibly in cookies on the user's device.
  • Forwarding: To web analysis service providers and possibly to advertising partners.
  • Deletion: Log files are automatically deleted after a certain time, cookies can be deleted by the user.

E-mail marketing

  • Data collection: Customers can register for the newsletter and provide their e-mail address.
  • Processing: The e-mail address is used to send newsletters and promotional offers.
  • Storage: The e-mail address is stored in the newsletter database.
  • Forwarding: To e-mail marketing service providers.
  • Deletion: Customers can unsubscribe from the newsletter at any time, which will remove their e-mail address from the database.
.

If you have employees, you can proceed in a similar way. Processing activities such as the application process, employee onboarding, personnel administration, payroll accounting, etc. can then arise here.

Conclusion

Defining processing activities in a record of processing activities can be more difficult than you think. With the right systematic approach, many mistakes can be avoided and a good quality directory can be created, which later provides great added value when generating data protection guidelines or data processing agreements.

Further contributions

How-To

Defining the purpose and legal basis of data processing

If you collect and process personal data, there should be a purpose and a legal basis for doing so. Determining the legal basis in particular is not an easy task for most people. In this article, we explain how to define the right purpose and the right legal basis as part of the record of processing activities.

Read more »