Privacy and Use Policy — Teaching Record

Last updated: 31 August 2026 Domain: sijilapps.com

Everything in this document that describes how the platform behaves is taken

from the code itself and verified — an automated test compares what we promise

here against what the code does there, and fails if they drift apart. What we

do not know, we say we do not know rather than smooth over.

Governing text: the Arabic version of this policy is the binding one. This

English text is a faithful translation provided for convenience; if the two

ever differ, the Arabic prevails.

1. Who we are

Teaching Record is a platform that helps a teacher build plans, assessments and worksheets, document evidence of their practice, and tie all of it to their standards.

• Operator: Khalil Mussa — a natural person, not a company. The platform today is one person's work, and we say so plainly because you are entitled to know who you are dealing with.
• Operator's base: the State of Qatar.
• Email: support@sijilapps.com
• Coming: the work is deposited in its author's name with the Intellectual Property Rights Protection Department at Qatar's Ministry of Commerce and Industry, and a Qatari company is being formed for the platform to move into. When that happens the "Operator" above changes, and we will tell you about the change as set out in §11 — fourteen days before it takes effect, and before any paid subscription.

2. What we collect

2.1 What you give us at sign-up

Changed from the previous version: email and phone used to be optional and

became required as of 27 August 2026. The reason is direct: support cannot help

an account whose owner cannot be reached, and a teacher who loses their password

with no registered email loses the account and all the work in it. Accounts older

than that date are asked to complete both fields at their next sign-in.

What we do not ask for and do not accept: student names, student numbers, or grades attributed to them. The platform does not contain a single field for identified student data.

2.2 What you produce while using it

• Your standards, their text, and how they map to subjects and grades.
• What you generate: plans, assessments, worksheets, decks, lesson materials. Their content is encrypted in the database.
• Your evidence: the description, tag, date and linked standard. The description and comment are encrypted.
• Usage log: what each model call cost and which task it was for. Used to enforce your monthly cap.
• Your preferences: interface language, templates, theme.
• Files you upload yourself — your prep, worksheets, tests and decks: stored as they are and encrypted in the database, not on the server's disk, split into chunks each encrypted separately. We do not read them unless you press "Read its contents" — only then is the content sent to the model, and a text copy is stored encrypted. They are deleted with one press, and with your whole account. And whatever you put in a cover file is shared in full through its public link: we do not read your file, so we cannot strip its answers the way we strip them from what we generate ourselves.
• School documents you upload — the prep template, the evaluation instrument: we extract their structure (section and column names, or domains and components) and delete the uploaded file. We do not keep your school's document; its text is sent once to the model to read that structure. The extracted structure is visible to colleagues at the same school — that is its purpose: you upload once so thirty people do not. So do not upload here what you would not want a colleague to see.

2.3 Images — the most important clause in this document

The platform keeps no image at all. An image is uploaded, read, a description and tag are extracted from it, and the copy is deleted immediately — on every exit path: success, failure, skip and retry.

