Special Terms of Service for the TEMPUS by Jurist Soft module
Article 1. Subject and Purpose
The TEMPUS BY JURIST SOFT module (hereinafter: TEMPUS) is a specialized, add-on module of the JuristBiro platform designed for the digital recording of working time, employee attendance, absence management, submission of internal employee requests, and other workforce management automation processes.
The module is intended exclusively for legal entities and entrepreneurs (hereinafter: the Service User) who use it for business purposes and the organization of work for their employees and engaged personnel. TEMPUS is not intended for, and may not be used by, natural persons for private, personal, or consumer purposes. By registering and activating the module, the Service User confirms its status as a commercial entity, thereby expressly excluding the application of consumer protection regulations of any jurisdiction. This is a critical provision for compliance with Google Play and GDPR regulations concerning B2B applications.
Article 2. Authorized Users and Account Management
Access to and use of the TEMPUS module are granted to the Service User via the primary administrator account, as well as to the employees and engaged personnel of the Service User (hereinafter: Employees) via individual user accounts.
The Service User retains the exclusive right and responsibility for creating, assigning, modifying permission levels, and timely revoking access rights for its Employees. The Service Provider has no insight into the justification for assigning accounts, nor any obligation to verify the identity of the persons for whom the Service User has created an account. The Service Provider fully excludes any and all liability for all actions, data entries, deletions, or misuses of data performed through user accounts to which access was granted by the Service User.
Article 3. Liability for Compliance with Local Labor Laws
TEMPUS represents a technical tool and a repository for recording data entered by the Service User and its Employees. The Service Provider does not perform any review, control, or validation of the entered data.
The Service Provider does not guarantee nor assume liability for the compliance of the generated records with local labor regulations and labor laws of the country in which the Service User operates (including, but not limited to, regulations on overtime, night work, breaks, and rest periods), the internal general acts of the Service User, or collective agreements. The Service User bears sole and full legal and material liability for the accuracy, legality, and use of the records maintained through the system in relations with Employees and the competent labor inspection authorities of the host country.
Article 4. Mobile Application and Technical Prerequisites
The TEMPUS mobile application enables Employees to use the system's functionalities via portable mobile devices. The Service User is solely responsible for providing appropriate hardware devices to Employees, as well as a stable internet connection, if it requires them to use the mobile application.
The Service Provider shall not be held liable for the inability to use the application, delays, or data loss resulting from:
- Physical malfunction, damage, or software incompatibility of the Employee's device.
- The use of outdated or modified (e.g., rooted, jailbroken) operating systems.
- Battery or memory restrictions and optimizations imposed by the device manufacturer or the operating system.
- Interruption, degradation, or loss of cellular or Wi-Fi internet connection.
- Issues in the operation of global third-party services (e.g., Google Play Store, Apple App Store, push notification services).
Article 5. Biometric Verification of Identity and Data Protection (GDPR and Local Laws)
The TEMPUS module may contain technical functionalities for the biometric verification of Employee identity (e.g., local face recognition or system-level fingerprint unlock) to prevent misuse. The decision to activate, apply, and determine the scope of such functionalities is made exclusively by the Service User.
Within the meaning of the EU General Data Protection Regulation (GDPR), as well as local personal data protection laws of countries in the region (Serbia, BiH, Montenegro, North Macedonia), the Service User acts as the Data Controller, while the Service Provider acts exclusively as the Data Processor, processing data solely upon the instructions of the Data Controller.
The Service User expressly guarantees that the application of biometric systems for the purpose of working time recording is permitted under the positive legal regulations of the country in which the Service User operates. The Service User commits to fulfilling the following requirements prior to activating biometric verification:
- Determine and secure a valid legal basis for processing this special category of personal data in accordance with local laws and the practice of competent supervisory authorities.
- Conduct a Data Protection Impact Assessment (DPIA) if required by law.
- Obtain explicit, informed, and freely given written consent from Employees, or offer an alternative non-biometric identification method (e.g., PIN code or QR code) for Employees who do not consent to biometrics.
- Fully inform Employees about the methods of data processing in accordance with its internal Privacy Policy.
The Service Provider provides exclusively the technical infrastructure. If the local legislation of the Service User's country prohibits or restricts the use of biometrics in employment relationships (as is the case in certain EU member states), the Service User is obliged to keep this functionality deactivated and shall bear full liability for the consequences of its activation.
The technical infrastructure used to process data under this module, including the results of biometric verification transmitted to the Service User's backend system, is hosted on servers located in Frankfurt, Federal Republic of Germany (Amazon Web Services). As Germany is an EU member state, this ensures that the processing infrastructure itself operates within the European Union, which is a relevant factor for the Service User's own GDPR compliance assessment.
Article 6. Confirmation of Presence at the Workplace (QR Code, Bluetooth, and GPS Location) and Protection Against System Misuse
The Service User may, depending on its own settings and the technical capabilities of the Application, enable one or more of the following methods for confirming the physical presence of Employees at the workplace: (i) scanning a QR code generated by a terminal device placed at the business premises (whereby the Employee's camera is used exclusively to read the content of the code, not to capture or store photographs/video); (ii) recognition of the proximity of a Bluetooth device (beacon) placed at the business premises; and/or (iii) reading the GPS location of the Employee's device at the moment of check-in or check-out, in order to verify whether the Employee is located within the permitted area (radius) around the workplace determined by the Service User.
The Employee's GPS location is read exclusively in connection with a specific check-in or check-out action and is used for server-side verification of whether that action takes place from within the permitted radius of the workplace. Such reading does not constitute continuous tracking of the Employee's movement or location beyond the context of the specific check-in/check-out.
The Bluetooth device (beacon) proximity-recognition function may operate even when the Employee is not actively using the Application, i.e., when the Application is closed (in the background). In that case, the operating system of the Employee's device briefly activates the Application solely to verify proximity to the relevant workplace beacon, after which the Application may offer the Employee a notification with the option to quickly check in or check out. This function does not involve the continuous collection, logging, or transmission of the Employee's precise GPS location in the background — only the technical beacon data (identifier, signal strength) necessary to determine proximity is processed.
The scope and combination of presence-verification methods referred to in this Article depend on the technical capabilities of the specific version of the Application and the choices made by the Service User, and may differ between Service Users. Any material change in the scope of these functionalities will be communicated to the Service User in a timely manner through an in-app notice, together with a corresponding update of this Article and the related TEMPUS module Privacy Policy.
TEMPUS registers exclusively the technical moment of code scanning, beacon proximity, or GPS coordinates as reported to the application by the mobile device's operating system. The Service Provider does not guarantee the actual physical presence of the Employee at the location, nor shall it be liable for situations where an Employee knowingly bypasses, deceives, or misuses the system (e.g., by sharing photos of the QR code with third parties, using GPS-spoofing software, using a VPN, or disclosing their access parameters to another person). The detection, penalization, and prevention of such misuses constitute an exclusive internal obligation and right of the Service User in accordance with its disciplinary regulations.
Article 6a. Error Diagnostics and Performance Monitoring (Sentry)
For the purpose of resolving technical errors and improving performance, the Application may use the Sentry diagnostics service, including a session-replay feature to facilitate understanding of the cause of a technical issue. The camera, text inputs, and image displays within the session replay are automatically masked/blurred before being sent to the diagnostics service, so that no content capable of revealing the Employee's identity or sensitive data is transmitted. This functionality is not used to monitor Employee behavior beyond diagnostic purposes, nor for marketing purposes.
Article 7. Offline Mode and Data Synchronization
In the event of temporary unavailability of the internet network on the Employee's device, TEMPUS may temporarily cache data regarding the time and place of the check-in locally. This data will be automatically synchronized with the central database as soon as the device establishes a stable internet connection.
The Service User agrees that the actual time of recording (the physical click within the application) and the time of synchronization (data reaching the server) may deviate due to technical circumstances beyond the control of the Service Provider. The Service Provider is not liable for the loss of locally stored data if the Employee deletes the application, clears the device's cache memory, or permanently damages the device before a successful synchronization with the server has occurred.
Article 8. Limitation of Liability of the Service Provider
The Service Provider is completely released from any and all liability for:
- Inaccurate, incomplete, false, simulated, or delayed data entered by the Service User or its Employees.
- Incorrect calculations of earnings, salaries, taxes, contributions, allowances, or overtime work based on reports generated from the TEMPUS module.
- Any business, financial, organizational, or legal decisions of the Service User's management made on the basis of data or statistics from the system.
- System interruptions caused by force majeure, telecommunication disruptions of global or local internet providers, or external cyberattacks.
- Actions of Employees that violate the internal work regulations, discipline, and safety policies of the Service User.
Article 9. Governing Law and Dispute Resolution Jurisdiction
These Special Terms constitute an integral part of the General Terms of Use of the JuristBiro platform and, together with them, form a single legal entity. On all matters not explicitly regulated by this document, the provisions of the General Terms of Use and the Privacy Policy of the JuristBiro platform shall apply directly. In the event of any conflict between the provisions of the General Terms and these Special Terms regarding the TEMPUS module, these Special Terms shall prevail.
These Special Terms, as well as all disputes arising out of or in connection with the use of the TEMPUS module, shall be governed exclusively by the laws of the Republic of Serbia, excluding its conflict of law rules.
In the event of any dispute that cannot be resolved amicably through negotiations, the exclusive territorial jurisdiction of the competent court in Niš, Republic of Serbia is hereby agreed upon, regardless of the seat of the Service User, the country of operation, or the location from which the module is accessed.
These Special Terms of Use for the TEMPUS module were adopted on 06.06.2026, in Niš, and apply from the date of publication within the Application.
Amendments made on 25.08.2026, to align with the confirmed technical state of the Application (including GPS, background Bluetooth, and Sentry diagnostics). Version: 1.2.0.