Xanivar Field

Field — Data Processing Addendum

Pre-release draft — pending legal review

Field has not launched yet. This document is published so it can be reviewed and so the rest of the product can link to it. It has not been finalised by qualified counsel, and text shown in square brackets is still to be settled. It is not a binding agreement in this form. We will publish the final version, with an effective date, before Field is generally available.

Effective date: [INSERT DATE] Last updated: [INSERT DATE]

Final draft for review by Xanivar Labs' legal counsel prior to publication. Items in [brackets] are to be completed by Xanivar Labs.

This Data Processing Addendum ("DPA") forms part of, and is subject to, the Field Terms and Conditions or other written agreement (the "Agreement") between Xanivar Labs Pte. Ltd. (UEN 202607828N), a company incorporated in Singapore ("Xanivar Labs", "we", "us", "Processor"), and the customer organisation that has entered into the Agreement (the "Customer", "you", "Controller"). It records the parties' obligations when Xanivar Labs processes Customer Personal Data on the Customer's behalf in providing the Field service (the "Service").

Where there is a conflict between this DPA and the Agreement in relation to the processing of Customer Personal Data, this DPA prevails. Where there is a conflict between this DPA and the Standard Contractual Clauses (Annex 4), the Standard Contractual Clauses prevail.

1. Definitions

1.1 Capitalised terms not defined here have the meaning given in the Agreement.

1.2 In this DPA:

2. Roles and scope of processing

2.1 For Customer Personal Data, the Customer is the controller and Xanivar Labs is the processor. Where the Customer is itself a processor acting on behalf of a third-party controller, Xanivar Labs is a sub-processor, and the Customer warrants it has the third party's authority to enter into this DPA on its behalf.

2.1A Worker Profile Data is outside this DPA. The Service also maintains a profile that belongs to an individual worker rather than to any one employer — their identity and contact details, the credentials, licences and training records they hold, and their verified work record. That profile follows the individual between employers and is not maintained on the Customer's instructions, so Xanivar Labs is the CONTROLLER of it and it is not Customer Personal Data. It is not processed on the Customer's behalf, is not covered by this DPA, and is not returned or deleted under Section 10 when the Agreement ends. It records the Customer as the employer together with the shape of the work — dates, hours, counts, and whether attendance was verified — and does not include the Customer's clients, the premises at which work was performed, or the Customer's pricing or commercial information. Xanivar Labs' handling of it is described in the Field Privacy Policy.

2.2 Xanivar Labs will process Customer Personal Data only: (a) to provide, secure, and support the Service; (b) in accordance with the Customer's documented instructions (including as configured through the Service and as set out in the Agreement and this DPA); and (c) as required by law, in which case Xanivar Labs will inform the Customer of that legal requirement before processing, unless the law prohibits it.

2.3 The subject matter, duration, nature and purpose of the processing, the types of Customer Personal Data, and the categories of Data Subjects are described in Annex 1.

2.4 Xanivar Labs will inform the Customer if, in its opinion, an instruction infringes Data Protection Laws (without obligation to provide legal advice).

3. Xanivar Labs' obligations

3.1 Confidentiality of personnel. Xanivar Labs will ensure that persons authorised to process Customer Personal Data are subject to appropriate confidentiality obligations and process the data only as instructed.

3.2 Security. Xanivar Labs will implement and maintain the technical and organisational measures described in Annex 2 to protect Customer Personal Data against a personal data breach, taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing.

3.3 Assistance to the Customer. Taking into account the nature of the processing and the information available to it, Xanivar Labs will provide reasonable assistance to the Customer to help it: (a) respond to requests from Data Subjects to exercise their rights (Section 6); (b) ensure the security of processing; (c) notify and communicate personal data breaches (Section 5); and (d) carry out data protection impact assessments and prior consultations with supervisory authorities where required (Section 7).

3.4 No sale of data. Xanivar Labs will not sell Customer Personal Data, will not retain, use, or disclose it for any purpose other than providing the Service (or as otherwise permitted by Data Protection Laws), and will not combine it with other data except as needed to provide the Service.

4. Sub-processors

4.1 The Customer provides general authorisation for Xanivar Labs to engage Sub-processors to process Customer Personal Data. Xanivar Labs' current Sub-processors are listed in Annex 3.

4.2 Xanivar Labs will impose data-protection obligations on each Sub-processor that are no less protective than those in this DPA, and remains responsible for its Sub-processors' performance of those obligations.

4.3 Xanivar Labs will give the Customer notice (for example by email or by updating a published list) before adding or replacing a Sub-processor. The Customer may object on reasonable data-protection grounds within [30] days of notice. If the parties cannot resolve the objection, the Customer may, as its sole remedy, terminate the affected part of the Service.

5. Personal data breach

5.1 Xanivar Labs will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data.

5.2 The notification will include, to the extent known and permitted, the nature of the breach, the categories and approximate number of Data Subjects and records affected, the likely consequences, and the measures taken or proposed. Xanivar Labs will provide further information as it becomes available and reasonable assistance to help the Customer meet its own breach-notification obligations.

