A family budget on iPhone — without sharing passwords

2026-07-19 · 5 min read

Most couples' “system” for money is a group chat, two banking apps and an argument at the end of the month. The apps that promise to fix this usually do it the crude way: one shared account, one shared password, both people logged into the same identity. It works — until it doesn't.

What a family budget actually needs

• One ledger, two phones. Both partners see the same accounts, transactions and budgets, live.
• Separate identities. Each person keeps their own Apple ID, their own Face ID, their own device security.
• Both can write. A budget only works if whoever bought the groceries logs the groceries.
• One payment. Nobody wants to buy the same app twice.

How Gilt does it

Two Apple technologies do the heavy lifting. iCloud sharing (CloudKit) carries the data: you invite your partner from the app, and the household ledger syncs directly between your personal iCloud accounts — no third-party server in between, ever. Apple Family Sharing carries the subscription: one Family plan purchase unlocks the app for up to five members of your Apple family group automatically, on their own devices.

The result feels almost boring, in the best way: your partner opens the app on their iPhone, everything is just there, and it stays in sync. No invite codes to a company's cloud, no shared login to rotate when a phone gets lost.

Multi-currency households

Plenty of families earn in one currency and spend in another — or split life between countries. A shared budget has to handle transfers between currencies without inventing money out of exchange-rate rounding. Gilt treats multi-currency as a first-class case: accounts keep their own currencies, transfers link both sides, and reports convert honestly.

And the privacy part

A household's finances are among the most sensitive data two people share. Everything above happens inside Apple's ecosystem — your devices, your iCloud accounts. Gilt has no servers and cannot see a single shared transaction. That's by architecture, not by policy.