Skip to main content
People arrive on this page with one of two questions: “who can see all this?” or “how do I get out?”. We answer both, but we start with the thing that explains the rest — whose data this actually is. The formal documents are separate, and they are the binding ones: privacy policy and terms. This page neither replaces nor summarises them — it explains how the product is built. If you came here asking “why do you want four digits of my child’s PESEL?”, that has a page of its own: Personal data and the PIN.

​
The data is yours, not the school’s

In most school systems the direction runs one way: the school collects data about pupils, and a parent gets to look at it. In Zebrania it runs the other way. Everything you fill in at the start of the year — contact details, after-school care, walking home alone, pickup authorizations, religion and ethics, the health statement, image consent — originates with you and stays yours. None of it is collected because the application wants it. Three things follow, and they are worth saying plainly:
  • Submitting a form is the act of sharing. You are not “entering data into the school’s system” — you are sending your own statement to a specific person you chose, for the purpose you chose.
  • A teacher is a person, not an office. They receive what you sent them, for the reason you sent it. They are not a window through which an institution looks at your data.
  • Zebrania is the messenger. We carry, store and render your statement on your behalf. We do not set the purpose of the message and do not become a party to what it says.
The school as an institution is not a party to any of this. There is no data-processing agreement, no school-level onboarding as a precondition, and no data protection officer’s sign-off gating any form.That is not an oversight — it is a deliberate choice, recorded in architecture decision ADR-110. A teacher signs up and creates a class on their own, without anybody in management signing anything. If an agreement at school level were required, this would be a different product.
Zebrania is an ordinary controller only for its own operational data: account identity, sign-in, audit records and billing. That is a narrow, separate role — it must not be conflated with the contents of your forms.

​
Two records, not one

The ownership model becomes concrete at the point that surprises people most. For the same person there are two separate records:
  • Child — on your My children list. It belongs to you. It exists on its own, without any school.
  • Student — in one particular class at one particular school. It belongs to the school.
When you enrol a child in a class, the school receives a copy of the child’s details. From that moment nothing keeps the two in step — it is a copy, not a window onto your data. What follows from that split is covered in Children and contact details. Remember it now, because it returns at the end of this page: deleting your account is not the same as withdrawing the statements you already sent.

​
Who sees what

The table below is about statements and contact details — the things you file in the app. Rows run from the widest access to the narrowest.
The health statement is the most tightly protected of the seven. The app says so outright: “Only you and your child’s homeroom teacher can see this statement. Other parents and teachers of other classes cannot.” School administration has no access to it — unlike the other lists.

​
What the homeroom teacher sees, and what they do not

A homeroom teacher’s access is not full sight, and the difference can be surprising: The full account of what is visible on the school’s side, on screen and on paper, is in Class views and printouts.

​
A missing statement is not a refusal

This rule cuts across the product, but it belongs on this page most of all. A blank means “nothing is known”, not “the parent said no” — and that is how the school sees it too. A child with no health statement has no row on the class list, so an empty cell cannot be misread as “healthy, no allergies”. Nowhere in Zebrania is a recorded “no” kept. Withdrawing a religion signup deletes the row rather than adding a note that the child does not attend. You do not have to delete your account to take one thing back. Every statement is withdrawn separately, in one click, with no “are you sure?” step. Withdrawal looks different in each case, and this is the most important table on the page if you care about what remains:
Withdrawing image consent does not remove photos already published. Zebrania does not publish photos and is not a party to that consent — we only relay your position, and the school is responsible for the lawfulness of any publication. Ask the school directly about a specific photo.
One separate convenience: every statement expires with the school year anyway. You file them again in September and nothing carries over. If you simply do not want to renew something, not filing it again is enough. The detail on each statement is in Consents and statements.

​
Deleting your account

There is no “delete account” button in the app today. It is not hidden in Settings or anywhere else — it has simply not been built yet. Account deletion is currently run by hand, on the Zebrania team’s side.
How to request it: write to whoever runs Zebrania at your school, or use the Report a problem button in the app and say that your request is about deleting your account. There is no separate helpline or email address for parents — Troubleshooting explains which of those two routes to take.

​
Deletion by anonymisation

Your account is not deleted as a row in the database — it is emptied of the data that points to you. That sounds like a dodge, but the opposite is true: deleting the row would break everything that refers to it, and some traces would then be left in places nobody would ever tidy up.
Deleting your account does not withdraw statements you already sent. This returns to the two records from the top of this page: the statement went into the school’s student record, and your account is a separate thing.If what you want gone is the content — usually the health statement and the pickup authorizations — withdraw them using the buttons in the table above, before you request account deletion. Withdrawing a health statement deletes the data irreversibly; deleting your account does not do that by itself.
There is no defined period after which anonymised rows are removed entirely. They stay indefinitely — stripped of what points to you, but they stay. We say so plainly rather than quoting a number that does not exist.

​
What deleting your account does not cover

  • Student records on the school’s side — that is a copy the school manages. Ask the school directly to correct or remove it.
  • Photos already published — see the warning under image consent.
  • Printouts — a list somebody printed has left the application and nobody controls it any more. Printouts carry a storage warning on them, but the school manages them.

​
The documents

Those documents are binding and take precedence over this page if anything written here appears to conflict with them.

​
What next