guide

Understanding Data Handling Terms

For more on this topic, take the Short Code: Navigating the Data Handling Questions

In partnership with

·2 min read

2 min read

Share this doc:

When we say...	We mean...	For example...
Data Controller: The legal entity that will control the purposes and means of processing the data made available to you by Meta Horizon through the requested permissions and/or features. This could be a natural or legal person, a public authority, an agency or other entity.	The person or organization responsible for determining what the data is for, and what's going to happen to it. That includes what data third-party service providers can access and how they can process it.	If your organization makes those decisions about the data you collect, process, and store - you are a data controller.
Data Processor: A separate entity that, on your behalf, processes the Meta Horizon User Data and/or Device User Data made accessible to you in order to provide you with a service.	Any entity or organization that processes personal data on behalf of the controller. You might be more familiar with the term “service provider” rather than data processor. Data processors do not own or control the data, they process it to deliver a specific service.	Data processors are typically third-party service providers that are external to the company. To identify your data processors or service providers, think of services you might use, such as AWS or Google Analytics that require access to the data you collect. In this example, your data processors are Amazon and Google, respectively.

Data Controller:

The legal entity that will control the purposes and means of processing the data made available to you by Meta Horizon through the requested permissions and/or features. This could be a natural or legal person, a public authority, an agency or other entity.

The person or organization responsible for determining what the data is for, and what's going to happen to it. That includes what data third-party service providers can access and how they can process it.

If your organization makes those decisions about the data you collect, process, and store - you are a data controller.

Data Processor:

A separate entity that, on your behalf, processes the Meta Horizon User Data and/or Device User Data made accessible to you in order to provide you with a service.

Any entity or organization that processes personal data on behalf of the controller.

You might be more familiar with the term “service provider” rather than data processor. Data processors do not own or control the data, they process it to deliver a specific service.

Data processors are typically third-party service providers that are external to the company.

To identify your data processors or service providers, think of services you might use, such as AWS or Google Analytics that require access to the data you collect. In this example, your data processors are Amazon and Google, respectively.

When we say...

Data Controller:

We mean...

For example...

If your organization makes those decisions about the data you collect, process, and store - you are a data controller.

When we say...

Data Processor:

A separate entity that, on your behalf, processes the Meta Horizon User Data and/or Device User Data made accessible to you in order to provide you with a service.

We mean...

Any entity or organization that processes personal data on behalf of the controller.

You might be more familiar with the term “service provider” rather than data processor. Data processors do not own or control the data, they process it to deliver a specific service.

For example...

Data processors are typically third-party service providers that are external to the company.

Disclaimer: This resource does not guarantee compliance with Meta policies, nor applicable data privacy laws. Review Meta Horizon's Developer Data Use Policy for a comprehensive overview of Meta's requirements.

For more on this topic, check out the badge:

Navigating the Data Use Checkup

The Data Use Checkup is a tool Meta uses to confirm whether you are operating within the bounds of the Developer Data Use Policy, and to grant you access to platform features. This badge walks you through preparing for the DUC, answering data handling questions, and navigating the submission and review process.

Get Started