This describes what the software actually does, not what it intends to. Where a claim below is enforced by how the site is built rather than by policy, it says so.
The planner works completely without an account, and that is the intended way to try it.
In that mode your plans, spending entries and wish list are held in your own browser's
local storage under keys beginning cashflow. — no row anywhere has your name
on it, and clearing your browser data deletes the lot permanently, including from us,
because we never had it.
One thing does leave your browser: when the forecast is calculated, the plan's figures are sent to the server, calculated, and the answer returned. Nothing from that request is written down — the calculation routes hold no data and have no database access for your plan. This is a real reduction on doing the arithmetic in your browser, and it is stated here rather than glossed over.
Signing in is what makes a plan portable between devices and lets you export it. From then on the following is stored against your account:
That is the whole list. It exists because those things are the app; none of it is collected for any other purpose.
Three, all strictly functional. None is used for tracking or advertising, and there is no third-party cookie.
cashflow_session — set when you sign in. Holds your account number and an expiry, signed so it cannot be forged, and readable only by the server, never by JavaScript. Thirty days.cashflow_anon — set for everyone, signed in or not. Holds a random identifier and nothing else. Its only job is to rate-limit the calculation endpoint fairly, so one visitor cannot exhaust it for everybody. Twenty-four hours.cashflow_oauth_state — set for ten minutes while you sign in, to ensure the sign-in that completes is the one you started.No analytics, no tag manager, no advertising pixel, no session recording, no fingerprinting. This is enforced, not merely promised: the page is served with a Content-Security-Policy permitting scripts only from this site, so a third-party tracker cannot execute here even if one were added by mistake.
Your figures are never sold, rented, shared with advertisers, or used to train machine-learning models.
The web server records requests so the site can be kept working — the time, the page, the response, and how long it took. Addresses are shortened before they are written, so a record identifies a network rather than a device or a person, and cookies are never written to the log. These records are kept for ninety days and then deleted. No address is ever stored in the database.
Administration of this site can see counts and account details — how many plans exist, when an account was created, which tier it is on. It cannot open your plan, your spending, your recorded days, or even a plan's name. That is a limit built into the software rather than a rule somebody follows, and it is why a message saying "my numbers look wrong" has to be answered by asking rather than by looking.
Every administrative action that changes anything is recorded in an audit log that cannot be edited or deleted.
The contact form stores what you type — your message, and the name and email address if you give them — so a person can read and reply. It also records which browser sent it, to help diagnose bugs. Your IP address is not stored with it. Nothing in the form is required except the message itself.
This is not intended for use by children, and no account should be created for one.
If what the software stores changes, this page changes with it — it is a description of the code, so the two are meant to move together. Material changes will be noted here with a date.
Questions about any of this, a request for a copy of your data, or a request to delete it: use the contact page. It reaches a person.