Privacy policy
Last updated September 30, 2026
Yearfolio stores the numbers you enter and the account they belong to. Nothing else. There is no advertising, no analytics, and no other company gets to see your budget.
Contact
If you have a question about this policy, or you want to use any of the rights below, write to support@yearfolio.com. We answer within 30 days, and usually much sooner.
What Yearfolio stores
Four kinds of data. Either you typed it in, or using the app produced it:
- Your account: email address, display name, the currency and language you picked, and either a password (kept only as a bcrypt hash, never in a form anyone can read) or the id of the Google account you sign in with.
- Your budget: the income, expenses, wallets and amounts you enter, the months you have completed, the years you plan, and any scenarios you save.
- Activity we need to run the service: when the account was created, when you last signed in, and when you complete, correct or reopen a month. These are times and event names, not the amounts.
- Email delivery: for each message sent to you, its type, whether it arrived, and any error the mail provider gave back. That is how a broken address gets noticed and fixed.
Why, and on what legal basis
Under the GDPR, every use of your data needs a legal basis. Yearfolio has two, and no third:
- To provide the service you asked for. This is performance of a contract, Art. 6(1)(b). Without your email address and the rows in your table there is nothing to run.
- To keep accounts safe. This is legitimate interest, Art. 6(1)(f). It covers the limit on sign-in attempts and the record of staff actions described below.
Where it is stored
Yearfolio runs on Amazon Web Services, in the United States, and your data is stored there.
If you are in the EU or the UK, that counts as an international transfer, so here is what it rests on. The European Commission’s Standard Contractual Clauses are part of the AWS customer agreement and of Resend’s data processing agreement, and the technical measures under Security below apply as well. Database backups sit on the same servers, under the same rules as the data itself.
Cookies
Two cookies. Both are strictly necessary, and neither is used to track you.
A session cookie keeps you signed in. It runs out after about half an hour without activity, and when you sign out.
A CSRF token cookie lets the server tell your own requests apart from ones faked by another site.
Yearfolio sets no analytics, advertising or third-party cookies. That is why there is no consent banner to click away.
Email we send
Only messages about your account: verifying your address, resetting your password, confirming that a password changed, confirming a deletion you asked for. There is no newsletter and no marketing, so there is nothing to unsubscribe from. These messages are simply how the account is kept safe.
Mail goes out through Resend, which handles the recipient address for us.
Who else sees it
Your budget is never sold, rented, shared with advertisers, or used to train anything.
There is one thing we could not refuse: if the law required us to hand something to an authority, we would have to.
Apart from that, three processors (companies that handle data for us) help run the service, and nobody else:
- Amazon Web Services: the servers and the database.
- Resend: delivering the emails above.
- Google: only if you choose Continue with Google, and only to confirm the account is yours. Yearfolio gets your email address, your name and a Google account id. Google gets no budget data.
How long it is kept, and how to erase it
Your account and everything in it stays until you decide otherwise. You can delete it yourself under Settings → Security → Delete account. It asks you to confirm by email. Once you do, the account, the budget rows, the scenarios and the activity records are gone for good. There is no bin to recover it from and no undo, so export anything you want to keep first.
Two small records outlive the account on purpose, and they protect you as much as us. When a member of staff looks at financial detail, disables an account, or deletes one, that action goes into a staff audit log that can only be added to. It holds the action, the time, and the email address it concerned. That is what lets us show what was done to an account after the account itself is gone. Email delivery records are kept the same way, so a message that never arrived can still be explained later. Neither record holds any of your amounts.
Your rights
If you are in the EU or the UK, the GDPR gives you the rights below. You are welcome to use any of them, and you do not need to give a reason. Most are already a button inside the app. For the rest, write to support@yearfolio.com.
- Access: ask us what is held about you, at any time.
- Portability: export a year as CSV under Settings → Export, whenever you like, without asking us.
- Correction: change your name, currency and language under Settings → Profile, and your amounts in the app itself.
- Erasure: delete the account under Settings → Security, as described above.
- Objection and restriction: ask us to stop, or pause, anything that rests on the legitimate interest above.
- Complaint: if something is wrong, tell us first and we will do our best to put it right. If we do not, your national data protection authority is there to take it up.
How it is protected
Traffic is HTTPS only. Passwords are stored as bcrypt hashes, never in a form anyone can read. Changing your password signs out every other session. Sign-in attempts are limited by IP address, and that address is used at the moment of the request, not stored against your account.
No service can honestly promise it will never be broken into. If that happened and it put you at risk, you would hear it from us quickly, and we would tell the supervisory authority too, as the GDPR requires.
Changes to this policy
The date at the top says when the wording last changed. If a change makes a real difference to how your data is handled, we will tell you by email before it takes effect. We will not quietly re-date this page.