1. Parties and subject matter
- This data processing agreement (the “DPA”) is concluded between the Customer under the Public Offer (the “Controller”) and the owner of the LTime service (the “Processor”) in accordance with parts four and five of article 4 of the Law of Ukraine “On Personal Data Protection” (Закон України «Про захист персональних даних»).
- The Controller instructs the Processor to process the personal data that the Controller and its Users enter into Schools, and the Processor processes it only within the scope and for the purpose defined by this DPA.
- Terms used in this DPA have the meanings given in the Public Offer and the Law of Ukraine “On Personal Data Protection”.
2. Purpose, nature and duration of processing
- Purpose: providing the Controller with access to the Service to organize the learning process — schedules, groups, attendance, learning materials and tests, tuition payments, teacher payroll, enquiries and notifications.
- Nature of processing: storage, organization, display to Users according to the permissions granted to them, backup, sending the notifications the Controller has set up, deletion.
- Records for billing: to issue invoices under the Plan, each School sends the Customer Portal a monthly list of Active Students (identifier, name and number of lessons). The list is needed so that the Controller can check the invoice and is used only for that purpose.
- Duration: while the License for the School is in force and, after it ends, until the data is deleted under section 9 of this DPA.
3. Categories of data subjects and data
| Data subjects | Data the Controller may enter |
|---|---|
| Students, including minors | Full name, phone number, email address, date of birth, profile photo, messenger contacts, groups, schedule, attendance, test results, certificates, invoices and payments, teachers’ notes |
| Teachers and staff | Full name, phone number, email address, profile photo, schedule, pay rates and pay accruals, access permissions |
| People who have submitted an enquiry | Name, contact details, preferred course, convenient days and times, manager’s notes |
| Other Users | Account data and the activity log in the School |
The Service is not intended for special categories of data (about health, ethnic origin, beliefs, biometric data, etc.). The Controller does not enter such data without the data subject’s explicit consent and compliance with the legal requirements for such processing.
4. Obligations of the Controller
- The Controller determines the purpose and scope of the data it enters into a School and warrants that it has a lawful basis for processing the data and transferring it to the Processor.
- For students under 14, the Controller obtains the consent of their parents or other legal representatives; students aged 14–18 give consent themselves unless the law provides otherwise.
- The Controller informs data subjects about the processing of their data in LTime, including the engagement of the Processor, and enters only the data needed for the learning process.
- The Controller grants Users access permissions according to their duties and is responsible for Users’ actions in the School.
- Data subjects’ requests concerning their data are handled by the Controller; it can fulfil most of them itself in the School (view, correct or delete data).
5. Obligations of the Processor
- The Processor processes data only on the Controller’s documented instructions. The instructions are this DPA, the settings and actions of the Controller and Users in the School, and the Controller’s written requests to support.
- The Processor does not use the Schools’ data for its own purposes, marketing or profiling, and does not sell it.
- The Processor ensures confidentiality: only those of the Processor’s personnel who need access to provide the services and who are bound to keep it confidential have access to the data.
- The Processor takes technical and organizational security measures (section 7).
- The Processor helps the Controller fulfil data subjects’ requests, respond to requests from the Ukrainian Parliament Commissioner for Human Rights and carry out risk assessments, to the extent of the information available to the Processor.
- The Processor does not transfer data to third parties, except to subprocessors under section 6 and in cases expressly provided for by law. The Processor notifies the Controller of a request from a public authority concerning School data, unless the law prohibits this.
6. Subprocessors
The Controller gives general authorization to engage the following subprocessors:
| Subprocessor | Function | Place of processing |
|---|---|---|
| Hosting provider | Servers, School databases | Ukraine |
| Google Cloud (Google LLC) | Storage of School files and backups | Google data centers |
| Telegram | Notifications the Controller has enabled for Users through the LTime bot | UAE and others |
- The Processor enters into agreements with subprocessors that ensure data protection no lower than under this DPA and is responsible for their actions as for its own.
- The Processor notifies the Controller of a new subprocessor by email or in the Customer Portal at least 14 days in advance. If the Controller has reasonable objections, it may withdraw from the Agreement before the subprocessor is engaged and receive a refund for the unused License term.
- Services that the Controller connects to a School itself under its own agreements (accepting payments via LiqPay or Stripe, the Checkbox software cash register (PRRO), video services for online lessons, an SMS provider, Google Drive, a custom domain) are not subprocessors of the Processor: data is transferred to them on the Controller’s instructions and under the Controller’s responsibility.
- The AI assistant sends OpenAI the names of the school’s course areas and subjects to check their structure, and the learning text from which a teacher asks it to write questions for an assignment. Students’ data is not sent to OpenAI; the Controller ensures that such text contains no personal data.
7. Security and incidents
- The Processor applies measures including: a separate database for each School; encrypted connections (HTTPS); passwords stored only as a hash; separation of User permissions in the School; server access only for authorized persons with personal keys; regular backups stored separately from the main servers; software updates.
- The Processor notifies the Controller of a security breach that has led to accidental or unlawful destruction, loss, alteration or disclosure of School data, or to unauthorized access to it, without undue delay and no later than 72 hours after becoming aware of it. The notice contains the circumstances known at that time, the likely consequences and the measures taken.
8. International data transfers
School databases are hosted in Ukraine. Files and backups are stored in Google Cloud. Data is transferred to subprocessors outside Ukraine in compliance with article 29 of the Law of Ukraine “On Personal Data Protection” — to states with an adequate level of protection or under agreements that contain standard data protection safeguards.
9. Return and deletion of data
- After the License ends or the Agreement terminates, School data is kept for at least 90 days so that the Controller can resume work or obtain a copy of the data.
- During this period, at the Controller’s request, the Processor provides a copy of the School data in a machine-readable format within 30 days of the request.
- After this period, the Processor may delete the School, warning the Controller by email at least 14 days in advance. At the Controller’s request, the Processor deletes the School earlier.
- Deleted data disappears from backups within their normal rotation cycle. The Processor may keep data longer only where the law requires it and only to the extent necessary for that purpose.
10. Information and audits
At the Controller’s request, the Processor provides the information needed to demonstrate compliance with this DPA: a description of the security measures, the list of subprocessors, information about incidents. On-site audits are possible by prior arrangement, no more than once a year, at the Controller’s expense and without access to other customers’ data.
11. Liability and term
- The parties’ liability under this DPA is governed by the “Liability” section of the Public Offer.
- This DPA remains in force for as long as the Agreement, and with respect to the deletion and confidentiality obligations, until they are fully performed.
- If the terms of this DPA conflict with other parts of the Agreement on matters of personal data processing, this DPA prevails.