§ 1

Scope and Definitions

1.1 These General Terms and Conditions (GTC) apply to all contracts between IT-Service Harting, proprietor Giovanni Harting, Hermann-Löns-Str. 93, 52078 Aachen, Germany (hereinafter "we" or "us"), and the customer. They also apply to future services and offers without needing to be incorporated again.

1.2 A consumer within the meaning of § 13 of the German Civil Code (BGB) is any natural person who enters into the contract for purposes that are predominantly outside their trade, business or profession. An entrepreneur within the meaning of § 14 BGB is a natural or legal person, or a partnership with legal capacity, acting in the exercise of their trade, business or profession when entering into the contract. Provisions of these GTC that apply only to consumers or only to entrepreneurs are marked accordingly.

1.3 Deviating, conflicting or supplementary terms of the customer do not become part of the contract unless we expressly agree to their application in text form.

1.4 Individual agreements between us and the customer always take precedence over these GTC pursuant to § 305b BGB. To avoid misunderstandings, we recommend having any verbal arrangements confirmed in text form.

1.5 In addition to these General Terms and Conditions, the product-specific service agreements (web hosting, e-mail hosting, Kubernetes, vServer, object storage, domains) and the Service Level Agreement apply. Where domains are the subject of the contract, the allocation conditions of the competent registry apply additionally.

1.6 Order of precedence
In the event of conflicts between the contractual documents, the following order of precedence applies: (1) the data processing agreement, (2) the product-specific service agreements, (3) the Service Level Agreement, (4) these General Terms and Conditions. The data processing agreement takes precedence over these GTC in particular with regard to liability for infringements of data protection law.

§ 2

Formation of Contract

2.1 Our offers are subject to change and non-binding unless expressly designated as binding. Technical and other changes remain reserved within reasonable limits.

2.2 By submitting the order via the "Order with obligation to pay" button, the customer makes a binding contractual offer. We may accept this offer within five working days, either by providing the service or by confirming in text form. An automated acknowledgement of receipt does not constitute acceptance.

2.3 The customer warrants that the data they provide is correct and complete. They will notify us of any changes within 14 days at the latest, in text form or via the customer portal. Upon reasoned request, they will provide evidence of the accuracy of the data.

2.4 Contract formation in electronic commerce
We store the text of the contract and send it to the customer together with these GTC in text form. The languages available for concluding the contract are German and English. Before submitting the order, the customer can review their entries in the order summary and change them at any time using the correction functions of the order form and the browser’s back function, or cancel the order.

§ 3

Contract Term and Termination

3.1 Contracts are concluded for an indefinite period. No minimum term is agreed.

3.2 The customer may terminate any contract at any time without giving reasons. The termination takes effect at the end of the day that falls one month after its receipt (§§ 187(1), 188(2) BGB); if that day does not exist in the following month, the contract ends at the end of the last day of that month (§ 188(3) BGB). Examples: a termination received on 31 January ends the contract with 28 or 29 February; one received on 15 March ends it with 15 April. We may terminate contracts on the same notice. The registration period of a domain (§ 6.2 of the Domains service agreement) is not a contract term and does not extend the notice period.

3.3 Form of termination
Termination requires text form and may be declared by letter, by e-mail to service@itsh.dev, or via the customer portal. For consumer contracts concluded in electronic commerce, the termination button „Verträge hier kündigen“ is additionally available; it is permanently available on our website, directly and easily accessible, and can be used without logging in. We confirm receipt of a cancellation declared through this button immediately by electronic means in text form, stating its content, the date and time of receipt and the end date. A confirmation link that we send to the email address of the customer account to protect it is not a condition for receipt or effectiveness of the cancellation.

3.4 Termination for cause
The right of both parties to terminate for good cause remains unaffected. Good cause exists for us in particular where the customer is in default with a not insignificant part of the remuneration and fails to pay despite a reminder and a reasonable grace period, or where they materially breach § 10 of these GTC despite a warning. No warning is required where it is unreasonable given the severity of the breach, in particular where the security or availability of our infrastructure is at risk or where content is manifestly criminal.

3.5 Transferring the contractual rights and obligations to a third party requires our consent and text form. We verify the authority of the transferring party and the identity of the third party.

§ 4

Scope of Services

4.1 The scope of the contractual service follows from the service description in force at the time of the order and the resulting agreements in text form. We may discontinue services offered free of charge, or offer them subject to charge in future, upon prior notice with reasonable warning.

4.2 Where the registration of domain names is the subject of the contract, we owe only the intermediation vis-à-vis the competent registry. We have no influence on the allocation decision. The customer may not assume allocation until we have confirmed it.

4.3 We undertake commercially reasonable efforts to achieve the availability stated in the Service Level Agreement. Details of measurement, exclusions and credits are governed by the Service Level Agreement.

4.4 Where the service includes the assignment of an IP address, there is no entitlement to a specific IP address. The IP address is not checked against blocklists. We may change the IP address for technical or operational reasons upon prior notice.

4.5 Support services going beyond the respective service description are charged separately upon prior agreement.

§ 5

Prices, Payment and Default

5.1 The prices published on itsh.dev at the time of the order apply. Vis-à-vis consumers, all prices are total prices including statutory value added tax and all other price components. Vis-à-vis entrepreneurs, prices are exclusive of statutory value added tax where it applies.

5.2 Depending on the contractual agreement, billing is monthly, quarterly, semi-annually or annually via the payment method chosen by the customer. The customer observes the terms of the payment service they use. If the contract ends before a billing period paid in advance has expired, we refund the fee attributable to the time after the end of the contract pro rata by the day within 14 days after the end of the contract, to the payment method originally used. If the fee was paid by SEPA direct debit and, at the end of the contract, the period within which the customer can demand a refund of that debit from their bank (eight weeks from the debit date, § 675x(2) and (4) BGB) has not yet expired, we refund within 14 days after that period expires. Usage-based fees incurred up to the end of the contract may be billed separately and set off against the refund. For the registration fee of a domain, § 6.4 of the Domains service agreement applies.

5.3 If the customer defaults on payment, the statutory provisions of §§ 286, 288 BGB apply. Vis-à-vis consumers, default under § 286(3) BGB only occurs if we have specifically drawn attention to this consequence in the invoice.

5.4 Invoices are issued free of charge in electronic form. For postal delivery we charge the costs actually incurred, provided the customer expressly requests it.

5.5 The customer is obliged to comply with applicable export and import control regulations insofar as their use of the services is affected.

5.6 VAT treatment
Whether and at what rate value added tax applies is determined by law, in particular by where the customer is established and whether they act as an entrepreneur. For VAT purposes we rely on the details in the customer account. A customer established in another member state of the European Union is invoiced without German VAT once they have provided us with a VAT identification number of that state which is confirmed as valid in the European Commission's VAT Information Exchange System (VIES); the customer then owes the VAT (reverse charge). A customer established outside the European Union who is registered as a business is invoiced without VAT, because the service is not taxable in Germany. For as long as a VAT identification number provided to us is not, or is no longer, confirmed as valid, we charge VAT. We check the VAT identification number when it is provided and periodically thereafter. The result available to us when each invoice is issued is decisive; a change takes effect from the next invoice issued after it, and we inform the customer of it in text form. Periods already invoiced are neither recalculated nor refunded. The customer keeps their details on entrepreneur status, address and VAT identification number up to date in accordance with § 2.3. If we must pay VAT in arrears because an entrepreneur provided incorrect details in this respect, we may claim it from them unless they are not responsible for the inaccuracy.

