PaideiaPaideia
Terms of UsePrivacy Policy
πŸ‡ΊπŸ‡ΈπŸ‡ΊπŸ‡¦Switch language

Paideia Privacy Policy

1. Platform owner2. What data is processed, and whose3. Purpose and legal grounds4. Who is the controller, who is the processor5. Who data is shared with6. Google user data7. Retention periods8. Data subject rights9. Children and students10. Cookies11. Data security12. Users in the EU/EEA13. Changes to this Policy14. Contact

Personal data processing policy

Paideia Privacy Policy

Effective from November 11, 2026

This Policy explains what personal data Paideia processes, why, on what grounds, and who it may be shared with. It is drafted in line with Ukraine's Law "On Personal Data Protection" and, for users in the EU/EEA, with the requirements of the GDPR (Regulation (EU) 2016/679).

1. Platform owner

Legal nameSole proprietor, Shkrebtii Andrii Volodymyrovych
Tax / registration number3372812256
AddressUkraine, Cherkasy
Email[email protected]

This Policy covers two distinct relationships: the User's and Team's own data (where Paideia is the controller) and Student/Parent data the User enters into the Platform (where Paideia is only a processor acting on the User's instructions, and the User remains the controller). Section 4 below explains this split in detail.

2. What data is processed, and whose

  1. 2.1. User and Team data (owner, admin, accountant, teacher/tutor): name, email, phone, Plan billing identifiers, usage data (event logs, IP address, device type).
  2. 2.2. Student data the User enters into Student records: name, age or date of birth, contact details, attendance, progress, grades, teacher notes, and other learning content.
  3. 2.3. Parent / contact person data: name, phone, email β€” for communication and billing that the User manages.
  4. 2.4. Paideia does not collect this data directly from Students or Parents β€” all of it reaches the Platform through the User.

3. Purpose and legal grounds

  1. 3.1. User and Team data is processed to perform the Agreement (providing access to the Platform, billing the Plan, technical support, security) and, with consent, for marketing messages.
  2. 3.2. Student and Parent data is processed only to the extent needed to operate the Platform (storage, display, backups), on the User's instructions β€” the User alone determines the purpose and lawfulness of such processing.

4. Who is the controller, who is the processor

  1. 4.1. For User and Team data, Paideia is the data controller and independently determines the purpose and means of processing.
  2. 4.2. For Student and Parent data, the User is the controller: the User decides whose data to enter, why, and on what basis, and is responsible for obtaining Parental (legal representative) consent wherever the law requires it. In this relationship Paideia is a processor β€” it stores and technically processes such data only to the extent needed to run the Platform, does not use it for its own purposes, and does not sell or share it with third parties beyond Section 5.
  3. 4.3. If Paideia or the User receives a request from a Student, Parent, or public authority about data the User entered, both parties assist each other in responding, each according to its role under clauses 4.1–4.2.

5. Who data is shared with

  1. 5.1. Data is processed and stored on servers operated by Hetzner Online GmbH in data centers located in the European Union.
  2. 5.2. Plan payments are processed by Plata by mono β€” Paideia does not store full card details.
  3. 5.3. Paideia may use analytics, email/SMS, and technical-support services that get access to data only to the extent needed to provide their service, under a confidentiality agreement.
  4. 5.4. Data is not shared with third parties for their own marketing purposes.
  5. 5.5. If you connect a Google account, data is exchanged with Google as described in Section 6.

6. Google user data

  1. 6.1. Google features in Paideia are optional. Paideia gets access to your Google account data only after you grant it on Google's consent screen, and uses it only for the features below.
  2. 6.2. Sign in with Google (scopes openid, email, profile): your name, email address and profile photo β€” to create your Account and sign you in. The photo is used as your avatar if you haven't uploaded one.
  3. 6.3. Google Calendar (scope calendar.events): for lessons you schedule in Paideia, Paideia creates, updates and deletes events in your Google Calendar with the lesson time, a description, a Google Meet link and your Students' email addresses as guests (Google sends them the invitations). To keep the schedule in sync, Paideia reads changes to your calendar's events: if an event created by Paideia is moved or deleted in Google Calendar, the lesson in Paideia is updated, and guests' replies (yes / no / maybe) are saved as attendance confirmations. Events that Paideia did not create are skipped and not stored.
  4. 6.4. Google Sheets (scope spreadsheets.readonly) is requested separately, only when you choose to import Students from a Google Sheet: Paideia reads the values of the spreadsheet whose link you provide, once per import, to create Student records. Instead of granting this permission, you can share the spreadsheet with the Paideia service address shown on the import screen; Paideia then reads only that spreadsheet. Paideia does not change your spreadsheets and does not open other spreadsheets or files.
  5. 6.5. What is stored: the Google access and refresh tokens (encrypted), the list of permissions you granted, the identifiers of your calendar and of the events Paideia created, and technical synchronization data; guests' replies as lesson attendance; the values read from a spreadsheet as part of the import and the Student records created from them. Paideia does not store the contents of your other calendar events or spreadsheets.
  6. 6.6. On paid Plans a lesson may be hosted in Paideia's own Google Workspace calendar, and you are invited to it as a guest. For such lessons Paideia gets attendance from the Google Meet audit log of its own Workspace domain: participants' email addresses and join and leave times, which are matched to Students by email address.
  7. 6.7. Paideia's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. In particular, Google user data is used only to provide and improve the user-facing features described in this section; it is not sold, not used for advertising (including retargeting, personalized or interest-based ads), and not transferred to third parties except as necessary to provide these features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to you. Paideia staff do not read this data unless you give explicit consent for specific data, it is needed for security purposes (for example, investigating abuse), to comply with applicable law, or the data is aggregated and anonymized for internal operations. Google user data is not used to develop, improve or train generalized artificial intelligence or machine learning models.
  8. 6.8. You can revoke access at any time: disconnect Google in your Paideia profile β€” Paideia then revokes the token at Google and deletes the stored tokens and synchronization data β€” or remove Paideia at https://myaccount.google.com/permissions. Events already created stay in Google Calendar until you delete them. To have other Google-derived data deleted, write to [email protected] or delete your Account (Section 7).

7. Retention periods

  1. 7.1. User and Team data is kept for as long as the Account exists, and for up to 3 years after deletion, to meet accounting and tax-record requirements.
  2. 7.2. Student and Parent data is kept until the User deletes it, or deletes its Account; after Account deletion such data is deleted within 30 days, unless the law requires a different period.

8. Data subject rights

  1. 8.1. The User and Team may learn how their data is processed, access it, request correction, deletion, or restriction of processing, and withdraw consent to marketing messages β€” through the personal dashboard or by contacting [email protected].
  2. 8.2. For Student or Parent data the User entered, requests for access, correction, or deletion should go directly to the User (the tutor or school) who maintains that profile β€” the User is the controller of that data under clause 4.2. Paideia assists with such requests at the technical level.

9. Children and students

  1. 9.1. Students may be minors. Paideia does not register Students as independent Users and does not obtain their consent directly β€” the Student's profile is created and maintained by the User.
  2. 9.2. Responsibility for obtaining Parental (legal representative) consent to enter a Student's data into the Platform rests with the User, per clause 7.2 of the Terms of Use.
  3. 9.3. If a Parent believes their child's data was entered into the Platform without a proper basis, they may contact either the User who maintains the profile or Paideia at [email protected] β€” Paideia will take reasonable steps to review the request and, if warranted, restrict access to the relevant data.

10. Cookies

  1. 10.1. Essential cookies are set without consent because the Platform cannot work without them: the sign-in session (session), device identifier (device_id), interface language (NEXT_LOCALE, locale), the plan picked on the site (PRICING-SHOW), invitation token (invitation_token), and the saved cookie choice (paideia_consent, 6 months).
  2. 10.2. Analytics cookies (Google Analytics: _ga, _ga_*) help us understand how visitors use the site. Marketing cookies (Google Ads: _gcl_*) measure advertising performance. They are set only after your consent (Art. 6(1)(a) GDPR); Google scripts are not loaded before it. Google may process this data outside the EEA under standard contractual clauses.
  3. 10.3. On the first visit the Platform shows a banner where you can accept all cookies, reject the optional ones, or choose categories. Rejecting is as easy as accepting.
  4. 10.4. You can change or withdraw consent at any time via the "Cookie settings" link at the bottom of the site; Google cookies are deleted on withdrawal. The Platform asks again after 6 months or when the list of cookies changes.
  5. 10.5. The User can also manage cookies in their browser settings; disabling essential cookies may limit the Platform's functionality.

11. Data security

  1. 11.1. Paideia applies technical and organizational measures to protect data from loss, unauthorized access, or disclosure, including encrypted connections, role-based access control, and regular backups.
  2. 11.2. In the event of a data breach that creates a risk to data subjects' rights, Paideia will notify the User and, where the law requires it, the competent authority, within the timeframes set by law.

12. Users in the EU/EEA

  1. 12.1. If a User or Student is located in the EU/EEA, processing of their data additionally complies with the GDPR: legal bases under GDPR Article 6, and the right to access, correction, deletion, restriction of processing, data portability, and objection to processing.
  2. 12.2. Data protection contact: [email protected].

13. Changes to this Policy

  1. 13.1. Paideia may update this Policy. A new version takes effect once published on the Platform. Material changes are additionally communicated by email or through the personal dashboard.

14. Contact

Legal nameSole proprietor, Shkrebtii Andrii Volodymyrovych
AddressUkraine, Cherkasy
Data inquiries email[email protected]
Phone+380508482068