ZEUS Subprocessor Disclosure

This page is the published Subprocessor list referenced by the Zeus Data Processing Addendum (the "DPA") and, through it, by the Zeus Global Terms of Service and the Enterprise Master Subscription Agreement. Capitalized terms have the meanings given in the Defined Terms Register of the Agreement (including Zeus, Customer, Agreement, Services, Customer Data, End-Customer Data, Account Data, Subprocessor, DPA and Data Protection Laws). Per the precedence architecture this page sits at notice tier: it creates disclosure and notice effects for the mechanisms that the DPA and the Agreement attach to it, and where this page and the DPA or the Agreement differ, the DPA and the Agreement control.

---

1. Purpose; Status of This Page; Change Mechanism

1.1 Purpose and status

Zeus engages third-party service providers to assist with data processing activities; where such a provider processes personal data within Customer Data on Zeus's behalf, it is identified on this page as a "Subprocessor" of Zeus.

This page is the published Subprocessor list maintained under Section 6.1 of the DPA; it is a disclosure page, not a contract, and the Customer's rights and remedies concerning Subprocessors are exclusively those set out in the DPA and the Agreement.

This list may change from time to time; the Customer must check back regularly for updates.

Nothing on this page limits any right that applicable law does not permit to be limited; jurisdiction-specific privacy disclosures for Canada, the United States, Australia and New Zealand are carried in the privacy supplements and the DPA annexes, which control for their subject matter.

1.2 Change mechanism; notice discharged by publication on this page

Zeus may add, replace or remove Subprocessors at any time by updating this page.

Publication of the change on this page discharges in full every obligation of Zeus to notify the Customer of the appointment of a new, or the replacement of an existing, Subprocessor. No individual notice is sent, and the burden of monitoring this page rests with the Customer. Zeus does not currently operate a change-notification subscription mechanism; if one is introduced, it will be described here, and notifications sent through it will supplement — not replace — publication on this page as the operative notice.

The objection window under Section 6.2 of the DPA (five (5) calendar days, silence deemed acceptance — see Section 4) runs from publication of the change on this page.

1.3 Ancillary vendors are not Subprocessors

Vendors whose services concern the examination, maintenance or support of data processing procedures or systems — including maintenance providers, support tooling, telecommunications carriers and similar ancillary providers — are not Subprocessors, are outside the Subprocessor regime, and require no listing on this page, no notice and no flow-down, even where incidental access to data cannot be excluded.

Zeus takes reasonable steps to protect the confidentiality of any data such ancillary vendors incidentally access.

1.4 Customer-directed connections are not Subprocessors

Third-party services, sites, applications, integrations and connections that the Customer chooses to enable or connect to its Workspace are not Subprocessors of Zeus: when the Customer connects or syncs with them, the Customer acts as the controller directing those data flows, the third party's own terms and privacy policies apply, and Zeus is not responsible for them.

Such customer-directed recipients are accordingly never listed on this page, and their acts, omissions and data-protection practices are addressed exclusively by the Third-Party Services provisions of the Agreement.

This is also why the third parties your own device contacts at your direction are not on this list: the OpenStreetMap tile server when you open the route map, Google Maps when you tap through for driving directions, YouTube when you play an embedded help video, and your device's own dialer, SMS and email applications when you send a message from the app. Those receive data directly from your device, not from Zeus. They are described in Section 5.2 of the Global Privacy Policy.

1.5 Feature-use consent; critical providers

Certain features of the Services require the ongoing disclosure and transmittal of data (including Customer Data) to that feature's Subprocessors — for example, photo and document storage to Zeus's infrastructure and object-storage provider, outbound email delivery to Zeus's email provider, and street-address geocoding to Zeus's geocoding provider — and use of any such feature constitutes the Customer's ongoing consent to disclosure of the associated data to that feature's Subprocessors.

No objection or opt-out right exists for providers Zeus deems critical to the Services, including infrastructure, fraud-prevention and abuse-prevention providers; where no choice is offered, Zeus maintains the safeguards described in the DPA. Product analytics is the one exception: it can be switched off for the mobile application in Settings › Privacy › Share Usage Data.

---

2. Current Subprocessors

2.1 Current Subprocessor list

As at the Effective Date of this page, Zeus's Subprocessors — the third parties that process personal data within Customer Data (including End-Customer Data) or Account Data on Zeus's behalf — are the following.

Zeus Affiliates may also act as Subprocessors under the general authorization in Section 6.1 of the DPA without separate listing on this page.

Product analytics. PostHog processes telemetry on Zeus's instructions and for no purpose of its own. Zeus does not enable PostHog's session-replay or autocapture features. A user can stop the mobile application sending analytics at any time in Settings › Privacy › Share Usage Data.

Crash and error diagnostics. Sentry processes diagnostic events on Zeus's instructions and for no purpose of its own, and Zeus does not enable Sentry's session-replay or screenshot-attachment features. Crash and error diagnostics are a service-integrity and security function of the mobile application and are not governed by the Settings › Privacy › Share Usage Data control, which turns off product analytics only. Before a diagnostic event leaves the device, its free-text fields pass through an automated pass designed to remove credentials and personal-data patterns (including email addresses, phone numbers, addresses and coordinates); that pass operates on the diagnostic layer only, it is described as a design measure and not as a guarantee, and Zeus does not represent or warrant that every such value is removed from every event. The Customer remains responsible for not deliberately entering personal data into free-text fields where it is not required, and Zeus's liability in connection with diagnostic processing is subject in all cases to the limitations and exclusions in the Agreement.