5.7 Plan switches
If the customer switches to another plan within a product, the contract continues with its current billing period. For quarterly, semi-annual or annual billing the following applies: For the time from the day of the switch to the end of the billing period already paid we charge or refund the difference between the previous and the new fee pro rata by the day; the day of the switch counts towards the new plan. We show the customer any difference payable as a total amount before the switch and charge it to the stored payment method; the switch to the higher plan takes effect once this amount has reached us. We refund any difference due to the customer under § 5.2 sentences 3 and 4, with the day of the switch taking the place of the end of the contract. From the following billing period the fee of the new plan applies. If the customer switches to a usage-billed plan, the previous fixed-price plan ends with the switch and we refund the fee for the time after it in the same way. For monthly billing the following applies: For web hosting the billing month continues, the switch takes effect at once, and we set off the difference for the rest of the month, pro rata by the day, against the next invoice. For Kubernetes the switch likewise takes effect at once, and the new plan is billed on the first of each month. For the time from the day of the switch to the end of the month we charge the new plan's fee, pro rata by the day, at once, and refund the fee already paid for the previous plan for the time from the day of the switch to the end of its paid billing period under § 5.2 sentences 3 and 4, with the day of the switch taking the place of the end of the contract. From the following first of the month the new plan's full fee applies. For a usage-billed plan this applies to its base fee; usage is billed from the switch at the published usage prices. We show the customer the amount due at once and the refund before the switch. A switch is not possible while the contract is terminated, an earlier switch has not yet been completed, a change of the billing period under paragraph 8 is scheduled, or the customer owes us a due fee or due compensation under § 12.7 from any contract of their customer account; the same applies while a withdrawn switch on any contract of their customer account has not yet been settled because a payment for it is still being processed. A consumer may withdraw from a switch to a higher plan and from a switch from the free to a paid plan under § 12; the withdrawal restores the previous plan, and we refund the amounts charged for that switch less the compensation under § 12.7 for the services provided on the new plan up to the withdrawal. The existing contract and the fee paid for it are not affected by the withdrawal.

5.8 Change of billing period
If a product offers several billing periods, the customer may change the billing period of their contract for the future in the customer portal. The change takes effect at the end of the current billing period. From then on the new period applies: its fee is charged in advance at its start, and each such period is followed by a period of the same length. Until the change takes effect, the customer may revoke it in the customer portal. A change is not possible while the contract is terminated, a plan switch under paragraph 7 has not yet been completed or can still be withdrawn, or the customer owes us a due fee under this contract. If the customer terminates the contract before the change takes effect, the change lapses. Deviating rules in the service agreement of a product take precedence.

§ 6

Changes to these GTC and to Prices

6.1 Changes to these GTC
Changes to these terms and to the service agreements apply to an existing contract only once the customer has expressly accepted the new version. We announce a change to the customer in text form at least six weeks before its intended effective date; the announcement names the changed sections and summarises the changes. From the announcement onward we make the new version and a comparison of the changed provisions with the previous version available in the customer portal for viewing and saving, and we obtain the customer's acceptance there. Silence, continued use of the service or payment of fees do not constitute acceptance. Until acceptance, the previous version continues to apply to the contract; after acceptance the new version applies from the intended effective date, or from acceptance if that is later. If the customer does not accept, either side may terminate the contract under section 3.2.

6.2 Changes to prices
Price increases for existing contracts likewise require the customer's express consent. We offer the customer the new price in text form at least six weeks before the intended effective date, stating the previous price, the new price and the effective date, and obtain consent in the customer portal. § 6.1 sentences 4 to 6 apply accordingly. Price reductions are passed on without the customer's consent.

6.3 VAT
Prices for consumers include the statutory VAT applicable at the time (§ 5.1). If the statutory VAT rate changes, the gross price changes by the corresponding amount from the day of the change; the net price remains unchanged.

6.4 Registration fees for domains
Changes to the price of a domain resulting from a change in the registration fee are governed solely by § 6.3 of the Domains service agreement.

§ 7

Customer Obligations and Data Backup

7.1 For the vServer/VPS service areas, the customer holds sole administration rights. They administer and secure these systems at their own cost and risk.

7.2 The customer sets up and operates the systems they administer so that the integrity and availability of third-party networks, servers and data are not endangered. In particular, use for (D)DoS attacks and the operation of open mail relays or comparable systems are prohibited. In the event of breaches we are entitled to suspend the affected service; § 3.4 remains unaffected.

7.3 The customer uses the services provided properly and refrains from abusive and unlawful acts.

7.4 Where the respective service agreement so provides, we create platform-side backups; their scope, frequency and retention period follow from it. These backups do not replace the customer’s own data backup. The customer remains responsible for their own backup, held separately from the system, and performs a full data backup before any change they initiate.

§ 8

Data Protection and Processing on Behalf

8.1We process personal data in accordance with the General Data Protection Regulation. Details of processing carried out under our own responsibility can be found in our privacy policy.

8.2 Where the customer processes third-party personal data using our services, they remain the controller within the meaning of the GDPR. We process such data as a processor pursuant to Art. 28 GDPR.

8.3 Data processing agreement
For web hosting, e-mail hosting, domains, Kubernetes including the container registry, vServer/VPS and object storage, the data processing agreement forms part of the service contract and is concluded together with the order. The customer may declare to us in text form that they do not process any third-party personal data via our services and therefore require no data processing agreement; we record such a declaration in the customer account. The current data processing agreement is available in the customer portal.

8.4 The customer informs us of the details required for processing on their behalf, in particular the purpose and the categories of data processed and of data subjects, insofar as these do not already follow from the data processing agreement.

8.5 The customer is responsible for the security of the content they upload and the configuration they choose. The technical and organisational measures we take are set out in the data processing agreement.

§ 9

Use by Third Parties

9.1 The customer is entitled to grant third parties a right to use the services they have ordered. In this case they remain our sole contractual partner and continue to be liable to us for compliance with the contractual agreements.

9.2 Where changes require the cooperation of the third party, the customer ensures already upon granting the right of use that the statutory and contractual provisions are complied with.

9.3 If the third party breaches the contractual obligations or fails to fulfil obligations to cooperate, the customer is liable for the resulting damage under the general provisions and indemnifies us against justified third-party claims based on that breach. The indemnity covers the necessary costs of legal defence.

§ 10

Permitted Use, Content and Notice Procedure

10.1 The customer independently reviews and observes the statutory provisions applicable to their use, in particular the German Telecommunications Act and the German Digital Services Act (DDG), as well as the provisions of copyright, trade mark, personality, competition and data protection law. They indemnify us against justified third-party claims based on a culpable breach of these obligations.

10.2 The customer does not publish content that infringes applicable law or the rights of third parties. This includes in particular, but not exhaustively, content that violates criminal law, content harmful to minors, unlawful gambling, and content infringing copyright, name, trade mark or personality rights.

10.3 Sending unsolicited advertising (spam) is prohibited, as is providing false sender data or otherwise disguising the sender’s identity. Also prohibited is the operation of applications for mining cryptocurrencies, including mining, farming and plotting.

10.4 Notice and action procedure
Notices of illegal content on services we operate can be submitted at any time via the reporting form on our website or by e-mail to abuse@itsh.dev. We handle notices in accordance with Art. 16 of Regulation (EU) 2022/2065 (Digital Services Act), confirm receipt and communicate the decision taken.

10.5 Where, on the basis of a notice or our own knowledge, we restrict access to the customer’s content or suspend a service, we notify the customer of the decision with a statement of reasons pursuant to Art. 17 of Regulation (EU) 2022/2065. The statement of reasons sets out the scope of the measure, the underlying facts, the legal basis, a reference to any automated decision-making, and the possibilities for redress. The customer may object to the measure within 14 days in text form; we review the objection and communicate the result with reasons.

§ 11

Warranty and Liability

11.1 We are liable for defects in our services in accordance with the statutory provisions.

11.2 Liability
We are liable without limitation for intent and gross negligence, for injury to life, body or health, under the provisions of the German Product Liability Act, and to the extent of any guarantee we have assumed.

11.3 In cases of ordinary negligence we are liable only for breach of a material contractual obligation, that is, an obligation whose fulfilment is essential to the proper performance of the contract and on whose observance the customer may regularly rely. In that case liability is limited to the foreseeable damage typical for this type of contract; vis-à-vis entrepreneurs it is additionally limited to the remuneration paid for the affected service in the preceding twelve months.

11.4 Liability is otherwise excluded. This does not entail any change in the burden of proof to the customer’s detriment.

11.5 We are liable for loss of data to the extent set out above only insofar as the loss would also have occurred had the customer carried out proper and regular data backups pursuant to § 7.4.

11.6 The above limitations of liability also apply in favour of our legal representatives, employees and vicarious agents.

11.7 If the customer breaches § 10 of these GTC, they are liable to us for the resulting damage under the general provisions and indemnify us against justified third-party claims based on that breach.

