money household
Back to money

Contact

We are a small team, so mail arrives at a person rather than a queue. There is no ticket number and no form that swallows what you wrote.

The address

One address, for all of it.

Asking for something

The board, where everyone can see what's been asked.

Ideas and bugs have somewhere to go that isn't an inbox: a list everybody signed in can read, vote on and reply to. If somebody has already asked for the thing you were about to write about, an upvote counts for more than a second email.

The board is behind sign-in — what is on it carries people's names, so it isn't a page for a stranger to read.

Worth writing about

Anything at all, really. These are the usual four.

A figure looks wrong

Which screen, which figure, and what you expected instead. Open the calculation behind it first — the working is usually the answer, and when it isn't, the working is the thing to send.

The import didn't read your file

Which bank or which spreadsheet, and what the preview said. A file with the figures replaced beats a description, and the app never needs the real one to fix a parser.

Something's missing

A thing your household does that this app can't keep up with yet. The requests board is the better door for these — somebody may have asked already, and a vote counts for more than a second email.

Your data

A copy of it, a correction, or all of it erased. You can do the last one yourself from Settings — ask and it gets done either way.

Never send us these

Two things this app has never asked for and never will.

A bank or broker login

No password, no card number, no net-banking PIN, no OTP, no read-only aggregator token. Nobody here will ever ask you for one, and a message that does is not from us. The app has no field that would take it.

Your real statement, to report a parser bug

Replace the figures and send that. What a parser gets wrong is the shape of a file — the header row, the date format, a merged cell — and none of that needs your actual money in it.