Contact

Get in touch

Every route reaches the same person. Pick whichever is easiest.

From inside the app — best for bugs

The round button at the bottom right of every screen. It sends your note, the app version and which page you were on. No statements, no amounts, no card numbers.

That context is why this route is the most useful one: “it broke on the calendar” is the sentence that makes a bug findable, and the one people most reliably forget to write.

GitHub — best for anything public

Feature requests, questions others would benefit from seeing, and release notes.

Open an issue

Before you write about a statement

Never send us a statement file. It carries your name, your card number and every transaction on it. No support question needs one, and we do not want it.

What actually helps: which bank, which month, and what the app did instead of what you expected. If a statement would not import, the report button inside the app on that screen already carries everything needed.

What to expect

Replies come from one person in Sri Lanka, not a support desk, so allow a few days. Bug reports get read even when they do not get an individual reply — the same report arriving twice the same way is usually what gets something fixed in the next release.

Security

If you have found something with security consequences, please report it privately through GitHub rather than opening a public issue, and give us a chance to fix it before it is described publicly.

Press and everything else

A direct e-mail address is coming with the domain. Until it is live, GitHub reaches us for anything that is not a bug.