Whose data is it? Theirs, and that's the answer they want to hear
When a school hands you a class list, that data reaches you because the school shared it, not
because a parent gave it to you. The school stays the data controller for its pupils. You process
it to run the sessions, and we're a processor working for you, holding it to run the app and for
nothing else. Two things are worth settling with each school rather than assuming: that their
privacy notice covers sharing with outside providers and the system you keep records in, and
whether you're acting as their processor or as a controller in your own right, which decides who
answers a parent when they ask. Their data protection lead will know in a two-minute conversation,
and asking is the thing that marks you out as the professional in the room. If a parent ever asks
to see everything held on their child, you can export it; if a school asks you to erase a child,
that clears the sessions, observations and photos too. The detail is in our
privacy policy.
Every school its own group, and a term set up once
Year 3 at St Mary's on Tuesdays for six weeks, the nurture group at Fairfield every Friday,
reception at the village school after half term. Set the term up in one go, with the right
children in the right group and the right wood attached, and every session arrives already
knowing who's coming and which assessments it needs. When a school sends an updated list in
January, you update that group, not your whole world.
One plan, however many schools you work with
Schools aren't a price lever here and neither are woods. Working on your own, you're a one-person
organisation on Solo at £8 a month. Take on an assistant or a second leader and it's Team at £29 a
month flat, VAT included, whoever's on the team and however many schools and woods you're across.
A cap on woods would just mean an undeclared wood, so there isn't one, on any plan. See
full pricing.