Privacy Policy

Version 2026.11.01.1. This is the same text the app shows before you sign up.

1 Who we are

Classroom Made Simple ("the App", "we") is software developed and operated by Jian Christopher C. Mariano, LPT, an individual developer in the Philippines. Contact: classroommadesimpleapp@gmail.com.

2 Two kinds of accounts, two kinds of responsibility

• School accounts are created by a school. For the learner and staff records in them, the school is the Personal Information Controller and we process the data on the school's behalf.
• Individual accounts are created by teachers for themselves. For the learner records a teacher enters, the teacher (and, where applicable, their school) is responsible for having the authority to record them; we process them only to provide the App.
• For your own account details and payment records, we are the Personal Information Controller.

3 What we collect

• Your account: name, email address, username, mobile number, role, the plan you are on, and when you agreed to these terms. Passwords are handled by Google Firebase Authentication and are never visible to us; the App keeps only a salted hash for offline sign-in on your own computer.
• Payments: the plan period, amount, payment method, reference number, date paid and any note you add. We never receive or store your GCash, Maya, bank or card login or PIN.
• Messages: what you send in Chat to other staff of your school, and when. Only the people in a conversation can read it — not your school head and not the developer. Please don't put learners' sensitive information in messages.
• Help & Feedback: what you write in a problem report, suggestion or question, with your name, school, role, the App version, whether you were on a computer or phone, and the page you were on, so the developer can follow up and reply.
• Learner records you enter: names, LRN, sex, birthdate, grade and section, grades, attendance, seat plans, anecdotal, intervention and feedback records, and similar classroom records. Anecdotal and incident reports list each learner involved with their role (offender, victim, witness or involved); a learner from a class you don't handle is recorded by the name and class you type in. For a class kept as a DepEd E-Class Record, a submitted term's scores and grades are kept as they were when submitted, and every change made after that is kept with its reason, who made it and when. The subject teacher enters and submits these grades; the section's adviser and the school head can see them but not change them. Its exports (the filled E-Class Record, the class record and the report card (SF9) data) are made on your device and hold learners' names, LRNs, grades and birthdates: keep them as carefully as the paper records.
• Learner photos and Document Vault files stay on the device where they were added. They are never uploaded to our servers and do not appear on your other devices.
• Lesson plans you import or export: you can import a lesson plan from a Word or PDF file. A plan the App exported comes back as it was, without the AI. For any other file, the file's text is sent to the AI (below) to copy into the plan's fields; the App doesn't take names out of it, so remove learners' names and other personal information first. The file itself isn't kept: only the plan you save, like any other. A lesson plan exported to Word carries a copy of the plan inside the file (what the page shows, plus the plan's settings) so it can be imported again; anyone you give the file to can import it too.
• Student IDs and class game results (CMS Interactive): a teacher can give each learner a short student ID (six letters and numbers, not the LRN, or the school's own number of 4 to 12 letters and numbers; it is shown after the school's code, or the teacher's in a personal account), kept with the learner's record. A learner types it, or scans their ID card, with their last name, on a phone, tablet or computer to join a game their teacher runs in class. The teacher's game screen checks the ID and last name against the class list; devices never receive the class list or anyone else's ID. For each learner who joins with their ID, or whom the teacher picks to play at the camera or keyboard, the game saves how many questions they got right out of the questions asked, and the game's points (used only for leaderboards, never for grades), with the class's records in the cloud. The teacher decides whether a game goes into the class record. While a class game is open, the full names of the learners who joined are shown on the classroom screen and can be read by anyone who has that game's 6-digit code; the game room is removed when the game closes, or after a day. A learner who doesn't know their ID can type their full name instead: only the teacher's game screen receives it, to find them on the class list, and the phone then asks the learner to confirm the name the teacher picked. In questions answered by typing or arranging (Identification, Fill in the blank, Matching, Sequencing, Enumeration), what a learner types is their answer and goes to the teacher's game screen like any other answer.
• Student-paced games (CMS Interactive): a teacher can assign a game for learners to play on their own phones, tablets or computers until a deadline. The game saves, with it in the cloud, a scrambled (one-way hashed) form of each learner's student ID together with their last name, with their first name (to greet them), so a device can check only the ID and last name typed into it: devices never receive the class list, anyone's ID or anyone's name. The first device to join as a learner keeps their place (by a random key it keeps); tries from other devices are shown to the teacher, who can let the learner in again. Each learner's answer to each question is saved as they go, until the deadline or until the teacher closes the game, and becomes the class game result described above. Anyone with the game's code can read its questions and their answers. A typed answer is saved as the learner typed it.
• Student-paced lessons (CMS Interactive): a teacher can assign slides with games to one or more of their classes, for learners to go through on their own phones, tablets or computers, at their own pace, until a due date; later is still taken, and marked late. A learner checks in with their student ID and last name: their device scrambles them (one-way) before sending them to our AI server, which checks the scrambled form against the lesson's seats with a secret key of its own, so neither the server nor any device ever receives a learner's ID or name. To slow down guessing, the server counts wrong tries for each lesson and each network address (kept only in scrambled form, for 15 minutes). The lesson keeps, for each learner, where they are, which slides they saw, the time spent on each slide, their answers to its games (and each try), and when they started and handed it in, so they can go on later on any device; the newest device a learner uses takes over, and the teacher sees that it moved. Only the teacher who assigned the lesson can see who each learner is and their results (by class: each learner's score goes to their own class's game results); a device can read only its own progress, and the lesson's link holds only its code. Anyone with the code can read the lesson's slides and its games' questions and answers (as for student-paced games). The teacher's notes and answer-key slides are never sent. A device remembers the learner going through a lesson for 8 hours; "Not you?" lets the next learner check in. A teacher can record their voice to explain a slide; recordings stay on the teacher's computer until our picture service takes audio too.
• Presentations and games (CMS Interactive): the slides and games you make (with the AI or by hand), and game sets you make without a lesson plan, are saved with your class's records in the cloud, so they open on any computer you sign in on. Colleagues who may change a lesson plan can open its slides and games too. The pictures you add to slides stay on the computer you added them on until picture uploads open (they aren't yet); then they are also kept on our picture service, so your slides show them on any computer; pictures for game answers are kept on our picture service (below). When you present to a class, "Call a student" shows a learner's full name, picked by chance from that class, on the classroom screen; the class list stays on your computer. Slides and game sets you remove, and slides the AI replaces, are kept with them in Recently removed for 30 days, then deleted (or sooner, when you choose Delete for good).
• Pictures for game answers and slides (CMS Interactive): a picture you add as an answer, lane, card or word in a game is made small by the App (at most 640 pixels on its longest side, which also drops the location and camera details a photo may carry) and kept on our picture service; so is a picture you add to a slide (at most 1,600 pixels), once for everyone who adds the same picture (below), so the game can show it on any computer and on the phones of learners playing it. Its web address can't be guessed, but anyone who has that address can see the picture, including anyone playing the game. Do not use pictures of learners or other people, or pictures showing personal information, as answer pictures.
• Our picture service (CMS Interactive): it keeps each picture once, by a code worked out from the file (a hash): if two teachers add the same picture, both use that one copy. With each picture it keeps which accounts use it, which account added it first, a short "look" code worked out from the picture (so a resized or re-saved copy of it can be recognised; it can't be turned back into the picture), and whether a photo still named the camera that took it (only yes or no, not the camera). It uses these only to keep one copy, to delete it when no one uses it, and to check that a picture shared to the library is the teacher's own. When we remove a picture because someone told us it uses their work without permission (Terms, section 7), it keeps the picture's code, so it can't be added again, with which account added it, and when and why it was removed.
• Drawings you ask for or send (CMS Interactive): when you can't find a drawing in Pisara, you can ask us for one (its name and what it should show) or send a drawing you made yourself (made small before it's sent). It's kept with your account, and only you and we (the developer) see it. If we approve it, a drawing based on it is added to the App's drawings for every teacher, in an update. Don't send anything that shows learners or anyone's face, name or personal details.
• The Pisara library (CMS Interactive): if you choose to share something you made for your slides (text, shapes, icons, drawings, your own pictures) or a whole slide, it is kept in the library with your account and, if you choose, your name. We (the developer) check it first; once we approve it, every teacher who uses CMS Interactive can see it and add it to their slides. A picture is shared only if you were the first to add it and no other teacher has added one that looks like it. Don't share anything that shows learners or anyone's face, name or personal details.
• Your school's logo and colours: set by its head teacher, principal or admin, kept with the school's data, and shown to its staff in the App (and on the sign-in screen of a computer where someone from the school last signed in).
• Records kept on your computer: the copy of your records the App keeps on a computer (for offline use), its backups and the saved sign-ins are encrypted for your Windows account. At a school, each account keeps its own copy, so a colleague signing in on the same computer doesn't open yours. Use your own Windows account where you can: anyone signed in to Windows as you could still open the App's files. In the web version (in a browser), the copy kept for offline use is stored in that browser's storage for the App's site and is not encrypted; on a shared computer, use a private window or clear the site's data after use. The sign-in screen lists the accounts that signed in on that computer, phone or browser (up to 5), so they can be picked next time: the name, the username or email, whether it signs in with Google or a password and, for a Google account, a small copy of its Google picture. This list is kept with the records on that device (encrypted the same way) and is never sent to us, but anyone who uses the device can see it. To keep your account off it, untick "Remember me" when you sign in; to take it off, press ✕ next to it on the sign-in screen, or choose "Sign out and forget me". If you sign in with Google and turn on "Stay signed in on this computer" with a PIN, Google asks you once, and the App keeps a Google sign-in key on that computer (for your name, email and picture only), encrypted for your Windows account and never sent to us, so you can pick your account and type your PIN even after signing out. It is deleted, and cancelled at Google, when you turn "Stay signed in" off, remove your PIN, enter a wrong PIN too many times, remove your account from the sign-in screen, or choose "Sign out and forget me"; you can also cancel it in your Google Account (Security, Third-party connections).
• Preventing misuse of the Free plan (individual accounts only): each installation of the App makes a random ID once and keeps it on your computer or phone. It is not a hardware ID or serial number, and says nothing about your device. When an individual account signs in, the App sends only a one-way hash of it (it can't be turned back into the ID), with the time and App version, and we note which accounts have signed in on the same installation. We also compare email addresses in a standard form (lowercase, without "+" tags, and without dots for Gmail) and mobile numbers, and check active classes against the plan's limit. For the Free AI allowance, our AI service keeps a one-way hash of your email address in that standard form, with the month's count of AI drafts. Only the developer can see this; your school head and other teachers can't. School staff accounts are not recorded or flagged, because teachers share school computers. These are hints we look at by hand before acting, not proof, and a reinstall gives an installation a new ID.
• Technical data: who last edited a record and when (to sync and show "Teacher X is editing"), counts of AI use (to apply plan allowances; for CMS Interactive, how many AI tokens each AI service used for each account each month, to set our prices), and when you last signed in, from which App version and on a computer or phone (to support you and plan updates). We do not use advertising or tracking cookies.

Anecdotal and intervention records may include sensitive personal information (DPA Sec. 3(l)), such as health notes. Incident reports may concern abuse, bullying or other child-protection matters and must be kept confidential under DepEd Order No. 40, s. 2012. Record only what is necessary for the learner's education and protection.

4 Why we use it (purpose and legal basis)

• To provide the App, sync your records across your devices, and keep backups — the performance of our agreement with you (DPA Sec. 12(b)).
• To process and verify payments, keep billing records, and contact you about your account, payments and security — our agreement with you and our legal obligations, including tax record-keeping (Sec. 12(b) and (c)).
• To prevent fraud and abuse and keep the service secure — our legitimate interests (Sec. 12(f)), including stopping one person from holding several Free accounts to get around the Free plan's limits.
• Learner records are processed on the school's or teacher's instructions, for the school's educational and DepEd record-keeping functions.

We do not sell personal data, use it for advertising, or use learner records for any purpose of our own.

5 Who processes data for us

• Google Firebase (Google LLC) — sign-in and cloud storage/sync, and the web version's old address (cms-araullohs.web.app).
• Cloudflare — runs our AI and notification service, including the AI allowance counters (by account, and by a one-way hash of your email address for the Free plan), and keeps the pictures you add as game answers (Cloudflare R2) and, once uploads open, the pictures you add to slides. It also serves the web version (app.classroommadesimple.com): like any website host, it handles your browser's requests to it, including your IP address.
• AI model providers (such as Groq, Cerebras, Google Gemini, Mistral, OpenRouter and Cloudflare Workers AI) — receive the text of an AI request to draft a reply. The App never adds learners' names or LRNs to AI requests by itself, and DepEd Records grades, scores and birthdates are worked out on your device and never sent to an AI service; do not type personal information into AI requests. When you import a lesson plan file the App didn't export, the AI receives the file's text as it is: remove personal information from the file first. To recommend interventions from a student-paced lesson, the AI receives the lesson's questions, their answers and how the class answered, with each learner as a label (S1, S2…), never their name or student ID. Free models may log requests under their own terms.
• Google Gemini (paid service) or Anthropic (Claude) — for CMS Interactive with tokens paid for (CMS Interactive on your plan or your school's, or bought tokens), receives the text of the lesson-plan session (or the sessions chosen) and the pictures you add, to design slides or a game. Neither uses them to train its models. We haven't set these up yet: until we do, all of CMS Interactive's AI goes to the free AI services below.
• Free AI services for CMS Interactive (Google Gemini's free tier, Groq, OpenRouter's free models) — with free tokens (without CMS Interactive, and a free trial's), and with every token until the paid services above are set up, receive the text of the lesson-plan session or sessions, one service after another until one makes it. Free services may keep what they receive and use it to improve their services, under their own terms. Your pictures go only to Gemini's free tier; the others receive only their descriptions. Don't put learners' names or other personal information in lesson plans.
• Resend — delivers payment and Help & Feedback notification emails to us (name, email, mobile number and payment details; or what you wrote in a ticket, with your name, school and App version).
• Your payment provider (GCash, Maya or your bank) processes your payment under its own terms.

6 International transfers

These providers may store or process data outside the Philippines. We choose providers with recognized security practices and remain accountable for data we control (DPA Sec. 21).

7 Security

Data travels encrypted (HTTPS). Server-side access rules let each account reach only its own data (and a school's staff only their school's). A school can also have each teacher reach only their own classes and records (Master turns this on for the school); its head teachers, principals and admins still reach the whole school. A Chat conversation can be read only by the people in it. Installation links, which account holds each mobile number, and suspension notes can be read only by the developer. Plan and payment fields can only be changed by us. Pictures for game answers are the exception to these rules: anyone with a picture's address can see it. What's in the Pisara library can be read by every teacher with an account, once approved; until then only you and we can. No system is perfectly secure: protect your password and devices, and tell us immediately at classroommadesimpleapp@gmail.com if you suspect unauthorized access.

8 How long we keep data

• Learner records stay until you (or your school) delete them, or until your account is deleted. Deleted records can remain in backups for up to 30 days.
• When you ask us to delete your account, we delete its records within 30 days, except what we must keep by law.
• Payment and billing records are kept for as long as Philippine tax and accounting laws require.
• Chat messages and Help & Feedback tickets are kept until your account is deleted (or, for a school account, until the school asks us to delete them). They can't yet be deleted one by one in the App.
• Class game results are kept with the class's records until your account is deleted (or, for a school account, until the school asks us to delete them). They can't yet be deleted one by one in the App. Slides and games are kept until you remove them (a game set) or your account is deleted. A student-paced game, with its scrambled list and answers, is kept until the teacher removes it after it closes; its result stays with the class's records. A learner's student ID stays with their record until the teacher makes a new one.
• A student-paced lesson, with its learners' progress and answers, is kept until the teacher deletes it (or the account is deleted). Its scores in each class's game results, and interventions sent from it, are kept like other class records. The AI server's count of wrong tries for a lesson (with a scrambled network address) is kept for 15 minutes.
• Pictures for game answers are kept until your account is deleted (or, for a school account, until the school asks us to delete them). Removing a picture from a game doesn't delete it yet; ask us at classroommadesimpleapp@gmail.com to delete one sooner. A picture used by several accounts is kept until none of them uses it; one shared to the library is kept while the library may use it. A picture we remove after a complaint is deleted at once; the record that it was removed is kept for as long as the picture service runs.
• What you share to the Pisara library is kept until you or we take it out. Slides that already use it keep their copy.
• A drawing you ask for or send is kept until you or we delete it from the list (or your account is deleted). A drawing added to the App from it stays in the App.
• Installation links and sign-in records are kept while your account exists and are deleted with your account's other records. The installation ID itself stays on your computer or phone until the App's data there is removed. The AI service's email hash and monthly count hold no name or address.
• If your Pro plan ends, your records are not deleted — they remain viewable and exportable on the Free plan.

9 Learners and minors

The App is for teachers and school staff, who must be at least 18. Learners do not use the App, except to join a CMS Interactive game their teacher runs in class: on a phone, tablet or computer, without an account, by typing the game's code and either their student ID and last name or a first name (or, if they don't know their ID, their full name, for the teacher to find them on the class list); or to play a game their teacher assigns until a deadline, the same way. Nothing else is collected from the device, and it keeps only the student ID it was given, so the learner doesn't have to type it again, and for a student-paced game a random key and the answers so far, so they can come back to it (not the last name); or to go through a student-paced lesson their teacher assigns, the same way (the device keeps the learner's first name, a random key and their place for 8 hours). Learner records are entered by teachers under the authority and consent arrangements of their school (for example, at enrollment). Do not record more than what is needed.

10 Your rights

Under DPA Sec. 16–18 you have the right to be informed, to access, to correct, to object, to erasure or blocking, to data portability (you can export your records), and to damages; and you may complain to the National Privacy Commission. For your own account, contact us at classroommadesimpleapp@gmail.com. For learner records in a school account, contact the school's Data Protection Officer — we will assist the school.

11 Personal data breaches

If a breach affecting data we control is likely to cause serious harm, we will notify the National Privacy Commission and affected people within the period required by the DPA and NPC rules (generally 72 hours from knowledge). For school-controlled data, we will notify the school promptly so it can meet its own obligations.

See also the Terms and Conditions. Questions: classroommadesimpleapp@gmail.com