Privacy Policy

Last updated: May 20, 2026 | Application: Krono System

KronoSoftwares is committed to strict corporate data sovereignty and enterprise privacy. This Privacy Policy describes the technical, local, and decentralized processing of data within the Krono application and ecosystem.

1. Local-First Architecture and Data Processing

Krono is designed under a Local-First philosophy, operating with total network independence through a high-performance local Room (SQLite) database. The application processes data entered directly by the organization and its users, covering:

Business and Client Data: Billing information, tax details (NIF, CNPJ, EIN), warehouse management (WMS) tracking with Serial Number (SN) verification, and executive reports.
Operational Data and Logistics: Service Orders (SO), checklists, fleet/vehicle records, digital signatures captured on canvas, and geolocation coordinates processed via the logistics engine.
Time Tracking (HR): Employee clock-in and attendance records processed via absolute Unix Timestamps and consolidated centrally based on the regional standard timezone (Europe/Lisbon).

2. Synchronization and Intelligent Cloud Backup

To ensure data persistence without compromising device storage, Krono utilizes a hybrid reactive synchronization architecture:

Delta Synchronization: Automatic and silent background updates managed by Android's WorkManager as soon as network connectivity is restored.
Private Cloud Backup: Hybrid integration with Firebase and Google Drive API through a "Clean Replacement" system, keeping only the latest healthy version of the database in the user's private cloud.

            Data Sovereignty: KronoSoftwares does not own centralized telemetry servers for this product. The entire database, audit logs, and generated PDF reports belong to and are controlled exclusively by the licensed enterprise.
        

3. Required Permissions and Justifications

Internet/Network Access: Used exclusively for synchronization traffic between instances (KronoGate Client/Firebase) and communication with backup APIs.
Location (GPS): Used strictly for service order routing and security auditing during background clock-in events.
Storage and Camera: Required for generating, reading, and locally persisting official A4 PDF reports and saving service evidence photos.

4. Contact

For technical inquiries regarding our data protection architecture, contact corporate engineering support at: suporte.kronosoftwares@gmail.com.