Privacy policy

Last updated: October 20, 2026

About this policy

Crownlog is a watch-collection app for Mac, iPhone, iPad, and Android made by Rappasoft, LLC. This policy covers the native apps. Visits to our website are covered by the Rappasoft website privacy policy.

Your collection on your device

Crownlog stores the watches, brands, retailers, and discovery entries you add, along with references, listing links, prices, purchase and service dates, wear counts, notes, tags, favorites, market estimates, saved watch photos and their source URLs, and price history. It saves this information in the app's local storage using Apple's SwiftData framework on Apple devices and SQLite on Android. Display-currency preferences and saved exchange rates are also stored locally.

The app does not read your clipboard in the background, record what you type in other apps, or request access to your camera, microphone, location, or contacts. You select the files it imports or exports, including photos you choose for a watch.

Private iCloud sync

On Mac, iPhone, and iPad, Crownlog uses Apple's CloudKit service to sync collection records, including saved watch photos, through a private database in your own iCloud account. Records include the collection details listed above, internal record identifiers, and timestamps needed for synchronization. Rappasoft does not run a collection server or have access to other users' private CloudKit databases.

Apple operates iCloud and handles the account and service information needed to provide it. iCloud's storage, encryption, retention, and account controls are governed by Apple's privacy policy and your Apple Account settings. Your collection uses your iCloud storage allowance. Changes save locally first and sync when the service is available. No Crownlog account is required.

Crownlog does not apply its own password or application-level encryption to the local database or exported files. Use your device's account security and built-in encryption, and keep backups somewhere private. Sample collections stay in memory and never sync.

Android backups and device transfers

Android stores your collection on your phone. If you enable system backups or transfer to another Android device, the operating system may copy the app's collection database, saved photos, and preferences through Google or your device's backup provider. That provider handles storage, retention, and restoration under its own policies and your device settings. For Google's service, see Google's privacy policy. Rappasoft does not receive those backups.

Android backup is not live synchronization and does not connect to your iCloud collection. Backup availability depends on your device, account, and settings. Google's cloud backup has a 25 MB per-app limit, so larger photo collections may not be backed up; use Crownlog's JSON export to keep a separate copy. Your market API key is excluded from Android cloud backups and device transfers. No Crownlog account is required.

Product pages, images, and currency rates

When you ask Crownlog to fill details from a product page, check a listing price, or discover a catalog, it contacts the public websites you choose directly. Downloading linked photos, including when importing a backup that contains image URLs without saved photos, requests those images from their hosts. The host receives the requested URL, your network IP address, and ordinary connection information. Its own privacy policy applies. Crownlog does not send your private notes, wear counts, or recorded purchase prices with these requests.

Saved photos display from local storage without another request to the source website. You can also choose your own image file. Crownlog resizes and re-encodes photos you choose or download in the app without their original camera or location metadata. Photos already embedded in an imported JSON backup are stored as supplied and may retain that metadata.

On Mac, Crownlog requests the European Central Bank's public exchange-rate feed at launch and when you choose Update rates. On iPhone, iPad, and Android, it requests the feed when you choose Refresh rates. That request includes standard network information; it does not include your collection or prices. Saved rates remain available offline.

Optional market estimates

Manual estimates stay with your collection. To use provider estimates, you can supply a personal The Watch Info API key in the app. Crownlog keeps that key in the device's Keychain on Apple devices, or encrypted using Android's Keystore on Android. It is not copied into collection backups, synced to iCloud, or sent to Rappasoft.

Model searches send the watch's brand and search terms based on its reference or model name to The Watch Info. Crownlog may try several searches if the first has no match. Refreshing a confirmed match sends its provider model ID. On Mac, saved provider estimates may refresh when you open Crownlog if their last check was at least a day ago, or when you use a refresh command. Requests authenticate with your API key, so the provider can associate them with your provider account. Private notes, wear logs, and purchase prices are not sent.

The provider handles its own account information and search or usage records under The Watch Info privacy policy. Remove your key in the app to stop authenticated market requests. Previously saved estimates remain in your collection. You can clear an estimate from the watch's detail screen.

Ads, analytics, and support

Crownlog includes no advertising, tracking SDKs, or Rappasoft analytics. Rappasoft does not sell your collection data. App Store purchases and Apple's optional diagnostics are handled by Apple; Google Play purchases and Google's optional diagnostics are handled by Google. The online services described above may retain their own request or usage records.

If you email us, we receive your address, message, and any attachments you choose to send. We use them to respond and troubleshoot, and retain the correspondence as needed for support and business records. Email providers process messages as part of delivery and storage. Please avoid sharing API keys or unnecessary private collection information. You can ask us to delete support correspondence, subject to any records we must keep by law.

Exports and deletion

JSON backups and CSV exports are unencrypted and include collection details such as notes and purchase prices. JSON backups include saved watch photos; CSV exports include photo source URLs but not photo files. You choose where to save them and are responsible for their security. Import merges matching IDs and retains unrelated records; it does not erase the existing collection.

Deleting a watch removes it, its saved photo, and its saved listing-price history from the app. On Apple devices, that deletion syncs when iCloud is available. Brand and discovery records remain. Discovery entries you dismiss are retained so that the same find does not immediately return, but their saved photos are removed. Removing a market API key does not delete watches or saved estimates.

Uninstalling the app does not guarantee removal of local storage, Keychain items, iCloud records, or device backups. Manage remaining app data using your device's, iCloud's, or backup provider's settings, and delete any exported files separately. Removing data on one Apple device requires working iCloud sync before other Apple devices receive the change. Android deletions do not change an iCloud collection or separately exported backups; previously saved system backups follow the backup provider's retention and replacement rules.

Questions

For support, access, or deletion requests, email [email protected]. If our practices change, we'll update this policy and its date. Visit the Crownlog support page.