Privacy policy

The short, human version

• At home we know only this about the child: a name or a nickname, the exercise settings and what the child has done.
• A class is just a name and a number of pupils to us — you do not enter a list of names into it. If you send homework home, the child writes their name or nickname only when they open it, and that name is saved with the result. Feel free to use nicknames.
• We collect no diagnoses and no health data. Never.
• Children do not message each other in Paidoria. There is no chat, no public profiles and no strangers.
• The data from the app is stored in the European Union. If you allow measurement cookies on the website, data about your visit to the website and about sign-up and payment in the app may also go to the USA.

The rest of the page says the same thing, only precisely and in legal terms.

1. Who we are

The controller is Vyskilluj s. r. o., Ulica Veterná 8760/43, 917 01 Trnava, Company ID 53388178, Tax ID 2121360032, registered in the Commercial Register of the District Court Trnava, Section Sro, Insert No. 47906/T. We run the https://www.paidoria.com website and the Paidoria children's app at https://app.paidoria.com.

We have not appointed a data protection officer. In matters of personal data protection, contact us at info@paidoria.com.

2. The account is created by an adult, not by a child

A Paidoria account is created by an adult — a parent or a teacher. A child does not create an account, does not enter an e-mail address or a password and never registers anywhere. The parent creates the profiles of their children, the teacher creates classes.

The child enters the app through the adult’s account or — in the case of school homework — through a link the teacher gives them. The adult who created the children’s profiles is responsible for them and for the data entered into them.

E-mails about the account. To the e-mail address of the account we send the messages needed to run it: an e-mail to confirm the address at sign-up, a link to set a new password when you ask for one, and a confirmation when the e-mail address is changed. If you order a subscription, we also send the confirmation of the contract to it, and if you withdraw from the contract, the acknowledgement of receipt of the withdrawal. They come from noreply@paidoria.com and are written in the language of the account; the confirmation of the contract is in the language in which you placed the order, and the acknowledgement of a withdrawal in the language in which you submitted it.

Voluntary questionnaire. After you sign in, we may ask you a few short optional questions in the app: how you heard about Paidoria, what you expect from it and, if you are a teacher, which grades you teach, in what role, and when and on which devices you use Paidoria; optionally also how you would like us to address you. You can skip any question, and skipping has no effect on your use of the app. We process the answers on the basis of our legitimate interest (Art. 6(1)(f) GDPR) in improving the service and understanding where our users come from. We evaluate them in aggregate – we work with counts of answers, not with names or e-mail addresses; with a small number of answers, however, it cannot be ruled out that an individual answer could be attributed to a particular account. The form of address is used only to address you. The answers are stored with your account for as long as the account exists – you can change or delete them in the app at any time (Account → Questionnaire), and they are deleted when the account is deleted. If an answer cannot be sent straight away (for example without an internet connection), it stays temporarily stored in the browser of your device and is removed from it once it has been sent. You may object to this processing at any time. After submitting its registration request, a school may voluntarily tell us how it heard about Paidoria; that answer is kept together with the request and for as long as the request itself.

3. What data we process for home use

• Parent: e-mail address and password (stored in a form from which the original password cannot be read), the language of the account (Slovak, English or Polish — the language in which the app is shown and e-mails are sent to you), a record that at sign-up you confirmed the general terms and conditions and this policy (together with their version) and that you are over 18, and technical records of sign-ins.
• Child profile: a name or a nickname and the exercise settings — the chosen exercises, the length of an exercise and filters such as “no jumping” or “no floor exercises”.
• Progress in the app: what the child has done and the state of their Buddy. It only serves to run the app, we do not pass it on anywhere.
• Activity rating: after a story or a mini-game the child or the parent may optionally give stars and write what they liked and an idea for another topic. We store the rating with the account and the child profile and use it only to improve the content; the legal basis is our legitimate interest, and the rating is deleted when the account is deleted.
• Payment: payment details are processed by Stripe. The card number never reaches us — we see the status of the subscription and the billing details needed for the receipt: the name and billing address you give when paying. They are required when paying — without them the payment step cannot be completed.