§ 12

Right of Withdrawal for Consumers

12.1 Withdrawal instructions
Consumers have a right of withdrawal. You have the right to withdraw from this contract within fourteen days without giving any reason. The withdrawal period is fourteen days from the day of the conclusion of the contract. To exercise your right of withdrawal, you must inform us (IT-Service Harting, owner Giovanni Harting, Hermann-Löns-Str. 93, 52078 Aachen, Germany, phone +49 3682 9180648, email service@itsh.dev) of your decision to withdraw from this contract by an unequivocal statement (e.g. a letter sent by post or an email). You may use the attached model withdrawal form, but it is not obligatory. You may also exercise your right of withdrawal online at https://itsh.dev/dashboard/withdraw. If you use this online function, we will send you without undue delay an acknowledgement of receipt on a durable medium (e.g. by email) containing the content of the withdrawal declaration and the date and time of its receipt. To meet the withdrawal deadline, it is sufficient for you to send your communication concerning your exercise of the right of withdrawal before the withdrawal period has expired.

12.2 Effects of withdrawal
If you withdraw from this contract, we shall reimburse to you all payments received from you, including the costs of delivery (with the exception of the supplementary costs resulting from your choice of a type of delivery other than the least expensive type of standard delivery offered by us), without undue delay and in any event not later than fourteen days from the day on which we are informed about your decision to withdraw from this contract. We will carry out such reimbursement using the same means of payment as you used for the initial transaction, unless you have expressly agreed otherwise; in any event, you will not incur any fees as a result of such reimbursement.

12.3 Early expiry of the right of withdrawal
In the case of a contract for the supply of services, the right of withdrawal expires upon complete performance of the service if you expressly consented, before performance began, to us beginning performance before the expiry of the withdrawal period, and confirmed your awareness that you lose your right of withdrawal upon complete performance of the contract. We obtain this consent and confirmation separately during the ordering process.

12.4 Special provision for domain registrations
The registration of a domain name is completely performed upon entry in the registry, because at that moment we irrevocably acquire the registration period from the registry. If you have consented to immediate commencement pursuant to paragraph 3, the right of withdrawal expires in that respect upon registration. The right of withdrawal remains unaffected as regards holding and administering the domain beyond the registration period.

12.5 No compensation for value (contractual promise, not part of the withdrawal instructions)
If you requested that the service begin during the withdrawal period and you withdraw from the contract, we nevertheless refund all payments in full. We do not claim compensation for the service already provided up to the withdrawal. For the withdrawal from a plan switch, paragraph 7 applies instead.

12.6 Model withdrawal form
The model withdrawal form is printed below. We also provide it on our website under "Withdrawal instructions" for retrieval and electronic submission.

12.7 Withdrawal from a plan switch
The withdrawal instructions above apply accordingly to a switch to a higher plan and to a switch from the free to a paid plan (§ 5.7 of the GTC); the withdrawal period is fourteen days from the day of the switch. If you withdraw from the switch, we restore the previous plan; the contract itself and the payments made for it remain unaffected. We reimburse the payments received for the switch without undue delay and not later than fourteen days from the day on which we are informed about your withdrawal, using the same means of payment. If you requested that the switch be carried out during the withdrawal period, you shall pay us an amount which is in proportion to what has been provided on the new plan until you have communicated to us your withdrawal from this switch, in comparison with the full coverage of the services agreed for the switch. The price agreed for the switch is decisive: for a fixed-price plan, the new plan's fee for the time from the switch to the withdrawal, with the fee already paid for the previous plan for the same time credited; for a usage-billed plan, the base fee for that time and the usage recorded up to the withdrawal at the agreed prices. We set this amount off against the payments received for the switch and refund the rest; where those payments do not cover it, we invoice the difference separately.

(If you wish to withdraw from the contract, please complete this form and return it.)

To
IT-Service Harting
Proprietor Giovanni Harting
Hermann-Löns-Str. 93
52078 Aachen
Germany
E-mail: service@itsh.dev

I/We (*) hereby give notice that I/We (*) withdraw from my/our (*) contract of sale of the following goods (*) / for the provision of the following service (*)

_______________________________________________

Ordered on (*) / received on (*): ____________

Name of consumer(s): __________________________

Address of consumer(s):
_______________________________________________

Signature of consumer(s)
(only if this form is notified on paper): _____

Date: ________________

(*) Delete as appropriate.
§ 13

Switching Providers and Data Portability

13.1 This section applies to data processing services within the meaning of Regulation (EU) 2023/2854 (Data Act), in particular web hosting, e-mail hosting, Kubernetes, vServer and object storage.

13.2 Notice of switching
The customer may give notice at any time in text form of switching to another provider or to their own IT infrastructure. The notice period is a maximum of two months.

13.3 Transitional period
Following notice of switching, the transitional period is a maximum of 30 calendar days; during this period we continue to provide the service unchanged. The customer may extend the transitional period once by a period they consider appropriate. If switching is technically not feasible within 30 calendar days, we notify the customer within 14 working days of receipt of the notice, give reasons, and state an alternative transitional period of no more than seven months.

13.4 Assistance and exportable data
We provide the customer with reasonable assistance in switching, maintain business continuity, point out risks known to us, and ensure a high level of data security. Which data and digital assets are exportable, and through which interfaces the export takes place, follows from the respective service description. Not exportable are components that serve exclusively our internal operations and whose disclosure would infringe trade or business secrets, in particular system architecture, platform code, security infrastructure and internal operational and monitoring data.

13.5 Retrieval period and deletion
After the transitional period has expired, we make the exportable data available for retrieval for at least 30 calendar days. After that retrieval period expires, we delete the data.

13.6 Charges for switching
We do not charge for switching or for the associated data transfer. From 12 January 2027, charging switching fees is in any event prohibited under Art. 29 of Regulation (EU) 2023/2854.

§ 14

Dispute Resolution and Final Provisions

14.1 We are neither willing nor obliged to participate in dispute resolution proceedings before a consumer arbitration board.

14.2 These GTC and the contractual relationship between us and the customer are governed by the law of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods. For consumers, this choice of law applies only insofar as it does not deprive them of the protection afforded by mandatory provisions of the law of the state in which they have their habitual residence.

14.3 If the customer is a merchant, a legal entity under public law or a special fund under public law, the exclusive (including international) place of jurisdiction for all disputes arising from the contractual relationship is our place of business in Aachen. In that case we are also entitled to bring proceedings at the customer’s general place of jurisdiction. For consumers, the statutory places of jurisdiction apply.

14.4 Authoritative language version
These GTC and the other contractual documents are provided in German and English. Only the German version is authoritative; the English version is provided for information only.

14.5 Should any provision of these GTC be or become wholly or partly invalid or unenforceable, the validity of the remaining provisions remains unaffected. The statutory provisions take the place of the invalid or unenforceable provision.

Web Hosting Service Agreement

1

Contact, Customer Support

All account types include free written support during the specified support hours. If this is included in the respective offer, free telephone support is also offered. Written support requests by the customer are made via the self-service customer portal. The customer must use their customer access to the customer portal (login: contact email, password: customer password).

In general, support orders by the customer are included in the flat rate of the product. Special support requests that are not included in the services of IT-Service Harting are only processed in exceptional cases. If more than 15 minutes of working time is required to resolve these problems, IT-Service Harting charges, after prior consultation with the customer, EUR 19.99 (incl. 19% VAT) per commenced quarter of an hour.

2

Monitored Services

  • Web server (HTTP)
  • Mail system (SMTP, POP3, IMAP, spam filter, virus scanner, mail sending volume)
  • Server services (SFTP)
  • Databases
  • Server load
  • Storage utilisation
3

System Outages and Maintenance

A system outage is usually announced on https://status.itsh.dev or announced in advance for planned maintenance work. Status notifications by email can be subscribed to in the self-service customer portal.

4

Mass Emails

For email sent through email accounts of the web hosting account, § 5 of the Email Hosting service agreement applies accordingly: per authenticated user at least 500 messages per hour and 2,000 messages per day are possible, and 30 messages per hour and 100 messages per day during the first 30 days after registration of the customer account; the limit technically enforced may be higher and may be lowered to these values at any time. Sending mass emails/newsletters via email accounts of the web hosting account or via the website of the web hosting account is not permitted. Sending unsolicited advertising is prohibited. IT-Service Harting is entitled to immediately block customer accounts that violate this.

