How the community directory works
It's a list of links. Other people write these add-ons, and we put them somewhere you can find them. That's the whole thing. Here's what it means in practice.
What we do
- • List the add-on and link you to whoever made it.
- • Pull facts out of their public code and show you what we found.
- • Turn down add-ons built for old versions of Wealthfolio, or with no license.
- • Check what moved each week, and take a listing down if it stops holding up.
What we don't
- • Write it, or build it.
- • Host the download, or send you updates.
- • Read the code.
- • Fix it when it breaks, or answer for what it does.
Where the facts on a listing come from
Almost none of it was typed in for us. The license, the version, which permissions it asks for, when they last worked on it — we read all of that straight out of their public code, and note which commit we read it from.
Two things are still the author's own words: the short description, and the reason given beside each permission. Those live in their manifest, so we can show you that an add-on asks for your transaction history, and we can show you what they say it's for. Only the first half is something we checked.
Reading beats asking where reading works — nobody has to remember to update a form, and nothing drifts quietly. It goes stale anyway, so a job re-reads every listed repo once a week and flags anything that moved. Acting on that is a person's job, not the script's, so a listing that stops holding up comes down once someone has looked at it rather than the moment it changes.
There's one thing we can't work out from code: what it costs. So whoever made it tells us, and the page says it's their word rather than ours.
The one thing we can actually promise
From Wealthfolio 3.6, add-ons run in a sandbox. If an add-on didn't ask for internet access, it can't get on the internet. Not "shouldn't" — can't. Wealthfolio blocks it. So when a listing says stays on your device, that's us telling you what the app does, not the author telling you what they'd never do.
It only works forwards. Add-ons built before 3.6 could quietly go online without asking, so there's no way to tell from the outside where your data ends up. That's why we don't list them, even good ones — we'd have nothing true to tell you.
When an add-on does ask for the internet, we show you which sites it named. You still say yes or no yourself when you install it. That box in the app is what gives it access, not this website.
If something goes wrong
Bugs, missing features, money questions, privacy questions — all of that goes to whoever made the add-on. They wrote it, they ship it, they're the only ones who can fix it. We can't help with a community add-on, and saying otherwise would just waste your afternoon.
Do tell us if a listing is wrong or out of date, or if an add-on is doing something it shouldn't. We'll take it down.
If you want the legal wording
Section 6 of the Terms of Use covers add-ons, and the directory policies list what a listing has to meet. Nothing on this page changes either one.