This is an English translation provided for convenience. The Polish version is the original and prevails in the event of any discrepancies.
Last updated: 18 October 2026. Version 1.2.
This Policy describes what personal data we collect in connection with the use of the geogps.cloud website, the web application (Web Panel), the geoGPS mobile app and the geoGPS QGIS plugin, for what purposes we process it, with whom we share it, where it is stored and what rights data subjects have.
1.1. The controller of personal data is ENCOM Sp. z o.o. with its registered office in Kraków, ul. Rzemieślnicza 1, 30-363 Kraków, Poland, entered in the register of entrepreneurs of the National Court Register kept by the District Court for Kraków-Śródmieście in Kraków, 11th Commercial Division of the National Court Register, under KRS number 0000345997, NIP (tax ID) 6793026054, REGON 121126530.
1.2. Contact in data protection matters: data-protection@geogps.cloud or in writing to the address of the registered office, marked “Personal data” (“Dane osobowe”).
1.3. We have not appointed a data protection officer; in all matters concerning personal data, please contact us at data-protection@geogps.cloud.
2.1. The Policy applies to data that we process as a controller, that is the data of users and of persons who contact us.
2.2. The Policy does not cover personal data contained in the Projects and Content entered into the Service by the customer (e.g. data of parcel owners, residents, employees). With respect to that data, the customer is the controller and we act as a processor on the terms described in the Data Processing Agreement (Part III of the Service documentation, geogps.cloud/dpa/en/). Persons whose data is contained in Projects should address requests concerning that data first to the Organization that entered it; requests addressed to us are forwarded to that Organization.
2.3. The Policy does not apply to third-party websites and services to which we link.
If your Account was created by the person managing the Organization (e.g. your employer or client), we received your data – first name and last name, e-mail address, role and membership of the Organization – from that Organization (Article 14 of the GDPR).
When you log in, we process a one-time verification code (stored exclusively as a cryptographic hash and valid for 3 minutes), the device's notification token (Firebase Cloud Messaging) by means of which the code is delivered, and information on login and password reset attempts (including the IP address), in order to protect the Account against unauthorised access and to limit the number of attempts.
The mobile app, within the scope of the functions started by the user, processes positioning data from the device's GNSS receiver or from an external receiver. This data includes coordinates, height, accuracy, timestamp and position quality parameters and, when corrections are used – the NTRIP stream identifier and the approximate position sent to the correction service (the NMEA GGA message).
Location data saved in the layers of a Project constitutes the customer's Content and is subject to the rules in section 2.2. Location data processed by us as a controller is limited to the necessary technical minimum, such as passing the position to the correction service and diagnostic records.
We remove location metadata (GPS coordinates stored in EXIF) from photos attached to objects; the location of an object is determined solely by its position in the Project layer. Other technical metadata of a photo (e.g. the date it was taken, the device model) may be retained. Photos may capture the image of persons or their property – they then constitute the customer's Content (section 2.2).
When you use public services (e.g. parcel search in the ULDK service, WMS/WMTS base maps of the Polish Head Office of Geodesy and Cartography) or download geoid models from cdn.proj.org, your device connects directly to the servers of those entities, which receive the IP address and the request parameters (e.g. coordinates or map extent). Those entities process this data as separate controllers, on the terms set out in their own documents.
Permission | What it is needed for | Effect of refusal |
|---|---|---|
Location (precise) | GNSS positioning, measuring points, navigating to an object, passing the position to the RTK correction service | No measuring or navigation; work only on manually entered data |
Background location | Continuous track recording with the screen off, if the function has been enabled by the user | Track recording is interrupted when the app is minimised |
Camera | Photo documentation of objects, attachments to forms | Photos cannot be added from the camera |
Storage / files | Import and export of data, saving offline maps, attachments | No import, export or offline maps |
Bluetooth | Connection to an external GNSS receiver | Work only with the built-in receiver |
Notifications | Delivering one-time login codes, information on completed synchronisation, conflicts and task status | No push notifications; the login code may need to be delivered in another way |
Background activity / disabling battery optimisation | Completing the synchronisation of large data sets | Synchronisation may be interrupted by the system |
Permissions are requested at the moment a given function is first used and can be withdrawn in the operating system settings.
We do not intentionally collect special categories of data (Article 9 of the GDPR) or data relating to criminal convictions. If the customer enters such data into a Project, it does so at its own responsibility as a controller; the legal basis and the assessment of admissibility are provided by the customer.
Purpose of processing | Legal basis | Retention period |
|---|---|---|
Creating and maintaining the Account, providing the Service, synchronising Projects, technical support | Article 6(1)(b) of the GDPR – performance of a contract | For the term of the agreement and 30 days after its termination or after deletion of the Account or the Organization (the period for downloading data); the data is then deleted, and from backups – in their rotation cycle. An Organization that has had no active Subscription continuously for 90 days is permanently deleted together with its data, without an additional period for downloading it (section 7a.4) |
Evidence of acceptance of the Terms of Service and of having read the Privacy Policy (document version, date, IP address, client identifier, channel – app, panel or QGIS Plugin) and the Manager's declarations on the authorisation of an Employee | Article 6(1)(b) and (f) of the GDPR – performance of a contract and the legitimate interest consisting in demonstrating the conclusion of the contract and defending against claims | For the term of the agreement and, after deletion of the Account – until the limitation period for claims expires |
Logging in, two-step verification, limiting the number of login and password reset attempts | Article 6(1)(b) and (f) of the GDPR – performance of a contract and the legitimate interest consisting in protecting Accounts | Verification code: 3 minutes (the record is deleted after 24 hours at the latest); data on failed login attempts and on password reset attempts: 2 days |
Billing, invoicing, handling payments | Article 6(1)(b) and (c) of the GDPR – contract and tax and accounting obligations | 5 years counted from the end of the calendar year in which the tax payment deadline passed |
Ensuring the security of the Service, detecting abuse, system logs | Article 6(1)(f) of the GDPR – the legitimate interest consisting in protecting the system and the users | API access log and error log: 90 days; records concerning incidents: until the investigation is completed and the related claims become time-barred |
Handling complaints and requests | Article 6(1)(b), (c) and (f) of the GDPR | Until claims become time-barred, as a rule 6 years (3 years for claims related to business activity) |
Establishing, pursuing and defending claims | Article 6(1)(f) of the GDPR | Until the limitation periods expire |
Detecting and fixing App crashes (Firebase Crashlytics) | Article 6(1)(f) of the GDPR – the legitimate interest consisting in ensuring the stability and security of the App | 90 days |
App usage statistics (Firebase Analytics) | Article 6(1)(a) of the GDPR – consent given at installation or in the App settings | Until consent is withdrawn, no longer than 14 months; pseudonymised data (installation identifier) |
Marketing of our own services to existing customers | Article 6(1)(f) of the GDPR | Until an objection is raised |
Fulfilling legal obligations (including requests from authorised authorities, obligations under the DSA) | Article 6(1)(c) of the GDPR | For the period required by law |
Providing data is voluntary, but necessary to create an Account and use the Service. Failure to provide billing data makes it impossible to conclude a paid agreement.
5.1. Data may be disclosed to the following categories of recipients: providers of infrastructure and hosting services, payment operators, providers of error monitoring and messaging tools, law firms, accounting offices, auditors and entities authorised under the law.
5.2. List of entities processing data on our behalf (sub-processors) – which also constitutes Part IV of the Service documentation:
Entity | Role | Location of processing | Basis |
|---|---|---|---|
home.pl sp. z o.o. (Szczecin, Poland) | VPS server (geoGPS Cloud database, files, backups), a separate server storing encrypted backups, sending e-mail messages | Data centres in the European Union | Data processing agreement (Article 28 of the GDPR) |
Google Ireland Limited (Dublin, Ireland), together with Google LLC (USA) | Firebase Crashlytics (crash reports), Firebase Cloud Messaging (push notifications, login codes), Firebase Analytics (only with consent) | EU and USA | Google's data processing terms (Article 28 of the GDPR); transfer to the USA – section 6.2 |
We inform Organizations of a planned change of sub-processors at least 14 days in advance, on the terms set out in the Data Processing Agreement.
5.3. Payments for Packages A/B/C purchased in the App are handled by Google as part of Google Play Billing. Google processes payment data as a separate controller, in accordance with its privacy policy (policies.google.com/privacy); from Google we receive only information on the subscription status and the purchase identifier.
5.4. Every entity processing data on our behalf acts on the basis of a data processing agreement meeting the requirements of Article 28 of the GDPR.
5.5. We do not sell personal data or make it available to data brokers. We do not use customers' Content to train machine-learning models, unless the customer gives separate, explicit consent to this.
6.1. We process and store geoGPS Cloud data – Accounts, Projects, Content, photos and backups – in the European Economic Area, on a VPS server provided by home.pl sp. z o.o. and located in a data centre in the European Union. We additionally keep encrypted backups on a separate server of the same provider, also in the European Union, and on an encrypted external medium that we keep in a safe, in a location separate from the data centre. Storing data in the European Union does not constitute a transfer of data to a third country.
6.2. Only data processed by the Firebase services (section 5.2) may be transferred outside the EEA – to Google LLC in the USA. The basis for the transfer is the European Commission's implementing decision of 10 July 2023 on the adequate level of protection of personal data under the EU-US Data Privacy Framework (Google LLC is certified) and, additionally, the standard contractual clauses adopted by the Commission (Article 46(2)(c) of the GDPR).
6.3. A copy of the safeguards applied can be obtained by writing to data-protection@geogps.cloud.
You have the right to:
Requests can be submitted to data-protection@geogps.cloud. We respond without undue delay, no later than within one month; in complex cases the time limit may be extended by a further two months, of which we will inform you. We may ask for additional information to confirm the identity of the person making the request.
7a.1. The Accounts of the members of an Organization are deleted by the User who registered the Organization. If you are a member of an Organization and want to delete your Account, contact that person or write to data-protection@geogps.cloud – we will forward the request to the Organization and confirm to you that it has been carried out, and as regards the data of which we are the controller, we will consider it directly under Article 17 of the GDPR.
7a.2. The Manager of an Organization may delete the Organization together with all its Accounts, Projects and Content. The deletion is irreversible; the data that is needed should be downloaded beforehand.
7a.3. After deletion, the data is promptly removed from the production system, and from backups – in their rotation cycle. Data that the law requires us to keep (e.g. billing data) is kept for the periods indicated in section 4.
7a.4. An Organization that has had no active Subscription continuously for 90 days (counted from the end of the last paid billing period or, if a Subscription has never been purchased, from the registration of the Organization) is permanently and irreversibly deleted together with all its Accounts, Projects and Content, in accordance with § 20(2a) of the Terms of Service. At least 14 days beforehand, we send the Manager a warning to the e-mail address assigned to their Account. Purchasing or renewing a Subscription before that period expires prevents the deletion. Section 7a.3 applies to the deletion.
We do not make decisions based solely on automated processing that would produce legal effects or similarly significantly affect data subjects. We use automatic anti-fraud and abuse-limiting mechanisms (e.g. detection of an unusual number of requests), whose operation may result in a temporary restriction of access; every such restriction is subject to human review at the user's request.
9.1. We apply technical and organisational measures appropriate to the risk, described in detail in the Security Specification (Part V of the Service documentation, geogps.cloud/security/en/). They include in particular encryption in transit (TLS), role-based access control, two-step verification at login, limiting the number of login attempts, storing passwords exclusively as a cryptographic hash, separation of environments, event logging, code testing and reviews, and backups in a separate location.
9.2. The Service runs on a VPS server in a data centre in the European Union, provided by home.pl sp. z o.o. The data centre holds ISO/IEC 27001 (information security management system) and ISO 9001 (quality management system) certificates, and the availability of the infrastructure is covered by an SLA at the level of 99.9%.
9.3. Users' first names and last names are encrypted in the geoGPS Cloud database with the AES-256-GCM algorithm, and backups of the database and photos are encrypted before they are saved. Photo files (attachments to objects) are stored on the server encrypted with the AES-256 algorithm and are decrypted only at the moment they are made available to an authorised User. They are additionally protected by access control (access only for authorised Users of the Organization, through the authenticated API), encryption in transit and the physical and organisational safeguards of the data centre.
9.4. In the event of a personal data breach, we notify the President of the Personal Data Protection Office within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to the rights or freedoms of natural persons, and if the breach is likely to result in a high risk – we also inform the data subjects without undue delay. Breaches concerning customers' Content are reported to the Organization as the controller, on the terms set out in the Data Processing Agreement.
10.1. The website uses cookies and similar technologies (localStorage, sessionStorage). The mobile app does not use cookies, but it may use installation identifiers for the purposes described below.
10.2. In the Mobile App we use Firebase (Google) packages: Firebase Analytics, Firebase Crashlytics and Firebase Cloud Messaging.
10.3. The website and the Web Panel use only the cookies and browser storage data necessary to provide the service requested by the User. We do not use analytics or marketing cookies on the website.
Category | Purpose | Basis | Lifetime |
|---|---|---|---|
Necessary | Maintaining the session of a logged-in user, authentication, CSRF protection, security | Article 399(3) of the Polish Electronic Communications Law – necessary to provide the service requested by the User; consent is not required | Session or up to 12 months |
Preferences chosen by the User | Remembering the chosen language, theme and interface layout (localStorage) | Article 399(3) of the Polish Electronic Communications Law – necessary to apply the setting requested by the User | Until deleted by the User |
10.4. If we introduce analytics or marketing cookies in the future, they will be used only after consent has been obtained through a cookie banner, and this Policy will be updated accordingly.
10.5. Cookie settings can be changed in the browser; blocking the necessary cookies may make it impossible to log in to the Service.
The Service is intended exclusively for adults. We do not knowingly collect data of persons under 18 years of age. If we learn that such data has been provided to us, we will delete it without undue delay. Please send reports in this matter to data-protection@geogps.cloud.
12.1. The Policy may be changed in connection with a change in the law, in the scope of the Service or in the tools used.
12.2. We inform about material changes at least 14 days in advance – by e-mail or by a notice in the Service. Earlier versions of the Policy are made available on request sent to data-protection@geogps.cloud.
12.3. Version in force: 1.2 of 18 October 2026.