Frequently asked questions

No. Today you type transactions in, or import statement files you download yourself (CSV, OFX, QFX, QIF, PDF), so Rudopo holds no online-banking login and uses no third-party aggregator. Bank sync is planned; when it arrives it will be optional, and entering transactions yourself stays available as its own, cheaper plan.

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. In the phone app you pay through the app store, which keeps your payment details: Rudopo never receives them.

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.

Yes — bank sync is planned, though we are not giving a date. When it arrives it will be optional. A plan where you enter transactions yourself will always exist, and it will cost less than one with bank sync, so you 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 schedules — 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 → API and read your budgets, accounts, transactions, categories and budget months over a small REST API. A token at Read changes nothing; one at Propose changes files every change in your review inbox for you to accept; one at Make changes writes directly, within limits you set, logged under its name. 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.

Yes. Rudopo runs a server for the Model Context Protocol, the standard assistants use to connect to other apps. Add Rudopo as a custom connector in an assistant that supports remote servers and sign in when it asks; it can then read your budget and answer questions about it. If you want it to make changes, you allow that on a Rudopo screen, never in the chat: either every change lands in your review inbox for you to accept, or it goes in directly under a limit you set.

Nothing, unless you set it to Make changes yourself — a connection starts at Read, and an assistant cannot raise its own level. Even then: never your account, your sign-in, your plan or your sharing; never a space, an account's closing or a reconciliation; never a reconciled transaction's amount, date or account. A delete still waits for your yes unless you tick a box for that connection. Every change is logged with the app's name, anything over the limits you set goes to your review inbox instead, and many of its changes can be undone for about 15 minutes.

It sees what your token or sign-in reaches: every space you belong to, or only the ones you choose when you create the token or approve the app. It reads one page at a time, and a full export is never offered to an assistant or a token — export stays a button in Settings, for you.

Nothing, because it never receives it. An assistant sends Rudopo one request at a time — a question about your budget, or a change it proposes — and Rudopo answers that request and keeps a record of the changes it asked for; an open proposal expires after 30 days. What you said to the assistant stays with the assistant, under its own policies.

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. A subscription bought in the phone app is cancelled with the app store you bought it from, and a refund is asked of that store first.

Any of 155 — every active ISO 4217 currency can be a space's budgeting currency. 49 of them carry official rates (daily reference rates, plus the official US-dollar pegs for the UAE dirham, Saudi riyal and Qatari riyal), and an account can be in a different currency from its space when both are among those.

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. On Android, there's the Rudopo app on Google Play. On any phone, Rudopo also runs in the browser with nothing to install: 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.

Yes — Rudopo for Android is on Google Play. It's the same Rudopo and the same account: create it in the app or at rudopo.app, with your email or with Google, and what you enter on one appears on the other. Subscribe on the site or in the app.

It's on the way, with no date yet — we'll announce it in the blog when it's on the App Store. Until then, Rudopo runs in Safari on iPhone and iPad, and Add to Home Screen gives it its own icon and a full-screen window.