Frequently asked questions

No. Rudopo has no bank connections: you type transactions in, or import statement files you download yourself (CSV, OFX, QFX, QIF, PDF). Because nothing connects, there is nothing to hold — no online-banking login, no third-party aggregator reading your accounts.

No. Sign-in is handled by Clerk, an established identity provider: your credentials are collected and held there, and Rudopo does not receive or store a password. Rudopo's own records hold an account id and your email address, not your password.

No. Payments are handled by Dodo Payments, the merchant of record: you enter your card on its checkout page, and card details are not sent to or stored by Rudopo. What Rudopo receives is a customer identifier, a subscription identifier, your plan, its status, the end of the current period and any trial end — enough to know your subscription is active.

The infrastructure providers named in the Privacy Policy, each for one job: sign-in, hosting, the database, fault reports, email, payments, and the AI tooling used to run Rudopo. Anyone you invite into a shared space sees that space. Beyond that, data is disclosed only in the cases the Privacy Policy lists, such as when valid legal process requires it. We do not sell your data, run ads, build profiles from it, or use it to train AI models.

Not from the operator console, which is built to show metadata only — it cannot list your transactions. The people who run Rudopo do have technical access to the database: it is how backups are taken, database changes are made and faults are fixed. When you report a problem, we read what you sent, including any screenshot you attached.

Data travels over TLS and is encrypted at rest at the database layer. Every request is authorised against your account's membership, and our test suite includes deliberate cross-account access attempts. Secrets are scoped per environment, database changes are rehearsed against a separate staging environment before they reach production, backups are taken and restore-tested, and production is checked every day. The Privacy Policy lists the measures in full.

In the United States, with the hosting and database providers named in the Privacy Policy. If you use Rudopo from elsewhere, your data is transferred to and processed there. Fault reports are the one exception: they are kept in the monitoring provider's European region.

We tell you. If an incident results in unauthorised access to personal data, we notify affected users without undue delay — by email to your account address and, where appropriate, in the app — and notify the authorities that applicable law requires, within the periods it sets. We commit to telling you even where no statute would require it, if it is something you would want to know. Suspected vulnerabilities go to security@rudopo.app.

We honestly haven't decided. What we promise: if bank sync ever arrives, it will be optional and priced as its own plan — a manual, connection-free plan will always exist with its own pricing, so you'll never pay for a connection you don't use.

Rudopo is built by a small independent company registered in the USA. We have no investors, so what gets built is decided by the people who use it, not by anyone looking for a return. Questions reach us at hello@rudopo.app.

Yes, and leaving is a button, not a request. Export your transactions as CSV that opens in Excel or Sheets and imports straight back, pull any individual table the same way, or download a complete JSON backup of every space and every table. Deleting your account removes the data for good. If a subscription ends and you don't resubscribe, we email you and delete the account no sooner than 12 months after access ends — everything stays exportable until then. An account that never starts a subscription is deleted the same way, with an email first, no sooner than 60 days after sign-up (counted from launch for an account created before paid plans began).

Yes — import bank statements or exports from other budgeting apps as CSV, OFX, QFX, QIF, or PDF. And you're never locked in: export everything, anytime.

Yes. Export your budget from YNAB and import the ZIP into a new Rudopo space. Accounts, categories, monthly assigned amounts and your transaction history come across; targets, scheduled transactions and flags do not.

Yes. A clean slate makes a new space that keeps your accounts at today's balances, your categories and targets, and your payees, labels, rules, reminders and recurring templates — and starts the envelopes empty. Your transactions and past assignments are not deleted or rewritten: the old budget is archived whole, under a dated name, and stays readable. You have fifteen minutes to undo it, and deleting the new space brings the old one back live at any time.

Yes. Privacy mode masks every amount in the app with one click, and one click brings them back — for a train, a shared screen, or someone reading over your shoulder.

Yes. Create a personal access token in Settings and read your budgets, accounts, transactions, categories and budget months over a small REST API. Tokens reach only what your account can, can be narrowed to specific budgets, and are revocable at any time. There is no client library to install — the API is described in OpenAPI so you can generate one in whichever language you use. See the developer page for a working example.

A 30-day free trial, then one plan at $4/month or $35/year, plus tax where it applies, with everything included — no feature gates, cancel anytime. A card is taken up front; cancel before the trial ends and you are never charged. Each customer has one trial period of 30 days, counted from the day their first trial starts. A later subscription by the same customer receives the unexpired part of that period, if any, and none once it has ended.

Yes, any time, in the app: Settings → Account, under Plan. Cancel during the free trial and you are not charged; cancel part-way through a paid period and you keep access to the end of it, and nothing renews after that. Refunds follow the Refund Policy.

Rudopo carries official rates for 33 currencies: the ECB's daily reference rates, and the official US-dollar pegs for the UAE dirham, Saudi riyal and Qatari riyal. Each space budgets in one currency; an account can hold a different one when both of them are on that list. A space can be budgeted in a currency outside it, but then holds only that currency.

Everywhere you can legally use a US service. Accounts can be created from any country, and euros, pounds, francs and every other currency Rudopo carries an official rate for are fully supported.

Yes. Rudopo is fully responsive: every screen is laid out for a phone, with a bottom bar for the places you go most and one-thumb entry for the purchase you just made. It runs in your phone's browser with nothing to install. Native iOS and Android apps are on the roadmap, and we'll announce them in the blog when they land.

Rupee, Dollar, Pound — the first two letters of each. They say where the idea started, not what it supports: the three in the name get no special treatment. A budget kept in rand, ringgit, or real works the same way as one kept in dollars, with rate history for each currency starting from the date its official rates begin.