Security

What not to type into the notes field of an expense tracker

A checklist of what never to type into an expense tracker's notes field, from card numbers and OTPs to ID numbers, with safer labels to use instead.

Editorial illustration for What not to type into the notes field of an expense tracker

Never type anything into a notes field that would let someone act as you: card numbers, CVV, PIN, OTP, passwords, or full ID numbers. A note should explain a purchase, not unlock an account. If you need to refer to a card or a document, use a label or the last four digits and keep the real thing elsewhere.

Why does the notes field need extra care?

Free text is the one place in a tracker where you can type anything, which is exactly why it is risky. A merchant name or an amount is structured data. A note is a blank space, and blank spaces collect habits: a quick reminder of which card was used, a password for the site you just paid, a number you did not want to forget.

Notes also travel. They can appear in exports, screenshots you share with a CA, backups and anything else the tracker can produce. So write each note as if a stranger might read it later.

What should never go in free text?

Do not typeWhy it is riskyWrite this instead
Full card numberEnough for someone to attempt purchases with other detailsCard name and last four digits, such as Travel card 1234
CVV or expiry dateCompletes a card's details for online paymentNothing at all; memorise or use the card itself
Card or UPI PINAuthorises paymentsNothing; no note ever needs it
OTP from a messageAuthorises a single transactionNothing; delete the message instead
Passwords or login hintsOpens accountsName the service only, such as Insurer portal
Full PAN, Aadhaar or passport numberIdentity theft and form fraudDocument type and last two or four digits if truly needed
Account number with IFSCUsed in social-engineering callsBank nickname plus last four digits

What can you write instead?

Good notes are short and answer a future question: why did I pay this, for whom, and where is the proof?

  • Purpose: Mother's cataract follow-up, Plumber for bathroom leak, Wedding gift for cousin.
  • Person or role: Tutor, Landlord, Driver; a short role tag instead of a full name when the payment is sensitive.
  • Where the proof is: Receipt saved, Warranty card in blue folder, Invoice in email.
  • Reimbursement status: To claim from employer, Claimed, Not claimable.
  • Account hint: Card ending 1234.

If you want the receipt itself, attach it to the transaction rather than copying details out of it. SpendixAI keeps receipts with their transactions, so the amount and the proof sit together and your note can stay short.

What if you already typed something sensitive?

  1. Open the entry and delete the sensitive part of the note now.
  2. If it was a password or PIN, change it, because deleting the note does not undo the exposure.
  3. If you exported or sent the data to someone, check whether the file contains the note and ask the receiver to delete it.
  4. If it was a card number, tell the issuer and ask whether to replace the card.
  5. Search your tracker for similar patterns, such as long runs of digits, and clean those up too.

Which notes habits make you safer?

Decide a few labels once and reuse them. A set such as Card 1234, Receipt saved and To claim is easy to type, easy to search and harmless if seen. Review your most recent notes once a month; five minutes is enough to spot a mistake. Before you ever share an export with an accountant, scan the notes column and trim what they do not need.

Finally, if you try an AI feature for categorisation, read how it works before assuming what is covered. SpendixAI describes the data its AI step uses, and you can read that explanation, but it is a good habit to keep free text clean in any tool.

SPENDIXAI JOURNAL

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

Explore your reports