5

Data Backup

All web hosting packages include daily, weekly and monthly backups of all data. Data is retained for up to 6 months. Restoring the backup is possible via our support. Both restoring individual files and complete folders or an account is possible.

6

Content and Data of Created Accounts

Changes by support staff, such as deleting, moving, overwriting content and sensitive data uploaded and/or received by the customer, can only be carried out if this request is verified via the self-service customer portal or in writing with company stamp and handwritten signature. For work that can be done by the customer themselves and is possible, there is no entitlement to execution by support staff.

7

Changes to Configuration Files

In general, except for the listed exceptions, no individual adjustments in configuration files are possible for web hosting accounts. This applies to system settings and the services offered. The following settings can be changed:

PHP

Selected PHP settings can be changed via the self-service customer portal. Settings that exceed the available values and set limitations cannot be changed. Additional PHP modules other than those offered will not be installed. Own PHP solutions, such as own PHP binaries, are not supported. Activated PHP modules can be viewed in the product overview.

IMAP

The value for parallel IMAP connections per IP address is limited for server stability reasons. An increase of this value is possible on request, but there is no entitlement to it.

SMTP

The offered settings such as forwards, autoresponder, spam filter, etc. can be changed by the customer. Further individual settings and configurations for the mail system will not be created. SPF records and DKIM/DMARC are automatically set by us and cannot be changed by the customer.

Databases

Individual settings on the database configuration are not possible for web hosting products. For each database created by the customer, a database user is set up who may only access this database. A global database user or users who have access to multiple databases will not be set up for security reasons.

8

Process Monitoring

To ensure the security and stability of the server, process monitoring takes place, which terminates the corresponding process in case of excessive runtime and/or RAM utilisation.

9

Installation of Additional Software

The installation of additional software or libraries is not carried out by support. The operation of additional software that requires root rights for installation or operation is generally not possible.

10

Protecting the Email Service from Spam and Viruses

All email accounts include a server-side spam filter that automatically sorts suspicious emails into the Junk folder. The Junk folder is accessible via IMAP and webmail. The spam filter uses rule-based detection, DNS-based blocklists and machine learning. Emails exceeding a critical spam score are rejected at SMTP level and not delivered.

Incoming emails are automatically scanned for viruses and malware. Emails detected as infected are rejected at SMTP level and not delivered. Virus definitions are updated automatically several times a day.

Senders listed in the recipient's address book are automatically classified as trusted. Spam filter sensitivity is configured by IT-Service Harting. Individual filter rules can be set up by the customer using Sieve scripts.

For customers with a separate Email Hosting product, the Email Hosting Service Agreement applies.

11

Prohibited Actions

To enable us to operate a high-performance and reliable network for our customers, the operation of applications for mining cryptocurrencies is prohibited.

12

Storage and Billing

Each web hosting package includes the storage stated in the service description for files, databases and mailboxes of all websites in the package. Use beyond the included storage is billed by consumption. The price per gigabyte and month published on itsh.dev at the time of the order applies. Billing is monthly. Later changes to this price are governed solely by § 6 of the General Terms and Conditions. Current storage use can be viewed at any time in the self-service customer portal.

Email Hosting Service Agreement

1

Contact, Customer Support

All Email Hosting products include free written support during the specified support hours. Written support requests are made via the self-service customer portal.

Support covers questions about the email infrastructure, delivery issues and account configuration. Special support requests that go beyond the standard services are charged at EUR 19.99 (incl. 19% VAT) per commenced quarter of an hour after prior consultation.

2

Monitored Services

  • IMAP (mailbox access)
  • SMTP (email sending and receiving)
  • Webmail
  • Spam filter and virus scanner
3

Storage and Billing

Each Email Hosting product includes a base storage allocation (pooled storage) shared across all mailboxes of the domain. The current storage amount is determined by the offer information valid at the time of ordering.

If the included storage is exceeded, the additional usage is billed on a usage-based model. The price per gigabyte and month published on itsh.dev at the time of the order is decisive. Billing takes place monthly. Any subsequent change to that price is governed exclusively by § 6 of the General Terms and Conditions.

Current storage usage can be viewed at any time in the self-service customer portal.

If the contract ends during a billing period paid in advance, we refund the fee for the time after the end of the contract pro rata by the day in accordance with § 5.2 of the General Terms and Conditions. Additional storage usage under paragraph 2 incurred up to the end of the contract may be billed and set off against the refund.

4

Mailboxes and Aliases

The customer may create up to 1,000 mailboxes and up to 5,000 aliases and mailing lists on their domain; within these limits no separate fee is charged for additional mailboxes, aliases or lists. The limits protect the platform against abuse. All mailboxes share the available pooled storage.

App passwords allow the use of email clients and third-party applications without sharing the main password. The customer is responsible for the secure storage of their credentials.

5

Sending Limits

Per authenticated user the customer may send at least 500 messages per hour and 2,000 messages per day (contractual sending limit). The limit technically enforced by the platform may be higher; IT-Service Harting may lower it at any time without notice down to the contractual sending limit to protect the platform and deliverability. Messages above the limit in effect are rejected at SMTP level with a temporary error code (4xx) and remain in the customer's email client; they are not lost. The monthly sending quota included in the product is determined by the offer information valid at the time of ordering.

By way of derogation from paragraph 1, reduced sending limits of 30 messages per hour and 100 messages per day per authenticated user apply during the first 30 days from registration of the customer account. The limitation serves to prevent spam being sent from newly created accounts. Messages above these limits are not lost; they are temporarily rejected at SMTP level with a temporary error code (4xx) and remain in the email client. Depending on the client, delivery is retried automatically, otherwise the message simply needs to be sent again. Once the 30 days have elapsed, the limits under paragraph 1 apply automatically; no action by the customer is required. Upon request via the customer portal we lift the limitation early, provided there are no concrete indications of abuse; this applies in particular when migrating existing mailboxes.

If the included quota is exceeded, the additional sending is billed on a usage-based model. The price per additional message published on itsh.dev at the time of the order is decisive. Billing takes place monthly. Any subsequent change to that price is governed exclusively by § 6 of the General Terms and Conditions.

Sending unsolicited advertising (spam), mass emails and newsletters via the email service is not permitted. Sending emails with falsified sender data or disguised sender identity is prohibited. IT-Service Harting is entitled to immediately block customer accounts that violate these provisions.

6

DKIM, SPF and DMARC

For each domain set up in Email Hosting, DKIM signatures, SPF records and a DMARC policy are automatically configured. These settings ensure the authenticity and deliverability of outgoing emails.

The automatically set DNS records for DKIM, SPF and DMARC cannot be changed by the customer. When using external domains, the customer is responsible for the correct configuration of the corresponding DNS records with their DNS provider.

7

Mailing Lists and Delegation

The customer can set up mailing lists for internal communication. Mailing lists distribute incoming emails to all registered members.

Delegation allows assigning individual app passwords and restricted access rights to mailboxes. The customer is responsible for managing delegation rights and controlling delegated mailboxes.

8

Data Backup

All Email Hosting products include daily, weekly and monthly backups of email data. Data is retained for up to 6 months.

Restoration requests can be made via the self-service customer portal or support. The customer is additionally responsible for backing up important emails and data themselves.

9

Prohibited Actions

In addition to the prohibitions stated in § 10 of the General Terms and Conditions, the following is specifically prohibited:

  • Sending spam, unsolicited advertising or phishing emails
  • Falsifying sender data or email headers
  • Using the service as an open mail relay
  • Operating applications for mining cryptocurrencies

Violations may result in immediate suspension of access and termination without notice.

Kubernetes Service Agreement

1

Contact, Customer Support

All Kubernetes products include free written support during the specified support hours. Written support requests are made via the self-service customer portal.

Support covers questions about the Kubernetes infrastructure, but not debugging of customer applications or support for application development. Special support requests that go beyond the standard services are charged, after prior consultation, at EUR 19.99 (incl. 19% VAT) per commenced quarter of an hour.

2

Scope of Service