Subscription order and withdrawal from the contract. When you order a subscription, we keep a record of the conclusion of the contract: when it was concluded, for how many children and at what monthly price, whether and until when the free trial runs, and that you expressly consented to the service starting before the withdrawal period expires and were informed of the consequences (time of the consent, version of the terms, wording and language). A record of this consent is also stored with the subscription at Stripe. We send the confirmation of the contract to the address of the account. If you withdraw from the contract through the function in the app, we process the first name and surname you enter, the e-mail address of the account, the identification of the contract, the wording of the statement and the date and time it was submitted, and we send you an acknowledgement of receipt. With the statement we also store details of the subscription at the time of the withdrawal: the number of children, the monthly price, whether the free trial was still running, how much you had paid and how much we are to refund, and the identifiers of the subscription and of the customer at Stripe. Our team receives a notice of the withdrawal without your name and address, so that it can refund your payments. The time of the withdrawal and the identification of the contract are also recorded with the subscription at Stripe; should the statement fail to be stored in our database, the name you entered is temporarily recorded there too — until we have stored the statement with us; we then delete the name from Stripe. We keep a short technical record that these e-mails were sent (time, kind of e-mail, result and, where there is one, an error code), without the address and without the content of the message. The legal basis is the performance of the contract and compliance with our legal obligations for distance contracts; for the technical record of sent e-mails it is our legitimate interest in being able to show that an e-mail was sent and in protecting the mailbox against overload.

One free trial only. The free trial is available to each customer only once. So that it cannot be obtained again by deleting the account and signing up anew with the same address or a variant of it, when a subscription is running — and when an account that had a subscription is deleted — we store a fingerprint of your e-mail address: a string calculated with a secret key (HMAC-SHA256) from the address in a unified form (lower case, without the part after the “+” sign and, for Gmail addresses, without dots). Addresses that differ only in these ways therefore have the same fingerprint. The address cannot be recovered from the fingerprint and the secret key is not stored in the database; with the fingerprint we store only the time when we last saw a running subscription for it or the deletion of an account that had one — no account, no name and no data about a child. At a new order we calculate the fingerprint of the address again and compare it; if we already hold it, we do not accept the order with the free trial, and the order summary then shows, before you submit it again, that payment is due at once. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in preventing the free trial from being used repeatedly; it interferes with your rights only slightly, because we do not use the fingerprint for anything else, do not disclose it to anyone, and without the secret key no address can be recovered from it or checked against it. We keep the fingerprint for 12 months from the moment we last saw a running subscription for it, or from the deletion of an account that had a subscription; then we delete it automatically. If you believe we refused you the free trial wrongly (for example because someone else used an address with the same fingerprint), write to us. You may object to this processing.

We collect no diagnoses and no other health data. The app works exclusively with non-medical settings and exercise filters. Please do not enter a child’s health data into a profile or into the messages you send us.

4. What data we process for school use

• Teacher: e-mail address, password, the language of the account, the school they belong to and the school registration code they used to join it at sign-up. As with a parent, we keep a record of the confirmation of the terms and of this policy at sign-up.
• Class: the name the teacher chooses (for example “3.A”) and the number of pupils. No list of names is entered.
• Homework sent by link: the name or nickname the child enters when opening the homework, the class and the result of the homework. Feel free to use nicknames.
• Activity rating: at the end of the homework the child may optionally give stars and write what they liked and an idea for another topic. Only we receive the rating and we use it to improve the content — the teacher does not see it. With it we store which task it was and the time; we do not store the child’s name with it, so please make sure the child does not write it in the text. Paidoria is the controller and the legal basis is our legitimate interest in improving the content; you may object to this processing.
• Class activity in a lesson: when a class finishes a story, Flip Cards or an Adventure Quest in a lesson, we store with the class and the teacher’s account the kind of activity, which content it was, the number of exercises and the exercise time. The record contains no data about pupils. We use it for statistics on how schools use Paidoria; Paidoria is the controller and the legal basis is our legitimate interest.
• Summary counts from homework: from submitted homework we compute summary counts without pupils’ names — the number of submissions, cards completed, questions and correct answers and the time of the last activity per school, per teacher and per task. They give the school an overview and serve our statistics on how schools use Paidoria and what content to create next; for our own statistics Paidoria is the controller and the legal basis is our legitimate interest.
• Supervision of teachers’ content: Paidoria’s administrator can view the tasks and card sets a teacher creates — seeing with them the teacher’s name and e-mail address and the school. We can remove content that breaks the law or the terms and conditions and block the teacher from creating further content; we then store the time of and the reason for the block. We do this to protect children and the service — on the school’s instruction under the agreement and on the basis of our legitimate interest; the administrator does not see pupils’ results in the app.

