1. Scope
This policy covers dersivaplan.com, online verification flows used by the Dersiva desktop application, and data processing related to the Dersiva Teacher Portal. School data that remains entirely local in the desktop application enters the scope of online processing only when the user invokes a feature that sends data to an online service.
2. Website and language preference
Dersivaplan.com uses the essential dersiva-consent cookie to remember the cookie choice. The selected site language is stored in the dersiva-language cookie only when the Preferences category is allowed. The current web package contains no advertising, behavioural profiling or third-party analytics tracking code.
3. License and API verification
The Dersiva desktop application may connect to Dersiva API services for license or user verification. These flows may process limited technical data required for verification, such as license status, client version and connection-related information. This policy does not claim that unverified device fingerprinting, location tracking or similar data is processed.
4. Teacher Portal
The Teacher Portal may process the teacher account created by the school, authentication data associated with the username and password, the teacher’s published weekly timetable, lesson/class information, and confirmed duty day or duty location. The purpose is to provide each teacher with access to their own published timetable and duty information.
5. School and timetable data
Teachers, lessons, classes, assignments, constraints and generated timetables may be stored locally by the desktop application. Such data should be sent to a server only when required by an online feature that the user actively uses. The separation between trial timetables and the applied timetable helps limit what is published to the Teacher Portal.
6. Technical logs and diagnostics
The Dersiva desktop application may create local logs for diagnostics. Online services may also generate standard server logs for security, troubleshooting and service continuity. Logs may include request time, error details, client version and technical connection information. Local error logs are not assumed to be uploaded automatically unless the user explicitly shares them for support.
7. Contact form
The current web package contains the contact-form interface and client-side validation, but no production submission endpoint is connected. Therefore, form data is not sent to a Dersiva server by the current package. If submission is enabled later, processing of name, email, school/organization, subject and message fields, together with retention details, must be added to this policy.
8. Cookies and local storage
In the current web package, the essential dersiva-consent cookie stores the cookie choice for 180 days. The dersiva-language preference cookie is used for 365 days only when the user allows Preferences. Analytics and marketing cookies are not used; if such technology is introduced, the Cookie Policy and consent version will be updated.
9. Purposes of processing
Data processing should be limited to authentication, license verification, delivery of the published teacher timetable, display of duty information, service security, diagnostics, remembering user language preference and support processes initiated by the user.
10. Third parties and sharing
This policy does not state that Dersiva sells user data to advertisers or shares it for marketing. Hosting, network, email or security providers may process data to the extent necessary to provide the service if they are used in production. Specific providers and roles should be disclosed once finalized.
11. Retention
This policy does not invent fixed retention periods that have not been verified. Data should not be kept longer than necessary to provide the relevant service, support security and diagnostics, and meet applicable legal obligations. Exact production retention periods should be published once defined.
12. Data security
Dersiva treats authentication, access control, secure communication and data integrity as product-design concerns. No internet service can guarantee absolute security. Users should protect their credentials and report suspected unauthorized access to the school administration or the relevant support channel.
13. Student and child data
Dersiva is a school-planning product, but the public website is not a social network or advertising service directed at children. If student data is required, only the minimum data necessary for timetable functions should be processed. Unnecessary student personal data should not be transferred to online services.
14. User rights
Depending on applicable law, users may have rights to access, correct, delete, restrict or object to processing of their personal data. The verified corporate channel for exercising such rights will be published here when that channel is enabled.
15. Policy updates
This policy should be updated whenever there is a meaningful change to data flows in the website, desktop application, API or Teacher Portal. The revision date is displayed at the top of the page.