Privacy policy

Purposes and legal bases of processing

We process data to operate accounts, conduct educational conversations, protect the system against abuse, assess the use of public pages and fulfill user rights.

Information about the legal bases for processing is currently unavailable. Please contact the portal administrator or the data protection officer about this.

Acknowledging this policy does not constitute blanket consent to all processing purposes. If the controller bases a specific purpose on consent, it specifies that purpose separately, together with the option to withdraw consent.

Account and conversation data

The account contains an email address or alias, a password hash, age, optional first and last name, role, document acceptance dates, and the tutorial completion setting and version. For a child, we store an alias, age, the link to a guardian and the guardian's confirmation. 2FA secrets are encrypted. Chat history includes questions, answers and cited sources. Do not enter personal or medical data, or information about third parties, in the chat.

The security log may contain the account ID, its email or alias, IP address, browser information (user-agent), time, type of action and the ID of the object the action concerns. Sign-in attempts are recorded separately, together with the entered email or alias and the result of the attempt. These logs do not store password or 2FA code field values or session tokens. Enter your password only in the password field, never as a login or in a report description.

The log is accessible to authorised administrators with mandatory two-factor sign-in. An administrator viewing a conversation is recorded; viewing it without automatic masking of detected personal data also requires a justification. Do not enter third parties’ data in such a justification. Activity details for child accounts are limited, but the account identifier and technical data may still be personal data. Conversation history is stored separately.

The public visitor counter keeps short-lived hashes of random session identifiers and their expiry time in server memory, by default after 5 minutes of inactivity. This counter does not store IP addresses, account identifiers or browsing history. Hidden tabs do not renew activity. The visitor count is an approximation of the number of people, as one person may open several tabs.

Recipients and third-party services

The Administrator determines the hosting operator, the entities maintaining the system and the terms of data processing entrustment. A local model processes content on the Administrator’s configured infrastructure; we do not determine the server’s location based on the domain.

Answers may be generated using third-party AI services. Answers use an external AI service. Your question, conversation context and relevant material extracts are sent to that service. Do not enter personal data. A short notice is always visible above the chat before you send a question; details can be expanded without interrupting the conversation. We do not require you to confirm it again. This is information about processing, not a request for consent or a standalone legal basis. Your question, earlier context and document excerpts may be passed to approved providers, including a fallback provider. Children's profiles use local models only.

The optional password security check with Have I Been Pwned sends the first five characters of the SHA-1 hash; it does not send the password or the full hash. Sentry diagnostics are disabled by default; enabling them requires an administrator's assessment.

Microphone and read-aloud

Browser speech recognition may use its provider’s services and send the recording outside the administrator’s infrastructure. It must be deliberately enabled; the microphone is disabled for children’s accounts. The backend receives the recognised text. Read-aloud with the app’s voice runs on the server; other voices depend on the browser provider.

Retention

We store messages for 12 months, and audit logs and login attempt logs for 90 days. A daily task removes older entries and empty, inactive conversations. Account data remains until the account is deleted. Backups and infrastructure logs are kept according to the Administrator’s separate schedule.

In the section Talk you can delete a selected conversation or your entire history. An authorised administrator can delete a specified conversation in the panel. Deletion covers messages in the active database, while a record that the operation was performed remains in the security log for the period stated above. Backups are deleted according to a separate schedule; when restoring, previously completed deletion requests must be taken into account.

Deleting an account erases conversations and login attempts and removes direct identifiers from the remaining audit events. Deleting a guardian account requires explicit confirmation and includes linked child accounts. Data can be exported before deletion; a change of guardian must be arranged with the administrator. Remaining security events are subject to the retention described above.

Visits and active accounts

On public pages we count full page loads. We take information about the browser and referring page from the request headers, convert it into general categories and store it as separate daily counters: pages, browser families, operating systems, device types and traffic sources. In these statistics we do not store IP addresses, full headers, URL parameters, account identifiers or the history of any individual visitor. We do not add cookies or browser identifiers to collect these page views. The statistics are available to the administrator and kept for up to 90 days.

For signed-in accounts, we record the time of last activity. An open, visible tab periodically confirms presence; a hidden tab does not send these confirmations. An authorised administrator can view the account name or nickname, role, last activity and sign-in time to oversee portal use. The list requires a valid session and recent activity. Viewing the list is recorded in the security audit; it does not include conversation content or browsing history.

Infrastructure logs and security events may contain IP addresses and request data. They are processed separately from aggregate statistics. The administrator determines the purpose, legal basis and retention of these logs and backups for the specific deployment.

Children

Self-registration requires stating your age and being at least 16. A child’s account is created by a verified adult guardian or an authorised administrator after confirming authority and consent. Ticking a box on the form does not replace the guardian verification procedure, which is organized by the deployment administrator.

Classroom and Janek’s Missions

These sections are available after signing in. The educator can show them to a group without creating separate accounts for children. Task answers, the selected stage and mission completion are stored only in the memory of the open page and are not sent to the server or to AI services. We do not collect children's names, grades, health information or type of disability. Janek's hints in Classroom are prepared task content, not a conversation with an AI model.

In the browser's local storage, we save only the selected mission view, larger text, and skipping or closing the tutorial. These settings are not linked to an account; on a shared device, they may be shared by subsequent users. They can be removed by clearing site data. Access is subject to the standard infrastructure logs and signed-in account presence confirmations described above.

The facilitator can open a separate chat. In that case, the conversation processing rules described in this policy apply. Children's data must not be entered in the chat or in reports. Links to PSP pages, videos and other sources open external websites that apply their own privacy policies.

Games and progress

Some games save your score, task completion or tasks to repeat in this browser. In the Academy and four guide exercises, saved data is linked to the account ID. This data is not sent to the server or to AI services and does not create a public leaderboard. Settings and local progress can be removed by clearing site data. Deleting a conversation does not delete these records.

User rights

Within the limits of the GDPR, you have the right of access, rectification, erasure, restriction of processing, data portability, objection and withdrawal of consent where consent is the basis for processing. In account profile you can export your data from the server and the data of children linked to your account, and delete your account after confirming with your password and 2FA code, if enabled. Account deletion and export do not cover local game results and settings on your devices; remove them by clearing site data in your browser. Send other requests and questions to the administrator contact given above. You can lodge a complaint with the President of UODO (the Polish data protection authority): uodo.gov.pl.

Automated decisions and browser storage

The assistant supports education. It does not make decisions about the user that produce legal effects within the meaning of Art. 22 GDPR. We do not profile conversations for advertising. Details of the necessary session cookie and local settings are described in cookie policy.