Privacy policy.

I. What we collect

Nothing. Receipt Folder does not have a server. There is no analytics SDK, no crash reporter, no advertising identifier, no third-party tag. The app is fully self-contained on your device.

II. What's stored on your device

When you add a receipt, the app saves the following locally on your device (via Apple's SwiftData, which writes to a private app database):

• The product name, store, purchase date, and price you entered or scanned.
• The receipt photo and an optional item photo.
• The calculated return-window and warranty-expiry dates.
• Any notes you add.
• If you capture proof-of-return: the counter-receipt photo, a timestamp, and your optional note.

III. iCloud sync (optional)

If you're signed into iCloud and have it enabled on your device, Receipt Folder uses a private CloudKit database — scoped to your Apple ID — to sync receipts between your iPhone, iPad, and Mac. This is end-to-end between your own devices and Apple's servers; the developer has no access to it. If you disable iCloud or sign out, the app falls back to local-only storage automatically.

IV. Photo scanning

Receipt photos are processed by Apple's Vision framework on your device. No image or extracted text is sent to any server — not to us, not to Apple. On devices running iOS 26 or later, optional Foundation Models may be used for smarter receipt parsing; this also runs entirely on-device.

IV-b. Email receipt import

When you share a receipt email to the app from Mail, the subject and body of that email are handed to a parser that runs entirely on your device. No inbox credentials, email bodies, message IDs, or attachments are ever uploaded — the feature is a one-time share from Mail to Receipt Folder, not a background inbox scanner. The parsed result is then saved as a regular receipt (see II).

On iPhones running iOS 26 with Apple Intelligence enabled, any retailer not covered by a built-in template falls back to Apple's on-device Foundation Models framework to extract the fields. The email subject and body are used as prompt input to the on-device model; no prompt or response ever leaves the device or touches the developer's infrastructure.

IV-c. Household sharing (optional)

If you opt into household sharing (Settings → Family sharing), the app creates a CloudKit shared record zone under your own iCloud account and invites participants through the standard iOS share sheet. Only receipts you explicitly flag Share with household are mirrored into that zone; all other receipts stay private. We never see the invite, the participants, or the shared records — the entire flow runs through Apple's CloudKit sharing primitives. You can end sharing at any time in Settings, which revokes participant access immediately.

V. Permissions

We ask for only what a feature actively needs:

• Camera — when you choose to scan a receipt, take an item photo, or capture proof-of-return.
• Photo Library — when you choose to import a photo.
• Notifications — to deliver the reminders you asked for.
• Face ID / Touch ID — only if you enable app lock.
• Calendar — only when you tap "Add to Calendar" on an item.
• Mail share sheet — invoked by you when you share an email receipt to the app; the app never reads your inbox.

Each permission can be revoked at any time in system Settings.

VI. Third parties

There are none. No ad networks. No analytics vendors. No crash reporting. The only external communication the app ever does is with Apple's iCloud on your behalf, and only if you've signed in.

VII. Children

The App is not directed at children under 13. We collect no personal information from anyone, which includes children.

VIII. Your rights

Because we don't hold your data, there's nothing for us to delete or export on your behalf. Your receipts are yours. To erase them, delete the app from your device — all local data is wiped. To export, use the app's built-in Export feature (Settings → Export data → CSV or JSON).

IX. Contact

Privacy questions: honorius@neogy.dev. Real human, real reply.

---

— End of policy —