Protected by design

Financial details.
Encrypted before upload.

Milely uses authenticated encryption for the financial content you save—while staying clear about what it does not hide.

AES256GCM · AUTHENTICATED ENCRYPTION

Product security feature.
Not a certification.

Three layers

Private by default.
Clear by design.

01

Encrypted on your device

Financial details are protected before they leave your phone.

What this covers

New transactions, saved card details, reward settings, receipt files and Auto Log purchase details are encrypted before storage.

02

Keys stay with you

Your device unlocks the data—not your account password alone.

How recovery works

On iPhone and Android, the unlocking key is kept in device-protected storage. Milely stores an encrypted recovery backup, but not the recovery key you are asked to save.

03

Sharing is deliberate

Shared wallets use separate keys for information you choose to share.

What sharing means

Members with a shared-wallet key can decrypt shared records. Removing someone stops future access after key rotation, but cannot erase information they already downloaded.

The honest bit

Encryption protects content.
Not every signal.

Your email, display name, wallet membership, record type and timestamps are still processed so Milely can run your account.

Other limits to know

Browser keys belong to the browser profile. Shared-wallet members can read records shared with them. Encryption cannot undo copies someone already downloaded.

See every data category in the Privacy Policy
AES-256-GCMAuthenticated encryption
2 minutesIdle time before app lock
ZeroBank passwords, full card numbers or CVVs requested

This describes Milely’s current application design, not an independent audit or certification. Production configuration and physical-device checks must also be completed before launch.

Make your next
card choice count.

Be first to hear when Milely launches.

Join the waitlist.

Launch updates only. Read our privacy policy.