سياسة الخصوصية — إضافة «بوابة التعليم الرقمية - جسر نور ومدرستي»

Privacy Policy — “Digital Education Portal - Noor & Madrasati Bridge”

Single purpose

The extension is a bridge between a school’s own account on digitalschool.sa and two Saudi Ministry of Education systems, Madrasati and Noor. It acts only inside the signed-in user’s own browser session and only when the user clicks a button, to do four things: (a) push the school timetable from the school’s account to Madrasati’s timetable and course-assignment screens; (b) pull teacher lesson-preparation follow-up (lessons, assignments, enrichments) from Madrasati’s teacher-report pages into the school’s account; (c) submit the day’s student absences from the school’s account into Noor’s absence-recording page (excused or unexcused), after the user confirms; (d) help a teacher prepare the week’s lessons in Madrasati: from Madrasati’s teacher weekly schedule (or our lesson-preparation page) it reads the teacher’s periods and course outlines, suggests each period’s lesson in sequence, and saves the preparation through Madrasati’s own page controls, after the teacher confirms. It performs no other function and loads no remotely hosted code.

Where it runs

• digitalschool.sa — announces that the extension is installed and relays the user’s request; it reads only one tag from the page (mf-role: whether the signed-in account is a school or a teacher) to show the right button. Results are delivered back from a tab on the same site, within the user’s session.
• schools/beta/external.madrasati.sa — a small collapsible button. Only on click, a script bundled in the extension reads the teacher-report pages (pull) or fills the timetable screens (push); it may open a temporary background tab and close it afterwards. On the teacher weekly-schedule page only, a “Prepare this week’s lessons” button opens an isolated panel; on click, a bundled script reads the week’s periods and course outlines and, after the teacher confirms, fills Madrasati’s lesson-preparation page in hidden same-origin frames and saves with Madrasati’s own buttons; a temporary minimized window may be used and closed.
• noor.moe.gov.sa/Noor/* — a small collapsible button. Only after confirmation, the bundled script opens Noor’s attendance page and records the selected absences within the user’s session.

Data handled

• Teacher names and national ID / iqama numbers as shown in Madrasati reports (Madrasati → our portal) — to link statistics to the teacher’s record.
• Lessons and their preparation status; number of assignments and enrichments and their creator (Madrasati → our portal).
• School name and its Madrasati identifier — used only to prevent mixing one school’s data with another’s.
• Timetable: subjects, classes, periods and assigned teacher names (our portal → Madrasati), passed to the Madrasati page from a small window on our own site.
• Absent students for a chosen day: name, grade, class, date and absence type (excused / unexcused) (our portal → Noor) — only after the user confirms.
• Noor’s class list and the class roster on the attendance page (name, section, current status) are read inside the Noor tab only, to match names and verify the result; they are not sent to our servers.
• Per-student result (saved / failed and why), plus the Noor account name and school name shown in Noor’s page header (Noor → our portal) — to show the outcome and log who uploaded and when.
• Lesson preparation: the teacher’s weekly periods (day, period, class, subject, preparation status), course outlines (units and lessons), the last lesson prepared per class, and lesson objectives/content from Madrasati’s bank — read from Madrasati to suggest lessons. In the Madrasati panel this stays in the browser and is not sent to our servers; when the teacher starts from our portal page, it is returned to that page for display.
• The teacher’s preparation choices (lesson per period, mode, objectives count, strategies, tools, activity and the texts the teacher writes) (extension → Madrasati) — saved only after the teacher confirms.
• From our portal page only: a log of what was saved (date, period, class, subject, lesson, result) and, if the teacher chooses, the lesson texts, stored in a shared lesson-text bank keyed by Madrasati’s lesson number — containing no student data.

Confirmation before uploading to Noor

An upload request is accepted only from our own site’s top-level page. The extension then opens its own window listing the date, the number of students and their names. The confirm button stays disabled until the user ticks the acknowledgement by hand; web pages cannot reach or click this window. Closing it, cancelling, or a three-minute timeout cancels the upload and Noor is not opened at all. The window also shows the absence type (excused / unexcused).

Lesson preparation follows the same rule: a save request is accepted only from the extension’s panel on Madrasati’s teacher weekly schedule or from our own site; the extension opens its own window (pconfirm.html) listing the subject, the number of periods and each period’s date, class and lesson. Nothing is saved to Madrasati until the teacher confirms by hand; closing the window or a timeout cancels it, and each confirmed batch runs once, only in the page that requested it.

What is never collected or stored

Passwords, cookies, session tokens (Madrasati or Noor), browsing history, any content from websites other than madrasati.sa, noor.moe.gov.sa and digitalschool.sa, or any Noor student data beyond what is needed to match the absentees the user chose to upload.

Local storage on the device

• storage.local — whether the user collapsed the on-page button; the signed-in account’s role on our portal (school or teacher) and when it was read; the teacher’s preparation preferences (mode, objectives, strategies, tools, activity); and a short record of the last lesson prepared per course and class, pruned after 120 days. All kept on the device and never sent anywhere.
• storage.session — a temporary random key per tab where our bundled tool was injected, so only our tool can talk to the extension; cleared when the tab or browser closes.
• The timetable tool saves, in the Madrasati page’s local storage in the user’s browser, the teacher/subject name mapping the user decides manually, for reuse; it is not sent anywhere.
• A per-site, isolated storage area reserved for the extension’s own tools exists but is not used by the current tools.

Permission justification

• scripting — inject the bundled reader/filler/lesson-preparation script into the open Madrasati or Noor page, and deliver results from a tab on our site, within the user’s session, when the user clicks.
• tabs — locate the open Madrasati / Noor / portal tab, or open a temporary background tab or minimized window and close it afterwards.
• storage — only what is listed under “Local storage”.
• host: *.madrasati.sa — source of follow-up data, and destination of the timetable and of teacher lesson preparation, within the user’s own session.
• host: noor.moe.gov.sa — destination of confirmed absence records, within the user’s own session.
• host: digitalschool.sa — the school’s own account: source of the timetable and absences, destination of follow-up data and upload results.

Storage, sharing and deletion

• Data pulled from Madrasati and Noor upload results are stored on our servers located in Saudi Arabia and are visible only to authorised staff of that same school.
• Absences submitted to Noor are stored in Noor under the Ministry’s own policies; we keep only a log of who uploaded, when, and Noor’s response per student.
• The extension sends nothing to any party other than the three sites above, and to no third-party service.
• Users can delete any captured Madrasati data themselves at any time from the “Madrasati Follow-up” page, and can request any other deletion by e-mail. Retention periods and data-subject rights in the platform privacy policy apply.
• We do not sell data, do not share it with third parties, and do not use it for advertising or any purpose other than the one stated above.

Contact

system@digitalschool.sa