Skip to content
GDPR Obligationscalendar_todayUpdated: 18 November 2026schedule4 min read

How do I record personal data in content my customers provide?

verifiedLast reviewed 18 November 2026 · GDPRWise legal team

Use the standard GDPRWise processor process for customer-provided content, refine expected data items where possible, or create a custom process when the work differs.

summarizeKey Takeaways
  • check_circleYou do not need to identify every individual piece of personal data in customer-provided content before receiving it.
  • check_circleUse the standard GDPRWise process for customer-provided content when it reflects your services, and refine the expected data items where possible.
  • check_circleCreate a custom process when the nature or purpose of your processing is materially different from the standard process.
  • check_circleYour data processing agreement must describe the agreed processing, including the relevant types of personal data and categories of data subjects.

When you process documents, files, messages or other content on behalf of customers, you may not know exactly which personal data they will provide. That does not prevent you from recording the activity. Describe the service and the types of data you can reasonably expect, then check whether the standard GDPRWise process fits your work.

Why can customer-provided content vary?

A software provider may let customers upload documents. An IT provider may store files for different businesses. An administrative service may handle contracts, correspondence and forms supplied by clients. The content can differ from one customer or document to another.

For example, one contract may contain only names and signatures. Another may also contain private addresses or bank account details. You do not need an inventory of every future field or value. You do need a meaningful description of the processing and the types of personal data that fall within the service.

First check your role. A processor handles personal data on behalf of another party and follows documented instructions. Your customer may itself be a processor for another controller, in which case you may act as a sub-processor. See Data controller or data processor: what is the difference?.

Use the standard GDPRWise process

GDPRWise includes the standard process Processing of customer-provided content. It covers personal data contained in content entrusted to you for the agreed services.

  1. Check whether the standard description matches the service you provide.
  2. If it does, use the standard process. You can keep it as provided.
  3. If you know which personal data are normally included, refine the data items to match what you actually process or reasonably expect.
  4. If the service differs materially from the standard process, create a custom process instead.

The standard process describes the source of the information. Its broad data item, Personal data contained in provided content, does not by itself identify every type of personal data. Add more detail when your service makes that possible.

Which data items should you expect?

Think about the normal purpose of the service and the content it requires. Depending on your work, the relevant categories may include:

  • Identification and contact details, such as names, addresses, email addresses and telephone numbers.
  • Professional information, such as job titles, employers and business contact details.
  • Contract and transaction information, such as details of contracting parties, signatures or payment information.
  • Other categories specific to the service, where customer instructions make them relevant.

These are examples, not a list to select automatically. Only record categories that are actually processed or reasonably expected within the agreed scope. The people concerned may include customer contacts, employees, suppliers or other third parties. Record the relevant categories of data subjects as well. See What are data subject categories under the GDPR?.

The business purpose should explain what service you deliver, such as document storage or administrative processing. Providing the agreed service on the customer’s behalf is a useful starting point, but name the actual service wherever possible.

When is a custom process necessary?

Use a custom process if the standard description does not reflect the nature or purpose of your work. For example, a service dedicated to analysing medical records needs a more specific description than general document storage.

A new customer document with different names, addresses or other ordinary details does not by itself change the process. Review the process when your service begins handling a materially different kind of content or performing different operations.

What if the content contains sensitive data?

Check whether special categories of personal data under Article 9 GDPR, such as health data, or data relating to criminal convictions and offences under Article 10 may be part of the agreed service.

If they are, identify the relevant types and ensure the agreement and security measures reflect the additional risks. Unknown content is not a reason to assume that sensitive data are absent. Equally, you should not mark every sensitive category as processed merely because it is theoretically possible.

What must the data processing agreement cover?

Article 28(3) GDPR requires a data processing agreement (DPA) or another binding arrangement that describes, among other things, the nature and purpose of processing, the types of personal data and the categories of data subjects.

The European Data Protection Board’s Guidelines 07/2020, paragraph 114, say the types of personal data should be described as specifically as possible. Simply saying that the processor handles all personal data supplied by customers is not enough on its own.

Different documents can remain within one agreed service and DPA if the processing stays within the defined scope. You generally do not need a new DPA for every upload. Review the agreement and instructions if the service, data types or risks change materially. See What is a processing agreement?.

What should you check before confirming the process?

  1. Does the standard process describe the service you actually provide?
  2. Can you refine the expected personal data categories and categories of data subjects?
  3. Could sensitive or criminal-offence data be included within the agreed scope?
  4. Does your DPA describe the same service, data types and safeguards?
  5. If the standard process does not fit, have you created a custom process?
auto_awesomeDo you process personal data on behalf of customers?

GDPRWise helps you document your processing activities and keep track of the GDPR steps relevant to your business.

ShareshareLinkedInmailEmail
GW
GDPRWise Editorial

This article was written by the GDPRWise team and reviewed by our privacy experts. We regularly review our content for accuracy and legal correctness.