DownloadBack up your encryption key
End-to-end encryption is set up automatically when you create your Commingle account. Most of your personal and financial data is already protected.
Open the menu
Tap the menu button in the top-right corner of the Home screen.
Go to encryption
Open End-to-end encryption, located just below your profile.
How most apps may see your data?
| ID | Date | Title | Amount | Category |
|---|---|---|---|---|
| 1 | 23 Aug | Rent | −$1850 | Household |
| 2 | 24 Aug | Salary | +$6,200 | Work |
| 3 | 24 Aug | Dinner | −$84.50 | Food |
The database contains readable financial data. Anyone who gains sufficient access to it may be able to understand your transactions – whether through authorised access, a mistake or a data breach.
What does Commingle see?
| ID | Nonce1 | Encrypted data |
|---|---|---|
| 1 | 7f2a91... | 4b8e0c91d7fa... |
| 2 | c1843d... | a07f39bc82e1... |
| 3 | 92e6ab... | f31d8a04c927... |
This is what leaves your device. Only the encryption key stored on your devices can turn this noise back into meaningful financial data. Commingle has no way of knowing whether you’re spending a few dollars or moving millions.
Nonce – a random value used during encryption, ensuring that even identical transactions, like your daily coffee, produce completely different encrypted data.
What is E2E-encrypted?
Personal transactions
Categories
Events
Wallets
Charts & summaries
Settings & preferences
What is not E2E-encrypted, and why?
Basic profile information
Your name, avatar, email address, gender, preferred currency and language are not end-to-end encrypted.
Why? This information lets Commingle identify your account, display your profile to friends and communicate with you when necessary.
Friends and balances
Your friends list and outstanding balances are not end-to-end encrypted.
Why? Commingle needs this information to calculate debts, keep balances up to date and send reminders when it’s time to settle up.
Shared transactions
Transactions involving other participants are not end-to-end encrypted.
Why? To provide collaboration features, Commingle needs limited access to certain transaction details. This allows us to:
- notify other participants about new or updated transactions
- calculate shared balances and debts
- automatically associate transactions with shared events
However, Commingle cannot see which personal category, wallet or event a shared transaction belongs to. Only internal identifiers are stored for those relationships.
We’re continuously evaluating whether more of this information can be protected with end-to-end encryption in future versions.
Does Commingle use military-grade encryption?
Yeah… military-grade. The term used by almost every website trying to make encryption sound fancy. Yes, Commingle uses what is often marketed as “military-grade encryption”. We prefer to call it industry-standard cryptography. The same well-established cryptographic building blocks are used everywhere – from banking systems to your local supermarket’s loyalty app. Where there is a meaningful choice, we opt for the stronger end of current recommendations – for example, AES-256 rather than AES-128. With today’s computers, properly implemented modern encryption is not realistically breakable by brute force. If you’d like to see just how absurdly large the numbers involved become, this video gives a fun illustration.
Quantum computers and “harvest now, decrypt later” are legitimate long-term concerns, although we don’t expect anyone to build a futuristic, enormously expensive machine specifically to uncover your grocery spending. We keep up with evolving cryptographic recommendations and will evolve Commingle’s encryption as new threats and standards emerge.
Where’s the catch?
There isn’t one. We really can’t see your personal transactions – and we don’t want to.
Since day one, Commingle has been built around a privacy-first principle. We’d rather be funded by our users through subscriptions than monetise your financial data by selling it to advertisers.
We also want to sleep peacefully at night. If we ever slip up and our database leaks, your personal transactions remain encrypted. That protects you, and it protects us from losing your trust – or facing some very unpleasant fines.
Caution: Technical jargon
How does end-to-end encryption work?
The following section describes Commingle’s cryptographic design for readers interested in the technical implementation.
Identity and key management
During registration, Commingle generates an X25519 public/private key pair directly on your device.
Your public key is uploaded to Commingle’s servers so other devices can encrypt data for you.
Your private key never leaves your device in plaintext. Once unlocked, it is stored securely using your operating system’s secure storage.
Setting up a new device
To protect your private key from loss and allow you to retrieve it on a new device, you can choose to securely store an encrypted backup on Commingle’s servers. You choose a password to protect this backup. Commingle derives an encryption key from your password using Argon2id and encrypts the backup with AES-256-GCM. Your password and unencrypted private key are never sent to Commingle’s servers.
Argon2id is intentionally memory-hard and computationally expensive, making brute-force attacks impractical. This operation happens only once when unlocking your key, not every time you access your data.
Commingle never knows your password and cannot recover your private key if the password is lost.
Encrypting your financial metadata
Categories, wallets, events, chart settings and other financial metadata are serialised as JSON directly on your device before being encrypted with AES-256-GCM.
The encryption key is deterministically derived from your unlocked private key using HKDF-SHA256.
Commingle stores only encrypted ciphertext. Names, icons, colours, balances, settings and other readable information never appear on the server in plaintext.
Encrypting your personal transactions
Personal transactions use envelope encryption.
For every transaction, Commingle generates a unique random 256-bit content key, encrypts the transaction using AES-256-GCM and then encrypts that content key with your X25519 public key.
Only your private key can recover the content key and decrypt the transaction.
Commingle stores only encrypted transaction data together with the minimum structural metadata required for synchronisation. Transaction titles, amounts, notes, categories and other protected fields remain unreadable.
Important to know
Analytics
We collect anonymous analytics to understand how people use Commingle and improve the app over time. Analytics never include your identity, transaction descriptions, receipt contents or individual transaction amounts. We may group users into broad, anonymous segments – for example, based on region or net worth range – to understand how different groups use Commingle’s features and help us make the app more useful for everyone.
AI Features
Commingle offers AI-powered features such as receipt scanning, voice transaction entry and automatic transaction categorisation to make managing your finances easier. When you choose to use one of these features, only the information required to process your request is securely sent to an AI provider. This may include a limited subset of your personal and financial data.