Namespace: The paid Kubernetes products consist of a dedicated Kubernetes namespace on a shared control plane operated by IT-Service Harting, with fixed resource quotas (vCPU, memory) and an included monthly outbound data transfer (egress) according to the booked plan. The namespace is suitable for development, testing and smaller production environments.

Included: The namespace provides persistent storage through the StorageClasses offered by the cluster (block storage with ReadWriteOnce, NFS storage with ReadWriteMany), connection of the customer's own hostnames through the cluster gateway, and the Container Registry under § 12 of this service agreement. Limits and billing of resources are governed by § 3 of this service agreement.

Not included: Dedicated control planes or worker nodes, managed databases (such as PostgreSQL or Redis) and backup services beyond § 5 of this service agreement are not part of the offer. Databases the customer runs inside the namespace are operated, administered and backed up by the customer on their own responsibility.

3

Resource Limits and Fair Use

Resource usage (CPU, RAM, storage) is limited according to the booked product tier. If the included quotas are exceeded, usage-based billing takes place. The prices for the respective resource published on itsh.dev at the time of the order are decisive. Any subsequent change to those prices is governed exclusively by § 6 of the General Terms and Conditions.

Processes that consume excessive resources and endanger the stability of the infrastructure may be terminated without prior notice. The operation of applications for mining cryptocurrencies is prohibited pursuant to § 10.3 of the General Terms and Conditions.

4

Availability and Maintenance

We aim for network availability of 99% as a monthly average (cf. § 4.3 of the General Terms and Conditions and the Service Level Agreement, which governs measurement, exclusions and credits). Planned maintenance work is announced via the status page.

Updates and security patches are automatically applied by IT-Service Harting. Nodes may be automatically restarted as part of regular maintenance to apply operating system updates.

Important: The customer is responsible for configuring their deployments to be tolerant of node restarts or failures (e.g. through multiple replicas, Pod Disruption Budgets).

5

Data Backup and Recovery

We back up daily the Kubernetes objects of each namespace and, at file system level, the contents of the persistent volumes that are mounted by a running pod at the time of the backup. Volumes not mounted at that time, for example because the associated workload is scaled to zero, paused or deleted, are not included in that backup; the customer keeps workloads whose data is to be backed up running at backup time. We state the daily backup time in the documentation. We retain the daily backups for 30 days. For paid plans we additionally retain a weekly backup for twelve weeks and a monthly backup for six months; the free namespace receives daily backups only. Backups are stored at a second location within the EU.

Backups are taken during live operation and are not application- or database-consistent: for databases and other applications with ongoing writes, a consistent restore point is not guaranteed. The customer remains responsible for their own application-specific backups (such as database dumps). The customer requests a restore from our backups via support; restores are performed at the level of the namespace or of individual persistent volumes.

6

Security and Isolation

Namespace-Tier: Isolation through Kubernetes RBAC and Network Policies within a shared control plane.

All namespaces are operated in ISO 27001 certified EU data centres. SSL/TLS encryption is enabled by default.

7

Access and Management

Access to the Kubernetes cluster is via kubectl with the provided kubeconfig file. The customer is responsible for the secure storage and management of their access credentials.

Root or admin access to the underlying infrastructure (nodes, control plane) is not granted. Changes to the infrastructure are made exclusively by IT-Service Harting.

8

Prohibited Use

In addition to the prohibitions mentioned in § 10 of the General Terms and Conditions, the following are particularly prohibited:

  • Operation of tools for (D)DoS attacks or network scanning of other customers
  • Exploiting security vulnerabilities in the Kubernetes infrastructure
  • Resource abuse that affects the stability or performance of other customers

Violations may result in immediate throttling or blocking of access as well as termination without notice.

9

Free Namespace (Free Tier)

IT-Service Harting offers a free Kubernetes namespace ("Free Tier") intended as a technical evaluation and trial environment.

Resource and Feature Scope
The Free Tier is subject to the following limits: 200 mCPU (equivalent to 0.2 vCPU), 512 MiB memory, 1 GiB persistent storage (exclusively via the NFS-based StorageClass), a maximum of 5 pods, and a monthly outbound network traffic (egress) limit of 10 GiB. A free OCI registry is provisioned alongside the namespace and is limited to 1 GiB of storage and 10 GiB of monthly egress.

Hostnames and Networking
Free Tier namespaces are reachable exclusively under subdomains of the form *.<namespace>.itsh-apps.dev. Custom domains are not available on the Free Tier. Outbound network traffic is restricted to TCP/80 (HTTP), TCP/443 (HTTPS) and UDP/53 (DNS, to designated resolvers); other protocols and ports are blocked.

Availability
The Free Tier is provided without an availability commitment, without a Service Level Agreement and without any entitlement to support. § 4.3 of the General Terms and Conditions as well as the Service Level Agreement do not apply to the Free Tier; service may be interrupted at any time without prior notice.

No Entitlement to the Offer
There is no entitlement to the provisioning, continuation or restoration of a Free Tier namespace. IT-Service Harting reserves the right to amend, discontinue or convert the Free Tier into a paid offering after prior notification (cf. § 4.1 of the General Terms and Conditions).

Testbed for New Features
The Free Tier additionally serves as a testbed for new or not yet generally available features of the ITSH platform. Such features may be made available to, modified within, or removed from the Free Tier without prior notice; there is no entitlement to their availability or continuation.

Intended Use
The Free Tier is intended for evaluation, development, and testing. Use for production or business-critical workloads, or for the processing of third-party personal data, is expressly discouraged; the customer bears sole risk in that regard.

10

Free Tier: Eligibility and Anti-Abuse

Eligibility
Provisioning of a Free Tier namespace requires a registered customer account with successful phone verification. The Free Tier may be claimed once per customer account (one-shot lifetime); after release or closure of a Free Tier namespace, a renewed claim from the same account is not possible. Customers with paid Kubernetes products may additionally claim a single Free Tier namespace alongside their paid resources.

Anti-Abuse Checks
To prevent multiple registrations and automated abuse, technical checks are performed prior to provisioning. These include uniqueness of the verified phone number, exclusion of disposable email providers, request frequency from the same IP network range and, where supplied, uniqueness of the VAT identification number. Further information on the data processed and the legal basis is set out in our Privacy Policy.

Rejection and Manual Review
The check is automated; if it yields a match, provisioning of the Free Tier namespace is refused. If you believe the refusal is incorrect, you may contact service@itsh.dev. We will then have the case reviewed by a member of staff, tell you the outcome, and provision the namespace if the refusal was not justified. The Free Tier may not be combined with promotional credits or discount campaigns.

No Resale or Third-Party Use
The Free Tier may not be resold, sublicensed, used on behalf of third parties, or used as the basis for any service the customer offers to its own customers (no service-bureau, reselling, or timesharing use).

Sanctions and Export Controls
The customer warrants that it is not located in an EU- or OFAC-sanctioned jurisdiction and is not on any applicable restricted-party list. Use in violation of Regulation (EU) 2021/821 or EU sanctions regimes is prohibited.

Investigative Access on Abuse Suspicion
Where IT-Service Harting has reasonable grounds to suspect abuse (in particular matches in reputation services, inbound abuse complaints from third parties, or anomalous egress or claim patterns), IT-Service Harting may technically access namespace contents (pods, logs, persistent volumes) to the extent necessary for investigation. Legal basis: Art. 6(1)(f) GDPR; access is logged.

Geographic Availability
The Free Tier is provided only to requests originating from the European Economic Area, the United Kingdom, Switzerland, the United States, Canada, Australia, and New Zealand. Requests from sanctioned jurisdictions are technically refused. The paid Kubernetes plans are not subject to this geographic restriction.

Payment Method Verification
Where a Free Tier request is assessed as presenting an elevated risk of abuse, provisioning may be made conditional on the verification of a valid payment method. Verification is carried out by way of a zero-amount authorisation via our payment service provider; no charge is made and no recurring payment is set up. The requirement does not apply to the majority of requests, and completing the verification does not affect the free nature of the Free Tier. The specific criteria used to assess risk are not disclosed, in order to preserve the effectiveness of the measure.

