Connecting Data Subjects with Processor and Controller Roles

Overview

Relyance helps automatically identify your controllers, processors and subprocessors.

When determining controllers and processors, Relyance first identifies any processing activities that a particular vendor does, and associates those processing activities to any relevant data subject categories. The data subject categories help determine your processing role.

For more information about controllers, processors and subprocessors, please see this help centre article: What are Controllers, Processors, and Subprocessors?

Processor / Controllers

By default, Relyance identifies Processors and Controllers based on the Data Subject Category. This table can help you determine how Relyance has categorized the Processor/Controller roles.

Data Subject Category	Processor / Controllers
Agents	Controller
Any Data Subject	Controller
Consultants & Advisors	Controller
Consumers	Controller
Contractors	Controller
Customer Personnel	Processor
Customer Users	Processor
Customers	Processor
Employees	Controller
End User Family Members	N/A
Interns	Controller
Job Applicants	Controller
In a very small set of cases processor is applicable
Legal Team	N/A
Marketing Prospects	Controller
None	N/A
On Premise Visitors	Controller
Partners	Controller
Personnel	Controller
Personnel Family Members	N/A
Recruiting Targets	Controller

Subprocessors: Relyance looks for data flows from source code, integrations, and microservices containing personal information originating with a controller to determine if a vendor should be considered a subprocessor.