Terms of Use

Dersiva supports automation; it does not replace administrative responsibility.

These terms explain the core rules, user responsibilities and service limits that apply to the Dersiva desktop application, Teacher Portal and related web services.

Last updated: August 26, 2026Terms 1.1
i

This text reflects the current product structure. It should be updated when the final legal provider, exact licensing model, commercial terms or governing-law details are established.

1. Acceptance of terms

Using Dersiva means using the product within its intended purpose under these terms, the applicable license conditions and the related privacy policy. When used on behalf of a school or organization, actions should be performed by users who have the appropriate authority.

2. Scope of the service

Dersiva may provide teacher, lesson, class and time-data management, timetable generation, timetable-quality evaluation, duty management, outputs, backup and publication of the applied timetable through the Teacher Portal. Features may vary by version, license and enabled modules.

3. License and right to use

Use of Dersiva may require a valid license or authorization. A license does not transfer ownership of the software; it grants a right to use it within the permitted scope. Exact term, device/school limits, fees, renewal and commercial conditions should be defined in the applicable license or sales agreement.

4. Account and password security

For the Teacher Portal or other account-based services, responsibility for protecting usernames and passwords is shared by the user and relevant school administration. Accounts should not be shared with unauthorized people, and suspected access should trigger password changes or account deactivation.

5. Accuracy of data

Timetable quality directly depends on the accuracy of teacher, lesson, class, weekly-hour, unavailable-day, capacity and other planning data. Incorrect or incomplete input may produce a technically valid timetable that is wrong for the school. Data should be reviewed before generation.

6. Solver results and administrative approval

A timetable generated automatically by Dersiva does not become the official school timetable unless it is reviewed and approved by school administration. The solver operates on defined rules and optimization objectives; it does not replace legislation, internal administrative decisions or final human judgment.

7. Trial timetables and the applied timetable

Different scenarios may be created as trial timetables. The timetable used for the Teacher Portal and official outputs should be explicitly selected as the applied timetable. Preventing trial scenarios from being treated as official publication is an important part of the workflow.

8. Duty planning

Automatic or administrative duty-day planning depends on the available teacher data and configured rules. Duty exemptions, administrative assignments, legal requirements and final duty locations should be verified by school administration.

9. Backup and restore

Dersiva may provide backup and restore tools, but users remain responsible for maintaining regular and safe backups of important school data. Backup accessibility, correct file selection and protection of existing data before restore should be checked by the user.

10. Updates

Dersiva may publish updates containing bug fixes, security improvements, new features or compatibility changes. Some versions may be test, pilot or development releases. Production use should take release notes and release status into account.

11. Service availability

Web, API, license-verification or Teacher Portal services may be temporarily unavailable because of maintenance, security, network, hosting or technical issues. Dersiva cannot guarantee uninterrupted operation of the internet or third-party infrastructure. Schools should not make critical data dependent only on online access.

12. Prohibited use

Unauthorized account access, bypassing security controls, disrupting the service, improperly disabling license mechanisms, distributing malicious code or attempting to access other users’ data without authorization are prohibited. Use of the product for unlawful purposes is also not permitted.

13. Intellectual property

The Dersiva brand, original interface, product documentation and original Dersiva software components belong to their respective rights holders. Use of the software does not transfer ownership of source code, branding or design elements to the user.

14. Third-party components

Dersiva may use third-party or open-source components for runtime, optimization, database, security or related functions. Those components may be subject to their own licenses. These Terms do not override third-party license rights or represent third-party components as owned by Dersiva.

15. Outputs and reports

PDF, spreadsheet, timetable or similar outputs reflect the program and data state from which they were generated. Before official use, the user should verify that outputs are current, accurate and match the applied timetable.

16. Limits of responsibility

Dersiva is software that supports the planning process. The software cannot prevent every consequence arising from incorrect data, user choices, insufficient backups, unauthorized account sharing or a timetable applied without administrative verification. Nothing in these Terms excludes liability where applicable law does not permit such exclusion.

17. Changes to the terms

These terms may be updated if product features, licensing, online services or legal requirements change. The update date is shown at the top of the page. Users should review material changes.

18. Governing law and disputes

This web package does not declare a specific court, jurisdiction or governing law before the final legal service provider and commercial agreement are established. The provider’s legal identity, governing law and dispute terms should be stated clearly in the applicable license or sales agreement before commercial use.

19. Contact

Questions about these Terms, licensing or product behavior can be directed through the Contact and Help Center pages. The verified corporate channel for formal contractual or legal notices should be published when it becomes available.

Usage approach

Four core boundaries

01

Automation ≠ approval

Solver output does not replace final administrative review and approval.

02

Data quality matters

Incorrect inputs can produce an incorrect timetable even with correct optimization logic.

03

Backups remain a user process

Backup tools do not remove the need to protect critical school data.

04

Check release status

Pilot, test and stable releases may have different intended uses.

Dersiva usage model

Responsibility across the workflow

1

User

Defines school, teacher, lesson and constraint data correctly.

2

Dersiva

Generates a solution from the defined rules and optimization goals.

3

School administration

Reviews the timetable, compares alternatives where needed and selects the applied timetable.

4

Publication

Only the selected timetable is published to teachers and official outputs.

Question about the terms

If part of the product flow is unclear, verify that workflow first.

Use the Help Center for technical usage and the Contact page for licensing and product questions.