Murtaka
Privacy Policy
Murtaka is a management system for nurseries and schools. Most of what passes through it is data about children and families that we do not own — the subscribing institution owns it, and we hold it on their behalf. That distinction is not wording: it decides who you write to when you want a copy of your data, or want it erased.
Two roles, two different responsibilities
The system serves two relationships, and conflating them is the most common mistake in privacy policies:
| The data | Who decides its fate | Our role |
|---|---|---|
| The subscriber account: institution name, administrator details, subscription and payments | We do | Controller — we decide why it is collected and how it is used |
| Children, families and staff inside an institution | The subscribing institution | Processor — we store and operate on it under their instructions, not our own decisions |
So if you are a parent or an employee at a nursery that uses Murtaka, your request goes to the nursery first — they hold the account and they decide. We carry out what they ask of us.
What we actually collect
We collect nothing that does not power a service you asked for. This list is taken from the database tables themselves:
- Account data — institution name, the registrant's name, email, phone and job title, and the number of branches.
- Child data — name, date of birth, gender, classroom and stage, and a photo if the institution uploads one.
- Family data — guardian names, phones and relationship, and who is authorised to collect a child.
- Health data — allergies, medication and medical notes entered by the institution when needed. These columns are encrypted at rest, not stored as readable text.
- Institutional financial data — contracts, instalments, payments and expenses.
- Usage records — who signed in and when, what was changed, and the IP address at sign-in. This is what makes tracing an error or a breach possible at all.
What we never store
No card number, no CVV, no expiry date — in any table we own.
When a nursery collects fees from a guardian online, it uses its own payment-gateway account with its own keys. The card is entered on the gateway's page, never on ours, and its number does not pass through us at any moment. What reaches us is a notification saying: this transaction succeeded or failed, for this amount.
Who outside us can reach the data
We do not sell, rent or trade data — not today and not in a later plan. The parties who can reach it are limited to those who operate the service:
| Party | What reaches them | Why |
|---|---|---|
| Paymob (payment gateway) | Payer name, email, phone and amount | To complete a payment. We are the controller and Paymob is the processor, and data may be processed inside Egypt and outside it. |
| Hosting provider | Everything in the database, by virtue of it sitting on their servers | To run the servers. Servers may be located outside Egypt. |
| Email provider | The email address and the message body | To send verification messages and alerts. |
| Your email, name and picture if you choose to sign in with Google | Sign-in only — no child data reaches it. | |
| Backblaze B2 (backups) | An encrypted copy of the full database | Keeping a copy outside our hosting provider, so a single failure does not lose everything. Servers are in the European Union, and the copy is encrypted at rest and opens only with our key. |
We disclose data to a competent judicial or regulatory authority where the law compels us. We notify the institution concerned unless the law forbids notification.
How long data is kept
- While the subscription is active an institution's data is kept in full — the historical record is the substance of the service: a grade sheet or a child file erased after a year loses its meaning.
- After a subscription ends data is held for a reasonable period so the institution can retrieve or export it, then erased on request.
- A trial account whose email is not verified within seven days is deleted automatically, together with what was entered into it — so no child data sits in an account whose owner was never shown to be its owner.
- Financial transaction records are kept for the period accounting law requires, even where everything else is erased.
How it is protected
- All traffic is encrypted over HTTPS.
- Passwords are stored as a one-way hash — we cannot read them or recover them, only reset them.
- Sensitive health columns are encrypted in the database.
- Each institution's data is isolated by a barrier that closes on doubt: a query that does not know whose it is returns not one row — rather than returning everything.
- Permissions follow the role: someone working in one branch does not see another, and someone whose role is teaching does not see the accounts.
No system is free of the possibility. If a breach touches an institution's data, we notify them with what we know — what happened, when, which data, and what we did — without waiting for the investigation to finish.
Your rights
You may request: a copy of your data · correction of errors in it · its erasure · a stop to its use for a particular purpose · and withdrawal of a consent you previously gave.
Where to send the request depends on your role: if you are the subscribing institution, write to us directly. If you are a parent or an employee, write to your institution — their instruction binds us and we act on it.
To delete your account: write from the email registered on your account to the address at the foot of this page, with the subject "Delete account". We respond within thirty days.
If you are a parent or an employee, your account is created and owned by the institution — send the request there. We act on their instruction, and we do not delete an account behind the institution's back.
What survives deletion survives for a legal obligation, not by our preference: tax law requires invoices and receipts to be kept, and they are separated from the account name where possible. See "How long data stays" above.
Cookies
We use no advertising cookies and no cross-site tracking. We set three and no more: the session cookie that keeps you signed in, the form-protection cookie that stops another site from submitting a request in your name, and the remember cookie on the parent portal only — it keeps you signed in between visits so you do not retype your password, and it is voided by a password change, a sign-out, or the account being suspended. Deleting them signs you out and does nothing further.
Children
The service is not directed at children and they do not create accounts in it. Their data is entered by the educational institution in its capacity as responsible for it, and under its relationship with guardians. Obtaining the necessary consents from them rests with the institution.
Changes to this policy
We may amend it. A material change is announced by email to subscribing institutions before it takes effect — not left to a date at the top of a page read by whoever happens to visit.
The Arabic text is the authoritative version; this translation is provided for convenience.
Back to home