Push notifications. Push delivery is live for the Zeus Android and iOS applications. Google LLC (Firebase Cloud Messaging) receives the registration token issued to each application install and each notification Zeus sends to it; the token is the personal-data element, and the message itself is reduced to a work label and record identifiers before it leaves Zeus's systems. On iOS, delivery additionally passes through Apple Inc. (Apple Push Notification service): the application registers a device token with Apple, and Firebase Cloud Messaging hands each notification to Apple for delivery, so Apple receives that token and the contents of each notification in transit, acting as a push-delivery party on the same terms — on Zeus's instructions, for no purpose of its own, and never for marketing. Zeus keeps one registration record per install and re-registers it when the operating system issues a new token; when a user signs out, that record is marked deleted and the token can no longer be used to reach the device. The device's notification permission and the operating system's notification settings govern whether a notification is displayed.

Bot and abuse prevention. Cloudflare Turnstile is the bot challenge Zeus runs on sign-up, sign-in, password reset, partner registration and the public booking-request page. It is a security and abuse-prevention control, so it falls within the no-opt-out category in Section 1.5. The challenge is solved in the browser or in the application; Cloudflare receives a challenge token and the connecting IP address of the device solving it, and Zeus verifies that token server-side. No name, email address, phone number, street address or document content is sent with the challenge. Where the public booking-request page is used, the person solving the challenge is a member of the public rather than one of the Customer's Authorized Users, and the connecting IP address is the only element of theirs that reaches Cloudflare through this control.

Geocoding. Zeus does not commit to any single, exclusive geocoding vendor and may substitute or add geocoding providers at any time under the change mechanism in Section 1.2. The routing above reflects current operational practice: Geocodio for United States and Canadian addresses, and the OpenStreetMap Nominatim service for every other country. New Zealand and Australian street addresses therefore leave for Europe today; that is a live disclosure, not a hypothetical, and it must be kept accurate to the routing actually in effect at each publication of this page.

Payment processing. Zeus does not process payments between the Customer and its Clients, and no payment processor is engaged as a Subprocessor today. If and when Zeus enables customer payment processing, the processor will be added to this page under Section 1.2 before the feature goes live.

2.2 No AI subprocessors; self-hosted OCR; conditional future AI mechanics

Zeus engages no artificial-intelligence subprocessors: no third-party AI, machine-learning or OCR vendor processes personal data within Customer Data on Zeus's behalf. Receipt-scan text recognition uses a machine-learning engine that Zeus runs on its own infrastructure, with no external data flow, so there is no vendor to list.

If Zeus ever proposes to engage an AI subprocessor, that engagement will occur only through the mechanics of this page and Sections 6.1–6.2 of the DPA — listing here before engagement, subject to the objection process in Section 4 — and any such provider will be contractually barred from using Customer personal data to train, improve or develop any model, product or service for itself or any third party.

Nothing in this Section is a present-tense statement that any AI feature or AI subprocessor exists.

2.3 Storage-region statement (operational fact, not a warranty)

Zeus states, as a description of current operational practice only, that its primary object storage (Cloudflare R2) is currently pinned to a North American storage region on a fail-closed basis. This statement is an operational fact, not a warranty, commitment, representation or condition of any kind: it excludes content delivery and traffic in transit (processed at Cloudflare's global edge), backups, diagnostics, email delivery (which has no region pin), geocoding, product analytics and support access; and Zeus may relocate data between facilities and regions at any time, with any resulting change to this page handled exclusively under the change mechanism in Section 1.2 and the objection process in Section 4. Section 3 states the transfer position in full.

---

3. Locations and International Transfers

3.1 Processing locations; consent; weaker-law and lawful-access acknowledgment

Personal data handled through the Services is stored and processed in the United States, in Canada, in Europe (street addresses outside the United States and Canada, including Australian and New Zealand addresses — Section 2.1), and in any other location where Zeus or its Subprocessors maintain facilities.

By using the Services or submitting information, all Customers and their users — expressly including those in Canada, Australia and New Zealand — consent to the transfer, storage and processing of their information in those locations.

The Customer acknowledges that the laws of those jurisdictions may be less protective than the laws of the Customer's or any individual's home country, and that data held there may be subject to lawful access by the governments, courts and law-enforcement authorities of those jurisdictions.

Anyone who does not consent to this processing must not use the Services.

3.2 No data-residency warranty; relocation; sole remedy

ZEUS MAKES NO WARRANTY THAT ANY STORAGE OR PROCESSING LOCATION, INCLUDING THE CURRENT REGION PRACTICE DESCRIBED IN SECTION 2.3, WILL MEET THE CUSTOMER'S DATA-RESIDENCY REQUIREMENTS.

Without limiting the foregoing, location statements on this page exclude content delivery and traffic in transit — which is processed at the Cloudflare data center closest to the connecting user, globally — as well as backups, diagnostics, email delivery and support access.

Zeus may migrate, or relocate the storage or processing of, any data between facilities and regions at any time.

The Customer's sole right and remedy in respect of any change in processing location is the Subprocessor-objection process referenced in Section 4.

---

4. Objections

4.1 Objection pointer

Objections to any new or replacement Subprocessor published on this page are governed exclusively by Section 6.2 of the DPA: the Customer may object only in writing to [email protected], only on reasonable, documented data-protection grounds, and only within five (5) calendar days of publication of the change on this page.

Where the Customer has not objected within that period in the manner described, the new Subprocessor is deemed accepted by the Customer.

On a valid objection, Zeus's cure options, the Customer's sole and exclusive remedy (termination of only the affected Services with all outstanding amounts payable, no refunds and no further claims), Zeus's interim suspension right, and Zeus's right to elect to terminate the Agreement are those stated in the DPA and the Agreement — this page adds none and removes none.