Milely does not connect to your bank. The financial details you save are encrypted on your iPhone before they are stored. This page sets out what that covers, and what it does not.
New transactions, saved card details, reward settings, receipt files and Auto Log purchase details are encrypted on your iPhone before they are stored, using AES-256-GCM authenticated encryption. Data travels to our servers over HTTPS.
The key that unlocks your data is kept in the iOS Keychain on that device, and opening it needs Face ID, Touch ID or your passcode. Milely locks itself after two minutes without use.
Milely keeps an encrypted recovery backup, but not the recovery key you are asked to save. Keep it somewhere safe: resetting your password cannot recover encrypted history if you lose both your device and your recovery key.
Shared wallets use separate keys for the information you choose to share. Members with that key can read shared records. Removing someone stops future access once the key is rotated, but cannot erase what they already downloaded. Spends marked private stay private.
On supported iPhones, receipt text is recognised on the device with Apple's Vision framework. Receipt images, the recognised text and the extracted details are encrypted before they are stored, and they are not sent to cloud AI services. Where recognition is not available, you enter the details yourself.
Cap alerts never show which card or how much. They read like this:
MilelyUnlock Milely — one of your cards is close to its bonus cap.
MilelyUnlock Milely to review a change to your card's bonus cap.
To run your account, Milely still uses your email address, your name, shared-wallet membership, and the types and dates of records. Encryption protects the financial content of those records.
This page describes how the app is built today. It is not an independent audit or a certification.
Milely is coming to iPhone first. Leave your email to save your place on the beta list.
By joining you agree to the privacy policy.