Hamanets

Personal finance for iPhone. Your money, on your device.

View My GitHub Profile

English · Українська

Hamanets — Privacy Policy

Effective date: 29 September 2026 Last updated: 29 September 2026


1. Summary

Hamanets is a personal finance app for iPhone. It has no user accounts, no sign-up, and no server operated by us.

Your financial data — accounts, transactions, categories, tags, budgets, debts and receipt photos — is created and stored on your device only. We cannot see it, we do not receive it, and we have no technical means of accessing it.

The app contains no analytics, no advertising, no tracking, and no third-party SDKs.

There are exactly four situations in which Hamanets communicates over the network, and each is described in detail in Section 4. Only one of them — sending us a problem report, which you start yourself — results in any information reaching us.


2. Who is responsible for your data

The data controller is:

Mykola Vasylevskyi, an individual developer, Ukraine. Contact: hamanets.app@icloud.com

Because Hamanets stores your financial data exclusively on your device and transmits it to no service of ours, we act as a controller only in respect of the limited information you choose to send us, as described in Section 4.3.


3. What Hamanets stores on your device

All of the following is written to storage inside the app’s own sandboxed container on your iPhone. None of it is transmitted to us.

3.1. Financial and organisational data

This is stored in a local database file inside the app container.

3.2. Receipt photos

If you attach a photo to a transaction, the selected image is copied into the app’s own storage as a file. Only the file name is recorded in the database.

Hamanets uses the iOS system photo picker. This means the app is not granted access to your photo library: iOS shows the picker outside of the app, and hands Hamanets only the single image you chose.

3.3. Credentials, held in the iOS Keychain

Both are stored in the iOS Keychain with the accessibility attribute kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly. In practice this means they are tied to this one device: they are not included in iCloud Keychain synchronisation and do not migrate to a new device through a backup restore.

3.4. Biometrics (Face ID / Touch ID)

If you enable biometric unlock, authentication is performed entirely by iOS. Your biometric data never leaves the Secure Enclave and is never made available to Hamanets; the app receives only a success or failure result. Hamanets neither collects nor stores biometric information of any kind.

3.5. Technical log of app launches and bank synchronisation

To help us diagnose problems with background bank synchronisation, Hamanets keeps a small technical log on your device. It records:

App starts, foreground and background changes, and background-task events are recorded with their date and time, to the second. The stages and outcomes of a sync attempt carry no time at all, and durations are recorded only as coarse ranges (such as “under 10 seconds”).

App starts and foreground and background changes are recorded whether or not you use bank sync. The other entries appear only if you have connected a bank account.

What the log never contains: no amounts, balances, account names or numbers, which or how many accounts were synchronised, whether or how many transactions were imported, currency codes, error messages, or anything you typed. Every entry is drawn from a fixed, predetermined list; the app cannot place arbitrary data into it.

How long it is kept: at most the last 7 days and at most 1,000 entries; older entries are deleted automatically. The log is excluded from device backups, and it is erased when you reset local data, disconnect your bank account, or delete the app.

The log never leaves your device on its own. It reaches us only as an attachment to a problem report that you choose to send (Section 4.3).


4. Network connections

This is the complete and exhaustive list of network destinations Hamanets contacts. There are no others.

4.1. Exchange rates — api.frankfurter.dev

Purpose: to convert amounts between currencies.

What is sent: currency codes (for example USD, EUR, UAH) and dates.

What is not sent: no amounts, no balances, no transactions, no account names, no device identifiers, no advertising identifiers, and no information that identifies you or your device.

The service requires no API key and no account, so these requests carry no credential that could link them to you.

4.2. Bank synchronisation — api.monobank.ua

This applies only if you choose to connect a monobank account. If you do not use bank sync, Hamanets never contacts this service.

How it works: you create a personal API token yourself in monobank’s own web cabinet and paste it into Hamanets. Your device then talks directly to monobank’s servers. There is no Hamanets server anywhere in this path. We do not receive, proxy, observe, or store your token, your bank credentials, your account details, or your transactions.

What is sent: your own token, in the request header, to monobank only.

What is received: your account information and statement entries, which are written to the local database on your device as described in Section 3.1.

Your use of monobank’s API is governed by monobank’s own terms and privacy policy. You can revoke the token at any time in the monobank cabinet, and you can disconnect the account inside Hamanets — with the option to delete the imported data at the same time.

4.3. Problem reports — email to us

This is the only path by which any information reaches us, and it never happens automatically. It occurs only when you choose Report a Problem — in Settings, or on the screen Hamanets shows if it cannot open your data — fill in the form, and send the message yourself.

How it is sent: Hamanets prepares a message and hands it to the standard iOS Mail composer. The message is sent from your own email account, through your own email provider. You can read, edit, shorten, or delete anything in it — including the attachments — before sending, and you can cancel without sending.

What the message contains:

  1. Your three free-text answers — what you were doing, what you expected, and what you saw. This text is entirely yours. The form explicitly asks you not to include account numbers, card numbers, or amounts.
  2. An error attachment, a plain-text JSON file named hamanets_<date>_<time>_error.err, containing only:
    • your device model and iOS version;
    • the Hamanets app version and build number;
    • the app’s internal database schema version;
    • up to three records of errors that occurred during the current session, each identified by a fixed code chosen by the developer in advance (such as which internal operation failed), not by your data.
  3. A sync-log attachment, a plain-text file named hamanets_<date>_<time>_sync.log, included only when the technical log described in Section 3.5 is not empty. It contains only:
    • the Hamanets app version and build number, the app’s internal database schema version, and the time the report was prepared;
    • the entries of that technical log, oldest first.

