This is an English translation provided for convenience. The Polish version is the original and prevails in the event of any discrepancies.

Data Processing Agreement

Part III of the geoGPS Service documentation. Last updated: 18 October 2026. Version 1.2.

This Data Processing Agreement (the “Agreement”) sets out the terms on which ENCOM Sp. z o.o. processes the personal data contained in the Content entered into the geoGPS System by the Organization. The Agreement is an annex to the Terms of Service of the geoGPS System (Part I, geogps.cloud/terms/en/) and is the contract referred to in Article 28(3) of the GDPR.

§ 1. Parties and conclusion of the Agreement

1. The parties to the Agreement are: (i) the entity on whose behalf the Organization was registered in the geoGPS System (the “Controller”), and (ii) ENCOM Sp. z o.o. with its registered office in Kraków, ul. Rzemieślnicza 1, 30-363 Kraków, Poland, KRS 0000345997, NIP (tax ID) 6793026054 (the “Processor”).

2. The Agreement is concluded in electronic form (Article 28(9) of the GDPR) at the moment the Manager accepts the Terms of Service when registering the Organization. The Processor keeps a record of the acceptance (document version, date, IP address and channel) on the terms described in the Privacy Policy.

3. The Manager declares that they are authorised to conclude the Agreement on behalf of the Controller (§ 3(5) of the Terms of Service).

4. At the Controller's request sent to data-protection@geogps.cloud, the Processor will make the Agreement available as a PDF file bearing the qualified electronic signature of a person authorised to represent the Processor. The content of such a copy is identical to this Agreement.

5. If the Controller processes the data contained in the Content on behalf of another entity (e.g. its own client), the Processor acts as a sub-processor, and the Controller declares that it is entitled to further entrust the processing on the terms of the Agreement. The provisions of the Agreement then apply accordingly.

6. Capitalised terms not defined in the Agreement have the meaning given to them in the Terms of Service.

§ 2. Scope of application

1. The Agreement applies only to the personal data contained in the Content, that is in the Projects, layers, objects, attributes, forms, notes, photos and other attachments entered into geoGPS Cloud by the Organization's Users (the “Entrusted Data”).

2. The Agreement does not apply to data that the Processor processes as a separate controller – in particular Account data, billing data, evidence of acceptance of the Terms of Service, security logs and correspondence. The rules for processing such data are described in the Privacy Policy (Part II).

§ 3. Subject matter, nature, purpose and duration of the processing

1. The Controller entrusts the Processor with the processing of the Entrusted Data, and the Processor undertakes to process it in accordance with the Agreement, the Terms of Service and the law.

2. Purpose of the processing: providing the Service to the Organization, that is storing and synchronising the Content between the App, the Web Panel and the QGIS Plugin, making it available to the Organization's authorised Users, export, making backups, ensuring the security of the Service and technical support provided at the Organization's request.

3. Nature of the processing: processing in an IT system, by automated means, including recording, storage, organisation, viewing, making available to the Organization's Users, modification on a User's instruction, making backups and erasure.

4. Duration of the processing: the term of the agreement for the provision of the Service and the period necessary to return and erase the data after it ends, set out in § 11.

§ 4. Type of data and categories of data subjects

1. The scope of the Entrusted Data depends on what Content the Organization enters into the Service. It typically includes:

Categories of data subjects

Types of data

Owners, holders and users of real estate, residents, recipients of services and business partners of the Organization

first name and last name or business name, address, property designation (parcel number, cadastral precinct, cadastral identifiers), contact details, information recorded in object attributes, forms and notes

Persons captured in photos and other attachments

image, vehicle registration numbers, view of property, other information visible in the photo

The Manager and Employees of the Organization – to the extent their data is part of the Content

identification of the author of an object or measurement, date and time of the measurement, location of the measured objects and recorded tracks, content of notes

2. The Service is not intended for processing special categories of data (Article 9 of the GDPR) or data relating to criminal convictions and offences (Article 10 of the GDPR). The Controller undertakes not to enter such data into the Service without prior agreement with the Processor in documentary form.

§ 5. Controller's instructions

1. The Processor processes the Entrusted Data only on documented instructions from the Controller. The following are regarded as documented instructions: (i) the Agreement and the Terms of Service, (ii) actions performed in the Service by the Manager and the Employees, including configuration of the Organization, granting permissions, exporting and deleting data, (iii) instructions given in documentary form from the Manager's e-mail address.

