Contact
A person answers. Usually the same day.
No ticket portal, no chatbot, no “we value your request.” Email lands in an inbox a human reads.
Support
Anything about using the product: statement formats, categories, balancing, packets, payments, refunds.
[email protected]Security
Vulnerability reports and anything about the privacy architecture. Please describe the behaviour — never attach client data.
[email protected]The founder
Fahad Joiya, directly. Product decisions, a figure you think is wrong, or anything you'd rather say to a name than to a queue.
[email protected]Response-time promise
One business day, and usually much faster. If you are inside a week of a filing deadline, say so in the first line and it jumps the queue.
Reporting a statement format we don't parse
This is the single most useful email we get. Tell us:
- The institution — "Wells Fargo", "Fidelity", "City National".
- The account type — checking, savings, brokerage, trust.
- Whether it's an e-statement PDF downloaded from their site, or a printed page you scanned, or a "print to PDF" of a web page.
That is nearly always enough to reproduce the layout from a sample of our own, and the format usually ships within a week. Do not send us a client statement. If we truly cannot reproduce it, we'll ask — and we'll send you a redaction guide first, and delete the attachment when the ticket closes.
Status
Sign-in and payments depend on our servers; preparing an accounting does not. If something looks down, the status page is linked from the sign-in screen, and the honest headline is that you can keep working on your accounting either way — it runs on your machine.
Postal address
Available on request for legal notices. Email [email protected].