BoatLedger is published by Flint Software, an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy question, write to captainlongevity@gmail.com.
Is there a BoatLedger server that holds my vessel records?
No. There is no BoatLedger server. Your vessels, safety equipment, registrations, and boater education certificates live in this app's local SwiftData store on your iPhone. We cannot read them, restore them, or transfer them.
Do you collect analytics, crash logs, or device identifiers?
No. There is no analytics SDK, no crash reporter, and no advertising identifier in the binary. We do not know how often you open the app, which screens you visit, or whether you have a paid subscription unless we look up your purchase via Apple's standard developer reports.
How does BoatLedger decide expiry dates and reference rules?
The expiry calculator runs deterministic, rule-based logic on your iPhone (flares = 42 months from manufacture; disposable fire extinguishers = 12 years from manufacture per 33 CFR §175.320). Reference content (50-state registration cycles, USCG 33 CFR equipment rules, NASBLA boater education state requirements) is bundled data we update through standard App Store releases. Everything runs on your device.
Do you talk to the U.S. Coast Guard, any state DMV/DNR, or any government agency?
No. BoatLedger makes no API calls to USCG, the National Association of State Boating Law Administrators (NASBLA), BoatUS, any state Fish & Wildlife / Boating Law Administrator agency, or any insurance carrier. All references to those organizations are bundled lookup content.
Do you add anything to my iCloud or my Apple ID?
No. BoatLedger does not declare the iCloud entitlement. No CloudKit container, no remote sync of any kind. Your records may be included in your standard iOS Backups (iCloud Backup or Finder/iTunes encrypted backup) when those are enabled — but that is Apple's standard backup behavior for all on-device data, not a BoatLedger feature.
Device-backup contents and recovery depend on your system settings, a successfully completed usable backup and Apple’s restoration process; enabling backup alone does not guarantee recovery of every record or original file. We cannot retrieve or restore your device backups.
This data may be included in your standard iOS Backups when you have those enabled. We do not have access to your iOS Backups. If you delete the app without an iOS Backup, your data is permanently lost. The safety checklist PDF is a reference document. The app has no full record export, import, or backup feature.
BoatLedger offers optional Pro access (an Annual subscription or a one-time Lifetime purchase on the current Pro screen; active Monthly subscriptions are still recognized) via Apple's StoreKit 2. When you subscribe, restore a purchase, or when the app verifies your entitlement, your device communicates directly with Apple's servers. The app uses verified StoreKit transaction and product information, including the product identifier and applicable expiration or revocation, to determine access on the device. We do not see your Apple ID, payment method, billing address, or transaction history. Apple's handling of subscription information is governed by Apple's Privacy Policy.
You can revoke any permission at any time in iOS Settings > BoatLedger. BoatLedger requests no camera, no microphone, no photo library, no location, no HealthKit, no contacts permission.
BoatLedger is a personal records organizer. It is not affiliated with the U.S. Coast Guard, any state Department of Motor Vehicles, Department of Natural Resources, Fish & Wildlife agency, or any other federal, state, or local government agency. The app does not provide navigation, weather, AIS, chart-plotting, legal, safety, or insurance advice. References to USCG 33 CFR rules, state registration cycles, and NASBLA-approved boater education are based on publicly available regulatory and educational content and are reference-only.
BoatLedger is intended for U.S. adults. We do not knowingly collect any information from anyone, including children. The app's age rating reflects this.
Deleting a vessel also deletes its equipment, registration and education records only after a checked save succeeds. Individual record deletion likewise checks the database first. A failed database deletion keeps the original record graph and Calendar links and does not begin external removal. After successful deletion, the App attempts to remove the known linked Calendar events; failed known identifiers are held in local preferences for Settings cleanup retry. There is no Recently Deleted or database-archive restore.
Removing the App normally removes its local container, not independently kept original media, exported files, recipient copies or older backups. Manage those copies separately. Device-backup recovery requires a usable completed backup; the developer has no record archive to retrieve.
BoatLedger is published in English and is marketed in the United States. The reference data (50-state registration, USCG 33 CFR, NASBLA boater education) is U.S.-specific. The App does not route records through a developer-operated record server. Apple services, legal-page hosting, support correspondence and any sharing destination you choose may process information outside your country under their own policies. Those services are separate from the App’s local record storage.
If a future release ever changes how the app handles data — for example, if a later version ever introduces any sync, analytics, or third-party integration — we will update this policy and surface the change in the app before that feature becomes available. The "Last updated" date at the top of this page reflects the most recent revision.
Privacy questions: captainlongevity@gmail.com
The app requests full Calendar access. Event titles, dates, notes and alarms created by the app are saved to your system calendar, which may sync to a calendar-account provider or be visible to people sharing that calendar. These Calendar copies are outside the app’s local database and App Lock; deleting an app record or uninstalling the app does not guarantee removal of every calendar or synced copy. Manage those copies in Calendar and the relevant account. To update or remove an event created by the integration, the app looks it up using its saved event identifier and selects a writable calendar when necessary.
These legal pages are hosted on Vercel. Opening a page sends ordinary request information, such as the IP address, browser information and requested URL, to the host for delivery and security; see Vercel’s Privacy Notice. This website request is separate from App record storage. If you email support, we receive the address and information you choose to send so we can respond. Send only the details needed for that request.
The updated App pauses the normal record interface if its persistent database cannot be opened and only a temporary in-memory store is available. New recording and editing through that interface are blocked. The App keeps the existing database and attachment files rather than treating the temporary empty store as your archive. Database-dependent startup work in that interface is paused; previously scheduled reminders, widget snapshots or independent copies may remain.
Check available device storage, close and reopen the App, and contact support before deleting or reinstalling it. This recovery screen is not a backup, a repair guarantee or an automatic restoration of missing records. Older installed versions may behave differently until updated.
The updated App checks vessel, registration, education, equipment and onboarding saves. Failed database writes retain original stored values and current open form entries for retry without rolling back unrelated drafts. A newly saved record is reused if Calendar subsequently fails, rather than inserting another record. Calendar updates reuse a linked event when it still exists, and a failed update does not first delete the old event. If Calendar succeeds but saving its link fails, the form retains that returned identifier or cleared-link state in memory, pauses further form edits and lets Save retry status only. Keep that form open; these pending link values are not a restart-proof journal. Settings retry saves pending local link values before continuing record-by-record sync and stops on a failure, so earlier successful events may already be updated. Known event-removal identifiers queued after committed deletion persist locally until cleanup succeeds; Settings Retry Calendar sync and cleanup retries them. Calendar and database writes are separate systems, not an atomic transaction: an interruption between their operations, a missing identifier or an older version can still leave independent Calendar copies or make duplication possible after restart. Inspect and manage those copies in Calendar when needed. The cleanup queue contains only known event identifiers, not a scan or deletion of unrelated events. Calendar accounts may sync copies externally, and App Lock does not protect those copies. Delivery of Calendar alarms is controlled by the system, not guaranteed. The updated App makes Calendar reminders for dated equipment available on the free tier as well as Pro. Record limits and expiry calculations are unchanged.