1. Your expense records
Amounts, dates, notes, categories and ledger preferences are stored locally on your device. The app and its own quick-entry extension share this ledger so Shortcuts and widgets can record expenses. If you enable an iCloud feature, the relevant records or backups are also sent to your own iCloud account as described below. The developer does not receive your expense records through the app.
There is no advertising SDK, behavioral analytics SDK or bank connection. You can edit, delete and export records in the app. Deleting a record does not remove copies already present in exported files, recovery snapshots or external backups.
2. Optional iCloud backups
Automatic iCloud backups are off by default. When you enable them or request a backup, a complete SQLite snapshot is sent to your own iCloud Drive through Apple's service. It includes expenses, categories, ledger preferences, timestamps and an installation identifier that distinguishes backups from different installations. The developer does not operate a server that receives these files.
Snapshots are backups, rather than live synchronization between devices. Automatic checks run during active, unlocked use. A queued transfer is shown as uploaded only after iCloud confirms completion.
After the latest snapshot is confirmed uploaded, automatic retention keeps that copy plus up to 30 daily copies for that installation. Pending or failed transfers and other installations' copies can remain. Turning automatic backups off keeps existing cloud files. Manage those files separately in iCloud Drive → Daily Expenses → Backups. Apple's privacy policy governs its iCloud service.
3. Optional iCloud sync
iCloud sync is off by default. If you enable it on compatible native app versions, expenses and categories are sent as records to your iCloud account's private CloudKit database in the Daily Expenses container. Records include amounts, dates, notes, category details, audit timestamps and random change IDs with relationships between changes. The app also keeps an account-bound sync cursor and pending changes on this device. The developer does not operate a server that receives these records.
Sync runs during active, unlocked app use and when you reopen the app. Other enabled devices on the same iCloud account can receive new expenses, edits and deletions. Appearance and app-protection preferences are not synchronized. Offline changes wait locally. Conflicting versions are retained for review; pausing sync does not delete existing cloud records.
Sync history is currently append-only: deleting an expense removes it from the current ledger, but previous values and deletion history remain in the private sync store. Superseded and deleted content, conflict versions and cloud backups are not automatically erased together. Manage the app's iCloud data separately using Apple's controls. Sync history has no automatic compaction in this version and uses your iCloud storage. Apple's privacy policy governs iCloud.
A recovery snapshot is saved locally before enabling sync. Sync state and account binding are excluded from portable ledger backups. Restore requires sync off; re-enabling reconciles the restored local ledger with iCloud rather than replacing all devices' data.
4. Exports, clipboard and recovery
CSV, JSON and SQLite files are sent only to destinations you choose using the system share sheet. The Spending copy action writes category totals to the system clipboard when you request it. Apps and services you choose may receive those files or clipboard contents under their own policies.
Exported files and SQLite snapshots contain readable expense data. App protection does not password-encrypt them. Restoring a backup replaces the current ledger and saves a recovery snapshot inside the app. Delete or retain external copies separately.
5. Device authentication
Optional app protection uses Apple's Face ID or device-passcode authentication. Daily Expenses receives an authentication result, not your facial data or passcode. Protection preferences and iCloud consent are stored separately from restorable ledger data.
Quick-entry actions use device authentication. A preset's configured label may be visible on a widget, so avoid putting sensitive text in a visible label.
6. App updates and network requests
Daily Expenses uses Expo EAS Update to check for and download compatible app updates. Requests include a random installation token, platform/runtime and update information. During update recovery, the installed update library may also send update-related fatal-error text. Network services receive connection information such as an IP address. These update requests do not include your expense ledger.
Expo processes update-service data under its privacy policy. Daily Expenses does not use an advertising identifier or cross-app advertising tracking.
7. Website and support
The support website has no advertising, analytics scripts, third-party fonts or contact-form database. Hosting and network providers process requests and may retain ordinary access and error logs to deliver and protect the website.
When you email support, your email address, message and any attachments you choose to include are processed to respond to your request. Email is handled through the support mailbox provider. Correspondence is retained as needed to resolve the request and meet applicable obligations; you can request deletion. Do not send passcodes, credentials or financial databases in a support message.
8. Retention and your choices
Your ledger remains on your device until you change or remove it. Deleting the app may remove local records and recovery copies, while system backups, iCloud files and exports can remain separately. Keep a completed backup outside the app before reinstalling it.
You can export, correct or delete local expenses, turn automatic iCloud backups off, manage cloud files, and disable optional app protection. Depending on where you live, you may also have rights to access, correct, delete or restrict processing of personal information. Contact support about information you have sent directly to the developer. The developer cannot retrieve a ledger stored only on your device.
9. Policy updates and contact
This policy may be updated when the app or its services change. The date above identifies this version. For privacy questions or requests, contact Astrit Zeqiri at astritzeqiri5@gmail.com.