What remains is the text description and a pointer to the original where it lives (your school's Drive, for example). The original stays under the school's responsibility and consents, not ours.

But — and this must be clear: the image is sent to Anthropic while being read, because extracting the description runs on their model. It leaves our server even though it does not remain on it.

And so the platform asks explicitly, before every upload:

• Do not upload personal photographs of students.
• Cover the names visible on their papers.
• Complying with your school's policy on images and consents is a precondition, and the responsibility for choosing what to upload is yours.

2.4 What is collected automatically

• Sign-in attempts: a hashed fingerprint (SHA-256 with a server salt) of the network address or the email, the number of failed attempts, and the time of the last one — to stop repeated password guessing. Neither the address nor the email is stored as text, and there is no way to read either from the table. A dormant row is erased after 30 days.
• Recovery codes: stored as hashes, valid for fifteen minutes, and burned the moment they are used.

We use no third-party tracking or analytics, and no advertising cookies. The only cookie is your session cookie; it lasts four hours and is sent over HTTPS only.

3. Contributing your corrections to the library

This clause is new, and we write it plainly because it concerns your own work.

When the platform generates a standard and you correct it, the difference between the two texts — what the model wrote, and what you sharpened — is stored in a shared table that improves the quality of what the platform generates for every teacher.

These are its terms, all of them:

• The stored row has no owner. It carries no account number, no name, and no column that ties it to you. We ourselves cannot tell whose correction it is.
• What is stored is the standard's text alone — subject, grade, framework, language, and the text before and after. Not your lesson content, not your evidence, nothing else.
• You can switch it off at any moment from the "Account" tab — the "Contribute to improving the library" toggle. It stops storing from that moment.
• And it does not erase what came before — because the rows have no owner, and there is no way to know which are yours. We say this here plainly rather than hide it.
• Default: on. The disclosure appears on the sign-up screen before you press.

4. Who your data reaches

We do not sell your data, do not rent it, and do not share it for marketing. Ever.

These parties receive it because the platform does not work without them:

We chose Frankfurt and Ireland deliberately so the data stays inside the European Union.

We may disclose your data if the law compels us, or to protect our rights or others' safety — and we will tell you if the law allows us to.

5. Security

• Encryption in the database: your phone number, the content of what you generate, your evidence descriptions, your comments and your reflections — all encrypted with a key the database does not hold.
• Passwords: bcrypt, never stored as text.
• Session: four hours, and its cookie is sent over HTTPS only.
• Two-step verification: available, and we recommend it.
• Backup recovery codes: ten codes, given once at sign-up.
• Rate limits on sign-in, recovery and verification.

No system is absolutely secure. If we learn of a breach affecting your data we will notify you and the competent authority within 72 hours of learning of it — the period required by Qatar's Personal Data Privacy Protection Law (No. 13 of 2016).

6. How long we keep things

7. Your rights

• To access your data — all of it is shown inside the platform, and you can export it whenever you want.
• To correct what is wrong in it.
• To delete your account — from the "Account" tab. You are asked to type a confirmation word rather than press a button, because deletion cannot be undone.
• To port it in a readable format.
• To stop contributing your corrections (§3).
• To complain — to the National Cyber Governance and Assurance Affairs (NCGAA) at Qatar's National Cyber Security Agency, or to your country's data protection authority if you are inside the European Union.

When you delete your account, everything belonging to you is erased from twenty tables — not the account row alone, but your file chunks, your usage log, and the fingerprint of your sign-in attempts. The only two exceptions are named above: ownerless corrections, and the nameless reason for leaving.

8. Children

The platform is for teachers, not students. Do not create an account for anyone under eighteen, and do not enter identified student data. A student who joins a classroom game types a display name for that lesson only — it is not kept after the session ends, and is not linked to any account.

9. Subscription and payment

There is no paid subscription today, no payment gateway, and no purchase page. The platform is free at this stage, and the code contains no integration with any payment processor — no card is requested from you, none of its data reaches us, and we store none of it.

When a subscription does open:

• It will not open before the company named in §1 is formed, and will not begin without prior notice as set out in §11.
• Payments will be processed through a specialised gateway, and your card details will not pass through our servers.
• Prices and refund terms will be published in this document before the first payment, not after.

And what you generate today stays yours either way: opening a subscription later does not withhold or delete work you produced before it.

10. What we do not promise

We say it clearly because vagueness here harms you:

• What the platform generates is a first draft, not a final text. The review is yours.
• Automatic marking from an image is approximate, and every result carries a confidence score. Extended-response questions are not machine-marked at all.
• The framework coverage percentage measures the presence of documented evidence, not the quality of performance.
• Classroom rooms (the board and the game) live in memory, and any restart ends them. Do not rely on them for an assessment that counts.

11. Changes to this document

We will tell you about any material change through your registered email fourteen days before it takes effect — including a change of operator (§1) and the opening of a paid subscription (§9). The date at the top of the document is the date of the last edit.

12. Governing law

This document and your relationship with the platform are governed by the laws of the State of Qatar, and its courts have jurisdiction over any dispute — because the platform's operator is there (§1).

This does not strip you of any right your own country's law grants you. Your data is stored in the European Union (§4), so anyone using the platform from inside it enjoys the full rights of the General Data Protection Regulation (GDPR) — which are the same rights set out in §7.

13. Contact us

• Email: support@sijilapps.com — a human reads it, and it is the same address for privacy questions and deletion requests.
• From inside the platform: the "Support" tab — the technical diagnostic is attached automatically, and you can attach a screenshot.