Sign inGet Started

Bird for European customers: entity, data region, and DPA

This article answers three questions a European buyer asks before choosing Bird: which company signs the contract, where the data is stored, and which data-protection terms apply. Each answer comes from Bird's published terms and documentation, with a link to the source so you can check it. It is not legal advice.

QuestionAnswerSource
Who do I contract with?Bird B.V., under the law of the Netherlands, for a customer domiciled outside the United StatesGeneral Terms and Conditions, section 15
Where is my data stored?In the eu1 region when you choose it at signupBase URLs and regions
Which data terms apply?The Data Processing Agreement, which forms part of your agreement with BirdData Processing Agreement
Who else processes my data?The sub-processors on the published list, each with its processing locationApproved Subprocessors

Who you contract with

Section 15 of the General Terms and Conditions names the contracting entity by where you are domiciled. A customer domiciled outside the United States contracts with Bird B.V. The agreement is governed by the law of the Netherlands, and the courts of Amsterdam have exclusive jurisdiction.

Sections 14.4 and 15 say how to give Bird B.V. notice under the agreement. Send it by email to legalnotice@bird.com. Or send it by registered prepaid post to Bird B.V., Attn: Legal, Keizersgracht 268, 1016 EV Amsterdam, the Netherlands, with a PDF copy to the same email address.

The entity differs in two cases. An order form can name another one. Bird Pay and the Push Notifications API Services each have their own entity, whatever your domicile. Read section 15 for the full table.

Where your data is stored

Bird runs two regions, us1 in the United States and eu1 in the European Union. Every organization is assigned to one region at signup. The region is detected from your location, and you can change it before you confirm. After that, the region cannot be changed.

Your workspace, API keys, messages, recipient data, and event logs remain in your organization's region and are not replicated to the other one. Authentication and account administration use globally replicated data, so they are served from a host that belongs to neither region.

To use the EU region:

  • In the dashboard: the region is detected from your location at signup. If it is not the EU region, change it before you confirm.
  • From a terminal: pass --region eu1 to bird auth create-org, as self-serve signup describes.
  • In your code: an eu1 organization's API keys start with bk_eu1_, and its requests go to https://eu1.platform.bird.com. The official SDKs and the CLI read the region from the key.

Each API response carries an X-Bird-Region header that names the region that served it. A request sent to the wrong region is rejected with 421 instead of being forwarded. Base URLs and regions covers both.

The region decides where Bird stores your data. Some processing is done by sub-processors, and the Approved Subprocessors page lists each one with its function and processing location.

Which data-protection terms apply

The Data Processing Agreement (DPA) forms part of your agreement with Bird, so you do not sign a separate document to get it. The current version was last updated on 21 November 2024. Its main points, with the section that states each one:

  • Role (sections 1 and 3): Bird processes Customer Personal Data as a processor, to provide the services on your documented instructions. Bird also processes it as an independent data controller where that is necessary for the business purposes listed in section 3.4, such as billing, account management, reporting, security, fraud and abuse prevention, business modeling, and improving the services you use.
  • Sub-processors (section 8): you give a general authorization for the sub-processors on the published list. You can subscribe to notifications of changes, and you can object to a change in writing within ten business days of the notice.
  • Transfers out of the EEA, Switzerland, and the United Kingdom (section 9): where personal data is transferred to a Bird entity in a country without an adequacy decision, the Standard Contractual Clauses apply, and the UK Standard Contractual Clauses apply to transfers from the United Kingdom. Both are incorporated into the DPA, so you sign no separate document. The EU clauses are governed by the law of the Netherlands.
  • Audit (section 10): the DPA commits Bird to regular audits of its platform against ISO 27001 or an equivalent standard, and to a summary of the audit report on written request.
  • Deletion and return (section 11): when the agreement ends, Bird deletes or returns Customer Personal Data, as you choose, unless the law requires Bird to keep it.
  • Security measures (Appendix II): the technical and organizational measures Bird applies.

The DPA itself governs. Read the section before you rely on a summary of it.

Next steps

Ga verder met de documentatie, handleidingen en voorbeelden voor dit onderwerp.