Questions to Ask About Privacy Before Picking a Receipt App

A year of receipts is a map of your life: where you eat, when you travel, which pharmacy you use, how your business actually makes money. Before you hand that to an app, spend ten minutes asking the questions below. Most of them can be answered from the privacy policy and the App Store listing without ever creating an account.

1. What happens to the image after it is read?

Every receipt scanner has to process the photo somewhere, either on your device or on a server. Neither is automatically wrong, but you should be able to find out which one it is, and what happens next. The specific thing to look for is whether the original image is stored indefinitely, stored only until you delete the expense, or discarded once the fields are extracted. If a policy talks at length about "improving our services" but never says how long images are retained, that is the gap worth emailing support about.

2. Is your data used to train models or build profiles?

Receipt data is unusually valuable because it is itemized. Card statements say "Grocery Store, $84.10." A receipt says exactly what was in the basket. Read the policy for words like "aggregated," "de-identified," "analytics partners," and "affiliates," then check whether there is an opt out. A clear answer reads like a sentence, not a paragraph. If you cannot tell after two readings whether your line items feed anything other than your own ledger, treat that as a no from the vendor.

3. Check the App Store privacy label before you download

On iOS, every listing carries a privacy label split into three buckets: data used to track you, data linked to you, and data not linked to you. It takes fifteen seconds to read and it is filled in by the developer under Apple's rules, so it is harder to hedge than marketing copy. The single most useful signal is the "Data Used to Track You" section. For a tool you are paying for, or that you expect to pay for, that section being empty is the baseline, not a bonus.

4. Does it demand your bank login?

Some expense tools require you to connect a bank or card account through an aggregator before they are useful. That is a real feature for some workflows, and it is also a much larger surface than a camera and a photo library. If your actual need is "turn paper and PDFs into a clean expense record," a receipt scanner that never touches your bank credentials solves it with far less exposure. Ask whether bank connection is optional or mandatory, and if it is optional, confirm the app is genuinely useful without it.

5. Can you get everything out, and can you delete it?

Two capabilities separate a tool from a trap. The first is export: you should be able to pull your expenses out as a plain file, such as CSV, without contacting support or upgrading. The second is deletion: there should be a way to delete your account and its data from inside the app, which Apple has required of apps that support account creation since 2022. If either one is missing, your data is a hostage, and switching later will cost you a weekend of retyping.

6. What does sign-in actually reveal?

Sign in with Apple and Google are both fine choices, and Apple's version can hide your real email behind a relay address, which limits what a vendor learns about you from day one. Whichever you use, check whether the app asks for permissions unrelated to its job. A receipt scanner needs the camera and, if you import screenshots or emailed PDFs, access to the files you choose. It does not need your contacts or your location history.

How Expense Rabbit answers these

Expense Rabbit is a receipt scanner, not a bank aggregator. You photograph a receipt, it reads the merchant, date, total, tax, and line items, then auto-categorizes the expense with a confidence score so you can see when it is unsure. It works on iPhone and on the web with one synced account, you sign in with Apple or Google, and your expenses export to a books-ready CSV whenever you want them. Full details are in our privacy policy, and if something there is unclear, that is a bug worth telling us about.

← More guides