Origin of the Request
The Free Tier is intended to be claimed over an ordinary residential or mobile internet connection. Requests originating from cloud, hosting, data-centre, or comparable networks, identified by the network operator (autonomous system) of the IP address used, may be technically refused. This restriction serves to prevent automated and large-scale abuse and does not apply to the paid Kubernetes plans.

11

Free Tier: Suspension, Data Retention and Upgrade Path

Automatic Suspension
Without prejudice to the rights set out in § 3.4 of the General Terms and Conditions, Free Tier namespaces may be suspended automatically if: (a) the monthly egress limit of 10 GiB is reached, (b) no outbound HTTP traffic is observed for 30 consecutive calendar days (inactivity), or (c) abuse signals are present (in particular matches in recognised reputation services, such as PhishTank or comparable public phishing databases, inbound abuse complaints from third parties, or anomalous claim patterns).

Resumption
Where suspension was triggered by the egress limit, the namespace is resumed automatically on the first day of the following calendar month. Where suspension was triggered by inactivity, the customer can resume the namespace via the self-service customer portal; a notification email is sent from day 23 of inactivity. Where suspension was triggered by abuse signals, no automatic resumption takes place; reactivation requires manual review by our team.

Data Retention During Suspension and on Release
During suspension, kubectl access is removed. All pods are terminated and deleted; data stored on persistent volumes (PVCs) is retained until the namespace is released. If the Free Tier namespace is released by the customer (via the "Release" function in the self-service customer portal) or deprovisioned as part of abuse handling, all namespace contents including persistent volumes are permanently deleted. Recovery is not possible thereafter. The customer is responsible for maintaining their own off-platform backups (cf. § 7.4 of the General Terms and Conditions).

Upgrade to a Paid Tier
Upgrading from the Free Tier to a paid Kubernetes tier is available at any time. Existing namespace contents are preserved during the upgrade; existing *.itsh-apps.dev hostnames continue to work after the upgrade.

12

Container Registry

Scope of Service
IT-Service Harting provides an OCI-compatible container registry for storing and serving container images. The registry is part of the Kubernetes offering and not a standalone product. Access is via registry tokens created by the customer in the self-service customer portal; the customer is responsible for their secure storage.

Storage and Billing
The included storage and the included monthly egress are determined by the respective Kubernetes product; for the free namespace, the limits under § 9 of this service agreement apply. If the included storage is exceeded, the additional usage is billed on a usage basis. The price per gigabyte and month published on itsh.dev at the time of the order is decisive. Billing takes place monthly. Any subsequent change to that price is governed exclusively by § 6 of the General Terms and Conditions.

Availability
The container registry is not within the scope of the Service Level Agreement; the credit scheme set out there does not apply to it. The customer's statutory rights remain unaffected.

Data Backup
The registry is a distribution service for container images, not a backup service. There is no claim to restoration of deleted images or tags. The customer keeps the sources required to rebuild their images, in particular build definitions, outside the registry.

Prohibited Use and Suspension
Stored images are subject to § 10 of the General Terms and Conditions; § 8 of this service agreement applies accordingly. In the event of violations, access to the registry may be suspended; the procedure, statement of reasons and right to object are governed by § 10.5 of the General Terms and Conditions.

Deactivation and Deletion
The customer can deactivate the registry in the self-service customer portal. After deactivation, access is blocked; stored images are retained for 30 days and then deleted unless the registry is reactivated beforehand. After the end of the contract, § 13 of the General Terms and Conditions applies.

vServer Service Agreement

1

Contact, Customer Support

All vServer plans include free written support during the specified support hours. Written support requests are made via the self-service customer portal.

Support covers the provisioning of the server, its reachability at the handover point of our network, the functions of the customer portal (in particular the web console, snapshots, firewall rules, plan changes and reinstallation) and setting the reverse DNS record (PTR) for the server’s IPv4 address, where it has one. It does not cover installation, configuration, hardening or troubleshooting inside the guest system. Special support requests that go beyond the standard services are charged, after prior consultation, at EUR 19.99 (incl. 19% VAT) per commenced quarter of an hour.

2

Scope of Service

IT-Service Harting provides the customer with a virtual machine (vServer) with the resources stated for the booked plan (vCPU, memory, disk space, number of snapshots). The offer information valid at the time of the order is decisive. When ordering, the customer selects an operating system image from the images we offer; custom images or ISO files cannot be used.

The service includes one IPv6 network and, where the booked plan includes one, a public IPv4 address (§ 6), a web console with access to the server’s screen and keyboard independent of its network configuration, utilisation graphs for CPU, memory, disk and network, email notifications when the server fails unexpectedly and when a file system is almost full, and firewall rules managed in the customer portal. Traffic is neither metered nor charged. Outbound traffic to port 25 is governed by § 6 paragraph 5.

The vServer runs on a single physical host. Automatic failover to another host and uninterrupted relocation (live migration) are not part of the service; the vServer is not highly available.

The customer can change the plan in the customer portal. The server is shut down and restarted for this. Disk space can only be increased, never reduced; a change to a plan with less disk space is only possible while keeping the existing disk space.

3

Administration and Hardening of the Guest System

Pursuant to § 7.1 of the General Terms and Conditions, the customer holds sole administration rights (root) over the guest system. They install, configure, update and secure the operating system and all applications running on it themselves, at their own cost and risk. This applies in particular to applying security updates, configuring a firewall inside the guest system and managing access credentials (SSH keys, root password). The vServer is not a managed service; we do not monitor or maintain the guest system.

We do not access the guest system. Excepted are actions the customer triggers themselves via the customer portal and that are executed through the guest agent running inside the guest system, in particular installing an SSH key and resetting the root password. Utilisation graphs are measured from outside the server; the almost-full file system notification reads the fill level through the guest agent.

The guest agent is set up by the offered images on first boot, with the exception of Flatcar Container Linux. Without a running guest agent, the actions named in paragraph 2 and the almost-full file system notification are unavailable. We recommend leaving the guest agent installed.

Credentials stored on the server, in particular SSH keys in the authorized_keys file and a root password that has been set, can only be removed or changed inside the guest system itself. Deleting an SSH key in the customer portal has no effect on servers already provisioned.

4

Availability, Maintenance and Host Restarts

We aim for network availability of 99% as a monthly average (cf. § 4.3 of the General Terms and Conditions and the Service Level Agreement, which governs measurement, exclusions and credits). Planned maintenance work is announced via the status page.

Maintenance on the host running the vServer, in particular updates to the host operating system and the virtualisation environment, may require a restart of the host. All vServers on that host are then asked to shut down cleanly via ACPI. A vServer that has not shut down after three minutes is powered off hard. vServers that were running beforehand are restarted automatically once the work is complete. We announce planned host restarts in accordance with the section "Maintenance Windows and Emergency Maintenance" of the Service Level Agreement. Emergency maintenance, for example to close a critical security vulnerability in the host, may be carried out under that section without prior announcement; the interruption is counted against availability.

Important: The customer configures the guest system so that it executes an ACPI shutdown request cleanly and starts its services automatically after a restart. For services that cannot tolerate an interruption, the customer makes their own provisions, for example through redundancy on a second server; high availability of an individual vServer is not owed (§ 2 paragraph 3).

Interruptions initiated by the customer, in particular by stopping, restarting, changing the plan, reinstalling or restoring a snapshot, do not count as downtime.

5

Snapshots and Data Backup

The customer can create snapshots of their server’s disk in the customer portal and restore the server to them; the number follows from the plan. A snapshot captures only the contents of the disk at the time of creation, not the memory. Snapshots reside on the same storage system as the server; a reinstallation or deletion of the server deletes all of its snapshots.

We do not create platform-side backups for vServers within the meaning of § 7.4 of the General Terms and Conditions. Snapshots are not a backup. The customer is solely responsible for regularly backing up data they cannot afford to lose to a location separate from the server. There is no entitlement to the restoration of data, snapshots or a deleted server.

Before a plan change we automatically create a safety snapshot unless the customer opts out. It is removed after a successful change and retained after a failure; it does not count against the plan’s snapshot quota.

6

Network and IP Addresses

Each vServer receives one /112 IPv6 network that is routed to the server in its entirety and, where the booked plan includes one, a public IPv4 address. Additional IPv4 addresses cannot be ordered. Pursuant to § 4.4 of the General Terms and Conditions there is no entitlement to a specific address.

