Home › Google Drive sync
Most trackers keep your transactions on their servers and ask you to trust them. TheWalletly writes your ledger to a file in your Google Drive instead, and asks for the narrowest permission Google offers.
Your wallet is a JSON file stored in your Google Drive's application data folder — a private area of your own Drive that only this app can write to. It does not appear in My Drive, so it will not clutter your file list, and it counts against your own Drive storage rather than ours.
Rather than one large document, the wallet is split: one file holds your settings, categories, accounts and plans, and each month of transactions is stored separately. Editing one month only rewrites that month, which keeps saves fast once you have years of history.
Signing in requests exactly one Google scope: drive.appdata. That scope grants access to the app's own hidden folder and nothing else — it cannot list, read or modify any other file in your Drive. This is not a policy promise; it is the limit of what the permission allows.
Because your balances are never sent to a server of ours, there is no account database to breach and nothing for us to sell. The trade-off is honest: if you lose access to your Google account, you lose access to the wallet, which is why backups exist.
Because the file is in Drive, every signed-in device reads the same wallet. Log an expense on your phone and it is there on your laptop the next time it syncs. There is no separate account to create and no invite flow — your Google account is the login.
You can revoke the app's access from your Google account settings at any time, and delete the wallet file with it. Before you do, export your data — see owning your financial data for the formats available.