Liveblocks: DPA, subprocessors and transfers

What to put in your subprocessor list

A ready row. Replace the purpose with what your client actually uses Liveblocks for.

Questions people ask about Liveblocks

Where is Liveblocks's DPA?

Liveblocks publishes its customer data processing agreement at https://liveblocks.io/dpa.

Is Liveblocks's DPA the same thing as a data processing addendum?

Yes. A data processing agreement and a data processing addendum are two names for the document Article 28 of the GDPR requires between a controller and a processor; vendors use both, and some call it processor terms. What it has to contain does not change with the name. Liveblocks's is at https://liveblocks.io/dpa.

Where is Liveblocks's sub-processor list?

Liveblocks publishes the list of its own sub-processors at https://liveblocks.io/subprocessors.

Which legal entity does Liveblocks contract through?

Liveblocks, Inc., registered in United States. That is the name to put in a record of processing or a sub-processor list, not the brand.

Where is Liveblocks's trust center?

Liveblocks publishes it at https://liveblocks.io/security. A trust center, trust page or security page is the same thing under different names: the vendor's own account of how it protects data, and the place it keeps its certifications. It is Liveblocks's page, so we link to it rather than repeat what it says.

Where to go next

Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.

• Vendors contracting from United States146 in the registry
• The vendor registryLegal entities, transfer mechanisms and DPA links, checked by a person
• Download the registry as a CSVFree, for a spreadsheet
• Guides for privacy practicesHow the work is actually done

Other developer tools

Six of them. All developer tools in the registry.

• Ably RealtimeGB
• AirbyteUS
• AlgoliaFR
• Atlassian BitbucketAU
• Auth0US
• BackblazeUS