A student's data is theirs
StudyBot reads a student's school accounts to help that student and for nothing else. It is never sold and never shared. Data stays in the EU.
About
School information should live in one place.
StudyBot began with a frustration a lot of schools will recognise: the week assembled from five portals, a calendar that disagreed with itself, and no single page anyone could trust to be current. So we built that page.
Built at a kitchen table in Barcelona.
StudyBot started as a project between a high-school student living the five-portal problem and a parent who builds software for a living. One of them knew exactly what it feels like when a deadline hides in portal number four. The other knew how to make a program read portal number four.
The first users were a class of actual classmates, which means every confusing screen got taken apart in a group chat until it stopped being confusing. That is still how it gets built, and it is why the product is calm: a teenager will not open something that nags them.
It is now a funded product team, working with schools directly. The student-facing part is the mechanism. The reason a school buys it is that the office stops being the integration layer between systems that were never designed to talk to each other.
What we promise
The rules StudyBot lives by.
Reduce anxiety, never add to it
No streaks, no confetti, no guilt. Every competitor that gamified this regrets it. Calm is the product, not the styling.
Find, explain, flag. Never act
StudyBot answers questions, makes numbers readable, and raises what needs attention. Anything leaving the school waits for a person to approve it.
Never answer from a guess
Answers come from a school's own published pages and name the page they came from. A question the pages do not cover goes to the office, not to a model's imagination.
See it on your own school week.
Schools get a walkthrough built on their own timetable. Families can just start tonight.