An IPv4 address stays assigned to the server across restarts and reinstallations, and across plan changes as long as the new plan also includes one, and is released when the server is deleted. The IPv6 network is reassigned on reinstallation; the customer adjusts dependent entries, in particular DNS records and firewall rules, themselves.

The server may send traffic only from its own addresses (IPv6 network, IPv4 address where it has one, and link-local addresses) and its own MAC address; other traffic is discarded. The firewall rules managed in the customer portal apply in front of the server; traffic that matches no rule is allowed through, subject to paragraphs 5 and 6. They do not replace the hardening of the guest system under § 3.

Services listening on a port inside the guest system are reachable from the internet over IPv6 and, where the server has one, IPv4 from the first boot unless the customer restricts access themselves.

For customers who ordered their first vServer on or after 26 October 2026, outbound traffic from their vServers to TCP port 25 (SMTP delivery to third-party mail servers) over IPv4 and IPv6 is blocked for three months from that first order. The block applies to all of the customer's vServers, including those ordered later, and is lifted automatically once the three months have passed. Submitting email over the authenticated submission ports 587 and 465, for example to the customer's mail provider, is not blocked. Customers who had already ordered a vServer before 26 October 2026 are not affected by the block, nor are their later servers. The block serves to prevent the sending of unsolicited advertising (§ 10.3 of the General Terms and Conditions); it is not a firewall rule under paragraph 3 and cannot be lifted by the customer themselves.

The customer may request in the customer portal or in text form, briefly stating the intended use, that we lift the block under paragraph 5 early. We decide on the request at our reasonable discretion with a view to preventing abuse and communicate the decision in the customer portal or by email; a refusal does not affect the automatic lifting under paragraph 5. Where there are concrete indications that unsolicited advertising is or was being sent from a vServer of a customer under paragraph 5, in particular complaints from recipients or their providers or the listing of one of the server's addresses on recognised blocklists, we may reinstate the block for all of that customer's vServers even after it has been lifted, for as long as those indications persist. Procedure, statement of reasons and right of objection for such a reinstated block are governed by § 10.5 of the General Terms and Conditions; § 9 remains unaffected.

7

Billing and Termination

The vServer can be booked monthly or with a billing period of three, six or twelve months. The price of a billing period is the monthly price of the plan multiplied by the number of its months. The prices published on itsh.dev at the time of the order are decisive; any subsequent change is governed exclusively by § 6 of the General Terms and Conditions.

With monthly booking, the monthly price of the plan is charged in advance at the time of the order. This payment covers the first month from the moment the server first runs. Thereafter the vServer is billed pro rata at an hourly rate, capped at the monthly price of the booked plan per calendar month and per server. The hourly rate is the monthly price divided by 730. The time in which the server exists is billed, regardless of whether it is running or stopped, because memory, disk space and IP addresses remain reserved for it.

With a billing period of three, six or twelve months, the price of the period is charged in advance at the time of the order. The first period begins at the moment the server first runs. Each period is followed by a period of the same length, whose price is charged in advance at its start. There is no hourly billing.

Not billed are the provisioning period, the time after a failed provisioning and the "Terminated" state under § 8. If a server ultimately cannot be provisioned, billing for it is cancelled in full and we refund the amount paid for it.

With monthly booking, after a plan switch the new hourly rate applies from the moment the switch takes effect; the monthly cap for the entire calendar month follows the plan currently booked. With a billing period of three, six or twelve months, § 5.7 of the General Terms and Conditions applies with the following deviation: On a switch to a higher plan we switch the server over as soon as payment of the difference has been initiated, even if it has not yet been received, for example with a SEPA direct debit; the fee of the new plan applies only from receipt of the payment. If such a payment has failed for a contract of the customer account within the last twelve months, we switch the server over on later switches to a higher plan only once the payment has been received. If the payment fails, the customer may, within 14 days, pay the difference for the remaining time of the period in the customer portal or switch the server back to the previous plan; a payment initiated within this deadline suffices if it is received. If the customer does neither, the contract ends when this deadline expires or, for a payment initiated in time that has not yet been received when the deadline expires, when that payment fails. While a change of the billing period under paragraph 6 is scheduled, a plan switch is not possible.

§ 5.8 of the General Terms and Conditions applies to a change of the billing period, subject to the following: Before the server first runs, a change is not possible. With monthly booking, the change takes effect at the end of the current monthly billing period, but not before the prepaid first month has expired. On a change to monthly booking, paragraph 2 sentences 3 to 5 apply from then on, without a new advance payment; on a change to a period of three, six or twelve months, paragraph 3 sentences 3 and 4 apply, with the price of the first period charged in advance when the change takes effect.

The customer may terminate the contract for a vServer at any time without a notice period. Deleting the server in the customer portal also terminates the contract: the server is deleted immediately, and billing ends with the deletion. If the customer terminates in another way, in particular via the termination button, § 8 paragraph 2 applies to the server. If the contract ends before the end of a prepaid period, § 5.2 of the General Terms and Conditions applies to the refund. § 3.2 of the General Terms and Conditions applies to termination by us.

8

Deletion, End of Contract and Data Export

Deleting a server takes effect immediately and is irreversible. Disk, snapshots and IP assignment are removed; there is no grace period and no recycle bin.

If the subscription ends without the customer deleting the server, in particular because payments have definitively failed, the server is stopped and placed in the "Terminated" state. Disk, snapshots and IP addresses are retained for 30 days; nothing is charged during this time, but the server cannot be started. We notify the customer by email when the server is stopped and again 7 days before the deletion date. On request via support, the server can be returned to operation with all its data within this period once it is billed again. After the period expires, the server is deleted together with its disk and snapshots.

Data export is performed by the customer themselves from the running server via the access they have set up, such as SSH; there is no separate export interface. § 13 of the General Terms and Conditions applies to switching to another provider; during the transition period and the retrieval period we continue to operate the server unchanged unless the customer deletes it first. We charge nothing for the retrieval period.

9

Prohibited Use

In addition to the prohibitions in § 7.2 and § 10 of the General Terms and Conditions, the following in particular is prohibited:

  • Operating tools for (D)DoS attacks or port or network scans against third parties or other customers
  • Operating open mail relays, open proxies or open DNS resolvers
  • Sending traffic with forged source addresses (IP spoofing)
  • Exploiting security vulnerabilities in the virtualisation environment or attempting to break out of the guest system
  • Operating applications for mining cryptocurrencies

Breaches may lead to immediate suspension of the server and to termination without notice. Procedure, reasons and right of objection are governed by § 10.5 of the General Terms and Conditions; § 3.4 remains unaffected.

If we suspend a vServer under paragraph 2 or under § 7.2 of the General Terms and Conditions, it is stopped and cannot be started, reinstalled or restored to a snapshot by the customer; disk, snapshots and IP addresses are retained. Access to the customer portal remains. We lift the suspension once the breach has been remedied and a repetition is not to be expected, or if an objection under § 10.5 of the General Terms and Conditions succeeds. Billing continues under § 7 paragraphs 2 and 3; if the suspension proves unjustified, we charge nothing for its duration. The customer may still terminate the contract under § 7 paragraph 7; § 8 paragraph 2 then applies to the server.

Object Storage Service Agreement

1

Contact, Customer Support

Object Storage includes free written support during the specified support hours. Written support requests are made via the self-service customer portal.

Support covers questions about the provision and reachability of the service and the management of buckets and access keys, but not the configuration of the customer's applications or S3 clients. Special support requests that go beyond the standard services are charged, after prior consultation, at EUR 19.99 (incl. 19% VAT) per commenced quarter of an hour.

2

Scope of Service

IT-Service Harting provides the customer with object storage exposing an S3-compatible API. The customer can create buckets, store, retrieve and delete objects, and manage access keys via the self-service customer portal. Data is stored in EU data centres.

The interface supports the common operations of widely used S3 clients. Compatibility with every feature of the S3 API or with every client is not owed; the supported feature set is stated in the product overview.

The stored data can be exported at any time during the contract term via the S3-compatible interface. That interface is also the export interface within the meaning of § 13.4 of the General Terms and Conditions.

No specific statistical durability figure and no specific storage technology are warranted.

3

