Privacy Policy
This policy describes which data SchulSaniApp processes, why it does so, how long it keeps it, and what rights you have. Last updated: August 2026.
1. Controller and contact
SchulSaniApp is operated by Viktor Gnjatic, reachable at info@schulsaniapp.com. Privacy requests go to the same address.
2. Who is the data controller?
When a school uses the app for its first-aid service, the school is the controller within the meaning of Art. 4 No. 7 GDPR. The operator of the software acts as a processor under Art. 28 GDPR. A data processing agreement between school and operator defines which data is processed, for which purpose, and for how long. For the hosted model the operator provides the full agreement; for self-hosting a separate agreement limited to push processing.
3. Which data is processed
- Account data: first and last name, email address, username, role in the service, phone number (optional).
- Duty and planning data: duty status, shifts and memberships, leave requests, missions (time, place, priority, status), news.
- Incident reports: details about the affected person, type and course of care, vital signs, measures taken, outcome — including health data within the meaning of Art. 9 GDPR. This content is end-to-end encrypted (§ 5).
- Notifications: in-app messages and device tokens for push notifications (§ 6).
- Logs: who changed which role, name or sign-in method when, and who viewed which incident report.
There are no analytics or advertising trackers. No data is shared with advertising networks.
4. Purposes and legal bases
The data is used solely to operate the app for the school: alerting first responders, documenting incidents, duty planning, leave management, and accountability for access. The legal basis is the contract with the school (Art. 6(1)(b) GDPR) together with the processing agreement; for health data, Art. 9(2)(h) GDPR (healthcare) applies within the school's first-aid organization.
5. End-to-end encryption
All health-related content of incident reports is encrypted on the responders' device before it reaches the server. The server stores only ciphertext and can technically never read the content in plain text. Decryption happens exclusively on the devices of the school's authorized users. The school-wide data key is wrapped individually for each recipient; without a grant, nothing can be decrypted.
6. Push notifications
Alerts are delivered through Apple's and Google's central push services (APNs and FCM) and the web push standard. The delivered messages deliberately contain no personal data: only a neutral notice ("New message") and technical identifiers. The app loads the content only after the user taps the notification, from the encrypted API. Device tokens are tied to the account and school and are removed on sign-out or account deletion.
7. Retention and deletion
The school decides when it receives its submitted incident reports: every six months, yearly, or after five years, each time as a PDF bundle. After the confirmed download, the exported reports are deleted from the server. Drafts that were never submitted are removed automatically once their deadline passes. Access and change logs are deleted after twelve months; older mission activity is anonymized. Users can delete their own account in the app; this removes their personal data and anonymizes the link to their entries, so the school's reports remain intact.
8. Your rights
You have the GDPR rights: access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). Contact info@schulsaniapp.com. Because the school is the controller, we forward requests concerning incident data to the school or support it in responding. You also have the right to lodge a complaint with a supervisory authority.
9. Security
Connections are encrypted only (TLS). Servers are located in the EU (Frankfurt). Access is limited by roles and permissions and is logged. Each school is isolated from the others; school membership is enforced server-side. The current technical and organizational measures are documented in the annex to the processing agreement.