Heirline Privacy Policy

Effective date: 2026-05-08 · Last updated: 2026-11-04

Short version: Heirline stores your watch archive — collection details, service records, box-and-papers, valuations, estate letters, photos, attachments — on your devices. With the default iCloud sync setting, the archive is also stored in your own private iCloud account using Apple's CloudKit private database. We do not operate an app-record server and no analytics. We do not automatically receive your archive. The only network communication the app performs is with Apple's StoreKit servers (subscription verification) and, while iCloud sync is enabled, with Apple's CloudKit servers under your Apple Account.

1. Who we are

Heirline is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy-related question, write to captainlongevity@gmail.com.

2. Information we do not collect

The app does not automatically send the following records to the developer for storage, advertising or analytics. User-selected exports, optional system services and support messages are handled as described in this policy:

We do not operate an app-record server. The app does not automatically send these fields to us; information you choose to include in a support message is an exception.

3. Information stored on your device

Heirline stores archive data in SwiftData on your device. For a new installation with no previous preference, iCloud sync is enabled by default for Free and Pro users. When a private iCloud store is available, the app uses Apple CloudKit under your Apple Account; it can fall back to local storage when the cloud store cannot be opened. Apple device backups are separate and depend on your system settings.

4. On-device processing

Several features process data locally on your device only:

5. Subscriptions and StoreKit

Heirline uses Apple StoreKit for a yearly subscription and a one-time non-consumable Lifetime purchase. Loading products, checking offer eligibility, purchasing, restoring and verifying access communicate with Apple. The app reads verified product and entitlement information, including expiration or revocation status where applicable, and keeps local access state. Apple processes payment; Heirline does not receive your payment-card details or Apple Account password. Current and supported historical purchase access depend on verified transactions. See the Heirline terms for the available plans and subscription handling.

5a. Private iCloud sync: enabled by default

Heirline enables iCloud sync by default when no earlier preference exists. This applies to Free and Pro; sync is not sold as an upgrade. The current onboarding does not contain a separate sync opt-in step. You can change the preference in Settings > Sync; follow the app's restart guidance so the chosen storage mode takes effect.

When enabled and available, your watch records, linked histories, documents and photos are replicated to a private CloudKit database associated with your Apple Account. Apple operates this service under its iCloud privacy and security terms. We have no developer-operated copy and do not use these records for advertising. Private CloudKit storage is not a claim that every field has end-to-end encryption or that Apple cannot respond to valid legal process.

Disabling sync stops subsequent syncing once the storage mode changes; it does not erase earlier iCloud copies or data on another device. Manage iCloud copies in Apple Account storage settings. Deleting an app from one device is not deletion of every copy.

6. Permissions the app requests

You can revoke any of these permissions at any time in iOS Settings > Heirline.

7. No automatic valuations or market data

Heirline never auto-values your watches, never connects to any market price database, and never transmits your records to any dealer, auction house, appraiser, insurance carrier, or watch brand. All values you see in the app are values you entered, with the source you attributed.

8. Children's privacy

Heirline is not directed to children under 13. The app has no child account or developer-operated record collection. Contact support if a child has sent personal information to us. The app's age rating reflects this.

9. Retention, recovery and copies

Recently Deleted marks original records with a deletion date for up to 30 days; it does not serialize a complete collection backup. Restoring clears the selected record's deletion marker. Restoring a watch makes only its still-retained, non-deleted children available; it does not restore separately deleted children or missing files. Permanent watch deletion, including expiry purge, cascades to service, box-and-papers, valuation, estate, document and journal records even if a child has time left in its own recovery window. Permanent deletion saves business-record removal and removal of unshared StoredAttachment payload rows together before deleting local cache files. Multi-page document manifests and retained references are checked; unverifiable references postpone deletion. Shared attachments remain while another record still uses them. A local filename-only cleanup journal is prepared before the database change. After a successful save, cleanup checks saved references in a separate database context and removes only queued, unreferenced files. Files still referenced by other records or retained deletion snapshots are kept. Failed cleanup is retried during normal App startup and through Retry attachment cleanup; unreadable references or journal data postpone removal. This is not guaranteed immediate or secure erasure and does not scan unknown older files. If a discarded new file cannot be added to the journal, its name is retained only in memory for retry while the App stays open; interruption can leave an untracked draft file.

Unreferenced synchronized assets keep the existing seven-day observation period before orphan cleanup; a failed save does not advance completion. With iCloud sync enabled, deletion propagation depends on Apple and device connectivity. A local commit is not confirmation that every device or cloud copy has been erased. Exports and older backups remain separate.

To remove the on-device archive, delete the app or use the available deletion controls. To remove iCloud copies, also manage the app's data in Apple Account iCloud storage. We cannot retrieve or erase copies held by Apple or a recipient on your behalf.

10. International users

The app is published in English and is primarily marketed in North America. The app does not route your archive through a developer-operated record server. Apple services, website hosting, support correspondence and sharing destinations may process information outside your region, as described in this policy. iCloud sync routing is governed by Apple under your Apple ID.

11. Changes to this policy

If we ever change how the app handles data, we will update this policy and surface the change in the app before you can use the affected feature. The "Last updated" date at the top of this page reflects the most recent revision.

12. Contact & Support

Privacy questions: captainlongevity@gmail.com

Older installed versions may use different save or cleanup ordering and may not offer these retry controls.

First-watch confirmation

The updated first-watch setup checks the database save before setting the onboarding-complete preference or moving to the normal collection. If saving fails, the current brand, model, reference, serial and optional year entries stay in the open setup form for retry; the failed attempt does not leave a duplicate watch. An entered nonempty year must be a complete integer before saving. These setup entries are temporary form memory, not a restart-proof draft or complete backup. A successful local save is not confirmation of completed iCloud propagation when sync is enabled. Updating the app preserves your existing collection records and your sync and purchase preferences.