Controller and contact
Stowarzyszenie ProHolia, ul. Górna Wilda 88, 61-563 Poznań
The ProHolia Association is the controller of data processed within ProHolia. The role of schools and other participating institutions must be established for each programme.
Data protection requests: kontakt@proholia.pl.
Data protection officer: [name and direct contact details to be confirmed].
Data we process
The website may process technical connection data such as IP addresses and request information. Staff accounts include identity, email, role and information needed to secure sign-in.
The app may hold children's and guardians' details, school and class information, guardian contact details, questionnaire answers, paper consent status and visit schedules. Depending on the examination, it may process vision, hearing, posture and movement results or PROLEXIA and PROFILO results concerning reading and neuropsychological functions. Some information may concern a child's health.
Selected app features allow photos or speech recordings during an examination; Cloudflare Workers AI provides audio transcription. Each child's participation must match the relevant consent form and information given to the parent.
Sign-in security monitoring
Monitoring covers completed explicit staff sign-ins after MFA and grouped failed password and login-MFA attempts in the app. An administrator after MFA can review unfamiliar sign-ins and failed attempts. Monitoring does not trigger automatic blocking or notifications and may have capture gaps.
Events may include staff identity, time, full IP address, country, coarse operating system and browser family, and reasons for unfamiliar context. Failed-attempt groups contain category, count and times, and the submitted email as a claimed target without confirming that an account exists. Older groups may contain a target pseudonym. Passwords, MFA codes and raw form data are not retained. Above the detail limit, only aggregate counts without target or context details are kept.
Unfamiliar sign-ins are retained for 4 calendar years from occurrence; failed-attempt groups for 4 calendar years from the end of their fixed hourly bucket. Familiar contexts expire after 180 days without use; learning dates span 14 local dates in Europe/Warsaw. Minimal profile initialization information remains until account deletion. Login deduplication data expires after 24 hours. The pending-login cookie expires after 30 minutes and its expiry hint after at most 24 hours. Cleanup diagnostics contain only operational data and are limited to 7 days.
Expired events immediately become invisible; hourly deletion has an execution budget of up to 30 seconds. Backlogs require operator intervention. Separate restricted monitoring recovery copies have a maximum lifetime of 30 days and may contain data that expires in the live system during that window. All overdue data is removed using its original deadline before restored access. This notice, processing locations and backup segregation and retention require approval before monitoring real data.
Purposes and legal bases
The screening programme aims at secondary prevention (phase II). Data is used to run accounts and access controls, organise visits, deliver questionnaires, record consent status, conduct and record screenings, and protect the service. The Article 6 GDPR basis and the additional Article 9 condition for health data must be determined for each programme and communicated to participants in its notice.
The cookies policy describes necessary browser storage.
Sources and recipients
Data may come from staff, a school, a parent or guardian, or be created during a screening. App access is limited by role, project and specialist assignment.
Infrastructure and service providers, particularly Cloudflare and Supabase, may process data as needed to operate the app. Authorised programme organisers and parties entitled by law or programme arrangements may receive data.
Retention and international transfers
The intended retention period is four years from the examination date for screening data, four years from account closure for staff accounts, and four years from the event date for logs. Voice recordings have a separate deadline of up to 14 days. Examination audit events currently have a five-year deadline; this period and deletion mechanisms need to be reconciled before publication.
The controller intends to keep all data within the European Economic Area. [Actual processing locations, Cloudflare and Supabase settings, provider access and processing agreements must be verified before publication.]
Working examination drafts may be stored temporarily in the browser on the device in use. Removing them from the device does not necessarily delete data already saved in the system.
Your rights
See “GDPR and your rights” for access, correction, erasure, restriction, objection, portability, consent withdrawal and UODO complaints.