This is an English translation provided for convenience. The Polish version is the original and prevails in the event of any discrepancies.
Part V of the geoGPS Service documentation. Last updated: 8 October 2026. Version 1.1.
This Specification describes the technical and organisational measures that ENCOM Sp. z o.o. (the “Service Provider”) applies to protect the data processed in the geoGPS System, within the meaning of Article 32 of the GDPR. It is an annex to the Terms of Service (Part I) and to the Data Processing Agreement (Part III). Capitalised terms have the meaning given to them in the Terms of Service.
1.1. geoGPS Cloud – the database, photo files and backups – runs on a VPS server provided by home.pl sp. z o.o., located in a data centre in the European Union.
1.2. The data centre holds ISO/IEC 27001 and ISO 9001 certificates, and the availability of the infrastructure is covered by the provider's SLA at the level of 99.9%. Physical security (access control, backup power supply, fire protection) is provided by the data centre operator.
1.3. The data of individual Organizations is logically separated: every record and every file is assigned to an Organization identifier, and the API makes data available only to the Users of that Organization.
1.4. The production environment is separated from the development environment and uses a separate database. The development environment does not contain customer data, and production data is not used for testing.
2.1. All communication between the App, the Web Panel, the QGIS Plugin and geoGPS Cloud takes place exclusively over an encrypted HTTPS (TLS) connection.
2.2. The server enforces encrypted connections with the Strict-Transport-Security (HSTS) header.
2.3. E-mail messages sent by the System (Account activation, password reset) are passed to the mail server over an encrypted connection.
3.1. Photo files (attachments to objects) are stored on the server encrypted with the AES-256-GCM algorithm and are decrypted only at the moment they are made available to an authorised User.
3.2. Users' first names and last names are encrypted in the database at the application level with the AES-256-GCM algorithm.
3.3. The encryption key is stored outside the database, in server configuration that is not accessible from the public network. The key for photo files is derived from the master key with the HKDF-SHA-256 function, so that individual uses rely on separate keys.
3.4. Passwords are stored exclusively as a cryptographic hash with an individual salt; when the recommended parameters change, the hash is automatically renewed at login. Access tokens, one-time login codes and password reset tokens are stored exclusively as a SHA-256 hash – their plain value is not written to the database.
3.5. Backups are encrypted before they are saved (section 8).
3.6. Other data stored in the geoGPS Cloud database is protected by: access control enforced on the server side (section 5), encryption in transit (section 2), encryption of backups (section 8) and the physical and organisational safeguards of the data centre (section 1).
4.1. Logging in requires a login and a password as well as two-step verification: a one-time code valid for 3 minutes, delivered by a push notification to the User's device. The number of attempts to enter the code is limited; once it is exhausted, the code becomes invalid.
4.2. The number of failed login attempts is limited both per Account and per IP address; once the limit is exceeded, further attempts are temporarily blocked.
4.3. A password is reset through a one-time link with a limited validity period, sent to the Account's e-mail address. The number of reset requests is limited per e-mail address and per IP address. The activation link for a new Account is valid for 24 hours.
4.4. After logging in, the App and the QGIS Plugin use a random access token with a limited validity period (no longer than 30 days). The token can be invalidated by logging out.
4.5. Higher-risk operations require re-confirmation with the password.
4.6. The number of registrations of new Organizations from a single IP address is limited in order to prevent abuse.
5.1. Access to data is role-based: the Manager manages the Organization, creates and deletes Employee Accounts and grants permissions; an Employee works on the Organization's data within the scope granted by the Manager. Data entered by a User can be edited only by its author.
5.2. Every API request is authenticated, and the right to access the Organization's data and the validity of the Subscription are checked on the server side, regardless of the interface from which the request originates.
5.3. Administrative access to the server and to the administrative functions of the System is held only by a limited number of individually authorised members of the Service Provider's staff, to the extent necessary to maintain the Service and provide support. These persons act on the basis of written authorisations to process personal data and are bound by a duty of confidentiality. Logging in to the server is possible only with individual SSH keys; password login is disabled.
6.1. Web Panel: session cookies with the Secure, HttpOnly and SameSite attributes, strict session mode, tokens protecting against CSRF attacks, a Content-Security-Policy, a ban on embedding in frames (X-Frame-Options), caching disabled for pages containing data.
6.2. API: database queries exclusively in parameterised form, validation of input data, request size limits, the X-Content-Type-Options header.
6.3. Photos: only specified image file types are allowed, a size limit applies, and the file is saved under a random name – the name given on the device does not reach the server's file system. A photo is processed before it is saved, as a result of which EXIF metadata, including GPS coordinates, is removed. Photos are available only through the authenticated API, not through a public file address.
6.4. Data stored temporarily on the Device in offline mode is protected by the security of the Device itself (section 11).
7.1. The API access log (timestamp, request identifier, method and path, response code, response time, IP address, client identifier, identifier of the Account and the Organization) is kept for 90 days, after which it is deleted automatically. The log does not contain passwords, tokens or the content of the transmitted data.
7.2. The application error log is kept for 90 days, after which it is deleted automatically.
7.3. Records of failed login attempts, password reset attempts and Organization registration attempts, used to limit the number of attempts, are kept for 2 days. The record of a one-time login code is deleted after 24 hours at the latest.
7.4. Acceptances of the Terms of Service and the Privacy Policy (document version, date, IP address, channel) are kept for the duration of the agreement and the limitation period for claims.
7.5. The retention periods of the individual records are also set out in section 4 of the Privacy Policy.
8.1. A backup of the database is made daily, and a full backup of the database together with the photo files – once a week.
8.2. Backups are encrypted with a public key immediately after they are created; the private key needed to decrypt them is not stored on the server. The integrity of every backup is confirmed by a SHA-256 checksum.
8.3. Backups are made by a dedicated system account with read-only access to the database.
8.4. The server keeps the 14 most recent daily backups and the 8 most recent weekly backups; older ones are deleted automatically. On a separate server, backups are deleted automatically after 60 days, and backups from the last 3 months are kept on an external medium. Data deleted from the production system disappears from the backups as they rotate, that is no later than after approximately 3 months.
8.5. The maximum data loss in the event of a server failure (RPO) is up to 24 hours for the database and up to 7 days for photo files.
8.6. After each run, the encrypted backups are automatically transferred to a separate server and, in addition, once a month they are downloaded to an encrypted external medium kept in a safe in a location separate from the data centre. Only encrypted files leave the production server.
8.7. The recovery procedure is documented, and a trial restoration of data from a backup is carried out at least once a month.
8.8. Backups serve to restore the Service after a failure; they do not replace the User's own copies of the Content, which the User is obliged to maintain (§ 9.2(4) of the Terms of Service).
9.1. The server's operating system, the server software and the libraries used by the System are kept up to date; security patches are deployed as a priority.
9.2. Code changes are subject to version control, review and testing before they are deployed to the production environment.
9.3. Credentials and keys are not stored in the code repository but in server configuration with restricted access.
10.1. Reports of vulnerabilities and incidents are accepted at security@geogps.cloud.
10.2. In the event of an Incident with a significant impact on the Content or on the availability of the Service, the Service Provider gives the Organization initial information within 48 hours of detection, an update within 72 hours and a final report within one month (§ 15a of the Terms of Service). Personal data breaches concerning the Content are reported to the Organization on the terms set out in the Data Processing Agreement (Part III).
10.3. The Service Provider documents incidents, their effects and the corrective actions taken.
Data security also depends on the Organization and its Users, who are responsible for:
The Service Provider may update the Specification as the Service develops and the state of the art changes, provided that the change does not lower the level of data protection. Changes that lower the level of protection require the procedure provided for amending the Terms of Service (§ 22 of the Terms of Service).