Skip to content

Terms of Service (AGB)

This English text is a courtesy translation for convenience. The German version is legally binding.

General Terms of Use

Provider: Cornelius Berger, Brückenaue 14, 51491 Overath, Germany, email: hallo@stundenplan-berechnen.de (the "Provider").

§ 1 Scope and conclusion of contract

(1) These terms govern the use of the Stundenplan & Verwaltung suite, its modules and the account at stundenplan-berechnen.de. (2) The contract is concluded by accepting these terms in the account. (3) This offer is directed exclusively at business users within the meaning of § 14 BGB (German Civil Code) — i.e. natural or legal persons or partnerships with legal capacity acting in the exercise of a commercial or independent professional activity when concluding the contract; this expressly includes freelancers. When purchasing tokens, the user actively confirms their business-user status (see the checkout declaration). This offer is not directed at consumers within the meaning of § 13 BGB.

§ 2 Description of services

(1) At the core of the offering is software for the automated computation of timetables and schedules (Solver). The Provider additionally supplies further modules for managing music schools/music teachers, such as student and master-data management, billing/invoicing, and calendar synchronization. The current scope of functions follows the current product description; individual modules may be added, changed, or discontinued. (2) Use is on a credit/token model (pay per use). There is no subscription in the sense of a recurring payment obligation: the user owes no running amounts, and purchased tokens do not expire. For continuously provided services — currently the hosted calendar under paragraph 3 — the existing balance is nevertheless debited by the day for as long as the service is active. Even then no payment obligation beyond the existing balance arises; if the balance runs out, § 7(5) applies. A free basic tier may be offered. (3) Hosted calendar (optional). At the user's request the Provider supplies a hosted calendar access (CalDAV) consisting of three calendars (lessons, free slots, offers) which the user can connect to the calendar applications of their choice. For this service one token is debited from the balance for every calendar day on which the access is active, starting on the day after activation; the day of activation itself is free of charge. No balance is required in order to activate. The user may end the access at any time in their account; no further debits are then made from the following day on. Before the first activation the user separately confirms the daily debit and its consequence for the right of withdrawal. (4) Scope of the hosted calendar. The service is provided in packages. One package comprises 12 calendars and 50,000 appointments in total and costs the fee under para. 3. Activation grants the User one package; three calendars are created automatically in the process. Within their package, the User may create, rename and delete calendars of their own as they see fit. (5) Additional packages. The User can unlock further packages in their account at any time. Each additional package raises the limits under para. 4 by the same amount and the daily fee under para. 3 by the same amount; this is shown before confirmation. Packages can likewise be given back, as long as the remaining scope still covers what is stored. (6) Reaching the limits. From 80 % of the appointment allowance under para. 4 onwards, the Provider gives notice of the fill level; once either limit is reached, the calendar accepts no further appointments or no further calendars respectively. Appointments already stored remain readable, editable, movable and syncable, and deletion is possible at any time. Appointments whose last occurrence lies more than five years in the past are removed automatically; indefinitely recurring appointments are exempt. (7) Responsibility for the automatically created calendars. If the User deletes one of the calendars created at activation, its synchronisation with the software ends. The Provider points this out in the User's account and offers to create the missing calendar again; the appointments it contained cannot be restored. (8) System notices in the calendar. The Provider enters notices about the operation of the hosted calendar — in particular about the fill level and about the limits under para. 4 being reached — as its own all-day recurring appointment in one of the User's calendars, changes it when the situation changes, and removes it once the reason no longer applies. This is stated expressly because it is write access by the Provider to the User's calendar data. This notice appointment occupies no time (shown as "free"), does not count towards the limits under para. 4, and is not covered by the five-year rule. The Provider enters no other content. The technical restriction on this access is described in the DPA (§ 5). (9) Notices by email. In addition to the notices in the account and in the calendar, the Provider notifies the User by email, to the address held in their account, when the token balance for the hosted calendar is running low, when the access is suspended, several times during the periods under § 7(5), and after deletion. The Provider cannot guarantee the arrival or delivery of these messages — they may fail to arrive through filters, full mailboxes, outdated addresses or faults at the sending service. The periods under § 7(5) run regardless; the User can check the current state in their account at any time. The obligation to keep a valid email address on file follows from § 3(3).

§ 3 User obligations

