This page is Annex C of the Helix Field Data Processing Addendum, reproduced as the current subprocessor list. How the list changes, and what notice BAW gives when it does, is governed by Section 7 of the DPA.
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, storage, and infrastructure | United States |
| Stripe, Inc. | Subscription billing for Helix Field, and customer payment collection for customers who use a Stripe account set up through the Service (Stripe also acts as an independent controller for its fraud prevention services, as described in its own privacy policy) | United States |
| Block, Inc. (Square) | Customer payment collection, only for customers who connect their own Square account (Square also acts as an independent controller for fraud prevention, the digital receipts it sends on its own behalf, and its own legal obligations, as described in its own privacy notice) | United States, with Square affiliates and service providers in other countries under Square's own transfer safeguards |
| Brevo | Email delivery | United States and European Union |
| Google LLC (Firebase) | Push notifications | United States |
| Mapbox, Inc. | Maps and geocoding of service addresses | United States |
| Geocodio (Dotsquare LLC) | Geocoding of service addresses | United States |
| Intuit Inc. (QuickBooks Online) | Accounting sync of customer, invoice, payment, and approved expense records (including vendor names created for expense entry), only for customers who connect their own QuickBooks account | United States |
| Zapier, Inc. | Delivery of the events and records the Customer chooses to send to its own Zapier account (new customers, scheduled and completed jobs, paid invoices, booking requests, and the customer and job records those carry), only for Customers who create an API key and connect Helix Field in Zapier | United States |
Service Data is stored at rest in the United States and Processed only in the locations listed above. Email delivery data handled by Brevo may be processed in the European Union in accordance with that provider's terms, and payment data sent to Square may be processed by Square's affiliates and service providers outside the United States in accordance with Square's terms.
A Customer connects one customer payment processor, Stripe or Square, and Service Data is sent only to the processor that Customer has connected: the invoice number, the amount, and the paying customer's name and email, with payment status returned to the Service. Card details are entered on the processor's hosted payment page and never reach BAW systems. Customer's own agreement with its processor governs its processor account.
A Customer may also send Service Data to software of its own choosing through an API key it creates in the Service and can revoke at any time. Software the Customer connects that way, including its own Zapier account, receives only the records the Customer chooses and acts as the Customer's own processor or recipient, not as a Subprocessor engaged by BAW.
If text messaging features launch, the SMS delivery provider will be added to this list with the notice described in Section 7.2 before any Service Data is sent through it.
Contact: helixfielddispatch@gmail.com · BAW International Inc., an Oklahoma corporation · Legal notices by mail: BAW International Inc., c/o Corporation Service Company, registered agent, 10300 Greenbriar Place, Oklahoma City, Oklahoma 73159