Why Zighop exists
A household with two working parents and three kids runs something close to a small logistics operation. Karate Monday, swim Tuesday, ballet at four and soccer at four-thirty in two different places. Every one of those is on somebody’s calendar; none of them is in the same place, and the person who has to drive both is usually the last to find out.
A week arrives like this.
Zighop holds it like this.
Zighop holds the whole week in one shared view and says something when it doesn’t add up. Every feature in detail.
Who it’s for
Parents and caregivers — the people keeping a household running, and whoever they share the load with. Not the children whose week it describes.
What we store about your children
A first name, an age in years, and the goals you set. That is the whole list — no birthday, no last name, no photo, no school, no location. The app refuses the rest: a request carrying a date of birth or a school name is rejected at the boundary, in the code rather than in a policy.
Zighop is not a children’s app. No child login, no kid mode. And assistant features never see a child’s name — it is swapped for a placeholder before anything reaches an AI provider, and restored on our own servers afterwards.
The full privacy policy spells out where each guarantee is enforced.
Where it is
Early, and we’d rather say so plainly than imply a finished product. The week, shared access, conflict detection, carpools, importing a schedule, camps and classes, and the assistant are all built and working. Tracking how a child progresses across a season is where we’re headed next.