Dongle Money   한국어

Dongle Money Privacy Policy

1. Operator and contact

Zeta4lab (zeta4app), an individual developer in the Republic of Korea. For privacy inquiries, or to access, correct or delete support messages and feedback held by the developer: zeta4app@gmail.com. You do not need to attach your ledger.

2. Records and settings you enter

Dongle Money is a personal ledger you write by hand. It handles the names of accounts, cash, cards, loans and payment methods; income, expense, transfer, loan and card records; categories; titles and notes; the date, time and time zone of each record and when it was created and changed; budgets and asset groups. It stores currencies and original amounts and works out balances and statistics. Free-text fields can hold personal information such as names; do not enter personal information you do not need.

The app does not fetch transactions from banks or card companies. It does not need and does not accept account numbers, card numbers or bank sign-in details. There is no sign-up and no sign-in. Settings such as language, appearance, statistics currency, reminders, app lock and screen cover are stored on the device only. The time zone is read from the device's own setting; location is not used.

3. Device storage, app lock and screen cover

The ledger is stored in the app's private space on the device. There is no developer server, and the developer cannot receive or see your ledger. Storage protection is left to the operating system; the app does not encrypt its database separately. Android uses app storage available after device authentication; iOS uses file protection available after the first device authentication following a reboot.

App lock (optional) calls the operating system's biometrics or device authentication. The app receives only the result, never biometric data or your device passcode, and does not ask for a separate app password.

Screen cover (optional, off by default): when on, on Android the app does not appear in screenshots or screen recordings and is covered in the recent apps list; on iOS it is covered while you switch apps and while the screen is recorded or mirrored. Screenshots cannot be blocked on iOS. When off, the screen shows as in any other app.

4. Notifications and permissions

In notification settings you can turn a daily reminder on or off and choose its time. Turning it on asks for the operating system's notification permission. It notifies once a day only while records still need review; whether it is on, the time, whether anything still needs review (not a count) and the notification language are handled on the device only. On Android the app receives the boot-completed broadcast to schedule the reminder again after a restart. The notification text is generic, such as "Open the app to review", and carries no titles, amounts, account names or notes. No server push is used.

Android declares the internet, notification, boot-completed and biometric permissions. The internet permission is used only for the requests in section 7, never to send your ledger. Files are read or written only at the destination you choose in the system picker. Advertising ID, location, contacts, camera and microphone are not used.

5. Optional backup and import

When you choose to export and pick a destination, a copy of the ledger is passed to that file provider. Backup files are not encrypted and contain transactions, account names, notes and archived records. Anyone who has the file can read it. Avoid shared folders or places others can reach. Import reads and checks the file you choose and applies it as you confirm. Before replacing the current ledger a separate copy is kept.

If the destination is a place such as iCloud Drive or Google Drive, that provider may sync the file to its servers under its own account settings, terms and privacy policy. The app does not control the provider's processing countries or retention. The app itself has no cloud sign-in and no automatic sync.

6. Retention and deletion

The ledger on the device has no automatic expiry. Deleting a record in the app moves it to the archive and leaves it out of totals; it is not permanent erasure. Archived records remain in backups. With no developer server and no account, the developer cannot remotely find or delete the ledger on your device.

Clearing the app's data or uninstalling the app removes the ledger. Check the copies you need first. Exported backups, copies kept before a restore, and a provider's trash or version history remain separately and are not removed by uninstalling; manage them with that provider's own deletion tools.

7. Requests the app sends off the device

New version check. An app installed from a store reads the store's public version when it starts, to tell you about a newer one. On Android it sends the package name and a region and language code to the app's Google Play page; on iOS it sends the app identifier and a region code to Apple's lookup address. Nothing from your ledger or settings and no device identifier is sent. The store handles connection information such as your IP address under its own policy, as for any web visit.

Automatic rates (optional, off by default). If you turn automatic rates on in settings, the app fetches the European Central Bank's public reference-rate file (www.ecb.europa.eu) once or twice a day and uses it to show totals across currencies. The request contains nothing from your ledger: no amounts, currencies, accounts or device identifiers; it is the same file anyone receives. The European Central Bank handles connection information under its own policy, as for any web visit. Fetched rates are stored on the device only and are not written into records or backups. Turning the setting off stops the requests. A ledger in a single currency makes no request even with the setting on.

The app sends no other requests of its own. It contains no advertising and no behavioural analytics tools.

8. Stores, purchases and test programs

The app does not sell anything at present. Code and libraries for store billing are included but switched off, so no purchase is looked up or requested. If purchases are offered, what they involve will be written here first. Payment details such as card numbers are handled by the store; the app and the developer do not receive them.

If you get the app through a Google Play test program or Apple's TestFlight, that store may collect crash and usage information and any feedback you send, under its own policy, and provide it to the developer. Depending on how you were invited, your name or email may be included. This is separate from the app sending your ledger, which it does not do.

9. What we receive when you contact us

If you email us, the developer receives your address, your message and anything you attach. Include only the app version, device, operating system and the steps and result; do not include financial details or passwords. Messages are used only to solve the problem and improve the app. The developer's copies are deleted within 90 days of the matter being resolved, and earlier on request.

10. Changes

If a feature that changes what is processed is offered, such as purchases, family sharing or automatic sync, this policy and the store disclosures are updated first. The date of the change is written at the top of this document.