Shipbook - Sub-processors

Shipbook Ltd. (“Shipbook”, “we”, “us” or “our”) engages a small number of third-party service providers (“sub-processors”) to help deliver our services. A sub-processor is a third party that processes customer or end-user data on our behalf. This page lists those sub-processors so that our customers can see who is involved in processing their data, in line with the transparency principles of the General Data Protection Regulation (GDPR) and our Privacy Policy.

We require every sub-processor to provide a level of data protection at least equivalent to our own, and to process data only for the purposes for which it was engaged.

1. Infrastructure and core service

These providers process application logs and account data as part of running the Shipbook platform.

Always in use

Engaged whenever the service runs, to store and deliver your data.

Sub-processorPurposeLocation
DigitalOceanCloud hosting and compute, managed MongoDB database, self-hosted Elasticsearch log storage, and Spaces object storageEuropean Union (Frankfurt)
Amazon Web Services (AWS S3)Encrypted off-site backups of the databaseEuropean Union (Frankfurt)
Twilio SendGridTransactional email (account, alert and billing notifications)United States

Opt-in

Engaged only when the user chooses to use a specific feature. No data is sent to these providers otherwise.

Sub-processorPurposeLocation
OpenAIAI-assisted log and crash analysis. Data is sent to OpenAI only when the user invokes an AI feature (such as LogChat) or has connected their code repository; it is never used automatically for all logsUnited States

2. Billing

These providers process the billing and contact information needed to charge for and invoice the service.

Sub-processorPurposeLocation
BlueSnapPayment processing. Card data is collected directly by BlueSnap; Shipbook does not store card numbersUnited States
GreenInvoiceInvoice generationIsrael
TremendousReferral reward payoutsUnited States

3. Product analytics and support

These providers process usage and interaction data of users signed in to the Shipbook console, to help us diagnose issues and provide support.

Sub-processorPurposeLocation
LogRocketSession replay and error diagnostics within the Shipbook consoleUnited States
DriftIn-app support chatUnited States

4. Optional customer-configured integrations

Shipbook also offers integrations that a customer can choose to enable, such as Jira, Slack, and GitHub, as well as Google and GitHub sign-in. When enabled, these send data to the customer's own third-party accounts at the customer's direction. They are not Shipbook sub-processors, because Shipbook does not determine how that data is used once it reaches the customer's own service. Whether these are used, and what data is shared, is controlled entirely by the customer.

5. Changes to this list

We may update our sub-processors from time to time as our services evolve. When we add or replace a sub-processor that processes customer data, we will update this page. Customers who would like to be notified of changes to this list may contact us at the address below.

6. Contact

Questions about this list or about how we process data can be sent to support@shipbook.io.