2. The Processor immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or other data protection provisions, and may suspend its execution until the matter is clarified.

3. If European Union law or Polish law requires the Processor to process the Entrusted Data, the Processor informs the Controller of that requirement before the processing begins, unless that law prohibits such information on important grounds of public interest.

4. The Processor does not use the Entrusted Data for its own purposes, including marketing purposes or training machine-learning models.

§ 6. Processor's obligations

1. The Processor ensures that the persons authorised to process the Entrusted Data have committed themselves to confidentiality or are under a statutory obligation of confidentiality, and that access to the data is held only by persons who need it to provide the Service.

2. The Processor applies the technical and organisational measures required under Article 32 of the GDPR, described in the Security Specification (Part V, geogps.cloud/security/en/). The Processor may change them, provided that the change does not lower the level of protection.

3. Taking into account the nature of the processing, the Processor assists the Controller in fulfilling its obligation to respond to requests from data subjects (Chapter III of the GDPR), in particular by providing functions in the Service for viewing, correcting, exporting and deleting the Content. A data subject's request addressed directly to the Processor is forwarded by the Processor to the Manager within 5 business days, and the Processor does not respond to it on its own as regards the Entrusted Data.

4. Taking into account the nature of the processing and the information available to it, the Processor assists the Controller in complying with the obligations set out in Articles 32–36 of the GDPR, including by providing the information needed for a data protection impact assessment.

5. The Processor keeps a record of the categories of processing activities carried out on behalf of controllers (Article 30(2) of the GDPR).

§ 7. Controller's obligations

1. The Controller declares that it processes the Entrusted Data lawfully, in particular that it has a legal basis for processing it and fulfils the information obligations towards data subjects.

2. The Controller is responsible for: the scope of the data entered into the Service (the principle of data minimisation), creating and deleting Employee Accounts and granting them permissions, securing the Devices and credentials of its Users, and keeping up to date the Manager's e-mail address to which the Processor sends the notifications provided for in the Agreement.

3. The Controller promptly informs the Processor of any circumstances affecting the performance of the Agreement, including a suspicion of unauthorised access to an Account (security@geogps.cloud).

§ 8. Sub-processing (sub-processors)

1. The Controller gives the Processor a general authorisation to engage further processors (“Sub-processors”). The current list of Sub-processors constitutes Part IV of the Service documentation and is published in section 5.2 of the Privacy Policy.

2. The Processor informs the Controller of its intention to add or replace a Sub-processor at least 14 days in advance, by a message to the Manager's e-mail address, indicating the Sub-processor, its role and the place of processing.

3. Within 14 days of receiving the information, the Controller may object on justified grounds relating to data protection, by writing to data-protection@geogps.cloud. The Parties will attempt in good faith to remove the grounds for the objection. If this proves impossible, the Controller may terminate the agreement for the provision of the Service with effect on the day preceding the start of processing by the new Sub-processor; the unused part of the subscription fee is then refunded proportionally. No objection within the time limit means consent to the change.

4. Where a Sub-processor urgently needs to be replaced for reasons of security or continuity of the Service, the Processor may shorten the time limit referred to in paragraph 2, informing the Controller without undue delay; the Controller's rights under paragraph 3 remain unchanged.

5. The Processor imposes on every Sub-processor, by way of a contract, data protection obligations no less strict than those arising from the Agreement, in particular the obligation to apply appropriate technical and organisational measures. The Processor is liable to the Controller for the acts and omissions of the Sub-processors as for its own.

§ 9. Place of processing and transfers of data outside the EEA

1. The Entrusted Data, together with backups, is stored in the European Economic Area, in a data centre in the European Union.

2. The Processor does not transfer the Entrusted Data to a third country or an international organisation without a documented instruction from the Controller. Should such a transfer result from a change of Sub-processor, the procedure in § 8 applies, and the transfer takes place only in compliance with the conditions of Chapter V of the GDPR.

3. The Firebase (Google) services indicated in the list of Sub-processors are used only to deliver one-time login codes and system notifications and to diagnose App crashes. No Entrusted Data or other parts of the Content are transmitted through them; with respect to the Entrusted Data, Google is not a Sub-processor.

§ 10. Personal data breaches

1. The Processor notifies the Controller of a breach of the Entrusted Data without undue delay, no later than within 48 hours of becoming aware of it, at the Manager's e-mail address.

