Why a budget app should not read your email

What the permission grants

Gmail read access is not scoped to bank emails. There is no permission that says “only the messages from my bank”. An app with read access can read the inbox — the filtering to transaction alerts happens after the fact, inside software you cannot inspect.

Google treats it accordingly. It is a restricted scope, requiring verification and an annual third-party security assessment, and the review is not a formality. That process exists because the access is broad.

Why we do ship it in India

We are not against the feature in principle, and pretending otherwise would be dishonest given that our Indian app has it.

In India nearly every bank and card sends a structured email alert for essentially every transaction. That makes inbox scanning genuinely transformative there: it turns a manual tracker into an automatic one, in a market where bank aggregation is comparatively limited. The trade — broad permission for a large gain — is a reasonable one to offer, with explicit consent.

Why the international app never will

The same trade does not hold in the US, the UK or Europe. Transaction alert emails are far less universal, so the gain is much smaller, while the permission is exactly as broad. And these markets have open banking, which is a regulated, consented, revocable, purpose-limited flow — strictly better designed for this job than reading an inbox.

So the international app requests no email access and no bank connection either. Manual, voice and receipt entry, and nothing that touches your inbox.

This is enforced on the server, not by hiding a button. A non-Indian account cannot reach the consent screen at all. Hiding an entry point in the client is not a control; a Gmail grant from an EU user would be a real regulatory problem that “the UI did not show it” does not answer.

What to ask if an app offers this

• Does it parse on your device, or upload email content to a server?
• What is retained after parsing — just the transaction, or the message?
• Can you revoke it, and does revoking delete what was already read?
• Has it passed Google's security assessment for restricted scopes?

Good answers exist. The point is to ask rather than to tap through.