Effective date: July 20, 2026 Publisher: Adam Fischer, independent developer, Florida ("we," "us," "the developer") Applies to: the LossList mobile application for iPhone and iPad (the "App")
LossList stores your claim documentation — inventory, photos, receipts, interview answers — on your device. We do not collect, receive, transmit, sell, or share your data. We do not run analytics, advertising, or tracking of any kind. Your claim file leaves your device only when *you* export and share it, and the exported file is encrypted so that only someone you give the transfer code to can open it.
Claim documentation. Your name and contact details, property address, loss details, inventory items, interview answers, and notes you enter are stored locally on your device using Apple's on-device database. This information is never transmitted to the developer or any third party by the App.
Photos and receipts. Photos you capture or import, and receipts you scan, are stored on your device within the App. When you take a photo through the App, the App records the date, time, and (if you have granted Location permission) the GPS coordinates of capture, and embeds them in the photo file. This supports the evidentiary value of your documentation. Receipt text recognition runs entirely on your device using Apple's built-in text recognition; receipt images and recognized text never leave your device.
Location. The App requests "While Using" location access solely to stamp capture coordinates on your photos. Location is not tracked in the background, stored outside your claim file, or shared with anyone. You may decline Location permission and the App will function without GPS stamping.
Barcode lookups — the App's only network feature. If you scan a product barcode, the App sends the barcode digits (only the digits — nothing about you or your claim) to a product database to identify the item's name and brand. If you never use barcode scanning, the App makes no network requests at all. Lookups are not linked to your identity, and the developer operates no server and receives nothing.
Encrypted exports you initiate. When you purchase the export unlock and generate your claim file, the App produces an encrypted package on your device. Sharing it — by AirDrop, message, or any share destination — is performed by you through your chosen service. The package can only be opened with the transfer code the App displays to you; the developer never receives the file, the code, or a copy of anything in it.
Device backups. Your data may be included in your device's iCloud or computer backup according to *your* Apple backup settings. Those backups are governed by Apple's terms and your Apple account, not by the developer.
The one-time export unlock is processed entirely by Apple through your Apple Account. We never see or store your payment information; Apple's handling of your payment data is governed by Apple's privacy policy. Your documentation remains yours and remains on your device whether or not you purchase the unlock.
Because your data lives on your device, you control it completely. Deleting items in the App deletes them from the App's storage. Deleting the App removes all App data from your device (subject to any device backups you maintain). Exported claim files you have shared are in the possession of whoever you shared them with — encrypted, and openable only with the transfer code you provided.
The App is intended for use by adults documenting property losses. It is not directed to children under 13, and we do not knowingly collect information from children.
Privacy laws in some regions (such as the California Consumer Privacy Act and the EU General Data Protection Regulation) grant rights over personal data a business collects. Because the developer does not collect or possess your personal data through this App, there is no developer-held data to access, correct, or delete — your device holds the only copy.
If a future version of the App adds features that change how data is handled, we will update this policy and note the new effective date before those features take effect.
Questions about this policy: Hello@Praxis-HQ.ai