Get a list of all subprocessors used by F1 NGINX Ingress Controller
Learn how to use Openli to get a full list of F1 NGINX Ingress Controller's’s subprocessors and all their GDPR and privacy related information.
What is a sub-processor?
A sub-processor is a third-party data processor engaged by F1 NGINX Ingress Controller. The sub-processor has or potentially will get access to personal data that F1 NGINX Ingress Controller processes on behalf of its customers.
Why and how should I assess this?
If you choose to use F1 NGINX Ingress Controller as a processor, the sub-processors listed will have access to personal data processed on your behalf. When you assess the sub-processors of your vendors, you need to ensure the following:
A signed data processing agreement
You need to have a signed contract in place that commits F1 NGINX Ingress Controller to only use sub-processors with your permission.
Transfers of data out of Europe
If F1 NGINX Ingress Controller uses a sub-processor located outside Europe, there must be a legal basis for the transfer.