Privacy

How the platform handles teacher and student data: no accounts, no advertising, and as little data as possible.

Last updated: 25 October 2026

In short

  • No account, email address or phone number is needed. Learners use a nickname they choose.
  • No advertising, no analytics, no advertising trackers, no third-party scripts or fonts, and no cookies on the public site.
  • What you make on your own stays on your device. A live lesson is stored on the server so its participants can see it, and is deleted automatically 24 hours after it was created.

Who is responsible

The person responsible for the processing described here is the publisher:

Dr. Mustapha El Amrani
The publisher's postal contact details

For questions or requests about your data, write to the publisher at the privacy address above. See also the contact page.

Hosting and what every request involves

The site runs on Cloudflare Workers, from Cloudflare, Inc. (United States). Like any website, every visit sends your device's IP address and technical details (browser, language, the page asked for) to Cloudflare's servers, which deliver the page. Cloudflare processes this on Bayyinli's behalf as a processor, under its data processing addendum. Cloudflare states in its privacy policy that it is certified under the Swiss–U.S. and EU–U.S. Data Privacy Frameworks; Switzerland has recognised the Swiss–U.S. framework as giving adequate protection for certified companies since 15 September 2024. Data may therefore be processed in the United States and in the other countries where Cloudflare operates. See Cloudflare's privacy policy.

  • Request logging: Bayyinli's own request logs (Cloudflare Workers observability) are switched off. Cloudflare keeps its own operational and security records about requests under its policy.
  • Rate limiting: to protect the service, your IP address is counted against limits, for example on how many boards can be created, lessons looked up, pictures loaded or connections opened. Only recent requests count: the last ten minutes, or the last hour for creating lessons. The counts are held only in working memory and are never written to the database. So that the limit on creating lessons holds across all of Cloudflare's server instances, one coordinating instance also counts creations by a one-way fingerprint (hash) of your IP address, likewise in working memory only.

What a live lesson stores

When a teacher shares a board, the lesson is stored on the server so everyone in it sees the same board:

  • The board: its pages, drawings, text, shapes, tables, stickers and the pictures and PDF pages added to it. Location and other metadata are removed from uploaded pictures before they are stored.
  • The class: learners' nicknames, who may write and who is waiting to (until the request is answered, cancelled or the lesson ends), answers to the question or game that is open (earlier answers are kept only in the lesson report, if the teacher switches it on), classroom tool results, and who was removed. The laser pointer is never stored.
  • Lesson report (off unless the teacher switches it on): only once the teacher switches on “Keep a report of answers”, and from that moment: for each question the teacher asks, its text and expected answer, each learner's answer, whether it was marked correct or incorrect and how many times it was sent. Nothing from before it was switched on is kept, and when devices connect and disconnect is not recorded. Only the teacher can open and download the report. It is kept with the lesson, within fixed limits, and deleted with it.
  • Private work and homework: learners' private boards, homework instructions and due dates, hand-in status, and the teacher's grades and notes. Learners see their own grade and note only. A due date cannot be later than the lesson's deletion.
  • Access: a fingerprint (hash) of the teacher link's secret and of each device's pass, and the private links learners make to continue on another device (the teacher can withdraw them). The secrets themselves are not stored on the server. After a learner's data is deleted on request, a one-way fingerprint of their former identity in that lesson is kept, so their device is told and gets nothing back; it goes with the lesson.
  • Review link (if the teacher publishes one): a read-only copy of the class-board pages the teacher chose, without private boards, answers or learner keys, and a fingerprint (hash) of the link's secret. Anyone with the link can view those pages until the teacher withdraws it or the lesson is deleted.

