By downloading or using HostLog (the "App"), you agree to these Terms of Service. If you do not agree, do not use the App. The App is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F); references to "we," "us," and "our" mean that developer.
HostLog is a personal documentation tool for independent short-term rental hosts. You enter information about properties you host, stays you accept, inspection photos you take, damage you observe, and communications you have; the App helps you organize that information and generate reports for your own use.
The App may surface platform-typical deadline windows (e.g., 24-72 hour guest response, 14-day claim filing, 30-day support escalation). These figures are heuristics drawn from public platform documentation and are informational only — they are not legal advice, not insurance advice, and not platform-specific claim guidance. Platform policies change; you are responsible for verifying the current rules for your specific listing platform and your specific situation. For legal counsel, consult a qualified attorney; for insurance questions, consult a licensed insurance professional.
The App is free to download and use with the following limits: 1 property, up to 3 stays per property, up to 5 photos per inspection, unlimited damage record logging, and a basic damage PDF (plain table, no comparison grid). Individual damage deadlines, local deadline reminders, App Lock, backup export, Recently Deleted recovery, and the Home Screen widget are also free.
New customers may unlock the same Pro feature set with either of these products:
Prices above are United States reference prices. The App Store displays the final localized price before purchase. Existing customers with a verified legacy Pro Annual subscription continue to receive Pro access through the end of each active paid period; Annual is not offered to new customers in version 1.2.
Pro Monthly automatically renews until canceled. Renewal is charged within 24 hours before the end of the current period unless auto-renewal is turned off at least 24 hours before that end. Pro Lifetime is charged once and does not renew. Payment is charged to your Apple ID. You can manage or cancel Monthly in Settings > [your name] > Subscriptions on your iOS device. Restore Purchases is available in HostLog Settings and on the purchase screen. Refund eligibility is determined solely by Apple under its published policies.
HostLog stores all records locally on your iPhone using Apple's SwiftData framework. Your Apple device backups may include app records according to your settings; recovery depends on a usable completed backup and successful restoration. From Settings > Your data, the universal-Free Export JSON backup action generates a portable archive you can save to Files, AirDrop, or email. We have no servers and we receive no copy of your records.
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.
Pro provides the following features. The behavior described here is binding on us — if a future App update materially changes any of these descriptions, we will revise this section.
The following features are available to all users (not gated by Pro):
The App is provided "AS IS" and "AS AVAILABLE" without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, accuracy, or non-infringement. To the maximum extent permitted by law, our aggregate liability arising out of or relating to the App is limited to the amount you paid us, through Apple, for the App in the twelve months preceding the claim. We are not liable for indirect, incidental, special, consequential, or punitive damages, including lost data, denied claims, or damage-recovery shortfalls. Reports generated by the App are tools for your use; we do not guarantee that any rental platform, insurer, or court will accept them.
Your use of the App is also governed by Apple's standard End User License Agreement (EULA) for licensed applications, available at https://www.apple.com/legal/internet-services/itunes/dev/stdeula/. In the event of a conflict between these Terms and the Apple EULA, these Terms govern as between you and us; the Apple EULA governs as between you and Apple.
We may update these Terms from time to time. Material changes will be surfaced in the App on next launch. Continued use of the App after a change constitutes acceptance.
These Terms are governed by the laws of the United States and the State of California, without regard to conflict-of-law principles. Disputes will be resolved in courts located in California, except that either party may seek injunctive relief in any court of competent jurisdiction to protect intellectual property rights.
JSON export and import cover supported structured records and local media-path references, not original photo or attachment binaries. The updated export requires every record query, encoding and file write to succeed before opening the share sheet. A failure displays an error rather than sharing an empty or partial substitute; an actually empty archive remains exportable. Successful exports create separate files and retain earlier archives. Import does not create an automatic safety backup. Imported paths do not make absent media reappear, and app-container photos are not automatically copies in Apple Photos. Protect the readable archive, preserve original media separately, and verify any device backup you rely on. We cannot recover files from a developer-held archive.
Support and legal inquiries: captainlongevity@gmail.com
The free JSON import adds missing identifiers and updates matching supported records, rather than skipping every duplicate or replacing the entire database. The updated import validates the complete JSON archive before changing records. Unsupported format versions, invalid or duplicate record identifiers, invalid parent references and non-empty parent references missing from the file reject the whole import. UUID letter case is normalized. An explicitly empty parent link is supported and can detach a matching record from its former parent. References are resolved from the imported archive, not silently substituted from the current device. Every supported existing record type is then read; if an imported identifier matches multiple local records, the whole import is rejected without changes. Existing duplicates are not automatically repaired. Successful import counts include only the validated records added or updated. If any read fails, it stops without inserting or updating records. Import edits and insertions use one checked save; a failed save restores affected field values and relationships and removes new objects from that attempt while preserving earlier pending input. This does not repair duplicates from an older import or recover absent original media. Imported path strings cannot recover missing original media. The updated App saves a separate snapshot for each record cascade-deleted with a property, stay or damage entry, in the same checked database operation. New stay and damage snapshots retain their full supported fields and media-path references. Recovery is per record: restore the property, stay and damage parents before their children. Missing or ambiguous parents, duplicate identifiers, unsupported payloads or a failed save leave the snapshot for retry instead of linking it to another record or overwriting existing data. Older snapshots remain readable, but missing fields and children that an older version never saved cannot be recreated. Snapshots do not duplicate original media bytes. Expiry purge runs when Recently Deleted opens, rather than on a guaranteed timer. Expiry purge and Delete Forever first queue known file paths, then commit snapshot removal; cleanup removes only unreferenced queued files. Failures can retain files and are retried during normal App startup or with Retry attachment cleanup. Unreadable reference data postpones removal. Original system photos, shared exports and earlier backups remain separate.
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.
Older versions may have written records to a separate fallback database. The updated App leaves those files in place and does not automatically merge, replace or delete them. 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 property, stay, communication, inspection and damage editors report failed saves and retain entered fields and selected photos where applicable. Original files selected for removal are queued rather than erased before saving. Damage records and their automatically prepared deadlines are committed together; reminder updates follow successful saving. Snapshot creation, deletion, restoration and permanent removal must save before the action reports success. 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.
Earlier exports should be checked before relying on them; the App update cannot repair an already saved incomplete JSON file. Older installed versions may use different save or cleanup ordering and may not offer these retry controls.