Privacy Policy
Actua is an independent, community-built Android client for Actual Budget. It is not affiliated with or endorsed by the Actual Budget team. This policy explains what data Actua handles and where it goes.
Your budget data
Actua connects directly to the Actual server you configure — your own self-hosted instance. Budget data (accounts, transactions, categories, budgets, rules, schedules and reports) is synchronized between that server and your device using Actual's end-to-end encrypted sync protocol, and a copy is kept in a local, on-device SQLite database so the app works offline.
Actua does not operate a server of its own, and your budget data is never sent to the developer or to any third party controlled by this project. The only network destination for your budget data is the Actual server you provide.
Credentials and encryption keys
Server credentials and sync/encryption keys are stored using the Android Keystore and are not readable by other apps. They are never logged or transmitted anywhere other than to your configured Actual server as part of authentication, sync and ending your session when you disconnect.
Location-aware payees
Actua can optionally suggest payees based on your location while the app is open. This feature is off by default, requires you to explicitly grant foreground location permission, and does not run in the background. When enabled, any saved payee coordinates are stored as part of your budget data (local SQLite database and your Actual server, subject to the same sync described above) — not with any separate location or advertising service. You can inspect or delete saved payee locations at any time from Settings → Privacy → Payee Locations, or turn the feature off to stop recording new locations.
Imports
CSV, OFX, QFX, QIF, CAMT.053, XLSX, PDF, SMS and notification imports are processed entirely on your device to create transactions in your budget. Imported files and their contents are not uploaded anywhere except as part of the transactions they produce, which sync to your own Actual server like any other budget data. A statement file shared to Actua from another app is read through the temporary access Android grants for that file and is not kept.
Exports
Actua can export transactions to a CSV file. The file is written only to the location you choose in Android's file picker and is not uploaded anywhere. It is an ordinary, unencrypted file that contains your transaction details, so keep it as private as the budget itself.
Bank notifications and automation apps
Capturing bank notifications is off by default. It works only after you turn it on, choose which apps to read, and grant Actua notification access in Android's settings. Actua then reads the title and text of new notifications from those apps only, on your device. It keeps just the transaction details it recognizes (date, amount, payee, reference, a card or account suffix, the source app's name) in a review queue on your device; it does not store the notification itself and ignores notifications from every other app.
Transactions sent by Tasker or other automation apps are accepted only while you have turned that option on, only with the private token Actua shows you, and they join the same queue. Nothing in the queue is written to your budget until you approve it.
To pre-fill accounts, Actua remembers on your device the account you chose for each card or source and an optional default account, per budget. Deleting notification data on the import screen removes the queue, those choices, the parser settings and the token.
App lock and screen privacy
Actua can optionally ask you to unlock it with a fingerprint, face or your device PIN, pattern or password. The check is done by Android's own biometric prompt: Actua only learns whether it succeeded and never receives, stores or transmits your biometric data or device credential. For this Actua declares Android's USE_BIOMETRIC (and USE_FINGERPRINT on older versions) permissions, which are normal permissions that show no prompt. The setting and its timeout are stored on your device only. A separate setting hides Actua's screens from the recents list and blocks screenshots and screen recording.
Notifications
Actua can post notifications only when you turn them on: credit-card payment reminders, scheduled-transaction reminders, and a notification for each captured transaction. They are created on your device from your budget data and never sent through a notification service. Scheduled-transaction reminders and capture notifications hide their details on a secure lock screen.
Local network access
On Android 17 and later, Actua asks for Nearby devices (local network) access only when your Actual server's address is on your local network. It is used only to reach that server.
No analytics, ads or tracking
The F-Droid build and the plain Actua-v<version>.apk on GitHub Releases do not include analytics, crash reporting, advertising or other third-party tracking SDKs, and Actua does not collect usage data about you.
The one exception is receipt scanning in the Google Play version and in Actua-v<version>-full.apk. It uses Google ML Kit, which can send technical diagnostics to Google (see Receipt scanning below). Actua itself still shows no ads, collects no usage data and sends no analytics of its own.
Diagnostics
Actua keeps a short log of recent app activity on your device (Settings → About → Diagnostics) to help troubleshoot problems: crashes, failed actions, screens opened, syncs and server requests. It records error types, code locations, request paths, status codes, timings and counts only. It never records error text, your server address, passwords, tokens, encryption keys or budget data. Entries older than seven days are deleted, and you can clear the log at any time. The log never leaves your device unless you copy, save or email the report yourself.
Backups and Google Drive
Automatic local backups stay in private app storage on your device and are not uploaded anywhere unless you configure an optional destination.
If you choose to enable Google Drive backup:
- Actua connects directly to the Google Drive API to upload encrypted backup archives to your personal Google Drive account.
- Actua requests least-privilege access strictly to files it creates (
https://www.googleapis.com/auth/drive.file). It cannot access your other Google Drive files or folders. - Backup archives are encrypted on-device before transmission using client-side authenticated AES-256-GCM encryption with a key derived from your backup password. Google cannot decrypt or view your budget contents.
- OAuth tokens and encryption keys are stored using the Android Keystore in private app storage and are explicitly excluded from Android cloud backups and device-to-device transfers.
- You can disconnect Google Drive and revoke access at any time from Settings → Backups.
WebDAV backup
If you choose to set up WebDAV backup (for example with Nextcloud, ownCloud, or a NAS):
- Actua connects directly to the WebDAV server whose address you enter. It does not use any server of its own, and nothing is sent to the Actua developers.
- Backup archives are encrypted on your phone before they are sent, with the same client-side authenticated AES-256-GCM encryption used for Google Drive backups, using a backup password you choose. The server only receives encrypted files and the file and folder names Actua creates (a folder per budget and a date-based file name).
- Your WebDAV username and app password, and the backup password, are stored using the Android Keystore in private app storage and are explicitly excluded from Android cloud backups and device-to-device transfers.
- Connections use HTTPS by default. Plain HTTP is only used if you turn it on yourself, after a warning that your username and app password could then be read on the network. If the server uses a self-signed certificate, you can review and trust that one certificate for that server; hostname checking stays on.
- You can disconnect WebDAV at any time from Settings → Backups. This makes Actua forget the address and passwords on your phone; it does not delete backups already on your server.
Receipt scanning (Google Play version only)
The Google Play version of Actua can read a receipt photo to suggest a payee, date and total:
- The photo is read on your phone with Google ML Kit's text recognition, using a model that is bundled with the app. Actua does not upload the photo or the text read from it, and nothing is sent to the Actua developers.
- Google may receive technical diagnostics from ML Kit. The ML Kit library that does the reading can send technical diagnostics and usage data to Google over HTTPS: for example the phone model and Android version, Actua's package name and version, an installation identifier that is not meant to identify you, and how long a scan took or whether it failed. Google's ML Kit documentation lists this data and says it is not passed on to other companies. The data Google lists is technical metadata; it does not list receipt photos, recognized text or budget data. Actua cannot switch this reporting off. We have not confirmed that ML Kit's bundled text recognition models send it, because Google's list does not cover them, so this describes what the library can do. See Google's ML Kit data disclosure.
- A photo you take is written to the app's temporary cache only while it is read, and is deleted straight after unless you choose to keep it (see below). A photo you pick from your gallery is read in place and not copied. Actua does not keep the recognized text.
- Nothing is saved from a scan until you check the transaction and tap Save.
- The camera app (not Actua) takes the photo, so Actua does not ask for camera permission.
- Latin, Chinese, Japanese, Korean and Devanagari scripts are read. Receipts in Cyrillic, Arabic, Hebrew, Thai, Greek or Bangla may be read badly or not at all.
- Receipt scanning is not in the F-Droid build, nor in
Actua-v<version>.apkon GitHub Releases (the same open-source build). It is in the Google Play version and inActua-v<version>-full.apkon GitHub Releases.
Keeping a receipt photo
After a scan you can turn on "Keep the receipt photo" before saving the transaction:
- The photo is stored as a compressed copy (longest side 1600 pixels) in Actua's private storage on this phone, in a folder per budget, named after the transaction. You can open it again from the transaction and remove it there.
- Photos are never synced to an Actual server. Encrypted WebDAV backups include kept photos from private storage and the currently accessible receipt folder, and restore them with their transactions. Local backups, Export archive and Google Drive backups still exclude photos. The transaction link is a file name, never a synced budget field. Android backup and device-to-device transfer exclude private photos.
- Restoring a WebDAV backup recovers its photos into private storage, including on another phone. Older backups without photos and re-downloading from Actual cannot recover them. Restoring preserves existing photos absent from the backup; restored copies take precedence over copies in the selected external folder.
- Deleting the transaction deletes its photo, and removing a budget from the device deletes that budget's photos.
- The app lock protects the photo while it is inside Actua. Actua includes it in WebDAV backups when you configure that destination.
Choosing a receipt photo folder
In Settings → Transactions → Receipt photos you can choose a folder for new photos, for example on an SD card or in a folder that a sync app such as Nextcloud mirrors. This is off by default.
- Photos in that folder are outside Actua's control: the app lock does not protect them, other apps with access to the folder can read them, and any app that syncs or backs up that folder will copy them. Actua includes readable photos in encrypted WebDAV backups when configured, as explained before the folder picker opens.
- The folder is picked with the system folder picker, so Actua can only reach that folder and keeps the permission only on this phone. The setting is excluded from Android backup and device transfer.
- Photos go to
Actua receipts/<budget>/<transaction>.jpginside the folder, one subfolder per budget. Photos already kept stay where they are, and are not moved when you change the folder; photos left in a folder you stop using are no longer shown in Actua. - Deleting a transaction deletes its photo in the folder, and removing a budget deletes that budget's subfolder, where the folder allows it.
- If the folder is gone, unmounted or no longer allowed, new photos are kept in private storage instead and Actua tells you; transactions always open.
- Photos enter encrypted WebDAV backups only, never Actual sync, local or Google Drive backups, or standard exports.
Other on-device data
Actua keeps app settings, which bank-synced transactions you haven't viewed yet, how many transactions you've added (so the Google Play version can ask once whether you'd like to support Actua, and whether it has already asked you to rate Actua on Google Play), whether Google Play last reported you as an Actua Supporter and when it was last checked (so the Google Play version can show cosmetic Supporter extras), the optional nickname you can give the Supporter greeting and the date it last appeared, and similar display state on your device. None of it is sent anywhere. Support Actua purchases and subscriptions are paid and managed by Google Play; Actua never sees your payment details. The rating request in the Google Play version uses Google's in-app review sheet, which Google Play runs; Actua is not told whether you rated or what you wrote.
Contact
Questions about this policy can be sent to [email protected], or raised as an issue on GitHub.