Security

An app permissions audit for money apps

Apps ask for access to contacts, location and more. A ten-minute audit shows what your money apps can really see.

Editorial illustration for An app permissions audit for money apps

Permissions are promises you gave

When you installed each app, you probably tapped allow on a few screens without reading. Over months and years, the apps on your phone accumulate access to your contacts, camera, location, microphone, files and notifications. Some of that access is necessary. Some is just habit.

An audit takes ten minutes and gives you a clear picture of who can see what.

How to run it

On most phones, the settings page has a section for privacy or permissions, grouped by type of access. Take each sensitive type in turn: contacts, camera, location, microphone, photos, files, and messages. Look at which apps have access.

For each money-related app, ask: does this feature need this access, and do I use that feature?

Typical reasonable permissions

  • Camera, for scanning receipts or QR codes.
  • Notifications, for alerts about payments and bills.
  • Biometrics, for unlocking the app.
  • Contacts, for choosing a person to pay, though many apps work without it if you enter details by hand.

Even reasonable permissions can be limited, for example by allowing access only while using the app or choosing a specific set of photos instead of the whole gallery.

Permissions to question

A calculator, a wallpaper app or a coupon app asking for contacts and messages is a puzzle. A money app that wants access to your messages should explain why, and you should be comfortable with the explanation. Reading messages can allow an app to see one-time codes, which is both useful for automation and risky if misused.

Where an app works fine without the permission, remove it.

Notifications as a permission

Notifications can reveal sensitive information on the lock screen. Decide whether you want balances and merchant names to appear when the phone is locked. Many phones offer an option to hide content until unlock. For payments, keep the alert but hide the detail.

Unused apps

Apps you have not opened for months still hold permissions. Uninstall them. If an app holds a balance, move it out first. Deleting the app does not always close the account, so look for a way to close or deactivate it if you no longer need it.

Recording the outcome

After the audit, write down what you changed in a short note. In your accounts overview, mark which apps are linked to which accounts, so the next audit is quicker. If you use an expense tracker, check which sources it reads from and whether you are comfortable with that. Entering transactions yourself or importing statements gives you control over what the tool sees.

Repeat twice a year

Updates can reset or add permissions. Put the audit on the calendar for twice a year, ideally alongside the review of devices and sessions signed in to your main accounts. If the audit finds nothing, it takes five minutes. If it finds something, you are glad you looked.

Reading a privacy summary

Many stores now show a short summary of what data an app collects and whether it is shared. Take a minute to read it for your money apps. Does it match what you expected? Are there categories that surprise you, such as precise location or contacts? If the summary is missing or vague, treat that as a mark against the app. You are not expected to be an expert, only to notice mismatches and ask whether the benefit justifies the exposure.

After a lost phone or a new one

A new phone is the best moment to rebuild permissions from nothing. Install only the apps you need, say no to each request, and grant access later if a feature truly stops working. Compared with restoring everything from a backup, which carries old permissions across, this gives you a leaner, safer setup. It takes an evening, and the phone feels faster as a bonus.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports