Last updated: July 8, 2026

This Privacy Policy describes how Horologe handles data.

Summary

• No account is required
• No analytics tools are used
• No advertising SDKs are used
• No user tracking is performed
• The developer does not collect personal data through the app’s remote servers
• iCloud sync, if enabled by the user on iOS, happens directly between the device and the user’s own Apple Account and does not pass through the developer’s servers

Data processed by the app

The app allows the user to locally save and manage information related to their watch collection, including:

• watch data entered by the user, such as brand, model, reference, serial number, year, price, currency, movement, diameter, case material, caliber, purchase date, box, documentation, and notes
• watch status (owned, sold, wishlist, or in repair), with sale date and sale price when applicable
• service or maintenance history, such as service date, service type, notes, cost, and currency, plus the recommended service interval used for reminders
• a log of the days on which a watch was worn (“Wear log”)
• rate-accuracy measurements manually entered by the user (daily deviation in seconds)
• documents attached by the user to a watch, such as warranty cards, receipts, or certificates
• images selected by the user from the device’s photo library for cover and gallery
• preferences such as language, theme, accent color, text settings, onboarding status, and the status of app lock and service reminders
• backup files in ZIP or JSON format generated or imported by the user
• PDF files generated by the user to export or share the details of a watch
• CSV files generated by the user to export the list of their collection

This information is stored locally on the device to enable the app to function.

Data collection

The developer does not automatically collect, receive, transmit, sell, or share user data through remote servers via the app.

Data normally remains in the app’s local database, in local app storage for images and attached documents, and in the device’s local preferences.

If the user chooses to export, save, or share a backup, a PDF, or a CSV file, that action is initiated manually by the user through operating system features. Any subsequent transfer depends solely on the destination chosen by the user.

If the user enables iCloud sync (see the dedicated section), a backup of their data is automatically saved to their own private iCloud storage via Apple CloudKit; even in this case, the developer does not receive or have access to that data.

iCloud sync (iOS only)

On iOS devices, Horologe offers an optional iCloud sync feature, disabled by default and enabled by the user from the app’s Settings.

When enabled:

• the app saves a copy of the collection data (equivalent to the ZIP backup: watches, history, wear log, accuracy measurements, attached documents, and images) to Apple’s private CloudKit database associated with the user’s Apple Account
• sync happens directly between the user’s device and Apple’s servers; data does not pass through or get stored on the developer’s servers
• data is accessible only from devices signed in with the same Apple Account as the user
• sync may happen automatically in the background after a data change, at app launch, or when the app returns to the foreground, while the feature is enabled

The user can disable sync at any time from the app’s Settings. Disabling it stops future syncs but does not automatically delete any copy already present in the user’s iCloud; it can be removed using the device’s iCloud storage management (System Settings > user name > iCloud > Manage Storage).

Notifications

Horologe can send local service reminders when the user enables this optional feature in Settings for a watch with a service interval configured.

Notifications are generated and shown locally on the device by the operating system; they do not involve any data transmission to external servers. To enable them, the app requests the system permission to send notifications.

Biometric authentication

Horologe offers an optional app lock via Face ID, Touch ID, or the Android equivalent (fingerprint or face recognition), enabled by the user from Settings.

Authentication is handled entirely by the device’s operating system through its biometric APIs. The app does not have access to the user’s biometric data, does not receive it, does not store it, and does not transmit it: it only receives the authentication outcome (success or failure) returned by the operating system.

Device permissions

Horologe may request access to:

• photos and images on the device, to allow selection of images associated with watches
• system files and documents, to import backups, attach documents to watches, or save backups, PDFs, and CSV files
• notifications, for service reminders (optional, if enabled by the user)
• biometric authentication (Face ID, Touch ID, or fingerprint), for the app lock (optional, if enabled by the user)

As of July 8, 2026, the app code uses image selection from the photo library. There are no active app flows that use the camera to capture new photos directly from within the app.

On iOS, the operating system may also require a location permission (NSLocationWhenInUseUsageDescription) to be declared, because some system libraries used for photo library access reference that permission to handle any geolocation metadata attached to photos. Horologe does not request or use the user’s location for any feature.

Data sharing

Horologe does not share user data with the developer or third parties for analytics, advertising, profiling, or tracking purposes.

The only exceptions are: when the user explicitly exports, saves, or shares a file using the platform’s sharing or saving tools, and automatic sync with the user’s own Apple Account via iCloud, if enabled by the user (see above). In both cases, data only reaches the destination chosen or controlled by the user, not the developer’s servers.

Data storage

App data is stored locally on the device using local app storage, including:

• local SQLite database for watches, service history, wear log, and accuracy measurements
• local app document storage for images and attached documents
• local preferences for configuration and interface settings
• temporary device directories for some export operations

Backup files, PDFs, and CSV files created by the user are saved only in the location chosen by the user or in a temporary location used to support export or sharing functions.

If enabled by the user, a copy of the data is also saved to Apple’s private CloudKit database, as described in the “iCloud sync” section.

Retention and deletion

Data entered into the app remains on the device until the user:

• manually edits or deletes watches, service history, the wear log, accuracy measurements, or attached documents
• imports a backup that replaces current local data
• performs a local database reset
• deletes images or content from the app
• uninstalls the app, subject to operating system behavior
• manually deletes backup files, PDFs, or exported CSV files from their storage locations

If iCloud sync has been enabled, any copy saved to the user’s Apple Account remains in the user’s iCloud storage even after disabling the feature or uninstalling the app, until removed by the user through the device’s iCloud storage management.

Because the developer does not receive or store app data on remote servers, the developer cannot access, correct, or delete the user’s local or iCloud data on their behalf.

Children

Horologe is not specifically directed to children and does not knowingly collect personal data from children.

Security

The app relies on the security mechanisms provided by the operating system and the app’s local storage. The optional app lock with Face ID, Touch ID, or fingerprint adds an extra layer of protection to access data on the device. When enabled, iCloud sync relies on the security mechanisms of the user’s own Apple Account.

No method of device storage, cloud sync, or file transfer can be guaranteed to be completely secure, especially after the user exports, saves, or shares a backup, a PDF, or a CSV file outside the app.

Changes to this policy

This Privacy Policy may be updated in future versions of the app. The latest version should be made available at the public privacy policy URL used in App Store Connect and Google Play Console.

Contact

Developer / Publisher: dimpemekug

Support email: dimpemekug.app@gmail.com