Privacy Policy of the “MC Meet” application
Effective date: 18.09.2026
1. General provisions
This Privacy Policy describes what data the MC Meet mobile application (the Application; inside the app itself it is titled “Montessori Meet”) processes, what it is used for, who it is shared with and how it is protected.
The Application is used to take part in online lessons of the Montessori Center school: a teacher runs the lesson and students join it through the teacher's personal link. The Application is not a public social network: it has no user directory, no public rooms and no way to find strangers.
The owner of the Application and the controller of personal data is:
Serhii Nochovkin (sole proprietor), trading as INTERSCHOOL ONLINE.
Contact for data protection matters: interschool@interschool.online.
2. What data the Application processes
2.1. Data provided by the participant
- A name for the lesson — typed on the entry screen and shown to the other participants of the same lesson. It may be a name, a short form or a nickname: the Application neither verifies nor requires real data.
- A Google account — for teachers only. The teacher signs in with the school work account so that the system recognises them as the host of the lesson; the e-mail address of that account is transmitted. Students do not sign in at all: they join through a link.
2.2. Lesson audio and video
During a lesson the Application transmits microphone audio and camera video (if the participant turned the camera on) to the other participants of the same lesson through the school's video server. The transmission is encrypted.
The server does not record the lesson. Audio and video pass through it and are not stored on it.
A recording is only possible on a participant's own device and only if that participant turned it on: the file stays on their device, never reaches us and is not processed by us. Responsibility for such a recording and for the consent of the other participants lies with the person who started it.
2.3. Lesson messages and files
Participants may write in the lesson chat and send files to other participants. Messages and files pass through the video server and are delivered to participants of the same lesson; they are not stored on the server and are not available after the lesson.
2.4. Technical data
- A persistent device marker — a random number created by the Application on first launch and kept on the device. It lets a lesson recognise a participant who comes back (for example after a network drop) and lets the teacher's restrictions work. It is not an advertising identifier: the Application neither requests nor transmits advertising identifiers.
- Device details — model, operating system version, application name and version. Needed to understand on which device a problem occurred.
- Lesson journal on the school server — records of who joined and left and when, whether the microphone and camera were on, how the connection held. Participant names appear in the journal. The journal is kept for 30 days and is cleaned automatically.
- Connection and audio quality data — delays, packet loss, audio route (speaker, headphones, Bluetooth), state of echo processing. Used only to tune lesson quality.
- Crash reports — if the Application crashes, a technical report is sent to Firebase Crashlytics: the place in the code, device model, system version. Such a report contains no lesson content.
2.5. Permissions requested by the Application
| Permission | Why |
|---|---|
| Microphone | to transmit the participant's voice during a lesson |
| Camera | to transmit video if the participant turned the camera on |
| Notifications | to show that a lesson is running while the app is in the background |
| Network and Wi-Fi state | to restore the connection when the phone switches between Wi-Fi and mobile network |
| Bluetooth | to recognise wireless headphones and route the audio to them |
| Background work (lesson service) | so that the lesson is not interrupted when the screen goes off or another app is opened |
The microphone and camera can be switched off at any moment with the buttons inside the lesson; permissions can be revoked in the phone settings.
2.6. Data the Application does NOT process
The Application does not request and does not receive: location, contacts, SMS, call history, photos and files (other than those the participant chose to send during a lesson), the device advertising identifier, biometric data.
The Application has no advertising, no ad networks, no third-party analytics and no behaviour trackers.
3. Purposes of data processing
| Data category | Purpose |
|---|---|
| Name for the lesson | to show the participant to others in the lesson and in the lesson journal |
| Teacher's work account e-mail | to recognise the teacher as the host and grant host rights |
| Audio and video | running the lesson itself |
| Lesson messages and files | exchange between participants of the lesson |
| Persistent device marker | to recognise a returning participant, to enforce the teacher's restrictions |
| Lesson journal, connection and audio data | troubleshooting and tuning connection quality |
| Crash reports | finding and fixing errors in the Application |
The processed data is not used for advertising, behaviour analysis or profiling, and is not shared with third parties for marketing.
4. Third parties involved in processing
- The school's video server — lesson audio, video, messages and files pass through it, and the lesson journal is kept on it. The server belongs to the school and is under its control.
- Google Sign-In — teacher sign-in with a work account. Governed by Google's policy: https://policies.google.com/privacy.
- Firebase Crashlytics — crash reports of the Application. Governed by the Firebase terms: https://firebase.google.com/support/privacy.
- Relay server (TURN) — when a participant's network does not allow a direct connection, audio and video travel through the school's relay in encrypted form. The lesson content is not decrypted or stored there.
No data is shared with any other third party.
5. Data storage
5.1. On the device
- the name used last time and the chosen interface language;
- the persistent device marker (section 2.4).
This data is removed together with the Application or by clearing its data in the phone settings.
5.2. On the school server
- the lesson journal — 30 days, then deleted automatically;
- information about rooms and teachers — in the school's information system, for the period set by the school.
Lesson audio, video, messages and files are not stored on the server.
5.3. Crash reports
Kept in Firebase Crashlytics under Google's terms, normally up to 90 days.
6. Security
- Exchange with the server goes over HTTPS/WSS.
- Audio and video are transmitted over WebRTC with mandatory encryption (DTLS-SRTP).
- A lesson is opened through the teacher's personal link; a room may have a waiting hall, and then the teacher admits participants manually.
- Host rights are granted by the server based on the teacher's work account, not on the client's claim.
7. User rights
A user — or, for a minor, their parent or guardian — may request information about the data processed, its correction or deletion, and may withdraw consent by ceasing to use the Application.
Requests go to interschool@interschool.online and are handled within a reasonable time, normally 30 days. Data related to the educational process is deleted in agreement with the school.
A student has no separate account in the Application: data on the device can be removed by uninstalling the Application or clearing its data in the phone settings.
How to request deletion, and what is deleted versus what stays with the school, is on a separate page: Account and data deletion.
8. Children
The Application is used by children, including those under 13 — they are participants of the school's lessons. We therefore follow these rules.
- Minimum data. All the Application needs from a student is a name for the lesson. No e-mail, phone number, address or date of birth is requested in the Application.
- Legal basis. Children take part in lessons under the school's contract with their parents or guardians; consent to processing a child's data is given by the parent or guardian when that contract is concluded.
- No advertising and no advertising identifiers. The Application has no ads, no ad networks and no device advertising identifier; children's data is not used for profiling or targeting.
- Closed lessons. A lesson can only be entered through the teacher's personal link. There are no public rooms, no user directory, no search and no way to meet strangers.
- An adult runs the lesson. The school's teacher hosts it, sees every participant, and can mute a participant, turn off their camera, remove them from the lesson or end the lesson.
- Messages and files are exchanged only inside a lesson and only between its participants; before the first send the Application shows a reminder about safe communication.
If you believe a child shared data through the Application that should not have been shared, write to us and we will help remove it.
9. Changes to the Policy
This Policy may change. The current version is always available at https://interschool.online/privacy-mc-meet/. Users will be notified through the Application about material changes.
10. Contacts
Serhii Nochovkin (sole proprietor, trading as INTERSCHOOL ONLINE)
E-mail: interschool@interschool.online
Questions about the Application itself: developer@montessori.ua.