What the attachments never contain: no amounts, balances, account names, account numbers, card numbers, transaction descriptions, categories, receipt photos, PIN, bank token, or any other content you entered into the app. The fields are a fixed, predetermined list; the app cannot place arbitrary data into them.

What the sync log can show: when you started, opened and left the app during the last 7 days, and when iOS ran background bank sync. Because it records events in order, it can also show whether a sync attempt that was interrupted — for example because you left the app, or iOS stopped a background task — had already reached the stage of requesting statements from monobank. Reaching that stage does not by itself mean there were new transactions, and the log cannot show which accounts were involved or how many, any amount, or whether anything was imported.

What we necessarily learn: because the message arrives as ordinary email, we will see the email address you sent it from, along with anything you wrote.

Legal basis (GDPR): Article 6(1)(b) and 6(1)(f) — handling a support request you initiated, and our legitimate interest in fixing defects in the app. You are never required to send a report.

Retention: support correspondence is kept only as long as needed to deal with your report and to fix the underlying problem, and is deleted no later than 12 months after our last exchange with you, unless you ask us to delete it sooner.

International transfer: our support mailbox is operated by a third-party email provider that may process the message on servers outside the European Economic Area. Such transfers rely on the safeguards offered by that provider, including the European Commission’s Standard Contractual Clauses where applicable.

4.4. Hamanets Pro purchases — Apple’s App Store

This applies when you open the Hamanets Pro screen, buy Pro, or restore a purchase.

How it works: Pro is sold only through Apple’s App Store, using Apple’s own in-app purchase system. The purchase sheet, payment, billing, renewals, cancellations and refunds are all handled by Apple. There is no Hamanets server anywhere in this path.

What is sent: when you open the Pro screen, the app asks the App Store for the names and prices of the Pro options. When you buy or restore, iOS completes the purchase with Apple under your Apple Account. The app adds nothing of its own to these requests — no identifier, no account token, and none of your financial data.

What is received: the Pro options and their prices, and Apple’s signed record of your Pro purchases. The app uses that record, as kept by iOS on your device, only to decide whether Pro features are unlocked. Hamanets does not keep its own copy of your purchase history.

What reaches us: no information about you or your individual purchase. Your name, Apple Account, payment details and billing address stay with Apple. Apple provides us only with aggregated sales reports, as described in Section 7.

Your purchases are governed by Apple’s terms and Apple’s Privacy Policy. You can manage or cancel a subscription in iOS Settings → [your name] → Subscriptions, and request a refund from Apple at reportaproblem.apple.com.


5. What Hamanets does not do

To state the absences explicitly:


6. Backups

If you have iCloud Backup enabled in iOS, your iPhone’s backup — which includes Hamanets’ data, as it does for other apps — is stored in your own iCloud account. This backup is created and controlled by Apple under Apple’s Privacy Policy, not by us. We have no access to it.

As noted in Section 3.3, your PIN verifier and monobank token are marked device-only and do not travel to a new device through a backup. The technical log described in Section 3.5 is excluded from backups altogether.

If you disable iCloud Backup in iOS Settings, Hamanets’ data stays only on the device.


7. Data we may receive through Apple

Independently of the app, Apple may provide us with:


8. Security

No method of storage is absolutely secure, but because there is no server and no account, there is also no central store of user data that could be breached.


9. Your rights

Under the EU/EEA and UK General Data Protection Regulation and, in Ukraine, under the Law of Ukraine “On Personal Data Protection” (No. 2297-VI), you have the right to access, rectify, erase, restrict and object to the processing of your personal data, the right to data portability, and the right to withdraw consent at any time.

How these rights work in practice for Hamanets:

Data on your device. You control it directly and completely, without needing to contact us. You can edit or delete any account, transaction, category, tag, budget or receipt inside the app at any time. Deleting the app from your iPhone removes its database, its stored receipt images, its technical log and its Keychain items. Copies may persist in your own iCloud backups until those backups are overwritten or deleted by you in iOS Settings.

Bank connection. You can disconnect a bank account in Settings → Bank Sync, and choose to delete the imported data at the same time. Either way, disconnecting also erases the technical log (Section 3.5). You can additionally revoke the token in monobank’s own cabinet.

Support correspondence. Write to hamanets.app@icloud.com to request a copy of what we hold from your report, to have it corrected, or to have it deleted. We will respond within 30 days.

Complaints. You may lodge a complaint with a supervisory authority — in the EU/EEA, the data protection authority of your country of residence; in the UK, the Information Commissioner’s Office; in Ukraine, the Ukrainian Parliament Commissioner for Human Rights (Уповноважений Верховної Ради України з прав людини).


10. Children

Hamanets is a general-audience personal finance app. It is not directed to children under 16, and we do not knowingly collect personal data from them. Since the app has no accounts and collects nothing automatically, we have no means of identifying a user’s age. If you believe a child has sent us a support report containing personal data, contact hamanets.app@icloud.com and we will delete it.


11. Changes to this policy

If this policy changes, the updated version will be published at this address with a new effective date. Material changes — in particular any change to what leaves your device — will also be noted in the app’s release notes on the App Store. Continuing to use Hamanets after a change means you accept the updated policy.


12. Contact

Questions about this policy or about your data:

hamanets.app@icloud.com