For school use the purpose and the means of processing pupils’ data are determined by the school — the school is the controller and Paidoria acts as the processor, processing the data on its instructions. This covers task results (name or nickname, class and result), classes, and the tasks teachers create. The terms are set out in the Data processing agreement under Article 28 GDPR, which the school concludes electronically — at school registration or through a confirmation link; its annex also lists the providers we use for this. For the teacher’s account, the school registration request, protection against misuse, statistics (including the summary counts from homework without pupils’ names) and the activity rating, Paidoria is the controller. We still recommend using nicknames in homework.

Record of acceptance of the data processing agreement. When you accept the agreement on behalf of a school, we store the name and address of the school, the version identifier of the agreement, the date and time of acceptance, the name and position of the person who accepted it on behalf of the school, the way it was accepted (at school registration or through a confirmation link) and the language in which it was displayed. We do not store an IP address or any device data. For this record Paidoria is the controller; the legal basis is our legitimate interest in being able to show that the agreement was concluded and who accepted it for the school. We keep the record for the duration of the cooperation with the school and for three years after it ends; if we do not approve the school’s request, we delete the record together with it.

School registration request. When you register a school on the school registration page, we process the name, position, e-mail address and phone number of the contact person, the school, the number of teachers and pupils, an optional note and the language in which you filled in the form (we send you the e-mail with the registration codes in that language). We use the data only to assess the request, set up the school account and issue registration codes for teachers, and only the Paidoria team can see it. For the request, Paidoria is the controller; the legal basis is our legitimate interest in handling the request and reaching an agreement with the school. We delete a rejected request after 90 days and keep an approved one for the whole duration of our cooperation with the school.

E-mail with registration codes. Once a request is approved, we send the registration codes for teachers by e-mail to the address of the contact person. When the app sends them, it keeps a short record of it — the time, the request it belongs to, the number of codes, the result of sending and, where there is one, a technical error code. The record contains neither the recipient’s address nor the codes themselves. It serves us as proof that the e-mail was sent and protects the mailbox against overload; the legal basis is our legitimate interest in being able to show that the codes were sent. We delete the records after 90 days; a note of when and how many codes we sent stays with the request.

Protecting registration codes against guessing. A teacher signs up with a code their school has received. So that codes cannot be tried at random, we record attempts to check and to redeem them: the time, the kind of attempt and whether it succeeded; for a check of the code before sign-up also the IP address (for an IPv6 address only its network part), and for redeeming a code the identifier of the account. The code itself is never stored in the record. We count failed attempts towards limits — once a limit is exceeded, we refuse further attempts for a while. For this processing, Paidoria is the controller; the legal basis is our legitimate interest in protecting teacher sign-up against misuse. We delete the records after 7 days.

5. Camera and reading aloud

The counting of repetitions through the camera is switched off — we are still preparing it. The app does not use the camera today and does not ask for access to it.

If it is switched on in the future, the camera image will be processed directly on the child’s device, nothing will be sent anywhere and no video or photographs will be stored.

Reading aloud. When the app reads a text aloud (for example a card or an exercise instruction for which we have no recording), it uses the voice of your device or browser: it prefers a voice produced on the device itself, but where there is none for the language, some browsers send the text being read, together with the IP address of the device, to their maker’s servers.

6. Contact form

