Giving feedback, and what public by default means

Short answer

Home education app feedback you send to Willowfolio is shared on the public board by default. You can tick a box to keep any individual piece private. Either way, a real person reads it.

Why is the default public?

The public board exists so that families can learn from each other. When you post a feature request publicly, other parents can see it, upvote it and add their own thoughts. That helps us understand what matters most to the community, and it helps you see that someone else has already asked for the thing you were about to request.

This is a deliberate design choice, not an oversight. Your feedback is not "leaked" onto the board. It is shared because shared requests move faster.

How to keep a single piece of feedback private

If you would rather keep something between you and the Willowfolio team, here is what to do.

1. Tap the feedback widget (the floating button you will see on every page) or go to the Feedback page.
2. Write your message. Choose whether it is a bug report, a feature request, or general feedback.
3. Before you send, look for the visibility option. The default is "Share with the community." To keep it private, tick "Keep this feedback private to my family."
4. Send. Done. Private feedback goes straight to us and does not appear on the public board.

You can mix and match. A feature request you want other families to rally behind can go public. A bug you found in your own data can stay private. There is no wrong choice.

Browsing the public board

Posts on the public board are anonymised: no family names, no personal details. Open the Feedback page to see what other home education families have asked for and what is already in the works. You can upvote a request you agree with (one tap), leave a comment, or just browse. You will see the text of the feedback and any status updates from the Willowfolio team, but nothing that identifies the person who wrote it.

What we do with your home education feedback

Every piece of feedback, public or private, is read by a real person. Bug reports get investigated. Feature requests get logged and, if they are on the public board, other families' upvotes help us decide what to build next. We will not always be able to reply individually, but we read everything and it shapes the roadmap.

If your feedback needs a reply (a question, a bug that is blocking you), we will get back to you at the email address on your account.

A quick example

Gemma, a single mum in Sheffield, has been using Willowfolio for a few months. She wishes the reading log had a way to mark a book as "abandoned halfway through" rather than just "finished." She taps the feedback widget, types a two-sentence feature request, leaves the visibility on "Share with the community," and sends it. Within a week, three other families have upvoted her idea on the public board.

A few days later, Gemma spots a formatting glitch in her Council Report preview. She taps the widget again, describes the bug, and this time ticks "Keep this feedback private to my family" because it is specific to her data and she would rather the team just sort it out quietly. Both submissions took under a minute.

If anything in Willowfolio feedback is not doing what you expect, write to us at [email protected] and a real person will sort it out.