(1) The user is responsible for the lawfulness of the data they process, in particular for any required consents of data subjects. For the processing of student data the Data Processing Agreement (DPA) applies in addition. (2) Credentials and the license key must be kept confidential. (3) The user keeps the contact details stored in the account up to date, in particular the email address, as this is the Provider's sole channel for contract- and security-relevant communications.

§ 4 Fees and tokens

(1) Prices follow the price list valid at the time of purchase. Billing is handled via the payment provider. (2) Already-purchased tokens keep the value valid at purchase; price reductions benefit existing balances, price increases apply only to newly purchased tokens. The same applies analogously to any adjustment of token consumption: the user is never disadvantaged by it and always receives whichever value is more favorable to them.

§ 5 Availability

The Provider strives for high availability but owes no specific availability quota. Maintenance windows and force majeure are reserved.

§ 6 Liability

(1) The Provider is liable without limitation for intent and gross negligence and for injury to life, body or health. (2) For simple negligence the Provider is liable only for breach of a material contractual obligation (cardinal obligation) whose fulfilment makes the proper performance of the contract possible in the first place and on which the user may regularly rely; liability is then limited to the foreseeable damage typical for the contract. (3) Otherwise liability is excluded. No warranty is given for the correctness or optimality of computed plans; the generated timetable is a proposal and must be reviewed by the user before publication. (4) Mandatory liability under the German Product Liability Act (ProdHaftG) remains unaffected by the above limitations and is neither excluded nor limited.

§ 7 Term and termination

(1) The usage relationship may be ended at any time by deleting the account. (2) Unused tokens do not forfeit as a result — not even a full deletion of the user's personal data affects the token balance. The user is responsible for keeping their own license key, though: only that key can reattach a remaining balance after an account deletion. (3) The provider additionally deletes an account automatically once it has been inactive for 365 days and holds neither a token balance nor any purchase history. An existing balance or purchase history excludes an account from this automatic deletion (paragraph 2 applies accordingly). Automatic deletion also removes the account's associated workspace (in particular any student data and timetables stored in it). (4) The Provider may discontinue the service entirely. It will give at least six months' notice by email to the address on file in the customer account. Within that period the user may request payout of their unused token balance; the Provider will pay the value of the unused balance — valued at the purchase price of the purchases not yet consumed — to an account named by the user. The user is obliged to keep the email address on file in the account current and to check it regularly for messages from the Provider. If the user does not come forward to request payout within the notice period, the balance forfeits without compensation once the period expires. (5) Suspension and deletion of the hosted calendar. Independently of paragraph 3, the following applies to the hosted calendar under § 2(3): if the balance does not cover the daily debit, the Provider suspends the access. The user's calendar applications can then, shortly afterwards — as a rule within one minute — no longer log in; the stored appointments remain unchanged. The same happens when the user ends the hosted calendar. The user may reactivate the access at any time and as often as they wish; the password set previously remains valid. Topping up the balance lifts a suspension imposed for lack of balance immediately. If the access stays suspended without interruption, the Provider deletes the calendar account together with all of the User's calendars once the following periods have elapsed, counted from the day of suspension: a) 30 days if the calendars hold no appointments; b) 180 days where the suspension rests solely on an exhausted token balance and appointments are stored. In that case the contract continues; the User can restore access at any time by topping up; c) 30 days where the User has ended the hosted calendar themselves. On ending it, the User may instead choose immediate deletion or a retention period of 180 days; the choice made applies. The Provider states the deletion date to the User in their account beforehand, additionally enters it as an appointment in one of their calendars (§ 2 para. 8), points it out to them by email several times (§ 2 para. 9) and provides an export of the calendars until then. The export is possible independently of whether access is currently suspended, including during a period running under this paragraph. The deletion covers live operation; holdings contained in backup copies are not edited individually but expire within 30 days. The token balance and the remaining services are unaffected by suspension and deletion.

§ 8 Data protection

The processing of personal data is governed by the privacy policy and — for the processing of student data on the user's behalf — by the DPA (Art. 28 GDPR).

§ 9 Final provisions

(1) German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. (2) As this offer is directed exclusively at business users within the meaning of § 14 BGB (§ 1(3)), the exclusive place of jurisdiction for all disputes arising from or in connection with this contract is Overath, Germany. Should a consumer within the meaning of § 13 BGB nonetheless have become a contracting party contrary to § 1(3), the statutory rules on place of jurisdiction remain unaffected for them; the above jurisdiction agreement does not apply to consumers. (3) Should a provision be invalid, the remainder of the contract stays valid.

Last updated: 2026-09-15