From the form on the Contact page we process the name, the e-mail address, the chosen role, optionally the name of a school or organisation, optionally a phone number, and the text of the message. To protect the form against misuse we also store a shortened technical fingerprint (hash) of the IP address — we do not store the full IP address. When you open the Contact page, the Cloudflare Turnstile service also loads and checks that the form is not being filled in by an automated program. For this it processes the IP address and technical data about the browser and device; Cloudflare uses them to recognise robots and to improve this protection. The legal basis is our legitimate interest in protecting the form against spam.

The legal basis is our legitimate interest in answering a message we receive and keeping a record of it. We keep messages for 12 months from the last communication, then we delete them.

Reporting a problem from the app. If you use “Found a bug? Let us know.” in the app, we process the text of the message, the e-mail address and identifier of your account, the type of device and browser, the app version and the latest technical errors of the app on your device. The message is stored in the same way as a message from the contact form, with the same legal basis and the same retention period.

7. Legal bases for processing

• Performance of a contract — running the account (including its language, the record of the terms confirmed at sign-up and the e-mails needed to run it — confirmation of the e-mail address, a new password, a change of e-mail address), providing the app and the subscription, including the record of the conclusion of the contract and handling a withdrawal from the contract.
• Legal obligation — accounting and tax documents; for the subscription, the confirmation of the contract, the record of a withdrawal from the contract and the acknowledgement of its receipt (consumer protection law).
• Legitimate interest — answering messages, handling school registration requests (including the record of registration codes sent by e-mail), the security and reliability of the service (including app error records), statistics on the use of the service (account visit history, the records of class activity in lessons and the summary counts from school homework without pupils’ names), improving the content on the basis of the optional activity ratings, supervision of content created by teachers, evaluation of the answers from the voluntary questionnaire, the record of e-mails sent about the subscription, showing the order, the consent given when ordering, a withdrawal from the contract and the refund of payments (including our defence in a possible dispute), showing that a school has concluded the data processing agreement, and protection against misuse (including the records of attempts to check or redeem a school registration code and the fingerprint of the e-mail address that prevents the free trial from being used repeatedly).
• Consent — pseudonymous analytics of app usage (you give this consent in the app) and the statistical and marketing tools on the website, including the measurement of sign-up and payment in the app (you give this consent in the cookie bar on the website, separately for statistical and for marketing cookies; the app does not ask for it again). You can withdraw your consent at any time: for analytics, in the app settings — the withdrawal applies to all your devices; for cookies, in the footer of the website (Privacy settings) — that choice applies to the browser in which you made it.
• Instructions of the controller — for school use we process pupils’ data for the school under the data processing agreement.

8. Who we share the data with

• Supabase — database and sign-in. The data is stored in the European Union region.
• Stripe — payment processing and subscription management. A record of the consent given when ordering and of any withdrawal from the contract is also stored with the subscription.
• Cloudflare — hosting of the website and the app, delivery of files and protection of sign-in and of the contact form against bots (Turnstile).
• Websupport — a Slovak hosting company that runs our e-mail mailboxes. Through its mail server we send the e-mails from the app (confirmation of the e-mail address, a new password, a change of e-mail address, registration codes for schools, the confirmation of the subscription contract and the acknowledgement of receipt of a withdrawal from the contract). A mailbox it hosts also receives e-mails with the content of messages from the contact form and of problem reports, with the contact details from school registration requests, and notices of withdrawals from the contract (without the parent’s name and address).
• Accounting — the accountant who keeps our books and has access to the accounting documents.
• Google Ireland Limited (Google Analytics 4) and Meta Platforms Ireland Limited (Meta Pixel) — they only load after your consent. Without consent they do not start. On the website they receive data about your visit; in the app they load only after a parent signs up and after a subscription order is completed, and they receive the information that a sign-up or a purchase took place.

We do not sell personal data. We do not provide it for anyone else’s marketing — the single exception is the Meta Pixel: if you allow marketing cookies on the website, Meta receives data about your visit to the website and the information about a sign-up and a subscription order in the app, and also processes it for its own purposes. We hand data over to public authorities only where the law requires us to.

