aWallet Next Privacy Policy

• Everything you enter into aWallet Next is stored encrypted on your own device. The encryption keys are derived from your master password, which is never sent anywhere. The author of the app cannot read your data and has no access to it.

• There is no aWallet account and no aWallet server that stores your data.

• If you turn on cloud sync, the encrypted vault file (data.crypt2) and encrypted attachment files are stored in your own iCloud Drive, Google Drive, Dropbox or WebDAV storage, transferred over encrypted connections. The cloud provider sees only encrypted files.

• The optional breach check sends the first five characters of a password's SHA-1 hash to the Have I Been Pwned service, never the password or the full hash. Results are cached only on the device.

• When you tap "Change password" on an entry, the app contacts that entry's website directly to find its password-change page. Nothing from your vault is sent.

• Subscriptions are sold and billed by the Apple App Store or Google Play. To confirm purchases the app uses the RevenueCat service, which receives a random identifier generated by the app (or the sign-in's account identifier, see below) and the store's purchase receipt, never your name, e-mail address or any vault data.

• Optionally, you can sign in with your Apple or Google account to use one subscription on your other devices, including between iPhone and Android. Firebase Authentication (Google) then keeps the sign-in record: an account identifier and, as provided by Apple or Google, your e-mail address and name. It is used only to link your subscription. You can delete it at any time in Settings ▸ Subscription ▸ Delete sign-in, or by writing to next@awallet.org. More: Delete your data.

• If you export data to CSV or share an entry as text, that copy is not encrypted; handle it with care.

• aWallet Next collects no analytics, no telemetry and no statistical data about you, and shows no advertising.

• Contact for privacy questions: next@awallet.org.

Google

aWallet Next uses Google services only when you choose to: Google Drive as your cloud for sync, or signing in with your Google account to use one subscription on your other devices.

• What we access. With Google Drive sync, the app asks only for the "files created by this app" permission (drive.file): it can see and change only the encrypted vault and attachment files it created in your Drive, none of your other files. With Google sign-in, Google shares your account's basic profile: account identifier, e-mail address and name.

• How we use it. Drive access is used only to store, update and download your own encrypted vault and attachments, so your devices stay in sync. Your Google sign-in is used only to link your subscription across your devices; the e-mail address (or name) is shown to you in Settings so you can see which account is signed in.

• Where it is stored. Your vault and attachments are stored in your own Google Drive, encrypted on your device before upload; Google and the author of the app cannot read them. The Drive sign-in token stays on your device. For the subscription link, Firebase Authentication (Google) keeps the sign-in record.

• Sharing. We do not sell, share or transfer Google user data to anyone. It is not used for advertising, analytics or to train any models, and no person reads it.

• Deleting your data. Remove aWallet Next's access at any time at myaccount.google.com/permissions, and delete the aWallet Next files in your Google Drive if you no longer need them. Delete sign-in in Settings ▸ Subscription deletes the sign-in record.

• aWallet Next's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

Dropbox

• What we access. With Dropbox sync, the app has access only to its own app folder in your Dropbox (Apps ▸ aWallet Next) and the encrypted files it creates there, none of your other files. It also reads your Dropbox account name and e-mail address, only to show you in Settings which account is connected.

• How we use it. Only to store, update and download your own encrypted vault and attachments.

• Where it is stored. In your own Dropbox, encrypted on your device before upload; Dropbox and the author of the app cannot read your files. The Dropbox sign-in token stays on your device.

• Sharing. We do not sell, share or transfer your Dropbox data to anyone.

• Deleting your data. Disconnect aWallet Next at any time under Dropbox Connected apps (https://www.dropbox.com/account/connected_apps), and delete the Apps ▸ aWallet Next folder if you no longer need it.

WebDAV

• The encrypted files are stored on the server you enter (for example your own NAS or a storage provider you choose), and the app connects only to that server.

• The server address and user name are stored on your device; the password is kept in the device's secure storage (Keychain on iOS, Keystore on Android). They are never sent to anyone else, including the author of the app.

iCloud Drive (iPhone and iPad)

• The encrypted files are stored in aWallet Next's folder in your own iCloud Drive. Your Apple Account sign-in is handled by iOS; the app never sees your Apple credentials, and Apple cannot read the encrypted files.