This page describes the sub-processors that Shipber engages under the Adber Data Processing Addendum (DPA) to perform processing activities on Customer Personal Data on behalf of our customers. The specific sub-processors relevant to a given customer may vary based on the regions selected for the Service and the particular product capabilities or integrations the customer enables.
We update this page before engaging a new sub-processor or replacing an existing one. We will provide advance notice here and in your Message Center, and, if you have subscribed to email notifications, we will also send the notice by email. The table below reflects the current sub-processors we use “as of” the date shown on this page.
Name |
Applicalbe Product | Purpose of processing |
Location of processing |
Categories of personal data
|
Trust & compliance |
|---|---|---|---|---|---|
Amazon Web Services (AWS) |
Shipber | Cloud Service provider |
USA |
Customer Personal Data necessary to host and operate the Service; operational and technical logs/telemetry generated by the Service
|
|
Zendesk, Inc. |
Shipber | Customer Support Services |
USA |
Customer Personal Data in support tickets (contact details, account identifiers, content/attachments); operational diagnostics
|
|
OceanBase |
Shipber | Managed database service (relational) |
USA |
Customer Personal Data stored to operate the Service (queries, transactions, persistence); operational/log data of the database service
|
|
Cloudflare, Ltd. |
Shipber | Content delivery network provider |
Customer traffic is processed globally at the data center closest to the end user. |
Network/request metadata necessary for delivery and protection (e.g., IP address, headers); limited identifiers if configured
|
|
Google Maps Platform |
Shipber | Address autocomplete (typeahead) | USA |
Address text entered by user; technical metadata necessary to provide suggestions
|
Last Updated: September 30, 2025
Comments
0 comments
Article is closed for comments.