Availability and Maintenance

We aim for network availability of 99% as a monthly average (cf. § 4.3 of the General Terms and Conditions and the Service Level Agreement, which governs measurement, exclusions and credits). Planned maintenance work is announced via the status page.

There is no entitlement to specific endpoint addresses. We may change endpoint addresses for technical or operational reasons after prior announcement with reasonable notice.

4

Storage, Limits and Billing

Storage consumption is billed on a usage basis. The price per gigabyte and month published on itsh.dev at the time of the order is decisive, as is, where stated there, the price per volume of data transferred (egress). Billing takes place monthly. Any subsequent change to these prices is governed exclusively by § 6 of the General Terms and Conditions.

Current consumption can be viewed at any time in the self-service customer portal. Limits on the number of buckets, object size and request rate are determined by the offer information valid at the time of ordering.

Request patterns that endanger the stability or performance of the infrastructure or of other customers, in particular sustained excessive request rates, may be throttled. Throttling is lifted as soon as the endangerment ceases. § 3.4 of the General Terms and Conditions remains unaffected.

5

Data Backup

Object Storage is a storage service, not a backup service. To protect against the failure of a location, we copy the stored objects once a day to a second, geographically separate location within the EU. The copy is not synchronous with the primary location, serves solely the operational resilience of the platform and does not replace a backup. The customer has no claim to restoration of individual objects, buckets or earlier object states.

Under § 7.4 of the General Terms and Conditions, the customer remains responsible for their own backup of their data, kept separately from the platform. Storing backup copies in Object Storage is permitted; in that case the customer ensures that the backed-up data does not exist exclusively in Object Storage.

6

Public Buckets and Content

Buckets are not publicly accessible when provisioned. The customer can flag buckets as public; the objects stored in them are then retrievable over the internet without authentication. The decision to make content publicly accessible rests solely with the customer.

The customer is responsible for the content they store and in particular for the content they make publicly accessible. § 10 of the General Terms and Conditions applies without restriction.

Where there are indications of unlawful publicly accessible content, we are entitled to block public access to the affected bucket or to individual objects. The procedure, the statement of reasons and the customer's right to object are governed by § 10.4 and § 10.5 of the General Terms and Conditions; § 3.4 remains unaffected.

7

Prohibited Use

In addition to the prohibitions stated in § 10 of the General Terms and Conditions, the following is specifically prohibited:

  • Storing or distributing malware
  • Providing content for phishing or comparable deception
  • Using the service as a distribution point for content that infringes third-party rights

Violations may result in immediate suspension of access and termination without notice.

8

End of Contract, Data Export and Deletion

Switching to another provider, the transition period, the retrieval period after the end of the contract and the subsequent deletion are governed by § 13 of the General Terms and Conditions (provider switching and data portability). Data export takes place via the S3-compatible interface.

After the retrieval period expires, we delete the stored objects. In replication and backup systems, complete deletion may, for technical reasons, lag by up to 30 days; during this time the data is protected against access and is not otherwise processed. The obligations under the data processing agreement remain unaffected.

Domain Service Agreement

1

Domain Registration

IT-Service Harting acts as an intermediary between the customer and the respective registration authority in domain registration. There is no entitlement to allocation of a specific domain (cf. § 4.2 of the General Terms and Conditions).

The customer is responsible for checking whether the desired domain violates the rights of third parties (in particular trademark, name or identification rights). IT-Service Harting does not carry out any such check.

2

Allocation Guidelines

For the registration and management of domains, the respective allocation conditions of the competent registration authorities additionally apply. This includes in particular:

  • DENIC eG for .de domains
  • ICANN-accredited registrars for generic TLDs (.com, .net, .org, etc.)
  • National registration authorities for country-specific TLDs (.at, .ch, .eu, etc.)

The customer undertakes to comply with the applicable guidelines in each case. The current conditions can be viewed on the websites of the respective registration authorities.

3

Holder Data and WHOIS

The customer is obliged to provide correct and complete holder data (registrant data). This is a requirement of ICANN and other registration authorities. Changes to the data must be notified within 14 days in accordance with § 2.3 of the General Terms and Conditions.

WHOIS privacy protection is offered for supported TLDs, insofar as this is permitted by the respective registration authority.

4

Domain Transfer

Domains are equipped with a transfer lock by default to prevent unauthorised transfers. This can be deactivated by the customer in the self-service customer portal.

For transfer to another provider, an AuthCode (authorisation code) is required, which can be requested via the self-service customer portal. The AuthCode is valid for 30 days. The customer is responsible for initiating the transfer with the new provider.

5

DNS Management

All domains include complete DNS management via the self-service customer portal. 26 different DNS record types are supported (including A, AAAA, CNAME, MX, TXT, SRV, CAA).

The customer is responsible for the correct configuration of their DNS records. IT-Service Harting assumes no liability for malfunctions resulting from incorrect DNS configurations.

6

Contract Term, Termination and Registration Period

6.1 The domain contract is concluded for an indefinite period and may be terminated by the customer at any time; the termination takes effect one month after its receipt (§ 3.2 of the General Terms and Conditions).

6.2 Registration period
This is distinct from the registration period at the registry. Depending on the TLD it is usually twelve months, and we acquire it from the registry in advance and irrevocably on ordering and on each renewal. The domain remains active until the end of each paid registration period.

6.3 Pricing
The price of a domain consists of the fee that the registry or our registrar charges us for the respective registration period (registration fee) and our markup. The markup is the amount by which the price agreed at the conclusion of the contract exceeds the registration fee applicable at that time; it is fixed at the conclusion of the contract and does not change through later changes of the registration fee. If the registry or our registrar changes the registration fee, the price of the domain changes by exactly the amount of that change, for increases and decreases alike; for consumers plus the VAT attributable to the amount of the change (§ 5.1 of the General Terms and Conditions). We notify the customer of an increase of the registration fee in text form at least six weeks before it takes effect, and of a decrease no later than when it takes effect. The notice states the amount of the change, its reason, the previous and the new price and the day it takes effect; the changed price applies to registration periods beginning on or after that day. If we learn of an increase less than six weeks before the start of a registration period, it applies only from the following one. The change takes effect without the customer's consent; consent is not deemed given. If the price increases, the customer may terminate the domain contract in text form with effect from the day the change takes effect; we point this out in the notice. For domain contracts concluded before this version applies to them, the day from which this version applies to the domain contract replaces the conclusion of the contract for determining the markup; the price applicable to the domain on that day and the registration fee applicable on that day are then decisive. Other price changes for domains are governed by § 6.2 of the General Terms and Conditions.

6.4 Refunds
If the contract ends during a running registration period, we refund fees paid in advance on a pro-rata basis. This does not apply to the fee for the registration period itself insofar as the registry does not refund it to us; we acquired that period irrevocably and cannot return it. The value remains with the customer: the domain continues to the end of the paid period and can be transferred to another provider by AuthCode at any time until then. We delete a domain early only on the customer's express instruction.

6.5 Verification of registrant data
We are required by § 49 BSIG to maintain accurate and complete registration data. To that end the customer verifies the e-mail address and telephone number of the registrant contact before registration, within 30 days of any change to that data, and for imported domains within 90 days of import. The procedure is described in our NIS2 guidelines.

6.6 Consequences of failed verification
If verification is not completed by the deadline, we may suspend the domain; a suspended domain no longer resolves, and the website, email and other services under the domain are then not reachable. A suspension imposed for missing verification is lifted as soon as verification is completed. For the duration of a suspension for which the customer is responsible, the agreed remuneration remains payable, because the registration period at the registry continues unchanged. If verification remains outstanding for more than 60 days after the deadline, we may terminate the contract for good cause and release the domain.

6.7 Objection
The customer may object to a suspension within 14 days in text form. We review the objection and communicate the result with reasons within seven working days.

6.8 After the contract ends, the domain is released in accordance with the rules of the competent registry.

7

Dispute Resolution

Domain disputes (e.g. due to trademark infringements) are handled according to the procedures of the competent registration authority. For generic TLDs, the Uniform Domain-Name Dispute-Resolution Policy (UDRP) of ICANN particularly applies.

IT-Service Harting is not a party to domain disputes between the customer and third parties and does not assume any mediator role.