The word accountability sounds automatically positive.
It suggests commitment, encouragement, and having someone notice when you are trying. For students who struggle to remain consistent while studying alone, that kind of presence can be valuable.
But accountability has an uncomfortable neighbour:
Surveillance.
The same system that makes effort visible can also make someone feel watched. A feature intended to encourage a student can become a source of pressure. Information collected to show progress can be used to judge them without understanding the circumstances behind it.
As EBO evolved, I realised that I could not build around accountability without deciding where that boundary belonged.
Visibility is not automatically support
When people know that someone else is present, they may find it easier to begin or continue difficult work.
That was part of what interested me about accountability.
Studying is often private. A student can quietly postpone a task, leave a routine, or stop showing up without anyone noticing. By the time the consequences become visible, a large amount of time may already have passed.
Making effort visible might help.
But more visibility is not always better.
A student may want a trusted friend to know that they completed a study session. That does not mean they want everyone to see their schedule, history, mistakes, or periods of inactivity.
They may want encouragement after a difficult week. They may not want a system converting that week into a permanent judgment about their discipline.
The question cannot simply be:
What information can the system collect?
It also needs to be:
What information should anyone be allowed to see—and why?
Numbers can appear more truthful than they are
Tracking creates numbers, and numbers look objective.
If someone records three hours of studying, the system can display three hours. But it cannot automatically prove that those hours involved meaningful learning.
Time spent is not the same as understanding.
A streak is not the same as progress.
Opening a focus session is not the same as completing valuable work.
This matters because productivity systems can accidentally turn incomplete measurements into confident conclusions.
A student with lower recorded activity may have been studying outside the system. They may have been ill, overwhelmed, or dealing with circumstances that a dashboard cannot understand.
Another student may record impressive numbers without learning effectively.
If EBO ever treats visible activity as complete evidence of effort or ability, it risks becoming dishonest.
Data can inform a conversation.
It should not pretend to know the whole person.
The danger of public performance
Social accountability can also change why someone studies.
If progress becomes too public, students may begin performing productivity instead of pursuing learning. The goal quietly shifts from understanding the subject to appearing consistent inside the system.
That creates the wrong incentives.
A student might chase visible time, points, or streaks because those are rewarded, even when a different form of study would be more useful. Missing a day might feel less like an ordinary interruption and more like a public failure.
I do not want EBO to turn studying into a performance.
Encouragement should not require broadcasting someone’s academic life.
Visibility should be limited, understandable, and connected to a clear purpose. It should exist to support the student—not to create an audience around them.
Privacy cannot be added at the end
It is easy to treat privacy as a legal page, a collection of settings, or a problem to address after the main features work.
That approach is especially dangerous when students may be minors.
Privacy changes the product itself.
It influences what information should be collected, how long it should remain, who can access it, what defaults should exist, and what control the student retains.
The principles I want EBO to follow are straightforward:
-
Do not sell student data.
-
Do not display email addresses publicly.
-
Collect as little personal information as the product genuinely needs.
-
Keep accounts private by default.
-
Make visibility controls clear rather than hiding them.
-
Do not expose study activity publicly without explicit permission.
-
Allow people to export and delete their information.
-
Never make surveillance-style claims about what the system can prove.
Writing these principles is much easier than implementing them properly.
Still, defining them early matters. They become limits on what the product is allowed to become.
Building for minors changes the responsibility
A product involving young students cannot assume that every user fully understands data collection, visibility, or long-term consequences.
Consent needs to be meaningful, not merely a box that everyone clicks.
Moderation and reporting cannot be improvised after a problem occurs. Account recovery, data retention, and advertising choices need conservative defaults. Research involving students must avoid unnecessary sensitive information and protect identifiable responses.
I am also a student, but that does not remove this responsibility.
Personal familiarity with a problem is not the same as expertise in safety, privacy, or child protection. There are areas where I will need guidance from people who understand them better than I do.
Being young may help me recognise how certain systems feel from a student’s perspective.
It does not give me permission to be careless.
Accountability should preserve dignity
A system can encourage honesty without humiliating people.
Earlier versions of my thinking included blunt categories for how time was spent, including the idea of tracking “wasted” hours.
That language now makes me uncomfortable.
A system cannot always understand why time was not spent according to plan. Labelling it as wasted may turn a complicated day into a moral judgment.
Students already experience enough pressure around performance. A product should not intensify that pressure merely to make its statistics appear clear.
Accountability should help someone notice patterns and return to their intentions.
It should not punish them for being human.
That means avoiding language designed to shame, avoiding claims that recorded time proves learning, and remembering that progress is rarely perfectly linear.
The buyer and the user may want different things
EBO also introduced a difficult product-design problem: the person using a system may not always be the person interested in its broader results.
Those perspectives can conflict.
Someone looking at overall activity may want more information. The student producing that information may want privacy and control.
It would be easy to resolve that conflict by giving the more powerful party greater visibility.
It would also be dangerous.
A student should not lose dignity merely because someone else finds additional data useful. Any useful overview must have boundaries, and those boundaries should be shaped before commercial pressure appears—not after.
I cannot claim to have solved every part of this tension.
But I know which side should not be treated as expendable.
The product should help students build consistency without giving anyone a window into their entire lives.
More power requires more restraint
EBO began as a personal tracker, so these questions were mostly invisible at first.
When I was the only user, I already knew what my information meant. I controlled the tool, interpreted the results, and decided what mattered.
Building for other people changes everything.
Information moves between contexts. Features affect relationships. A motivational mechanic can become pressure. A useful statistic can become an unfair label.
The more a system can observe, calculate, or share, the more carefully it must limit itself.
That principle now shapes how I think about EBO:
Accountability should make it easier for a student to return—not easier for someone else to control them.
I am still learning where every boundary should be.
But I no longer believe that privacy and dignity are secondary features.
They are part of the product’s definition.