Get a list of all subprocessors used by OpenCage Geocoding API
Learn how to use Openli to get a full list of OpenCage Geocoding API'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 OpenCage Geocoding API. The sub-processor has or potentially will get access to personal data that OpenCage Geocoding API processes on behalf of its customers.
Why and how should I assess this?
If you choose to use OpenCage Geocoding API 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 OpenCage Geocoding API to only use sub-processors with your permission.
Transfers of data out of Europe
If OpenCage Geocoding API uses a sub-processor located outside Europe, there must be a legal basis for the transfer.