5.3 Xanivar Labs' notification is not an acknowledgement of fault or liability.

6. Data subject requests

6.1 If Xanivar Labs receives a request from a Data Subject to exercise rights under Data Protection Laws in respect of Customer Personal Data, it will, unless legally required to respond, direct the Data Subject to the Customer and promptly notify the Customer.

6.2 Xanivar Labs will provide reasonable assistance, including through the functionality of the Service, to enable the Customer to respond to such requests.

7. Impact assessments and consultation

Taking into account the nature of processing and the information available to it, Xanivar Labs will provide reasonable assistance to the Customer with data protection impact assessments and any prior consultation with a supervisory authority that the Customer is required to carry out under Data Protection Laws.

8. International transfers

8.1 Xanivar Labs will not transfer Customer Personal Data to a country outside the country of origin unless it has taken measures necessary to ensure the transfer is lawful under Data Protection Laws.

8.2 EU/EEA and UK transfers. Where Xanivar Labs processes Customer Personal Data subject to the EU GDPR or UK GDPR and transfers it to a country not subject to an adequacy decision, the Standard Contractual Clauses apply and are incorporated into this DPA:

(a) the EU SCCs apply, with Module Two (controller-to-processor) where the Customer is a controller, and Module Three (processor-to-processor) where the Customer is a processor; with the options and annexes completed as set out in Annex 4; and

(b) the UK Addendum applies to transfers subject to the UK GDPR, completed as set out in Annex 4.

8.3 PDPA transfers. For Customer Personal Data subject to the PDPA, Xanivar Labs will take reasonable steps to ensure a standard of protection comparable to the PDPA for any transfer outside Singapore.

8.4 Data residency. Where the Customer selects a data-residency option in the Service (for example, the European Union), Xanivar Labs will store the relevant Customer Personal Data in the selected region in accordance with that configuration.

9. Audit

9.1 Xanivar Labs will make available to the Customer information reasonably necessary to demonstrate compliance with this DPA and Article 28 of the EU/UK GDPR.

9.2 The Customer may audit Xanivar Labs' compliance no more than once per year (unless required more frequently by a supervisory authority or following a personal data breach), on reasonable prior written notice, during business hours, subject to confidentiality, and without unreasonably disrupting Xanivar Labs' operations. Xanivar Labs may satisfy an audit request by providing a recent third-party audit report or security summary where available.

10. Return and deletion

10.1 On expiry or termination of the Agreement, the Customer's account becomes export-only for thirty (30) days. Within that period Xanivar Labs will, at the Customer's choice, delete or return Customer Personal Data and delete existing copies, unless retention is required by law. This is the same period as in Clause 4.4B and Clause 16.4 of the Terms.

10.2 Backups containing Customer Personal Data are deleted in accordance with Xanivar Labs' standard backup-retention cycle. Until deleted, such data remains protected under this DPA.

11. United States — service provider terms

11.1 To the extent the CCPA applies, the Customer is a "business" and Xanivar Labs is a "service provider". Xanivar Labs will not: (a) sell or share Customer Personal Data; (b) retain, use, or disclose it for any purpose other than the business purposes specified in the Agreement, or outside the direct business relationship; or (c) combine it with other personal information except as permitted by the CCPA. Xanivar Labs certifies that it understands and will comply with these restrictions.

12. Liability and precedence

12.1 Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Agreement.

12.2 This DPA is governed by the same law and subject to the same dispute-resolution provisions as the Agreement, except where the Standard Contractual Clauses require otherwise. Except as amended by this DPA, the Agreement remains in full force.

Annex 1 — Details of processing

Annex 2 — Technical and organisational security measures

[Confirm/adjust to match Xanivar Labs' actual controls before publication.]

Annex 3 — Approved Sub-processors

[Confirm exact legal entity, role, and processing location for each before publication.]

Sub-processorPurposeProcessing location
Supabase [Inc. / Pte. Ltd. — confirm entity]Database, authentication, and hosting[Singapore / EU per residency config — confirm]
Cloudflare, Inc.Object storage (R2) for media/files; security and bot protection (Turnstile)[Global / EU jurisdiction bucket per config — confirm]
Postmark (ActiveCampaign, LLC / Wildbit) [confirm entity]Transactional and notification email[United States — confirm]
Product analytics, crash reporting and push notificationsNo additional sub-processor. Field’s product analytics are first-party: events are written to the Supabase database listed above. Web push is self-hosted (VAPID). There is no third-party analytics, crash-reporting or push vendor.As per Supabase, above

Annex 4 — Standard Contractual Clauses: completed options

EU SCCs (Decision 2021/914):

UK Addendum:

Signatures

Controller (Customer) Name: ______________________ Title: ______________________ Date: __________

Processor — Xanivar Labs Pte. Ltd. Name: ______________________ Title: ______________________ Date: __________

This document should be reviewed and approved by Singapore-qualified counsel (and, for the SCCs/UK Addendum, EU/UK-qualified counsel) before use. Keep Annexes 2 and 3 current as your controls and sub-processors change.


Terms · Privacy Policy · Authorized User Terms · Cookie Policy · Privacy settings · Delete account