BackThe Group That Never Sleeps
This chapter is saved on your device for offline reading
Chapter 16

A Screenshot Cannot Be Deleted

The old screenshot circulated again the next day. This time it did not come from Ms. Mwaka’s group. It appeared in a smaller chat for parents of students in one course, forwarded by someone Rehema did not know. The image showed eight rows and five columns from the deleted sheet. Asha’s name was absent, but half of Rehema’s name was visible.

Asha’s first instinct was to hunt every copy. Who had sent it? Who had saved it? How many groups had it reached? Could they demand deletion confirmations from everyone? Could the student body apply pressure?

Salma found her in the canteen writing a list of possible recipients.

“You know you cannot verify every copy,” Salma said.

“I know.”

“And you are still writing names.”

“Because I do not want to simply accept it.”

“Accepting irreversibility is not surrender.”

Asha shut the notebook hard. “Easy to say when it is not your information.”

“It is my information in this screenshot,” Rehema said from across the table. “And I do not want the rest of my university life to become a mission to delete it.”

Asha looked at her.

“I want the new source stopped,” Rehema continued. “I want people told not to forward it. I want university policy. But I cannot crawl into people’s phones.”

It was another boundary Asha did not like but needed to learn. Control did not mean reversing time.

Student affairs and the new parent-notices channel issued a joint message: old screenshots should be deleted and not redistributed; individual student information should not be retained for monitoring; anyone with a real concern should use the official welfare route or speak to the student directly. No recipients were publicly named.

Ms. Mwaka posted her own statement: *I created this system. I believed I was helping. I was wrong to allow personal information to be combined without consent. Please delete any copies you hold.*

Asha read it twice. Accountability without self-defense had weight.

Then she met Zuri.

Their friendship had become polite. They still shared a room without fighting, but they no longer laughed together late at night. Zuri did not ask how Asha’s internship interview had gone. Asha did not volunteer the answer.

“I saw the notice,” Zuri said.

“Okay.”

“I deleted every screenshot I had. And I told the student representative everything I sent.”

“Okay.”

Zuri sat on her bed. “I want to apologize properly. Not ‘sorry because you were upset.’ I am sorry because I sent information that was not mine to send. I treated it like a small favor for my aunt. I did not think about the fact that you would be the one carrying the consequence.”

Asha did not answer immediately.

“And I will not ask for our friendship to go back to how it was,” Zuri said. “That would turn the apology into a transaction.”

Asha’s eyes burned. “I thought you were a safe person.”

“I know.”

“And now I do not know.”

“That is okay.”

“It is not okay.”

“I mean it is okay that you do not know yet.”

They sat in silence. Zuri did not cry, reach for her, or stage a scene designed to clean the emotion away. She let the consequence remain in the room.

Later Asha opened her mother’s chat. Mariam had written only: *I saw the screenshot notice. Do not exhaust yourself trying to search every phone. Build what is in front of you.*

A month earlier Asha would have heard that as *let it go*. Now she understood the difference. Accepting that every copy could not be destroyed was not the same as allowing the system to continue.

She deleted her recipient list. She kept the official notices, the policy draft, and the consent prototype. Those were things she could still control.

A student who had never attended their meetings messaged Asha later. The old screenshot had made the student’s father ask questions about her bursary, but the new notice had given her words to answer him: *This is my information. If I need help, I will ask.*

Even an undeletable copy did not have to control a relationship forever. People could place new context around old information.

Zuri went to Salma and Musa and asked that her statement remain in the process file, not in the parent group or a public student chat. She offered to help with a digital-boundaries workshop for future volunteers. Asha agreed only on one condition.

“Do it because it is useful,” she said. “Not so everyone can say you are a good person again.”

“I understand.”

The answer showed a change in Zuri too: less hunger for approval, more willingness to carry a consequence without an audience.

Asha also abandoned the idea of demanding a deletion confirmation from every parent. Such a campaign could create a new chain of names, accusations, and reposted screenshots. Instead, the notice requested deletion and gave people a private route to report continued circulation. Musa promised that complaints would not be debated in a public thread.

That night Asha did something she had not expected to do. She deleted her own unredacted copy of the screenshot containing other students’ rows. She had kept it because she feared she would someday need to prove every detail. But the official review now preserved the agreed structural evidence. Keeping the full image would only increase the risk that she herself became a future source of leakage.

Rehema later told her that her father deleted his copy in front of her without needing a second demand.

“He did not ask me to prove why I was angry,” Rehema said. “He said he understood.”

Some copies would disappear through relationships rather than enforcement. That could not be measured neatly, but it was still part of repair.

Asha made one more personal rule: she would not accept another unredacted screenshot unless an official review specifically required it. She wanted necessary evidence, not a new collection of people’s lives.

Zuri apologized without asking for the friendship back immediately.

Reading settings
Line spacing
Theme