2. The notification contains the information that the Processor has at that time, and at least: a description of the nature of the breach, where possible the categories and approximate number of data subjects and records concerned, the likely consequences, the remedial measures taken or proposed, and the contact details of the person providing the information. If the information cannot be provided at the same time, the Processor provides it in phases: an update within 72 hours of becoming aware of the breach and a final report within one month (§ 15a(2) of the Terms of Service).

3. The Processor promptly takes action to limit the effects of the breach and documents its circumstances, effects and the remedial actions taken.

4. Notification of the breach to the supervisory authority and communication to data subjects are carried out by the Controller. The Processor provides the Controller with the necessary assistance in this respect and does not inform third parties of the breach without agreement with the Controller, unless such an obligation arises from the law.

§ 11. End of processing – return and erasure of data

1. Throughout the term of the agreement, the Controller may itself download the Entrusted Data in the export formats available in the Service and delete it.

2. After termination of the agreement for the provision of the Service, the Processor enables the Controller to download the Entrusted Data for 30 days (§ 20(5) and § 20a of the Terms of Service), and then permanently erases it from the production system.

3. Deletion of the Organization by the Manager is an instruction to erase the Entrusted Data immediately; in that case the period referred to in paragraph 2 does not apply, and the erasure is irreversible.

3a. If the Organization has had no active Subscription continuously for 90 days, the agreement for the provision of the Service is terminated and the Processor permanently and irreversibly erases the Entrusted Data from the production system, on the terms set out in § 20(2a) of the Terms of Service, after notifying the Manager at least 14 days in advance. The period referred to in paragraph 2 does not apply in that case.

4. The Entrusted Data is erased from backups in the backup rotation cycle described in the Security Specification (Part V). Until then, the backups remain encrypted and are not used for purposes other than restoring the Service after a failure.

5. The Processor may keep the data longer only to the extent required by European Union law or Polish law. At the Controller's request, the Processor confirms the erasure of the data in documentary form.

§ 12. Audits and information

1. The Processor makes available to the Controller the information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR, in particular: the Security Specification, the list of Sub-processors, information on the certificates of the infrastructure provider and answers to a security questionnaire.

2. If the information referred to in paragraph 1 proves insufficient, the Controller or an auditor authorised by it, bound by a duty of confidentiality and not being a competitor of the Processor, may conduct an audit. An audit requires at least 30 days' prior notice and agreement on its date and scope, takes place during the Processor's working hours, no more than once a year and at the Controller's expense – unless the law, a decision of the supervisory authority or an established breach of the Entrusted Data justifies an additional audit.

3. An audit does not include access to the data of the Processor's other customers or to information whose disclosure could weaken the security of the Service. As regards the Sub-processors' infrastructure, the audit is carried out by making their certificates, reports and documentation available.

4. The Processor remedies the deficiencies found in the course of an audit within a period agreed with the Controller, appropriate to their seriousness.

§ 13. Liability

1. Each Party is liable to data subjects on the terms set out in Article 82 of the GDPR.

2. The Processor is liable to the Controller for damage caused by processing the Entrusted Data in breach of the Agreement or of the provisions of the GDPR addressed directly to processors. As between the Parties, the rules and limitations of liability set out in § 17 of the Terms of Service apply, subject to mandatory provisions of law.

§ 14. Remuneration

The Processor's remuneration for performing the Agreement is included in the subscription fee. Activities going beyond the standard functions of the Service – in particular participation in an on-site audit or preparation of non-standard reports – are performed by the Processor after their scope and cost have been agreed with the Controller.

§ 15. Final provisions

1. The Agreement remains in force for the term of the agreement for the provision of the Service and, as regards the obligations concerning confidentiality and the return and erasure of data – until they have been performed.

2. In matters concerning the protection of the Entrusted Data, in the event of a discrepancy between the Agreement and the Terms of Service, the provisions of the Agreement prevail.

3. The Agreement is amended in the procedure provided for amending the Terms of Service (§ 22 of the Terms of Service). A change to the list of Sub-processors takes place in the procedure set out in § 8 and does not constitute an amendment to the Agreement.

4. The Agreement is governed by Polish law. Disputes are settled by the court having jurisdiction under § 23 of the Terms of Service.

5. Contact in matters concerning the Agreement: data-protection@geogps.cloud; security reports: security@geogps.cloud.