For the Meta Pixel we are joint controllers with Meta Platforms Ireland Limited under Article 26 GDPR, for the collection of data about your visit to the website and about a sign-up and a subscription order in the app, and its transmission to Meta. Everything Meta does with the data afterwards it does as a separate controller under its own policy. You can exercise your rights with us and also directly with Meta.

9. Cookies and measurement

We need essential cookies to run the site and to remember your choice. We only switch on statistical and marketing cookies with your consent — it is given separately for each category and refusing is just as easy as agreeing. The details, including the list of cookies, are in the Cookie policy.

Measuring sign-up and payment in the app. Your choice in the cookie bar on the website also applies to the app — the app does not ask again and reads the choice from a cookie that the website sets for the whole paidoria.com domain. If you allowed statistical cookies, the app loads Google Analytics 4 right after a parent signs up and after a subscription order is completed on the payment page; if you allowed marketing cookies, it loads Meta Pixel. The tool receives the information that a sign-up or a purchase took place (for a purchase, also the price of the subscription), together with the technical data it also receives when you visit the website (an identifier from cookies, the page address, the IP address and data about the browser and device). Within a few seconds of sending that information, the app switches the tool off again; until then Google Analytics may also record further data about your visit to the app (for example a move to another screen). At no other time do the Google and Meta tools load in the app — neither when it starts, nor while you browse it, nor during play — and without your consent they never load. This tells us which sources of visits and which adverts lead to sign-ups and subscriptions.

Measurement in the app without consent. In the app we anonymously count how many times a story is started and finished and in which part playback ends. The record contains only the story, the day and the place where it ended — no data about the child, the parent or the device, and it cannot be linked to a specific person. It is therefore not personal data, and nothing is stored on your device. We use it only to improve the content. More detailed analytics in the app is switched on only with your consent.

Account visit history. For every account — parent and teacher alike — we record on which days it was active in the app. Only the date is stored with the account — no time, no content and no data about the child. From these days we calculate how often users come back (a streak of days, the average number of visits per week); we use this for statistics on the use of the service and for support when you write to us. It is recorded even without consent to analytics — the legal basis is our legitimate interest in improving the service. You can object to this processing. The records are deleted automatically after 400 days.

App error records. When the app runs into a technical error, we store a short record of it: the error text, the place in the app, the type of device and browser and the app version. For a signed-in user, the record also contains a pseudonymous identifier of the child profile — not a name or an e-mail. The record does not contain the content of forms or the child’s answers. It serves only to fix errors; the legal basis is our legitimate interest in the reliable operation of the service.

Protecting sign-in against bots. When you sign in, register (including the check of a school registration code), reset your password or change or delete your account, we use the Cloudflare Turnstile service to check that the form is not being filled in by an automated program. Turnstile processes your IP address and technical data about your browser and device for this; Cloudflare uses them to recognise robots and to improve this protection. The legal basis is our legitimate interest in protecting accounts against misuse, such as password guessing. Children opening a task sent by link do not go through this check.

You can change your cookie choice at any time with the Privacy settings button in the footer of every page; the change also applies to measurement in the app.

10. Data transfers outside the EU

The data from the app and from the website is stored in the European Union (Supabase, EU region — a data centre in Frankfurt am Main; Cloudflare hosting). Supabase is established in Singapore and Cloudflare in the USA; Cloudflare delivers the website and the app through a worldwide network and may also process operational data (such as IP addresses) in the USA. Stripe, Google, Meta and Cloudflare may transfer part of the data to servers in the USA — such a transfer relies on the adequacy decision of the European Commission (EU–U.S. Data Privacy Framework) and on standard contractual clauses; for Supabase, on standard contractual clauses. Data is transferred to Google and Meta only if you have allowed statistical or marketing cookies on the website; the transfer then also covers the data about a sign-up and a subscription order in the app.

11. How long we keep the data

