Privacy policy

1. Who we are

dev. Hub is a learning platform for schools: books, games, simulators, tasks, reports, the Active Board and live sessions. It is operated by Eng. Mahmoud Yakoub under the name dev. (“we”). A school that uses dev. Hub decides who joins it and what they do there; for the personal data of its staff and students, the school is the one responsible to them, and we process that data on the school’s behalf and on its instructions.

2. What we collect

• Your account: your name, your email address or username, your role (student, teacher, staff), your school, your classes; a phone number, a country and a city when they are added to the profile (staff accounts must give them); a profile picture if you add one; your password, kept only as a one-way hash that cannot be read back.
• Your work: where you stopped in each book, the notes, drawings and programs you save in My files, the tasks you hand in and the marks and feedback on them, your messages in class discussion groups, your answers in live quizzes and games, and the questions you send to your teacher.
• Use and security: when you sign in and how long you stay, the kind of device and browser, your internet (IP) address, which books you open, and blocked attempts to print, save or capture a page. A school may switch on a look-up of the town you connect from; it is off unless the school turns it on.
• Live sessions and recordings: described in sections 4 and 5.

We do not collect payment card details, and we do not buy data about you from anyone.

3. How we use it

Only to run the platform for your school: to sign you in, show you your books and classes, let teachers set and mark work, produce reports for the school, keep the service working, and protect the books from copying and the accounts from misuse. There is no advertising, we do not sell or rent personal data, and we do not use it to profile you for anyone else.

4. Live sessions

In a live session the teacher’s camera, microphone and shared screen, and a student’s microphone or camera once the teacher allows it, are carried through our own media server (live.dev-dott.com, on our own server). Students join with their microphone and camera off; a student turns them on only after the teacher allows it, and the browser asks for the student’s permission first. The audio and video pass through and are not stored by us, except when the teacher records the session as described below.

5. Recordings and Google user data

A school may connect its own Google Drive so that teachers can record live sessions. This is the only use dev. Hub makes of Google APIs.

• What we ask Google for: the permission https://www.googleapis.com/auth/drive.file only. With it, dev. Hub can see and manage only the files and the folder it creates itself in that Drive (“dev. Live recordings”). It cannot see, open or list any other file in the Drive. We also read the email address of the connected Google account, to show the school’s administrators which account is connected.
• How we use it: to create the folder, to upload each recording into it, and to read a recording back when a person allowed to watch it (the teacher, the school’s approvers, and after approval the students of that session) presses play inside dev. Hub. Nothing else.
• What we keep: the Google refresh token, encrypted on our server (AES-256-GCM) so that it cannot be read without our key; short-lived access tokens, in memory only; the email address of the connected account and the identifier of the folder and of each file. Recordings themselves are kept only in the school’s Drive, not on our server.
• Encryption: a recording is encrypted in the teacher’s browser before it leaves the computer, with a key made for that recording and kept encrypted on our server. Outside dev. Hub the file in Drive cannot be played. Browsers never receive the Google token or the Drive upload address.
• Sharing: we do not share, sell or transfer Google user data to anyone, we do not use it for advertising, we do not use it to train artificial intelligence or machine learning models, and no person reads it except where needed for security, to comply with the law, or with the school’s permission to fix a problem.
• Limited Use: dev. Hub’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
• Disconnecting: the school’s director or the staff member it chose presses Disconnect on the Recordings page, which deletes the stored token from our server at once. Access can also be withdrawn at any time at myaccount.google.com/permissions. The recordings stay in the school’s Drive, which the school controls and may delete.

6. Services we rely on

• Hosting and email: our server and our email (info@dev-dott.com) are provided by Namecheap. Emails are sent only for the account itself: confirmation, approval, password resets and notices of the platform.
• Artificial intelligence: some features ask a model by Anthropic (Claude) through its API: the unit planner (the plan’s text), reading a school calendar from a PDF, the smart reply of a discussion group (the students’ first names and short excerpts of their messages, with the task and a few lines of the book), a short lesson suggestion from class results (without student names or answers), the security monitor (counts, account numbers and internet addresses, never what a person wrote), and Dax, the study helper on the Library page (the student’s question and a few lines of their own books, never their name). Each request is short and is not used by us to train models.
• Speech in the browser: when a student turns on Dax’s voice, their browser turns what they say into text with its own speech service (in Chrome and Edge this sends the voice to Google or Microsoft). The student agrees to this first; we receive only the text of their questions, never the voice. Dax’s answers are spoken by the browser on the device.
• Google: Google Drive for recordings when a school connects it (section 5), and the fonts of the pages, which your browser loads from Google Fonts.
• Town look-up: only when a school switches it on, the internet address is sent to ipwho.is to find the town and country.

7. Cookies and storage

One cookie keeps you signed in, and on a school’s address one more remembers that school. Your browser also keeps small settings on your device, such as the light or dark theme. We use no advertising or tracking cookies and no analytics by other companies.

8. Children and schools

Most students are children. Their accounts are created or approved by their school or their teacher, and schools are responsible for having the agreement of parents or guardians where the law of their country requires it. Students under the age of digital consent in their country should register only with the agreement of a parent, guardian or their school. Parents may ask the school, or us, to see or delete their child’s data.

9. How long we keep data

Account data and work are kept while the account is active and the school uses dev. Hub. When a school leaves, its data is kept for 30 days so that it can export it, and is then deleted. Security logs are kept only as long as needed to protect the platform. Recordings are kept in the school’s Drive for as long as the school decides.

10. How we protect it

Connections use HTTPS. Passwords are hashed, secrets are kept outside the code, each school’s data is kept in its own database, every request is checked against what the person may see, and the platform watches for unusual activity. No system is perfectly secure; if a breach affected your data, we would tell your school and, where the law requires it, you.

11. Your choices and rights

You can see and change your profile in the platform. You, a parent or guardian, or your school can ask us to see, correct, export or delete personal data; a school can also do much of this itself from its dashboard. Requests made through a school are answered with the school.

12. Changes

If this policy changes, the new version is published on this page with its date, and important changes are announced in the platform.

13. Contact

For any question about privacy or your data: info@dev-dott.com. See also the Terms of use and copyright.

© 2026 dev. All rights reserved.