Retention and deletion: a lesson, with its pictures, review link and everything above, is deleted automatically 24 hours after it was created. From that moment it can no longer be opened; it is erased then, or, if the server is not running at that moment, as soon as it runs again. Reconnecting, editing or publishing does not extend this. The teacher sees the exact time when starting the lesson and during it, with a warning shortly before. Ending a lesson closes it to learners but does not delete it. Lessons created before this rule keep the earlier one: they are deleted 30 days after their last activity, and may still hold connection times recorded until then.

  • The whole lesson, sooner: the teacher can delete it at any time with “Delete lesson now” in the board's Students panel, after a confirmation; this cannot be undone. Otherwise, a teacher writes to the privacy address with the board code (never the teacher link). We check that you hold the teacher link by asking you to write, on the board, a word we send you.
  • One learner's data only: a learner, or a parent for a learner, can have that learner's own data deleted without deleting the rest of the class. We send a word. The learner opens the lesson on the device they used, chooses "Request about my data" in the board menu (also offered after the lesson has ended), types the word and sends us the code shown. The code is made on that device and reveals nothing else.
    • We then delete their items on the class board and on their private board, and pictures only they used.
    • We also delete their nickname, answers, grades and notes, hand-in state and private links, and their answers in the lesson report (and their connection times, in lessons created before the 24-hour rule). Their device continues as a new learner.
    • Copies of their work, or mentions of them, in other people's work are assessed one by one. We tell you what we kept and why.
    • If the usual check is impossible (the device was lost or its storage cleared), say so: we look for another way rather than refuse.

Deleted data disappears from the service at once. Cloudflare's database recovery may keep earlier copies for up to 30 days before they are gone for good. Copies that people downloaded to their own devices are outside our reach. Deleting a lesson on the server, at its expiry or sooner, does not clear what browsers keep: a board still open in a tab, the browser's storage and cache, and files downloaded from the lesson stay on those devices until their users remove them.

Who can see what

  • The teacher link gives control of the board; it stays on the teacher's devices. The class link or code lets learners join and ask to write.
  • With private boards on, each learner's work is visible only to that learner and the teacher.
  • A learner's private resume link opens only that learner's work on that board, and the teacher can revoke it.
  • The operator (the publisher) holds an administrator key that can list current lesson codes, export a lesson as a backup, delete a lesson and erase one learner's data. It is used only to run the service, to answer a request about data, or where the law requires it. It gives no access to what stays only on your device.

On your device (local storage)

The site stores some things in your browser (localStorage and IndexedDB) so that it works:

  • Boards you make on your own, and drafts not yet sent to a live lesson.
  • The links to boards you created, with their teacher secret, so you can reopen them. They stay in your browser after the lesson itself is deleted, until you clear this site's data.
  • Your device's key and pass for each lesson you joined, and your nickname.
  • The lesson tray, your worksheet presets and "My words" (including their photos).
  • In practice: the questions to practise again, the rest of an unfinished round and the last lesson you opened. Only the questions' keys are kept, never names or typed answers; "Clear what is kept on this device" on the practice page removes them.
  • Your choices: theme, keyboard and similar settings.

None of this is sent anywhere unless you use it in a live lesson. You can remove it at any time by clearing this site's data in your browser's settings. The site then forgets your boards, presets and links on that device.

Lesson files and exported pictures, PDFs and ZIP files are made in your browser and saved on your device; they are not uploaded. Opening a lesson file does not upload it; its pictures are uploaded only if you then start a live lesson.

Cookies

The public site sets no cookies. One essential cookie exists only in a protected internal preview that is not part of the public service.

When you write to us

Messages to our addresses are forwarded by Cloudflare's email routing to the publisher's mailbox. Your message and contact details are used only to answer you, and are not kept longer than needed for that.

Not part of the service today

  • The Quran reader is not available on the public site. When it is, this page will explain how it works and credit its sources.
  • Saving boards in a personal online "locker" is only a proposal and is not built.

Your rights

You may ask what data about you is processed, and ask for it to be corrected or deleted. We assess each request and answer free of charge, as a rule within 30 days, saying what we did and, if we could not do all of it, why. Because there are no accounts, please give the board code. We then check that the request comes from the learner's device (see above), never from a nickname alone. You can also contact the Federal Data Protection and Information Commissioner (FDPIC) in Switzerland, or the data protection authority where you live.

Children

Learners need no account and should use a nickname, not their full name. Teachers should not put pupils' personal details on a board.

Changes

This page may change as the site changes. The date of the last change is shown at the top.

Report a bug

Tell us what went wrong. This page sends nothing: you send the report yourself, by email.

Do not paste private board links, lesson codes, or learners' names or details: they are not removed automatically.

Technical details (you can edit or remove them)