Data Processing Agreement – Fieldmind AS
This Data Processing Agreement (the "DPA") is entered into between:
- (a) Customer, acting as data controller (the "Controller"), and
- (b) Fieldmind AS (organization number 934 997 557), acting as data processor (the "Processor"), with address Gaustadalleen 21, 0349 Oslo, Norway.
Each of the Controller and the Processor is a "Party" and together the Controller and the Processor are the "Parties".
1. Introduction and Background
1.1 The purpose of this DPA is to set out the terms under which the Processor processes personal data on behalf of the Controller in accordance with Article 28(3) Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC ("GDPR"), and adjacent laws applicable to the Parties ("Applicable Data Protection Law").
1.2 This DPA applies to the Processor's processing of personal data on behalf of the Controller in connection with the services described in Annex 1 (the "Service").
1.3 In the event of a conflict between this DPA and any other agreement between the Parties concerning the processing of personal data in connection with the Service, this DPA shall prevail to the extent necessary to address such conflict for the processing described in Annex 1.
1.4 This DPA does not reduce or replace any mandatory obligations that apply to either Party under Applicable Data Protection Law.
1.5 Capitalized terms not otherwise defined in this DPA have the meaning given to them under Applicable Data Protection Law (where relevant) and otherwise shall be interpreted in a manner consistent with that law.
2. The Rights and Obligations of The Controller
2.1 The Controller is responsible for ensuring that the processing of personal data using the Service is lawful, including determining the purposes and essential means of the processing.
2.2 The Controller is responsible for ensuring it has a valid legal basis for the processing, including where it chooses to process special categories of data and/or criminal offence data through the Service.
2.3 The Controller is responsible for the lawfulness of the personal data it uploads, imports, generates, or otherwise makes available to the Processor through the Service, including personal data relating to third parties (such as farmers) where the Controller's primary users are agricultural advisors.
2.4 Where the Controller is subject to sector-specific rules, regulator requirements, or internal security requirements that go beyond the Processor's standard measures, the Controller shall notify the Processor in writing and describe the additional requirements. The Parties shall discuss in good faith whether such requirements can be supported, including any impact on the Service and any additional costs.
3. The Rights and Obligations of the Processor
3.1 The Processor shall process personal data only on Documented Instructions, as defined below, from the Controller unless required to do so by Applicable Data Protection Law to which the Processor is subject.
3.2 Documented Instructions include:
- (a) the Controller's configuration and use of the Service through its normal functionality (including user management, permissions, data sharing settings, integrations, and workflows);
- (b) written instructions sent by the Controller to the Processor via the agreed contact channels; and
- (c) instructions submitted via the Processor's support channels by the Controller's authorized users.
3.3 The Processor shall inform the Controller without undue delay if, in the Processor's opinion, an instruction infringes GDPR or Applicable Data Protection Law.
3.4 The Processor shall ensure that any person acting under its authority who is authorized to process personal data is bound by a duty of confidentiality, whether by contract or by an applicable statutory obligation, and is permitted to access such personal data only to the extent necessary for the performance of their duties.
3.5 The Processor shall, upon request, make available information reasonably necessary for the Controller to complete records of processing activities under Article 30 GDPR, limited to the Processor's role and processing under this DPA.
4. Security of The Processing
4.1 Taking into account the nature of processing, the Processor shall assist the Controller, by appropriate technical and organizational measures, insofar as possible and to the extent applicable to the processing under this DPA, for the fulfilment of the Controller's obligation to respond to requests for exercising data subject rights under Chapter III GDPR and assist the Controller in ensuring compliance with the Controller's obligations pursuant to Articles 32 to 36 GDPR.
4.2 The Processor's technical and organizational measures are described in Annex 2. The Processor may update the measures from time to time, provided that such updates do not materially reduce the overall security level.
5. Use of Sub-Processors
5.1 The Controller grants the Processor a general authorization to engage sub-processors in accordance with this Clause 5 and the Processor shall maintain an up-to-date list of approved sub-processors in Annex 3.
5.2 The Processor shall notify the Controller of any intended addition or replacement of sub-processors in advance, giving the Controller an opportunity to object on reasonable data protection grounds.
5.3 If the Controller objects, the Parties shall discuss in good faith a commercially reasonable solution. If no solution is agreed, either Party may terminate this DPA upon written notice with effect from the date the change would otherwise take effect. If the Controller also has a separate commercial agreement for the Service, termination of that agreement is handled outside the DPA.
5.4 Any request by the Controller to change sub-processors, including any associated data migration required as a result of such change, shall be at the Controller's expense.
5.5 The Processor shall ensure that each sub-processor is bound by written terms that impose data protection obligations no less protective than those set out in this DPA (as applicable to the sub-processor's services).
5.6 The Processor remains liable to the Controller for the performance of its sub-processors.
6. International Transfers
6.1 Where processing under this DPA involves a transfer of personal data to a country outside the EU/EEA (whether by the Processor, the Controller, or a sub-processor), such transfer shall take place only in accordance with applicable data transfer requirements under Applicable Data Protection Law.
6.2 Where a sub-processor involves international transfers, the relevant transfer mechanism shall be documented in Annex 3 or otherwise provided to the Controller in writing.
7. Personal Data Breach Notification
7.1 In the event of a personal data breach, the Processor shall notify the Controller without undue delay after becoming aware of the breach.
7.2 The notification shall include information that enables the Controller to meet its obligations under Articles 33 and 34 GDPR, to the extent such information is available to the Processor, including (i) the nature of the breach, (ii) categories and approximate number of data subjects concerned, (iii) categories and approximate number of personal data records concerned, (iv) likely consequences, and (v) measures taken or proposed to address the breach and mitigate adverse effects.
8. Audits
8.1 The Processor shall, upon reasonable request, make available information reasonably necessary to demonstrate compliance with this DPA.
8.2 The Controller may request and carry out an audit of the Processor's compliance with this DPA once per calendar year. The Controller may also request an additional audit if there are reasonable grounds, including a material personal data breach affecting the Controller's personal data, credible indications of material non-compliance, or a binding request from a competent supervisory authority.
8.3 As a default, audits shall be performed as a documentation audit. Documentation may include relevant policies, procedures, security summaries, certifications, statements of applicability, and independent assurance reports, subject to appropriate confidentiality obligations.
8.4 Where the Controller demonstrates a documented and reasonable need that cannot be satisfied through a documentation audit, the Controller may request an on-site audit. The Parties shall agree on the scope, timing, and practical arrangements in advance. The audit shall be limited to what is necessary and proportionate, shall not unreasonably interfere with the Processor's operations, and shall not compromise the confidentiality or security of other customers.
8.5 The Controller shall provide reasonable prior written notice of any audit request. Unless urgent circumstances apply, such notice shall be at least thirty (30) days.
8.6 If any audit does not identify material non-compliance by the Processor, the Controller shall bear all costs of the audit, including the Processor's reasonable costs. In all other cases, each Party shall bear its own costs of the audit. For the purpose of this clause, "material non-compliance" means non-compliance that is not trivial and that has caused, or is reasonably likely to cause, a significant risk to the rights and freedoms of data subjects, or a significant failure to meet the Processor's core obligations under Article 28 GDPR and this DPA.
9. Return and Deletion of Personal Data
9.1 Upon termination of the Service, the Processor shall, at the choice of the Controller, delete or return all personal data to the Controller and delete existing copies, unless Union or Member State law requires storage.
9.2 Unless the Controller instructs otherwise in writing, the Processor shall complete deletion of personal data no later than six (6) months after termination, unless the Processor is required by applicable law to retain certain personal data for a longer period.
9.3 For cloud deployments, deletion includes data in primary systems and copies under the Processor's control. Handling of backups shall follow the Processor's backup lifecycle, provided that backup copies are protected and are deleted or overwritten within the six (6) month period, unless technically infeasible. If technically infeasible, the Processor shall inform the Controller and agree to an alternative deletion timeline in writing.
10. Data Use Restrictions
10.1 The Processor may process personal data to provide the Service functionality that is explicitly requested by the Controller, which may include AI assisted features such as transcription, summarization, and redaction, to the extent such features are enabled and configured by the Controller.
10.2 The Processor may use test data for development and testing. Test data shall, as a default, be synthetic or anonymized.
10.3 Where AI-assisted features are provided through a sub-processor, the Processor shall ensure that such sub-processor is subject to the obligations in this DPA.
11. Liability
11.1 Unless otherwise agreed in writing between the Parties, each Party shall be responsible for its own compliance with this DPA and Applicable Data Protection Law. The Controller shall be liable for damage caused by processing that infringes the GDPR. The Processor shall be liable only where it has failed to comply with obligations specifically directed to processors or has acted outside or contrary to the Controller's lawful instructions, in each case in accordance with Article 82 GDPR.
11.2 Nothing in this DPA shall be construed to limit either Party's liability to data subjects or supervisory authorities where such limitation is prohibited by applicable law.
12. Term and Termination
12.1 This DPA takes effect when the Processor begins processing personal data on behalf of the Controller in connection with the Service.
12.2 This DPA terminates when the provision of the Service terminates, subject to Clause 9 (Return and deletion of personal data).
13. Miscellaneous
13.1 Each Party shall designate contact points for data protection and security matters and shall keep such information up to date.
13.2 Unless otherwise agreed, this DPA shall be construed in accordance with laws of Norway.
13.3 Unless otherwise agreed, any dispute or claim arising out of this DPA shall be subject to the exclusive jurisdiction of Oslo District Court.
Annex 1 – Description of Processing
Description, purpose and nature of the processing
The Service is a digital platform built for agricultural advisory workflows, intended to simplify fieldwork documentation, reporting, knowledge sharing, and to provide a farm overview, including visit history and generated summaries/reports.
Processing is performed solely to provide the Service on behalf of the Controller and its authorized users (for example advisors). Processing may include:
- collecting and importing data;
- capturing and uploading content from mobile devices; and
- storing, organizing, indexing, searching, displaying, editing, generating reports/summaries, sharing (including within the Controller's organization), exporting, audit logging, access control, customer support, maintenance, and incident handling.
The Service may include an end-user view for farmers (e.g., "My Page / Min side") if enabled by the Controller, allowing the farmer to view information related to their farm and history, and to express preferences regarding internal sharing of certain farm-related information within the Controller's organization, as configured by the Controller.
Processing occurs for the duration of the Controller's use of the Service, and thereafter until deletion/return in accordance with Clause 9.
Categories of data subjects and personal data
Depending on what the Controller uploads or otherwise processes through the Service, the Processor will process the following categories of personal data:
- (a) Identity and contact information (e.g., name, email, phone number, postal address);
- (b) Identifiers and reference numbers used to identify a farm/operation, including producer number (produsentnummer) and any related organization number, to the extent such identifiers relate to an identifiable person;
- (c) location-related data and property/field identifiers (e.g., municipality number, farm and usage numbers (gårds- og bruksnummer)) to the extent they are linked to an identifiable person;
- (d) Content uploaded or captured by users in the field (e.g., GPS-tagged notes/images, documents, reports);
- (e) Access logs, audit trails, and system usage metadata.
Relevant categories of data subjects may include: the Controller's users (such as employees and contractors acting as agricultural advisors), farmer contacts and farm representatives, and any other individuals whose personal data is included in content uploaded to or generated within the Service.
The Service is not designed for any specific special category of data as such. However, special categories of data and/or criminal offence data may be processed depending on what the Controller chooses to input into free-text fields, uploads, or attachments, and the Controller's legal mandate and instructions.
Sources of personal data and integrations
The Service may process personal data that is (i) provided directly by the Controller (including extracts from the Controller's CRM or other internal systems), and/or (ii) retrieved via third-party data sources or integrations configured by the Controller (for example through a Controller-provided API key and/or credentials), where the Controller is responsible for ensuring it has the required rights/authorizations and legal basis for such retrieval and onward processing.
Annex 2 – Technical and Organizational Measures
Security governance and Cloud infrastructure and platform security
The Service is hosted and operated using Google Cloud Platform and Firebase services as applicable. The Processor relies on the security measures implemented by Google for the underlying infrastructure and platform layers (including technical, organizational, and physical measures) as described in Google's applicable data processing and security terms for such services. These measures include, as applicable:
- physical security of datacentre facilities;
- redundancy and resilience measures for infrastructure;
- encryption in transit (e.g., HTTPS/TLS) and encryption capabilities for data;
- access controls and privilege management for production systems;
- logging and monitoring capabilities; and
- personnel security and confidentiality obligations.
The Controller may find more information here Firebase Data Processing and Security Terms and here Cloud Data Processing Addendum | Google Cloud.
Encryption and key management
Where relevant to the Service, the Processor will use available logging/monitoring capabilities to support security operations and incident investigation, consistent with the Google/Firebase incident notification and security documentation mechanisms described in the terms referenced above.
Logging, monitoring, and accountability
Where relevant to the Service, the Processor will maintain appropriate operational logging/monitoring and will use available information to support breach investigation and communications, consistent with Google/Firebase incident notification and security documentation mechanisms, as elaborated in the links above.
Business continuity, backup, and recovery
The Processor maintains backup and recovery measures designed to support business continuity and restoration of availability and access to personal data in a timely manner following an incident. Backups are protected through access restrictions and security controls appropriate to the risk. The Processor maintains and tests recovery procedures at appropriate intervals.
Data return and deletion
Upon termination, the Processor maintains procedures to return and/or delete personal data in accordance with Clause 9 of this DPA.
Annex 3 – Approved Sub-processors
The sub-processors listed below are approved as of the date this DPA commences pursuant to Clause 12.
| Sub-processor legal name | Service provided | Processing location(s) | International transfers and mechanism |
|---|---|---|---|
| Google Cloud EMEA Limited | Google Cloud Platform (cloud infrastructure hosting for the Service) | Ireland (Belgium and Finland) | SCCs |
| Google Cloud EMEA Limited | Firebase (mobile/app platform services, as applicable to the Service) | Ireland (Belgium and Finland) | SCCs |
| PostHog, Inc | Product analytics and user behavior tracking | Germany | SCCs |