• The account and the children’s profiles — for as long as the account exists. Once it is cancelled we delete the data; the exceptions are the statements of withdrawal from the contract, the fingerprint of the e-mail address and the accounting documents with their billing details listed below.
• Answers from the voluntary questionnaire — for as long as the account exists or until you delete them; a school’s answer for as long as its request.
• School classes — until the teacher or the school deletes them, or for as long as the school’s access lasts.
• Records of class activity in lessons (class, teacher, kind of activity, content, number of exercises and time — without data about pupils) — 3 years, then they are deleted automatically; they disappear earlier when the class is deleted or the teacher’s account is cancelled.
• Pupils’ submitted homework (name or nickname, class and result) — 13 months from submission, then it is deleted automatically. The teacher can delete it earlier.
• Activity ratings from homework sent by link — 400 days, then they are deleted automatically.
• Account visit history (on which days the account was active) — 400 days, then it is deleted automatically.
• School registration requests — rejected ones for 90 days after rejection; approved ones for the whole duration of our cooperation with the school, because the teachers’ registration codes are linked to them.
• The record of acceptance of the data processing agreement (school, version, time, name and position of the person, way of acceptance and language) — for the duration of the cooperation with the school and three years after it ends; for a request that is not approved, it is deleted together with the request.
• Records of registration codes sent to a school by e-mail (without the recipient’s address and without the codes) — 90 days, then they are deleted automatically.
• Records of attempts to check or redeem a school registration code (time, IP address or account and result — without the code itself) — 7 days, then they are deleted automatically.
• Messages from the contact form — 12 months from the last communication.
• App error records and app analytics — at most 400 days, then they are deleted automatically. Anonymous story start counts are not personal data.
• The record of the conclusion of the subscription contract (including whether and when the confirmation e-mail was sent) — for as long as the account exists. The record of the consent given when ordering and of any withdrawal (its time and the identification of the contract) stays with the subscription record at Stripe for as long as Stripe keeps it together with the payment data (which is kept for the period required by tax and accounting rules). Legal basis: performance of the contract; for the record of the consent also our legitimate interest in being able to show that we informed you before the order and that you gave the consent — under consumer protection law the burden of proving this is on us.
• Statements of withdrawal from the contract (first name and surname, e-mail address, identification of the contract, wording and time of submission) — 3 years from the withdrawal, then they are deleted automatically. We keep them even after the account is cancelled, so that we can show the withdrawal and the refund of payments. They include the details of the subscription at the time of the withdrawal (number of children, price, amounts paid and to be refunded). Legal basis: the legal obligation to accept the withdrawal, acknowledge its receipt and refund the payments (consumer protection law) and, once it has been handled, our legitimate interest in being able to show the withdrawal and the refund and to defend ourselves in a possible dispute — hence 3 years, the general limitation period under Section 101 of the Slovak Civil Code.
• Notices of withdrawals from the contract in our team’s mailbox (without name and address: the identification of the contract, identifiers at Stripe and amounts) — no longer than 3 years from the withdrawal. Legal basis: the legal obligation to refund the payments within 14 days and our legitimate interest in being able to show that we did.
• Records of e-mails sent about the subscription (without the recipient’s address and without the content) — 90 days, then they are deleted automatically. Legal basis: our legitimate interest in the reliable delivery of the confirmations required by law.
• The fingerprint of the e-mail address (one free trial only) — 12 months from the moment we last saw a running subscription for it, or from the cancellation of an account that had a subscription; then it is deleted automatically.
• Accounting documents and their billing details (name and billing address) — for the period required by tax and accounting rules.

12. Your rights

You have the right of access to your data, to have it corrected and erased, to restriction of processing, to portability, the right to object to processing based on legitimate interest and the right to withdraw a consent you have given at any time.

Just write to info@paidoria.com. If it concerns data from a school environment, turn to the school first — it is the controller and we act on its instructions.

If you believe we are handling your data incorrectly, you can lodge a complaint with the supervisory authority: the Office for Personal Data Protection of the Slovak Republic, Hraničná 12, 820 07 Bratislava, dataprotection.gov.sk.

13. Changes to this policy

We may update this policy when the app or the law changes. The current version is always at this address and we will point out any material change in the app or by e-mail.

Effective from: 7 October 2026