Privacy Policy — Waleeta

Last updated: 23 October 2026

This policy explains how the Waleeta iOS app handles your data, including backup export and restoration, contacting support, and visiting our website.

1. Data you enter and how it is used

Waleeta lets you record salary, income, expenses, budgets, commitments, subscriptions, debts, installments, savings goals, categories, notes, and preferences.

The financial state also includes payment and savings records, previous salary cycles and their adjustments and historical snapshots, and archived items. Names and notes may contain personal information you choose to enter.

The app processes this data on your device to organize your records and calculate and display balances and indicators.

2. Local storage

The active financial state is stored in a SQLite database inside the app’s container on your device. The app also uses limited local preferences, including initialization markers. An older financial copy may remain in localStorage within the container until removed through the app’s procedures.

Core financial features do not require an account, and the current version does not automatically send your financial records to Waleeta servers to provide those features.

Not every copy of the data exists exclusively in SQLite. Exported files, temporary export files, and backups retained by the operating system under your device settings may also exist.

3. Export, sharing, and restoration

You can export the saved financial state, including historical records and archived items, to a JSON file, then choose to save or share it through the iOS share sheet. The file is not a backup of every app file or every internal data store.

The app creates a temporary file for sharing and attempts to delete it after the operation. The file may remain if cleanup fails, and the app displays an error when it detects that failure. Completing the share action alone does not confirm that you saved a copy outside the app; check the destination you selected.

You can select a compatible backup through Files. Waleeta checks its format, compatibility, checksum, and data structure, and presents a preview and warning before your explicit approval to replace the entire current financial state, rather than merge it.

When restoring over an existing state, the app retains the previous state in an internal SQLite recovery record until a later restore or a full reset, with no fixed retention period. This record is not an off-device backup, and there is currently no separate user interface for manually restoring it.

4. Backup-file integrity

Exported JSON files are unencrypted and are not password-protected. They may contain sensitive financial and personal information, including archived items. Anyone who obtains the file may be able to read its contents.

The SHA-256 checksum helps verify that the financial-state text inside the file matches its stored checksum. It does not encrypt the file, establish its creator or origin, or guarantee the accuracy of financial information entered by the user.

Keep backups in a secure location and share them only with a destination you knowingly choose. Protection of a copy held by an external storage or sharing service depends on that service’s settings and policies.

5. Data protection and storage errors

Waleeta relies on the protections iOS provides for the device and app container. The current version does not enable separate, additional encryption for the SQLite database.

The app checks important read, save, and restore operations and displays an error when they cannot be confirmed. A read error is not intended to automatically create a new financial state over existing data.

Recovery cannot be guaranteed in every case of device damage, loss, or inaccessible storage. Keep a secure export outside the app, and do not delete or reset the app to troubleshoot a storage error before confirming that you have a suitable backup.

6. Device permissions and external services

The app uses file selection and the share sheet when you request restoration or export. The current version does not require general access to your photos, contacts, camera, microphone, or location for its financial features.

If you enable “Shake to undo,” the app may request device-motion permission when iOS requires it. Motion signals are processed locally to detect shaking; they are not stored as a motion history or sent to Waleeta. You can disable the feature in the app’s settings.

The current version contains no advertising, usage-analytics, tracking, or crash-report submission tools added by the Waleeta developer. The Tajawal font loads from files bundled with the app.

iOS services, file providers, and destinations you choose to share with may connect to the network under their own settings and policies. This is separate from the app automatically sending your financial records to Waleeta.

7. Retention and deletion

Ordinary deletion of supported items moves them to the recoverable Deleted Items Archive; it does not permanently erase those items.

When you confirm “Reset the entire app,” the app replaces the financial state of the affected environment with starting data and removes its active financial data, archive, cycle records, internal restore recovery record, and matching old financial localStorage key. This operation does not affect data in the other app environment.

Reset does not delete JSON files saved outside the app, iOS backups, or support correspondence. It does not guarantee removal of every technical trace or remaining temporary file, and it does not guarantee forensic erasure.

Deleting the app may cause the loss of data in its container. Export a suitable backup before deleting the app or changing devices. Waleeta cannot remotely delete your local files or copies you have saved with other services; those copies must be managed on your device or through the relevant service.

8. Children

Waleeta is intended for personal money management and is not designed specifically for children. The current version does not require a user account. The age requirements and rating shown in the App Store apply.

9. Changes to this policy

We may update this policy when the app’s features or data-handling practices change. The revised policy will show its last-updated date. Review the policy when using a new version or service.

10. Contact and support website

For privacy or data enquiries:

Official email: waleeta.support@gmail.com
Support website: https://waleeta-app.github.io/

When you contact us, the support mailbox receives your email address, message, and any attachments you choose to send. This correspondence is separate from financial data that remains locally within the app. Avoid sending a complete financial backup or sensitive information that is unnecessary to explain the issue. We retain support correspondence as needed to resolve and follow up on enquiries, and review older messages and delete those no longer needed, subject to applicable legal retention obligations. You can use the same address to enquire about your support correspondence or request deletion; we will review the request and delete what we can under applicable obligations. We do not request a complete copy of your financial data; if information is needed to resolve an issue, we ask for the minimum necessary with your consent.

Gmail is used to receive support correspondence, and Google’s processing of email is subject to its policies. The support website is hosted on GitHub Pages, which records visitors’ IP addresses for security purposes under the GitHub Privacy Statement. Visiting the website or contacting support does not automatically give us access to the Waleeta database on your device.