Terms of Service

1. Introduction

1.1 Definition of the Company and identification details

Konet, hereinafter referred to as the “Company”, is a provider of internet services such as web hosting, domain name registration, SSL certificates, email services, cloud backup, servers and other advanced solutions. The Company's activities are carried out by Konet, established in Greece, at Stefanou Veldemiri 5, Sykies, 56625, Thessaloniki, Tax ID (VAT No.) 153133759, Tax Office: E' Thessalonikis, General Commercial Registry (G.E.MI.) No. 134646304000, contact telephone 2310501800. These Terms and Conditions govern the use of the Company's website, located at konet.gr, hereinafter referred to as the “Website”, and the services it provides.

1.2 Acceptance of the Terms of Service by the Customer

By browsing the Website or using any service provided by the Company, users unconditionally accept the Terms and Conditions set out in this document, as they may be amended in the future. If any user or user representative does not accept these terms, they must leave the Website and refrain from using the Company's services.

1.3 Definitions of Customer and service users

For the purposes of these Terms, users of the Website and the services, whether they have completed orders or are simply browsing the Website, shall be referred to as “Customers/Customer”. This terminology applies to all natural and legal persons.

1.4 Compliance with Greek and European law

The Company undertakes to operate in accordance with applicable Greek and European legislation, providing high-quality services, protecting the personal data of its Customers and respecting the moral standards, customs and traditions of Greece, as well as the principles and doctrine of the Orthodox Christian Faith.

1.5 Communication channels and notices

The Company officially communicates with the Customer and delivers updates or notices (technical, contractual, billing, etc.) through:
a) the Client Area, and
b) corporate email addresses ending in @konet.gr.

Notices are deemed to have been received by the Customer: (i) at the time they are posted in the Client Area, or (ii) at the time they are sent to the Customer's contact email address as declared from time to time. The Customer must regularly monitor the Client Area and their email, keep their contact details up to date and ensure that messages from @konet.gr are received (e.g. filter/antispam settings, whitelisting), in accordance with 3.1.

For security reasons, the Company will never ask for passwords or 2FA codes by email or any other channel. In the event of a suspicious message, the Customer must communicate through the Client Area (see Chapter 9).

Technical posts/updates may be affected by the availability and maintenance provisions (see 2.2). Matters of liability/compensation are governed exclusively by 2.4.

2. Liability of the Company

The provisions of Chapter 2 apply to all services and prevail in the event of conflict with specific provisions of other chapters, unless expressly provided otherwise (e.g. as provided in a Service Level Agreement).

2.1 Disclaimer of warranties

The Company makes every possible effort to provide high-quality services. However, to the extent permitted by applicable law, the services are provided “as is” and “as available”, without any express or implied warranty of fitness or merchantability, and without any warranty of a specific level of availability or performance, unless expressly provided in a Service Level Agreement (SLA). The services are used at the sole responsibility of the Customer, who must assess whether the services meet their business or technical requirements. Any availability guarantees are governed exclusively by the terms of Chapter 4. The statutory rights of consumers are not affected.

2.2 Availability, maintenance and force majeure

The Company may carry out scheduled or emergency maintenance work, at its reasonable discretion, to ensure the quality and security of the services. During such work the services may be temporarily unavailable. For scheduled work, the Company makes reasonable efforts to give prior notice through the Client Area or by other appropriate means. For emergency work, advance notice may not be possible.

The Company makes reasonable efforts to restore service in cases of malfunction, without a guaranteed restoration time. Unavailability or degradation of services caused, in whole or in part, by events beyond the Company's control does not constitute a breach of obligation. Examples include: extensive failures or faults of third-party networks, power outages, large-scale cyberattacks, natural disasters, pandemics, terrorist acts, wars or other cases of force majeure.

Where a Service Level Agreement is expressly provided, the terms of Chapter 4 apply exclusively to any credits or special arrangements. No availability credits are provided for services without an express SLA.

2.3 Security and Customer responsibility for data

The Customer is solely responsible for the integrity, confidentiality and availability of the data they store or transfer through the services. The Customer must implement appropriate organizational and technical measures, such as strong and unique passwords, enabling 2FA where available, role-based access restriction, regular software updates, encryption at rest and in transit, and maintaining and regularly testing independent backups outside the platform. Responsibility for the use of login credentials and for the actions of the Customer's users is also governed by 3.2.

The Company provides its infrastructure at platform level and does not undertake to control or curate the Customer's content. The more specific technical policies on backups, email and usage limits are set out in Chapter 8. The processing of personal data is governed by the Privacy Policy.

For any specialized data protection or advanced backup services, the specific terms of the respective services apply and prevail in the event of conflict. Matters of liability or compensation are governed exclusively by 2.4.

2.4 General limitation of liability

To the maximum extent permitted by applicable law, the Company is not liable for indirect, incidental, special or consequential damages, including, by way of example and without limitation, loss of profits, revenue, reputation/clientele (goodwill), data, interruption of work, penalties or fines imposed by third parties, or interruption of business activities, regardless of whether the claim is based on contract, tort or any other legal basis.

The Company's total liability for any claim relating to a specific service is limited to the total amount paid by the Customer for that specific service during the last two months before the incident. Multiple claims arising from the same event or from a series of related events are deemed to be a single claim.

The Customer is obliged to take all reasonable measures to mitigate any damages. Failure to mitigate reduces any liability of the Company accordingly. The Customer may not set off claims without the prior written consent of the Company.

The above limitations do not apply in cases of willful misconduct or gross negligence and do not affect the statutory rights of consumers. Where an express Service Level Agreement is provided, the exclusive remedy is defined by Chapter 4.

2.5 Lawful access and compliance with authorities

The Company may access files, data and other content hosted on its infrastructure only when this is required by applicable law or following a lawful and duly substantiated request from the competent authorities. Examples include public prosecutor orders, judicial or administrative requests, complaints of illegal or harmful activity, or compliance audits.

In each such case, access and any disclosure are limited to the strictly necessary and proportionate information, following a legality check and in compliance with internal procedures, with appropriate documentation. Where not prohibited by law or by the competent authority, the Company makes reasonable efforts to inform the Customer of the relevant request in a timely manner.

The processing of personal data, including record keeping and transmission to authorities, is governed by the Company's Privacy Policy. Any technical work to collect, extract or preserve information for the purposes of investigations is carried out in accordance with the procedures and charges provided in the specific incident sections of Chapter 8.

2.6 Compliance and infrastructure protection audits

The Company may carry out periodic or targeted audits to protect the integrity of the platform, prevent abuse and enforce the Terms of Service and the Acceptable Use Policy. These audits are carried out on the principles of necessity and proportionality, by authorized personnel and/or automated security systems, and do not constitute general or continuous monitoring of content.

As a rule, technical signals and metadata are used (e.g. indicators of malicious activity, traffic anomalies, signs of spam/malware). Customer content is accessed when there are indications of a breach of the terms or suspicious/illegal activity, or when required by law or following a lawful request from a competent authority, in accordance with 2.5. Data is handled confidentially, the necessary actions are logged and internal approval procedures are applied.

Where permitted by law or the competent authority, the Customer is informed through the Client Area or by other appropriate means about the audit and any necessary technical actions. In urgent cases, advance notice may not be possible.

The processing of personal data in the context of audits is carried out in accordance with the Privacy Policy (for example: legal basis, minimum necessary, record keeping, retention periods). Any measures/sanctions against services or accounts (e.g. restriction, quarantine, suspension) are applied as specifically provided in 8.13, while investigation, remediation or forensics work and the related charges are governed by 8.26.

By using the services, the Customer grants the necessary authorization for the above audits, within the limits and with the safeguards described here and in the Privacy Policy. Matters of liability and compensation are governed exclusively by 2.4.

2.7 Customer responsibility for the quality, legality and technical suitability of hosted material

The Customer bears sole responsibility for the accuracy, legality, quality and overall suitability of the material they host on the Company's infrastructure. The Customer declares that they hold all required rights, licenses and consents for the use, reproduction and public display of their content and that it does not infringe the rights of third parties or applicable law.

Material uploaded by the Customer must be ready for use, compatible with the supported environments and must not require curation or further processing by the Company. The Customer must ensure that their content or code does not contain malware or functions that degrade or disrupt the services, and that it complies with the limits and technical policies of Chapter 8 (for example: resources, inodes/disk space, email/anti-spam, backups, application compatibility).

The Company is not obliged to pre-screen or curate the Customer's content. Without prejudice to the compliance and infrastructure protection audits of 2.6 and the lawful access of 2.5, the Customer is obliged, upon notice through the Client Area or by other appropriate means, to remove, modify or replace without delay any material that breaches the terms or creates an operational risk. In urgent cases, temporary technical measures may be taken in accordance with 8.13, while any investigation/remediation work is governed by 8.26.

Matters of liability or compensation are governed exclusively by 2.4.

2.8 Backup policy and Customer obligations

The Company keeps periodic operational backups for business continuity and recovery purposes. The availability, frequency and retention history of backups are defined per service in the respective technical specifications and policies. Backups are provided as a convenience and are neither a guaranteed service nor a substitute for the Customer's own backups. For services without an express SLA, there are no guaranteed RPO or RTO targets.

The Customer is solely responsible for maintaining up-to-date, independent backups of their data outside the platform and for testing their restore. Storing personal backups within the hosting account is not permitted, as defined in the technical policies of Chapter 8, including local backup files created by installation tools or similar archive files. The specific prohibitions and limits are set out in 8.22.

Upon request, the Company may restore from an available backup, provided one exists and is usable, with reasonable effort and without a guaranteed completion time. The Customer accepts that any recent changes may not be included in the backup and that the restore may affect the current state of the data or the service. Any restore or investigation work is governed by the respective procedures and charges described in 8.26.

Upon expiry or termination of a service, the lifecycle and deletion provisions of Chapter 8 apply, including any post-expiry retention periods as defined in 8.24. The Company may amend its backup policies for reasons of security or operational efficiency. Where appropriate, prior notice is given through the Client Area or by other appropriate means.

Matters of liability or compensation relating to data loss or data restore are governed exclusively by 2.4.

2.9 Third-party supplier services and limitations/changes

Certain functions or features of the services are provided through third-party suppliers or rely on third-party infrastructure/software. For those functions, the technical specifications, policies and terms of the respective suppliers apply, and the Customer must comply with them. Any specific terms per service are set out in the relevant chapters (for example: Domain Names in Chapter 5, SSL in Chapter 6, email/filtering policies in Chapter 8), and the list of sub-processors and the terms of personal data processing are described in the Privacy Policy.

The Company may, at its reasonable discretion, replace, upgrade or cease cooperation with specific third-party suppliers, and change interconnection points, server names, IP addresses, certificates or other integration parameters. Where a change has a material effect on the Customer's use of the service, the Company makes reasonable efforts to give prior notice through the Client Area or by other appropriate means. In urgent cases or for security/compliance reasons, immediate changes may be required without notice. Matters of availability and force majeure are governed by 2.2.

The Customer is responsible for making, in a timely manner, the required adjustments arising from changes by third-party suppliers, such as, for example, DNS settings, SPF/DKIM/DMARC updates, whitelists/firewall rules, upgrades of software or add-ons, changes to API keys or connection parameters, and testing for proper operation after the changes. Any costs or expenses of compliance/adjustment are borne exclusively by the Customer.

For services covered by an express Service Level Agreement, any compensation due to impact from third-party suppliers is limited to what is defined in Chapter 4. As a general rule, matters of liability or compensation are governed exclusively by 2.4.

2.10 Access and management through the Control Panel - disclaimer

The Company provides the Customer with access to, and basic instructions for using, the Management Environment (Control Panel, e.g. cPanel, Plesk or other) for self-service and management of their services. The Control Panel is not a managed environment service, and the Company does not undertake to maintain the Customer's code, application settings or content.

The Customer is responsible for the actions they perform through the Control Panel, for the correct configuration of their services based on the instructions and for the security of their credentials. For account security rules, the use of strong passwords and 2FA, 3.2 applies. Matters of availability, maintenance and force majeure are covered by 2.2, while matters of liability and compensation are covered by 2.4.

The Company may, at its reasonable discretion, upgrade, change or restrict functions of the Control Panel, and modify integration settings or interfaces, for reasons of security, compliance or improvement. Where a change has a material effect on the Customer's use, reasonable efforts are made to give prior notice through the Client Area or by other appropriate means. In urgent cases or for security matters, immediate changes may be required without notice.

More specific technical policies relating to the Control Panel, such as the use of installation tools, application compatibility and supported environments, are described in Chapter 8, in particular in 8.22 and 8.23.

2.11 Scope of service support and exceptional additional assistance

The Company provides basic platform-level support for the services it offers (for example: access and basic configuration through the Control Panel as per 2.10, service activations/settings, technical checks of infrastructure operation). The procedure, communication channels and any response/escalation time limits are defined in Chapter 9, and communication takes place through the Client Area or by other appropriate means.

The following are not included in the scope of basic support, unless expressly provided in a specific contract or offer:

• customizations or fixes of code/themes/add-ons (e.g. PHP, JS, CSS, CMS),
• installation, configuration or maintenance of third-party applications not provided by the Company,
• application-level performance/security optimizations, SEO, campaigns or analytics/pixel settings,
• migrations, malware cleanups, content restores beyond what is provided in the backup policies,
• any work that exceeds the technical limits and the compatibility/support policies of Chapter 8 (for example 8.22–8.23).

Exceptionally, and at its reasonable discretion, the Company may provide additional assistance outside this scope, subject to express agreement with the Customer. Such assistance does not constitute a managed service, is provided “as is” and is governed by the applicable charges/procedures of 8.26 or by a separate offer/contract. Compliance with the policies/terms of third-party services is governed by 2.9.

Instructions, suggestions or recommendations provided in the context of support are informational in nature and do not replace the Customer's responsibility for their settings and choices. Matters of liability or compensation relating to support are governed exclusively by 2.4.

2.12 Log files (logs)

The Company keeps log files solely for the purposes of security, proper operation, compliance or incident investigation. The reasonable retention period of these files, as well as the related technical policies, are determined exclusively by the Company, which is the sole body competent to judge their necessity and duration, always limited to what is strictly necessary in accordance with the GDPR and applicable law.

3. Customer Obligations

3.1 Accuracy of information and obligation to keep it up to date

The Customer must enter true, complete and up-to-date account, billing and contact information (for example: full name/company name, Tax ID and Tax Office where required, address, telephone, a valid contact email, authorized contact persons). Any change must be declared without delay through the Client Area or by other appropriate means made available by the Company.

Official communication and notices take place as defined in 1.5 (Client Area and emails ending in @konet.gr). The Customer must ensure the continuous accessibility/monitoring of the contact details they have declared.

When the Customer acts on behalf of a legal person, they declare that they have the relevant authority and that the details of the legal person and its authorized representatives are accurate and up to date. Where it considers it necessary, the Company may request documentation to verify information, in accordance with the compliance audits of 2.6 and the Privacy Policy.

Specific accuracy/formatting requirements for information connected with particular services (for example: holder/WHOIS details for domain names, verification requirements for SSL certificates) are defined in the respective service chapters (Chapter 5 and Chapter 6).

Consistency note: Any measures due to incomplete or inaccurate information are applied as defined in Articles 2.6 and 8.13. Matters of liability/compensation are governed exclusively by 2.4.

3.2 Account security, 2FA and confidentiality of credentials

The Customer must protect access to their accounts and services and keep all credentials confidential (for example: passwords, API keys, SSH keys, recovery tokens, application passwords). The Customer is obliged to use strong and unique passwords, avoid reusing them on other systems, apply periodic change/deactivation (rotation) when required or when compromise is suspected, and use secure storage tools (e.g. a password manager). The same applies to credentials created within the Customer's applications. The minimum technical specifications for passwords/keys and the related instructions are posted in the Client Area and/or in the Company's documentation.

The Company will never ask for your password or 2FA codes. Do not share them, and report suspicious requests immediately through the channels of Chapter 9.

Enabling Two-Factor Authentication (2FA) is mandatory where it is made available by the Company or required for security reasons. The Customer must keep their verification details (e.g. email/telephone) up to date, store recovery codes securely and be aware that resetting/bypassing 2FA may require identity verification procedures. The Company may make 2FA mandatory at any time for specific services or categories of users.

Credentials may not be shared with or used by unauthorized persons. The Customer may designate authorized users/sub-accounts with appropriate roles/permissions through the Client Area. The actions of authorized users are deemed to be actions of the Customer. The Customer must periodically review permissions, disable access that is no longer needed and keep their contacts up to date (see 3.1). For access via SSH, the specific terms of 8.18 also apply.

In the event of loss, leakage or suspected unauthorized use of credentials, the Customer must notify the Company within 48 hours through the support channels (see Chapter 9) and immediately change/revoke the credentials and check their devices/applications, with updates provided through the Client Area and/or from @konet.gr email addresses, in accordance with 1.5. The Company may apply appropriate technical protection measures as defined in 2.6 and 8.13 (for example: forced password changes, session invalidation, access restrictions, temporary suspension). Investigation, remediation or forensics work, where offered, is governed by the procedures and charges of 8.26. Matters of lawful access/disclosure of data are covered by 2.5.

The Customer expressly accepts that the Company bears no liability for damages or losses arising from unauthorized access to or compromise of their accounts due to inadequate protection, negligence or failure to comply with the above obligations.

Matters of liability or compensation relating to account security are governed exclusively by 2.4.

3.3 Acceptable use and consequences of violations

The Customer must use the services solely for lawful purposes, in accordance with Greek and European law, these Terms and the specific policies of each service. In addition, the Customer complies with the terms and policies of any third-party providers on which the services depend (for example: domain name registries, SSL certificate authorities, antispam/CDN providers), as defined in 2.9.

The following are prohibited, by way of example:

• a) storing, distributing or linking to illegal or harmful content, or infringing intellectual/industrial property,
• b) breaches of privacy/personal data and unlawful processing,
• c) sending unsolicited communications or abusive use of email (see 8.12, 8.17, 8.20, 8.21),
• d) attempts to breach security, scanning/exploiting vulnerabilities without permission, distributing malware, C2/booters,
• e) fraud, phishing, spoofing, misleading practices or use of false information,
• f) abusive consumption of resources, circumvention of technical limits, running processes that degrade the platform or networks (for example: uncontrolled automations, crypto-mining, open relays/proxies), in breach of the technical policies/limits of Chapter 8,
• g) using the services as a repository/backup storage outside the applicable policies (see 2.8 and Chapter 8),
• h) load testing or penetration testing without prior written permission from the Company.

The Customer is responsible for the actions of the users they authorize or the sub-accounts they create (see 3.2). Resellers are also responsible for the compliance of their end customers, in accordance with 8.29. The Customer cooperates in good faith with the Company in investigating complaints or incidents and in remedying their effects (e.g. removal/modification of content, change of credentials), in accordance with 2.6.

In the event of a violation, appropriate technical and administrative measures are applied in accordance with 2.6 and 8.13 (for example: recommendations/notices through the Client Area, restrictions, quarantine, temporary suspension or termination of services, notification of the competent authorities where required under 2.5). Measures/updates are communicated in accordance with 1.5 (Client Area and @konet.gr emails), unless there are reasons of urgency or legal restrictions. Investigation/remediation work or incident handling charges are governed by 8.26. Matters of liability/compensation are governed exclusively by 2.4, while matters of expiry/deletion of services are governed by 8.24.

3.4 Access to and use of the Client Area

Maintaining an active account in the Client Area requires that the Customer has at least one (1) active hosting service (Hosting or Server) or, alternatively, at least ten (10) active domain names registered with the Company.

Otherwise, if the Customer has fewer than ten (10) active domains and no active hosting service, access to domain management through the Client Area is disabled. Management is then carried out only upon the Customer's written request, which is executed manually by the Company, within a reasonable time and in accordance with the applicable procedures and charges.

The Company reserves the right to revise the above limits and conditions for reasons of security, stability or operational organization, without any obligation to pay compensation.

3.5 Requests concerning the services

Requests concerning the management, modification or cancellation of services (for example: domain names, hosting, SSL certificates, email accounts, upgrades/downgrades) are accepted exclusively from the registered owner of the customer account in the Client Area.

The Company is not obliged to accept or carry out requests submitted by third parties, regardless of any capacity or ownership right they may have (e.g. even if the requester is the registered domain holder or the website owner). Only requests originating from the registered account owner in the Client Area are processed.

All requests are processed strictly and exclusively through the Client Area. Requests submitted by other means (for example: by telephone or from unregistered email addresses) are ignored and/or referred for resubmission through the Client Area.

3.6 Account access recovery

Access to the Client Area belongs exclusively to the registered account owner.

Requests to recover access (such as a password reset or a change of login details) are considered only if they originate from the registered owner themselves and only through the Client Area. For security reasons, the Company may require additional identification procedures (for example: documents or verification via 2FA).

4. Service Level Agreement (SLA)

4.1 Availability targets

The Company sets the following service availability targets:
(i) For Shared services (Web, Managed WordPress, Managed WooCommerce) / Semi Dedicated / Reseller, a target of 99,9% availability per calendar month and per service.
(ii) For VPS / Dedicated, a target of 99,9% monthly network availability in the data center and, where applicable, service availability at node/VM level.

For the purposes of this Agreement, “availability” means the ratio of actual uptime to the total time of the month in question, as derived from the Company's monitoring systems. The SLA applies only if the Customer maintains an active service with no overdue balances, complies with the applicable Terms of Service and the Acceptable Use Policy, and none of the exclusions of Article 4.4 apply. This Agreement covers exclusively the core hosting service. Domains, SSL, licenses, additional services and third-party add-ons are excluded. The method for calculating credits and the more specific exclusions are set out in 4.3 and 4.4.

4.2 Incident reporting procedure and availability measurement

The Customer reports unavailability incidents exclusively through the Client Area (ticket), in accordance with Article 1.5 on official communication channels. Exceptionally, if the Client Area is not accessible, the initial report may be sent by email to the Company's declared contact details, with the obligation to submit a ticket within 24 hours of access being restored.

For the purposes of this Agreement, “downtime” means the complete unavailability of the covered service for at least 5 consecutive minutes, as determined exclusively by the Company's monitoring systems. Measurements or snapshots from third-party services do not constitute evidence of downtime.

The Company is the sole party competent to certify the occurrence and duration of downtime, based on its own monitoring systems and log files, and its findings are binding for the application of the SLA unless a manifest error is proven. The Company may combine incidents that are related in time or technically into a single event for measurement and credit purposes. Discrepancies between the timestamps of the Customer's systems and the Company's systems are not taken into account. Partial performance degradation that does not amount to complete unavailability is not considered downtime.

Each incident report must include (a) the service identifier, (b) the period during which unavailability allegedly occurred, and (c) any evidence the Customer has. The Customer is obliged to cooperate by providing reasonable information and authorizations for the investigation. In the event of non-cooperation, the Company is entitled not to examine the report further.

Scheduled and/or emergency maintenance is handled in accordance with Article 4.4. The calculation of availability and any credits are governed by 4.1 and 4.3.

4.3 Availability credit policy

If, in a calendar month, the availability of a service falls short of the targets of Article 4.1, the Customer may receive a time credit as the exclusive remedy, under the following conditions and terms:

a) Availability is calculated as defined in Articles 4.1 and 4.2.
b) The credit applies only to the core hosting service of the specific contract and is applied as an extension of the subscription period, without any refund or other compensation.
c) The Customer must submit a request by ticket within 14 days of the last related downtime incident, stating the service identifier, the alleged time period and any evidence. Late or incomplete requests are rejected.
d) A credit is granted on condition that the Customer maintains an active service with no overdue balances and has not violated the Terms of Service or the Acceptable Use Policy. The Company may require reasonable cooperation and access for verification.
e) The provisions of Article 4.2 apply to the combination of related incidents and to timestamp matters.
f) Credits are granted within 60 days of approval of the request and are used in subsequent billing cycles or as an extension of the service term. The Company may set off the credit against any claims it has against the Customer.

Credit scale
For each service, per calendar month:
• 97% to 99,9% monthly availability: a credit of 50% of the monthly charge for that service.
• Below 97% monthly availability: a credit of 80% of the monthly charge for that service.
The total amount of credits per service and per month may not exceed 100% of the service's monthly charge. Credits are not cumulative across months and are not transferable.

Excluded charges and services
Credits do not cover and are not calculated on: domain names, SSL, software licenses, acquired IP addresses, additional resources or add-ons, third-party services, or bank/transaction fees, interest, payment commissions, taxes and duties. Downtime exclusions that do not give rise to a right to credit are defined in 4.4.

Exclusivity of remedies
The granting of a credit as described above is the Customer's sole and exclusive remedy for failure to meet the availability targets of Article 4, without any further liability of the Company, subject to the general limitation of liability of Chapter 2.

4.4 SLA exclusions and circumstances that do not constitute downtime

No right to credit arises, and the following do not constitute “downtime” within the meaning of Articles 4.1–4.3:

a) Scheduled maintenance work and emergency security interventions (for example: software updates, vulnerability patches, kernel updates/reboots, infrastructure changes, migrations), when announced in a timely manner where feasible or carried out immediately for security reasons.

b) Force majeure events or exceptional incidents beyond the Company's reasonable control (see 2.2), including DDoS attacks beyond reasonable defense capabilities, and extensive failures of upstream network/power providers or infrastructure operators.

c) Failures of third parties or external dependencies: the Customer's networks/access providers, DNS not managed by the Company, Cloudflare/other third-party CDNs or WAFs, naming/registry services, third-party email platforms, app stores, payment providers, as well as recipient filters/policies affecting email delivery (deliverability).

d) Responsibility or actions of the Customer or their authorized persons: incorrect settings (e.g. of applications, CMS, plugins, .htaccess), excessive resource consumption or rate limiting triggered by their usage, code/database errors, software incompatibility, failed upgrades.

e) Suspensions/restrictions due to outstanding balances, breach of the Terms of Service/Acceptable Use Policy/Good Content Policy or abusive/illegal use (including cases of spam, phishing, malware, infringement of rights).

f) Partial degradation of performance or functions that does not amount to complete unavailability of the service, as defined in 4.2 (threshold of 5 consecutive minutes).

g) Waiting times due to the Customer's lack of cooperation (e.g. failure to provide access, information or authorizations) or to incorrect/incomplete incident reports.

h) Administrative/regulatory actions: requests/orders of authorities, court decisions, notice-and-takedown procedures, legal obligations or compliance requirements (e.g. GDPR, copyright).

i) Backups/restore: unavailability of restore windows, delays in executing a restore, or inability to recover due to incomplete/outdated backups or incorrect choices made by the Customer in the self-service environment, in accordance with the backup policy.

j) Domain name matters: expiry/suspension/transfer/misconfiguration of a domain or DNS by the Customer, delays of registries/registrars or third-party policies (domains are not covered by the availability SLA).

k) Third-party services/add-ons: software licenses, additional resources, IPs, modules or third-party services that are not part of the core hosting service.

The Company is the sole party competent to determine whether an event falls within the above exclusions and to establish any effect it has on availability and credits. The Company's findings are binding for the application of the SLA, as defined in 4.1–4.3, unless a manifest error is proven. The general limits of liability of 2.4 apply.

4.5 Scheduled and emergency maintenance - Infrastructure changes

The Company is entitled to carry out maintenance, upgrades, security updates and infrastructure changes that are necessary for the stability, security and performance of the services. Such work does not constitute downtime and does not give rise to a right to credit, in accordance with 4.4.

a) Notice and work windows. Where feasible, the Company informs the Customer in advance through the Client Area and/or by email:

• at least 24 hours in advance for routine maintenance work,
• at least 7 days in advance for extensive work that may require a brief service interruption or migration.
• Work may take place within defined maintenance windows, preferably outside peak hours. In cases of urgent need or security risk, work may be carried out without notice.

b) Changes to parameters. The Company may change settings or versions of the software and services of the hosting environment (for example: PHP, web server, database, modules, cPanel, OS/kernel, anti-malware, WAF, security policies, nameservers, IP addressing) when this is required for reasons of security, compliance, performance or compatibility.

c) Customer obligations. The Customer must:

• keep their contact details up to date,
• monitor announcements in the Client Area,
• take their own backups before significant changes to their own software,
• adapt their application to changes in protocols or versions,
• lower the DNS TTL before a scheduled migration, if requested,
• verify the operation of their application after the work is completed.
• Failures of the Customer's applications, plugins, themes or customizations are not the responsibility of the Company.

d) Timing and grouping. The Company is the sole party competent to determine the timing, classification and grouping of related work into a single maintenance cycle, and to postpone or cancel scheduled work for operational or security reasons.

e) Relationship with the SLA. The work under this Article is expressly excluded from the availability calculation and the granting of credits under Articles 4.1–4.3. For force majeure circumstances and the general limitation of liability, 2.2 and 2.4 apply respectively.

f) Specific hardware replacement times. Any equipment replacement times or special clauses concerning VPS/Dedicated are governed by Chapter 8 and are not the subject of this Article.

4.6 Relationship with Other Terms - Scope, Exclusivity and Amendments

For the scope of the services covered by the SLA and for downtime exclusions, Articles 4.1–4.4 apply, and in particular 4.1 and 4.4.
The exclusive remedy and the method/terms of granting it are defined in Article 4.3, subject to Articles 2.2 (force majeure) and 2.4 (limitation of liability).

In the event of conflict between this Chapter 4 and other terms, the specific provisions of Chapter 4 prevail with respect to availability and credits, while in all other respects the general terms of Chapters 1–3 and the specific terms of Chapter 8 apply.

The Company may amend this Chapter 4 for reasons of security, compliance, operational needs or service improvement, with notice through the Client Area. Unless otherwise specified, amendments take effect from their posting and, where required for billing transparency, from the next billing cycle. Continued use of the services after the notice constitutes acceptance of the amendments.

Any credit or extension granted by the Company on an exceptional basis does not constitute a waiver of rights or an amendment of this Agreement, nor does it create a customary right for future cases.

4.7 Request procedure and deadlines

The Customer submits a credit request exclusively by ticket in the Client Area, in accordance with 4.2 and 4.3, within 14 days of the last related downtime incident. Late or incomplete requests are rejected. The required details of the request and the method of calculating the credit are governed exclusively by 4.2 and 4.3. The Company is the sole party competent to certify the occurrence and duration of downtime based on its systems, and its findings are binding for the application of the SLA, unless a manifest error is proven.

4.8 Interpretation, exclusions and relationship with other Terms

For the definition and measurement of downtime, the exclusions and the credits, Articles 4.1–4.6 apply exclusively. In the event of conflict with other provisions, the specific provisions of this Chapter 4 prevail with respect to availability and credits, while in all other respects the limitation of liability of 2.4 and the force majeure provision of 2.2 apply. For the exclusivity of the remedy, Article 4.3 applies in conjunction with Article 4.6.

Important Clarification

This SLA fully describes the obligations and guarantees of the Company. Any other claim or compensation beyond what is provided in this Agreement is not recognized by the Company.

5. Domain Name Services

5.1 General provisions on domain names

The Company provides domain name registration, renewal, transfer and management services, acting (i) as an accredited .GR and .ΕΛ domain name registrar of the Internet Names Registry of the Hellenic Telecommunications and Post Commission (EETT), with Registrar Registry No. 15-069, and (ii) as an intermediary through partner registrars for .CY and all other TLDs. By submitting an order, the Customer fully and unconditionally accepts the applicable regulations of the competent Registry, including any future amendments, as well as the related dispute resolution policies.

The completion of a registration/renewal/transfer is subject to the approval of the competent Registry. Availability checks are indicative and do not bind the Registry. The allocation policy is first-come-first-served. The Company does not guarantee the successful execution of requests that depend on third parties, nor is it liable for rejections/delays/changes caused by the Registries or their policies.

The Customer must provide accurate, complete and up-to-date holder/contact details and comply with WHOIS/registrant information requirements. Inaccurate details or non-compliance may result in suspension, rejection of a request or cancellation by the Registry and/or the Company, without liability on the part of the Company. Responsibility for third-party rights (e.g. trademarks, trade names, intellectual/industrial property) rests exclusively with the Customer, who declares that the use of the domain name does not infringe the rights of third parties.

Every domain order is prepaid on the same day in accordance with Chapter 10. Amounts paid for domains are non-refundable in any case where the request has been forwarded to the Registry, with the exception, specifically for .GR/.ΕΛ, of the option of revocation within five (5) days of the initial assignment, in which case any amounts are credited to the Client Area. There is no cash refund. Any grace/redemption periods and restore fees are defined per extension and are stated on the presentation page of each extension.

DNS/nameserver settings and activations may require a reasonable propagation time (DNS propagation), which depends on third-party access/network providers and is not under the Company's control. The Company is not liable for delays or service interruptions caused by DNS/Registries/third-party providers or by incorrect settings made by the Customer.

For .GR/.ΕΛ, the EETT Regulations apply. For .CY and all other TLDs, the rules of the respective Registries/partner registrars apply. For gTLDs, the ICANN policies apply (e.g. registrant rights/obligations, dispute resolution mechanisms). Details of the procedures (registration, transfer, WHOIS, changes of details, rejections/suspensions) are set out in Articles 5.2–5.4.

5.2 Registration and payments by bank deposit/other methods

Registration/renewal/transfer requests for domain names are executed only after final confirmation that the relevant payment has been credited, as more specifically defined in Chapter 10 (payments/invoicing). The Company issues “Billing Statements” (through WHMCS), which serve as a pro forma invoice, before the expiry, purchase or renewal of each service. The order is prepaid on the same day so that it can be forwarded to the competent Registry.

Accepted payment methods: Stripe (subscription where applicable), Alpha Bank (one-time), PayPal and bank deposit. For immediate registration, methods with immediate confirmation are recommended (card/Stripe, Alpha Bank one-time, PayPal). A bank deposit may involve a delay in matching/confirmation (especially outside banking days/hours) and does not reserve the requested name. Sending proof of deposit by ticket does not replace final confirmation that the payment has been credited.

All bank charges/deductions are borne exclusively by the Customer. Transaction currency: EUR. For VAT, invoicing, deadlines and failed payments, Chapter 10 applies exclusively.

The Customer is obliged to enter accurate and complete details. If acting on behalf of a third party, the Customer must declare the third party as the holder and may declare their own details as the technical/administrative/billing contact for notices. Inaccurate details or non-compliance may result in suspension or rejection by the Registry and/or the Company (see 5.3–5.4).

Prices and availability may be changed by the Registries. In cases of “premium”/special pricing or a price change before/during execution, the Company informs the Customer to obtain their consent. In the absence of consent, the order is canceled and any amounts are credited to the customer account (credit). Final registration is subject to confirmation by the Registry (see 5.1).

The Company may suspend/temporarily refuse execution until payment/identity is verified in cases of indications of fraud, non-payment or breach of terms, subject to 5.10. Delays or failures caused by banks/payment providers are not the responsibility of the Company. Untimely confirmation does not secure priority.

Amounts paid for domains are non-refundable from the moment the request is forwarded to the Registry. Specifically for .GR/.ΕΛ, revocation within five (5) days applies, with a credit to the Client Area and without a cash refund (see 5.1 and Chapter 10).

References: 5.1 (status/confirmation of Registries, .GR/.ΕΛ exception), 5.3–5.4 (correction/transfer of holder, Registry/ICANN regulations), 5.10 (refusal/suspension), Chapter 10 (payments/invoicing/VAT/refunds).

5.3 Transfer/correction of details and Registry procedures

a) General. After a domain name has been assigned, any change of details is carried out in accordance with the rules of the competent Registry and, where applicable, the ICANN policies, as in force from time to time (see 5.4). The Company acts as an intermediary and is not liable for rejections/delays caused by Registry/ICANN rules or actions of third parties.

b) Correction of details without a change of holder. Non-material corrections (e.g. contact email/telephone/address) are made through the Client Area. Substantive changes that alter the identity of the holder may be considered a “change of holder” by the Registry and follow a specific procedure. The Customer is obliged to keep the details accurate and up to date (see 5.4).

c) Change of holder (registrant change).
– .GR/.ΕΛ: a transfer application is required in accordance with the Registry rules, together with payment of any fees.
– gTLDs/other TLDs: a change of holder may require confirmations (e.g. by email) and may result in temporary transfer restrictions/locks, where applied by the Registry/ICANN.
All related fees and obligations are borne by the Customer.

d) Documentation & authorization. The Company may request identification/legal representation documents or express authorization for changes of details/holder. In the event of conflicting instructions between the holder and the other contacts (admin/tech/billing), the holder's instruction prevails. If the Customer acts on behalf of a third party, they are obliged to have valid authorization and to declare the third party as the holder (see 5.2).

e) Effects on transfers - locks. Changes to holder/WHOIS details or verification procedures may result in temporary restrictions (e.g. clientTransferProhibited/locks) or waiting periods, where applied by Registries/ICANN. The Customer must take the above into account when planning transfers.

f) Special cases (succession on death, corporate changes). In the event of the holder's death or corporate changes (e.g. merger/transfer of business/succession), legal proof may be required (e.g. court/administrative acts, corporate documents). The Company may apply a “freeze/hold” until the checks are completed, without liability for any interruptions.

g) Errors/typos after assignment - IDN/Punycode. Corrections to a misspelled domain name are not possible after assignment. A new registration is required, if the name is available. For IDN/Greek characters and Punycode, the technical restrictions of the Registries apply. The Customer is responsible for checking the correct form/rendering before ordering.

h) Registry procedures and deadlines. The exact procedures, deadlines and any fees for correction of details/change of holder are defined per extension by the Registries and/or the ICANN policies and are set out on the presentation pages of each extension. In the event of conflict, the Registry rules prevail (see 5.4).

i) Fees - financial terms. The related fees for correction/transfer/identity checks are borne by the Customer and may vary by extension or Registry decision. For payment methods/invoicing/VAT, Chapter 10 applies. Non-refundable amounts for domains are governed by 5.1 and Chapter 10.

j) Exclusions of liability. The Company does not guarantee the successful completion of a correction/transfer when it depends on verifications, locks, Registry/ICANN rules or actions of third parties, nor is it liable for deadlines/delays beyond its control. The Customer is responsible for the accuracy/legality of the details and for the timely submission of documentation.

5.4 WHOIS and accuracy of holder details

a) Obligation of accuracy and updating. The Customer declares that all holder and contact details (administrative, technical, billing) are complete, accurate and current, and updates them without delay whenever they change. At the request of the Company and/or the competent Registry, the Customer is obliged to provide appropriate supporting evidence (e.g. proof of identity/legitimation documents) for verification. Non-compliance may result in suspension, cancellation or non-execution of requests.

b) Verification of details. The Customer completes in a timely manner every verification procedure requested by the Registries/ICANN/the Company, including, by way of example, email confirmation and any identification by telephone/documents. Failure to complete it may result in temporary suspension until compliance.

c) Obligation to respond to correction/documentation requests. In the event of indications of inaccuracy, unavailability or falsification of details, the Customer must respond within the reasonable deadline set by the Company/Registries. The Company, at its discretion and based on the evidence provided, may judge the sufficiency of compliance and maintain temporary measures (e.g. “hold”) until the matter is finally remedied.

d) WHOIS Privacy/Proxy services (if provided). Privacy/proxy coverage concerns the public display of details and does not constitute legal anonymity, nor does it remove the obligation to provide true details to the Company and the Registries. Details may be disclosed following a lawful request from a competent authority or under administrative procedures (for example UDRP/URS) or in cases of abuse/non-payment. Breach of the privacy/proxy terms results in suspension of the service.

e) Registration/action on behalf of a third party. When the Customer acts for a third party (natural/legal person), they must declare the third party as the holder and may designate their own details as the technical/administrative/billing contact upon written authorization. The Customer assumes sole responsibility and the obligation to indemnify the Company for any third-party claim arising from inaccuracies/omissions or lack of authorization.

f) Compliance measures and sanctions. In the event of non-compliance with the above, the Company may, at its discretion and/or in application of Registry/ICANN rules, impose, for example: temporary or permanent “ClientHold/RegistrarHold”, “TransferProhibited/UpdateProhibited”, suspension of privacy/proxy, rejection or cancellation of change/transfer requests, up to and including deletion in accordance with the applicable regulations. These actions do not give rise to any right to compensation.

ICANN information links (rights/responsibilities & disputes):
• Registrant Information (Registrant Rights/Responsibilities).
• Uniform Domain Name Dispute Resolution Policy (UDRP).

5.5 Data protection and usage restrictions

a) Account and credential security. The Customer is obliged to ensure the confidentiality of the account credentials and the integrity of the declared contact email. Enabling two-factor authentication (2FA) where available, and changing passwords regularly, is expressly recommended. Disclosing or transferring credentials and/or EPP/AuthInfo codes to unauthorized persons is prohibited. Any action carried out with valid credentials is presumed to originate from the Customer, unless the Customer proves otherwise with sufficient documentation.

b) Channels and identity checks. Requests concerning domain names (e.g. WHOIS/DNS changes, transfers, issuing EPP codes) are submitted exclusively by ticket in the Client Area, with the possibility of additional verification (e.g. identification/legitimation documents). The Company will never ask for full card details or EPP codes by plain email/telephone/unauthorized channels.

c) Contact email and receipt of notices. The Customer must maintain an active and accessible email address, preferably one that does not depend on a domain name under management. Spam filters, full mailboxes or inability to access the email are not the responsibility of the Company and do not release the Customer from their obligations (e.g. renewals, responses to verifications - see 5.2, 5.3, 5.4).

d) Protection of sensitive payment data. Sending full payment card details or other sensitive data by email/ticket is prohibited. Payments are made exclusively through the integrated providers listed in Chapter 10. The Company may reject or delete messages/tickets containing sensitive data for security reasons, without liability.

e) System usage restrictions. Automated access (bots/scripts) without written approval, scraping/harvesting of data (including WHOIS/zones), circumvention of security mechanisms, and vulnerability/penetration testing without prior written consent are prohibited. Using the Client Area or the domain tools for activities that violate the law, Registry/ICANN regulations or these terms is prohibited. The Company may apply rate limits, technical measures and/or temporary access restrictions.

f) Anti-fraud checks and temporary measures. In the event of indications of fraud, abuse, unauthorized access or breach of terms, the Company may impose protective measures (for example: ClientHold/RegistrarHold, Transfer/Update Prohibited, temporary suspension of request execution), request KYC/additional documents, or refuse/suspend transactions as more specifically defined in 5.10.

g) Responsibility for third parties/representatives. When the Customer authorizes third parties (for example, partners/agents) to act on their account, the Customer remains solely responsible for their actions and for their compliance with these terms. Conflicting instructions between the holder and the other contacts are resolved as defined in 5.3(d).

h) Indemnity clause. The Customer undertakes to indemnify, defend and hold harmless the Company and its partners against any claim, damage or expense arising from a breach of the security obligations/usage restrictions, from abusive or illegal use of the system/services or from actions of authorized third parties on the Customer's account.

5.6 Renewal, grace period and expiry

a) General. Timely renewal of domain names is the sole responsibility of the Customer. The expiry date/time is determined by the respective Registry and may differ from the Customer's local time zone (e.g. UTC, DST). Notices/reminders are sent as a convenience and do not constitute a guarantee, see 5.5(c).

b) Renewal procedure. Renewal starts only after final confirmation that the relevant payment has been credited, as more specifically defined in Chapter 10. The Company may invoice and/or attempt renewal earlier than the expiry date, where this is required by Registries/TLD policies (for example, up to ten (10) days before). Payment failure or untimely confirmation means that the renewal is not carried out, without liability on the part of the Company.

c) Automatic renewal (auto-renew). Where available, the auto-renew function requires an active payment method and a sufficient balance/limit. Enabling it does not guarantee renewal. Failed charges or rejection by the payment provider/Registry result in non-renewal. The Customer must check the auto-renew setting and the validity of the payment methods.

d) Grace period (grace). After expiry, a grace period may apply where and as provided by the Registry. The existence, duration and terms of the grace period differ per extension and it may not be provided at all. Renewal within the grace period is not guaranteed and requires full payment and acceptance by the Registry. Specific provisions per extension are set out on the TLD presentation pages and/or in 5.4.

e) Status and services after expiry. After expiry, the name may be placed in parking by the Registry/registrar, or nameservers/zones may be modified for technical/administrative reasons, resulting in interruption/degradation of services (website, email, etc.). The Company is not liable for the consequences of these practices imposed by third parties (Registries/providers).

f) After the grace period. If renewal is not completed within any grace period, the name may enter a redemption period or other stages before deletion, in accordance with the rules of each TLD. The restore procedure and fees are governed by 5.8.

g) Transfers close to expiry. Transfers close to expiry may be delayed or may not result in an extension of the term, in accordance with Registry/ICANN rules. The Customer must plan in good time and take into account locks/windows resulting from previous changes of details (see 5.7–5.9).

h) Prices and special categories. Price changes by Registries/registry operators may apply before/at renewal. Premium or reserved names are subject to special pricing/terms. The Company gives notice of any differences and, in the absence of consent, cancels the renewal and credits any amounts to the customer account (credit), subject to Chapter 10.

i) Exclusions of liability. The Company does not guarantee successful renewal when it depends on Registries, payment providers or actions of third parties, nor is it liable for time zone differences, processing delays or rejections based on TLD/ICANN rules.

5.7 Domain transfers and EPP codes

a) Scope and definitions. Domain name transfers are divided into transfers between registrars (inter-registrar) and transfers within the same registrar (intra-registrar). The procedures and conditions are defined by the competent Registries and/or the ICANN policies, as in force from time to time (see 5.4).

b) Conditions for transfer to/from the Company (for example).
– Name status: unlocked/transfer lock removed, no registry/client holds where applicable.
– TAC/EPP/AuthInfo code: valid and recent, issued exclusively through the Client Area after identification (see 5.5).
– Contact email: active and accessible (preferably not dependent on the name under management) for confirmations.
– WHOIS/privacy: any privacy/proxy services may be disabled or modified for confirmation/procedural purposes, where required by Registries/ICANN (see 5.4(d)).
– Time restrictions: windows may apply (e.g. within 60 days of registration or change of holder) where provided by Registry/ICANN policies.
– Expiry/stages: transfers close to expiry or in redemption/pending delete may not be permitted or may require additional fees/steps (see 5.6, 5.8).

c) Procedure. The transfer is initiated by the new registrar (gaining registrar), using the TAC/EPP, is completed within the deadlines set by the Registries/ICANN and is subject to any confirmations/notices they require. During the transfer, the nameservers/DNS usually remain as they are, unless otherwise set after completion.

d) Lawful grounds for refusal/suspension. The Company and/or the respective registrar/Registry may lawfully refuse/suspend a transfer in cases provided by Registry/ICANN policies, such as, for example: a court/administrative order, UDRP/URS proceedings, indications of fraud, pending verification of details or change of holder, active locks/holds, redemption/pending delete status, or failure to meet procedural requirements. The Company may apply temporary protective measures (e.g. hold) until the checks are completed, subject to 5.10.

e) Issuing the EPP/Authorization Code.

The TAC/EPP/AuthInfo code is issued to the Customer exclusively through the Client Area, after an identity check and, where required, written authorization. Only in the case of .GR and .ΕΛ domain names, the Authorization Code is issued by the new Registrar through the DACoR mechanism (see e-1). The Company may temporarily refuse/delay issuing it in cases of indications of fraud, outstanding balances/identity checks, legal/regulatory obligations or locks, as defined in 5.10.

Customers who do not have an active account in the Client Area (for example, due to a small number of domain names under management) are obliged to submit a request exclusively by ticket in the Company's support system. A ticket can be submitted even without an existing account. In any case, the Company executes a request to issue an Authorization Code only upon a recorded request (ticket) and completed identification of the requester as the holder or the lawfully authorized representative of the holder of the domain name. The Company may request proof of identity/legitimation (for example: identity card/passport, authorization, Government Gazette (FEK)/articles of association for legal persons) before processing. Requests by plain email, telephone or other unrecorded channels are not accepted.

e-1) Self-service Authorization Code request (DACoR) for .GR/.ΕΛ - Data logging

i. Description of the procedure. Specifically for .GR and .ΕΛ domain names (as well as the second-level .com.gr, .net.gr, .org.gr, .edu.gr), an Authorization Code (EPP/AuthInfo Code) is issued exclusively through the DACoR (Domain Authorisation Code Request) mechanism of the Internet Names Registry. Customers who have an active account in the Client Area may submit a request to issue an Authorization Code directly through self-service, by selecting the “Request EPP Code” function on the domain name management page, without needing to submit a ticket or contact the support department. Customers without an account in the Client Area submit a request exclusively by ticket, as defined in 5.7(e).

ii. The DACoR mechanism. Once the Customer submits the request:

• (a) The Company automatically forwards a DACoR request (dacor:issueToken) to the Registry via the EPP protocol.
• (b) The Registry sends an email to the declared email address of the Registrant (holder) of the domain name, containing a unique link (URL) with a security token.
• (c) The link remains active for a period of six (6) hours from sending.
• (d) The Registrant follows the link and the Authorization Code is generated automatically by the Registry. The code consists of sixteen (16) alphanumeric characters and is valid for fourteen (14) calendar days.
• (e) The Authorization Code is automatically invalidated after each successful change of Registrar or renewal of an expired name within fifteen days.

iii. Sole responsibility of the Registrant. The Authorization Code is sent exclusively to the Registrant's declared email address, as registered with the Registry (WHOIS/registrant email). The Company does not receive, store or disclose the Authorization Code. The Registrant must keep the declared email address active and accessible. Otherwise, any inability to receive the code is not the responsibility of the Company (see 5.5(c)).

iv. Logging and processing of DACoR request data. For reasons of security, fraud prevention, internal auditing and compliance with the Company's obligations as an accredited Registrar (Registry No. 15-069), every request to issue an Authorization Code through DACoR is recorded in a dedicated audit log. The data recorded include, for example:

• (a) Customer details: account identifier (Client ID), full name and email address, as held in the customer management system.
• (b) Technical connection data: IP address, user agent (browser), session identifier (session ID).
• (c) Request details: full domain name, extension (TLD), date and time of submission.
• (d) Information on the current status of the domain name: current Registrar, status, expiry date, as retrieved through the Registry's WHOIS REST API at the time of submission.
• (e) Request outcome: EPP result code, result message, success/failure indication.

v. Legal basis for processing. Logging is carried out:

• (a) For the performance of contractual obligations towards the Customer (GDPR, Art. 6(1)(b)).
• (b) For compliance with legal obligations arising from the EETT Regulation on the operation of Registrars (GDPR, Art. 6(1)(c)).
• (c) For the purposes of the Company's legitimate interests, in particular the prevention of abuse, documentation of transactions and protection of legal claims (GDPR, Art. 6(1)(f)).

vi. Retention period. The audit log data are retained for a period of three (3) years from the date of recording, or for such longer period as is required for compliance with legal/regulatory obligations or for the establishment/exercise/defense of legal claims.

vii. Data subject rights. The Customer may exercise the rights of access, rectification, restriction of processing, portability and objection as set out in the Company's Privacy Policy and the General Data Protection Regulation (EU) 2016/679 (GDPR). Requests are submitted by ticket in the Client Area or to the email address dpo at konet.gr. Since the logged data are necessary for the Company's compliance with its legal obligations as an accredited domain name Registrar (EETT Regulation, electronic communications legislation, obligations to keep transaction records), the right to erasure (Art. 17 GDPR) cannot be exercised for the DACoR audit log data, in application of the exception of Art. 17(3)(b) GDPR (compliance with a legal obligation) and Art. 17(3)(e) GDPR (establishment, exercise or defense of legal claims). The data are retained for the entire retention period defined in paragraph (vi) and are deleted automatically after it has elapsed.

viii. Exclusions of liability. The Company is not liable for:

• (a) Delays or failures in the sending/receipt of email from the Registry to the Registrant caused by spam filters, a full mailbox, an inactive/incorrect email address or technical failures of third parties.
• (b) Failure to complete the procedure because the six-hour (6-hour) activation time limit of the link has elapsed.
• (c) Unauthorized use of the Authorization Code after it has been issued to the Registrant.
• (d) Actions, changes or restrictions imposed by the Registry or other third parties.

ix. Abuse. In the event of indications of abuse of the self-service function (for example: repeated requests without a reasonable purpose, requests from unauthorized persons, or in combination with indications of unauthorized access to the account), the Company may restrict or temporarily suspend the ability to submit requests, as defined in 5.10, and inform the Customer by ticket. In addition, the Company reserves the right to notify the Internet Names Registry (ICS-FORTH/EETT) as well as any competent authority (for example: the Hellenic Data Protection Authority, public prosecutors, the Cyber Crime Division) of the reported abuse, providing those bodies with all the recorded audit log data, including identity details, technical connection data and request history, without prior notice to the Customer where this is justified by the seriousness or urgency of the abuse.

x. Relationship with other provisions. The provisions of this subsection do not affect the general transfer provisions (5.7 a–d), the security obligations (5.5), the option of authorized issuing of a code upon ticket/identification (5.7 e), or the Company's rights of refusal/suspension (5.10). For domain names other than .GR/.ΕΛ (gTLDs, .CY, other ccTLDs), the Authorization Code is issued in accordance with the rules of the respective Registry/registrar and the provisions of 5.7(e).

xi. Applicable regulations. The DACoR procedure is governed by the provisions of the Regulation on the Management and Assignment of .GR/.ΕΛ Domain Names (EETT) and the technical specifications of the DACoR system as in force from time to time. In the event of conflict between this provision and the regulations of the Registry/EETT, the latter prevail.

f) Financial terms. Transfers are subject to fees, which are borne exclusively by the Customer. Some Registries apply an automatic renewal with the transfer, and the related costs are added to the transfer fees. Any amounts owed to previous registrars are not the responsibility of the Company. For payment methods/invoicing/VAT, Chapter 10 applies.

g) DNS, visibility and operation during the transfer. The Company is not liable for any interruptions/changes in the operation of services (website, email) resulting from DNS/nameserver changes made by the Customer or third parties during or after the transfer procedure. It is recommended that transfers be scheduled outside peak periods/critical business operations.

h) Special categories/extensions. For .GR/.ΕΛ, the rules of the competent EETT Internet Names Registry apply. For .CY, the special manual procedures of the competent authorities apply. Details per extension are set out in 5.4 and 5.11–5.13, as well as on the extension presentation pages on the Company's Website. In the event of conflict, the rules of the Registries/ICANN prevail.

i) Exclusions of liability. The Company does not guarantee the successful completion of a transfer when it depends on Registries, previous registrars, payment providers or identification procedures/locks, nor is it liable for delays/rejections beyond its control.

5.8 Deletion, restore and related fees

a) Definitions - distinction from “expiry”. “Deletion” differs from “expiry” (expiration). After expiry, some TLDs apply a grace period and/or a redemption period. Final deletion occurs after completion of the stages defined by the respective Registry (see 5.6). For gTLDs, a Redemption Grace Period (RGP) of ~30 days must, at a minimum, be offered, in accordance with the ICANN ERRP policy.

b) Specifics per extension (for example)
– gTLDs (.COM, .NET, etc.): After expiry, a “grace” window may apply, followed by an RGP of ~30 days. The RGP is followed by a “pending delete” stage, during which restore is not permitted. The exact deadlines/stages are defined by the Registry/ICANN.
– .GR/.ΕΛ: The EETT Internet Names Registry provides a period of 15 days after expiry for renewal by the holder. The remaining procedures (suspensions/deletions) follow the EETT/Registry Regulation. The exact mechanisms and deadlines are defined exclusively by EETT/the Registry.
– .EU/.CY and other ccTLDs: Specific rules apply per Registry, including special recovery/revocation windows or eligibility requirements.

Indicative TLD comparison table

*The above costs are indicative. The exact fees and deadlines may vary by Registry/ICANN and are stated in the Company's price list in force from time to time.

c) Restore request procedure. Restore requests are submitted exclusively by ticket in the Client Area by the holder or a lawfully authorized representative. The Company may request KYC/identification/legitimation documents before forwarding the request to the Registry. The restore starts only after prepayment of all related fees (restore fees + renewal fees) and is not a guaranteed service, as it depends exclusively on the rules/availability of the Registry. If the permitted window has passed, the name cannot be reactivated (see 5.6–5.7).

d) Fees and refunds. Restore fees and any related Registry fees are prepayable and non-refundable from the moment the request is forwarded to the Registry. If the restore is not possible for reasons relating to the Registry (e.g. outside the window/policy), any amounts that have not been paid to third parties are credited to the Customer's account, without any right to a cash refund, in accordance with Chapter 10 (payments/invoicing/VAT). In any case, third-party fees (e.g. bank/payment fees) and administrative costs are not refunded.

e) Technical consequences - DNS/zones/parking. After expiry and/or deletion, the Registries/registrars may apply REGISTRY-HOLD/CLIENT-HOLD and/or parking on third-party nameservers, with the result that the zone (website/email) does not work. A restore does not imply recovery of previous DNS settings. The Customer must check/restore nameservers/zones after completion.

f) Lawful grounds for refusal/impossibility of restore. The Company and/or the Registry may lawfully refuse or not permit a restore in cases such as, for example: court/administrative orders, pending UDRP/URS proceedings, inaccurate WHOIS/unverified details, breach of terms or expiry of the relevant windows (e.g. RGP/pending delete). In such cases, the Company may apply protective measures (e.g. hold) until the final decision (see 5.4, 5.7, 5.10).

g) Final deletion - available for re-registration. After completion of the stages defined by each Registry, the name is permanently deleted and may become available for re-registration by a third party, possibly through “drop”/auction procedures provided by the operators. The Company bears no liability for any re-registration by third parties or for the commercial practices of Registries/expired name markets.

h) Customer actions - responsibility. The Customer must: (i) monitor the expiry date (see 5.6), (ii) submit a restore request in good time within the windows provided by the Registry, (iii) prepay the related fees and (iv) recheck DNS/zones after any restore. Delays/failures caused by Registries/payment providers/third parties are not the responsibility of the Company.

5.9 Registration/renewal failures and Customer responsibility

a) Scope. This Article governs cases in which a registration or renewal request is not successfully completed by the competent Registry, through no fault of the Company, as well as the consequences/actions that follow. Final execution is always subject to the approval of the Registry (see 5.1).

b) Indicative causes of registration failure. A registration may fail, for example, due to:
(i) untimely/non-final confirmation of payment (see Chapter 10, 5.2), (ii) a premium/reserved/prohibited name or Registry eligibility policies, (iii) inaccurate/incomplete holder/contact details or failed verifications (email/KYC) (see 5.4), (iv) conflict of rights/distinctive titles or pending proceedings (e.g. UDRP/URS), (v) technical restrictions/errors (EPP outages, rate limits, registry maintenance), (vi) DNS/IDN restrictions (e.g. punycode, unsupported characters).

c) Indicative causes of renewal failure. A renewal may fail, for example, due to:
(i) a delay in payment being credited or a failed auto-renew charge (see 5.6, Chapter 10), (ii) locks/holds or pending verifications/changes of holder (see 5.3–5.4), (iii) price/policy changes by the Registry (premium status), (iv) expiry of grace windows or renewal restrictions for specific TLDs (see 5.6).

d) Notification and remedy procedure. In the event of failure, the Company informs the Customer by ticket and, where feasible, provides remedy instructions. The Customer must respond within the deadline set in the ticket, providing any required documents (e.g. identification/legitimation). Depending on the case, the Customer may choose:
(i) resubmission of the request after the cause has been remedied, (ii) an alternative extension/name (different TLD/variant), or (iii) a credit of any amounts not paid to third parties, in accordance with Chapter 10. Success is not guaranteed. It depends on the rules/availability of the Registry.

e) Financial settlement. Third-party fees (Registries, payment providers), bank charges and administrative costs are not refunded. Amounts that have not been paid to third parties are credited to the Customer's account (credit), without a cash refund, subject to Chapter 10. Special provisions for .GR/.ΕΛ (5-day revocation with credit) apply exclusively as set out in 5.1.

f) Anti-fraud, chargebacks and protective measures. In the event of indications of fraud/abusive behavior or a reversal/dispute of a transaction (chargeback), the Company may impose a temporary hold/suspension/cancellation of requests and/or cancel a name where Registry rules permit, subject to 5.10. Any related cost/damage is borne by the Customer.

g) Technical/third-party causes - exclusions of liability. Delays/failures due to EPP/registry outages, scheduled maintenance, rate limiting, Registry policies, DNS propagation or actions of third-party providers are not the responsibility of the Company. Failure to receive email notices (due to spam/a full mailbox/an inaccessible email) does not release the Customer from their obligations (see 5.5(c)).

h) Customer responsibility. The Customer is obliged to: (i) provide accurate/up-to-date details and complete validations (see 5.4), (ii) prepay in good time in accordance with Chapter 10, (iii) monitor expiry dates/windows and any locks (see 5.3, 5.6–5.7), and (iv) comply with Registry/ICANN rules.

5.10 Right of refusal, suspension or cancellation by the Company/Registries

a) General principle. The Company reserves the right, at its sole discretion, to refuse, suspend, restrict or cancel the provision of any service relating to domain names when there is a legal, regulatory or contractual reason, and/or when this is required by the competent Registries or other third parties.

b) Indicative grounds for refusal/suspension/cancellation. Without limitation, the following cases constitute grounds for intervention:

• Illegal or abusive use of a domain name or related services (e.g. breach of law, misleading practices, breach of personal data, violation of morality).
• Security/malicious activity: sending bulk unsolicited communications (spam), phishing, distributing malware, operating botnets, DNS abuse, attacks.
• Infringement of third-party rights: trademarks, intellectual/industrial property, personality rights.
• Inaccurate or unverifiable holder/contact details (WHOIS), refusal or failure to complete verifications, or non-compliance with correction/documentation requests.
• Default on financial obligations: late prepayment, failed charges, bank returns, chargebacks.
• Indications of fraud or abusive behavior, impersonation, lack of lawful authorization to act on behalf of a third party.
• Breach of the technical/security rules of the Client Area or the infrastructure (e.g. automated access without approval, attempts to circumvent measures).
• Non-compliance with the terms/policies of the competent registries or other regulatory bodies, or pending administrative/judicial proceedings (for example UDRP/URS) or binding orders of authorities.

c) Measures that may be imposed. Depending on the seriousness/urgency, the Company may impose one or more of the following measures, temporarily or permanently:

• ClientHold / RegistrarHold / ServerHold, Lock/TransferProhibited/UpdateProhibited, change/parking of nameservers.
• Rejection or suspension of registration, renewal, transfer or change requests.
• Restriction of access to the Client Area with respect to the specific domain name or related functions.
• Cancellation and/or deletion of the domain name in accordance with the applicable regulations in force.

d) Notification and remedy procedure. In urgent cases relating to security, malicious use, compliance with a binding order or imminent risk, measures may be taken without prior notice. In other cases, the Company may set a reasonable deadline for remedy/compliance. Failure to comply fully and in good time allows the measures to be maintained or escalated.

e) Financial consequences. The imposition of measures does not create any right to a refund. Registry/third-party fees, bank charges and administrative costs are not refunded. Any reinstatement of services (e.g. lifting a hold/lock, restore after deletion) may require payment of the related fees and full compliance. The Company may impose reasonable handling charges for examining/processing cases.

f) Binding nature of acts of authorities/Registries. The Company is obliged to comply with binding decisions/orders of competent authorities, registries and recognized dispute resolution procedures. In the event of conflict, the applicable regulations/decisions of those bodies prevail.

g) Exclusion of liability. The Company is not liable for consequences, direct or indirect, arising from the imposition of measures and/or from requirements/restrictions of registries, authorities or third-party providers, when the measures are imposed in accordance with the law and/or within the framework of these terms.

h) Indemnity. The Customer is obliged to indemnify, defend and hold harmless the Company, its officers and partners against any claim/damage/expense arising from a breach of the above, from illegal or abusive use of the domain name or from actions of third parties whom the Customer has authorized or whose access the Customer has permitted.

5.11 Compliance with EETT/ICANN and Registry regulations

a) Principle of precedence and binding nature. Domain name services are governed by the regulations of the competent Registries and, where applicable, by the ICANN policies and the EETT rules. These regulations are binding on the Customer and the Company and prevail in the event of conflict with these terms. Secondarily, these terms apply and, after them, any announcements/instructions of the Company.

b) Dynamic compliance. The Customer accepts that the regulations of the Registries/ICANN/EETT are amended periodically and agrees to be bound by every subsequent amendment without the need for new consent. The Company may adjust procedures, technical parameters and financial terms (including prices/fees) to the extent required for compliance with such changes, with reasonable notice.

c) Categories of regulations.

• .GR/.ΕΛ: the rules of the competent Registry under the supervision of EETT apply, including the procedures for assignment, renewal, changes and sanctions.
• gTLDs (e.g. .COM, .NET, etc.): the ICANN consensus policies apply, for example the Transfer Policy, the Expiration/Update rules, as well as the UDRP/URS dispute resolution mechanisms and the TMCH rights management.
• Other ccTLDs: the national/local regulations of the respective Registries apply, including special eligibility requirements, renewal/restore windows and technical restrictions.

d) Customer obligations. The Customer is obliged to study and comply with the applicable regulations corresponding to the extension of the domain name they choose or manage, to keep accurate details and to complete in good time any verifications or corrections requested by the Company or the Registry. Failure to comply may result in rejection of requests, imposition of restrictions/suspensions or cancellation of the domain name.

e) Compliance measures. In the event of non-compliance with the regulations, the Company may impose corrective or preventive measures (for example: administrative corrections, technical restrictions/holds/locks, changes of nameservers, rejection of requests or cancellation), depending on the seriousness and the necessity of compliance with the rules of the Registries/ICANN/EETT.

f) Changes of prices/procedures by Registries. If the competent Registries amend fees, procedures or technical requirements, the Company is entitled to adjust the corresponding charges/procedures and to require compliance with any new conditions. Such adjustment does not give rise to any right to compensation or withdrawal beyond what is mandatorily imposed by the regulations or the law.

g) Language clause. In the event of a discrepancy between translations of Registry regulations or ICANN policies, the original text of the respective regulations as published by the competent body prevails.

h) Information and due diligence. Before ordering or changing a domain name, the Customer must check the applicable conditions/restrictions of the extension, the deadlines and any special fees or technical restrictions. The Company makes reasonable efforts to provide information, without guaranteeing the completeness/currency of third-party announcements.

i) Exclusion of liability. The Company is not liable for changes, restrictions or delays caused by regulations/decisions of Registries, ICANN, EETT or other authorities, nor for the consequences arising from the compliance with them that is imposed.

5.12 Charges, refunds and credit balance

a) General principles of domain charges. Charges for domain names are determined by the competent Registries/providers and may change without notice due to decisions of third parties. Prices may differ for “premium” or special categories of names.

b) Special charges. In addition to the base prices, the following may be charged: (1) transfer fees (with/without automatic renewal, according to Registry rules), (2) redemption/restore fees after expiry, (3) administrative fees for manual procedures/identity checks where required, (4) charges of third parties (for example: ICANN/Registries) that are passed on without constituting revenue of the Company. The above are non-refundable from the moment the request has been forwarded to the Registry or they have been paid to third parties.

c) Non-refundable costs. Bank/interbank charges, payment provider fees, Registry/ICANN fees, redemption/restore fees and administrative costs of checks/identification are not refunded. If the Registry is technically unable to complete a request, amounts that have not been paid to third parties may be credited as credit.

d) Refund policy. No refund is provided for domain name registrations/renewals/transfers from the moment the request has been submitted to the Registry. Where any exceptions are provided by Registry regulations, any amounts are returned as a credit balance.

e) Credit balance (credit). Credits cannot be exchanged for cash, are not transferable, and are set off automatically against future charges. They are valid for twelve (12) months from being recorded (unless otherwise specified). SLA/promotional credits do not apply to domains, redemption/restore or external fees.

f) Billing errors. In the event of obvious typographical/accounting price errors, the Company is entitled to cancel the order and refund/credit the amount paid.

5.13 Free domain and special terms of promotions

a) Scope. Promotions with a free/subsidized domain apply exclusively to new orders and only for the first year of registration, unless otherwise stated. These terms supplement these Terms.

b) Eligibility - restrictions. (1) The offer applies per customer/Tax ID/account and is not transferable, (2) it may require the simultaneous purchase of a specific service (e.g. hosting) with a minimum term, (3) it cannot be combined with other discounts/coupons/credits, unless expressly stated, (4) premium/reserved names, special phases (sunrise/landrush) and extensions outside the promotion are excluded.

c) Technical rules. The choice of extension, availability and any additional eligibility requirements are determined by the respective Registries/providers.

d) Transfer and changes. A transfer or change of holder/registrar during the promotional period may be excluded or may result in loss of the promotional benefit, according to the Company's policy and/or Registry rules.

e) After the first year. Renewal is charged according to the price list/Registry rules in force from time to time. The promotional benefit does not extend automatically to renewals.

f) Bundled offers. If the other service (e.g. hosting) that “unlocked” the free/subsidized domain is canceled/refunded, the regular value of the domain and any third-party fee paid are deducted.

g) Abuse - anti-fraud. In the event of indications of abusive exploitation (e.g. multiple sign-ups/accounts), the Company may refuse/revoke the promotional benefit and adjust the charge to the regular value.

h) Amendment/end of promotions. The Company may change/suspend/revoke promotions at any time, with effect for new participations.

5.14 Conflict of interest and restrictions on the “issuing” of domain names

a) Principle of impartiality - prevention of “front-running”
The Company, its officers, partners and resellers are prohibited from exploiting non-public information (e.g. availability checks, support requests, customers' business plans) to preempt domain name registrations or to profit (e.g. resale, auctions, parking for their own benefit). The related data are used exclusively for providing the service and for security/compliance purposes.

b) Management of conflicts of interest
If an actual or potential conflict arises (e.g. the interested Customer and the Company/a partner are interested in the same name, or a request is assigned to an officer with a personal interest), the Company:

• undertakes not to act in competition with the Customer,
• changes the handler/team for the specific request or applies an internal “Chinese wall”,
• where required, refrains from any registration action for its own benefit until the final outcome of the Customer's request.

c) Regulatory restrictions on the “issuing”/assignment of names.
The “issuing” (assignment) of a domain name is subject to mandatory restrictions of the competent Registries/extension rules and applicable legislation. For example, the following names are not permitted, or are permitted only with a license/documentation, namely names that:

• violate the law, public order, morality or the principles and doctrine of the Orthodox Christian Faith,
• incorporate or infringe the rights of third parties (trademarks, trade names, intellectual/industrial property),
• are misleading as to identity/relationship with authorities, bodies, persons or trademarks,
• include geographic/state/international terms or names of public authorities without the required authorization,
• belong to reserved/premium lists or special regimes (sunrise/landrush, professional/category eligibility, IDN restrictions).

The Company may refuse or suspend an assignment request when any of the above grounds applies or when prior verification/documentation is required.

d) Neutrality in the aftermarket/brokerage
The Company does not act as a broker/auction house on its own account, nor does it purchase names searched for by customers for its own exploitation. If the Customer expressly requests an intermediary service (e.g. acquisition from a third party), it is provided only under a separate written agreement, with clear fees and disclosure of any objective obstacles.

e) Use of the Company's trademarks/name
Registering/using names that contain or imitate the Company's trademarks, name or distinctive marks, in a way that falsely implies endorsement, sponsorship or a corporate relationship, is prohibited without prior written permission.

f) Procedure in case of suspected violation or conflict
In the event of an indication of a violation of the above or a conflict of interest, the Company may:

• request additional information/documentation from the Customer,
• apply temporary technical measures (e.g. hold/lock) until the check is completed,
• reject or cancel the request, if the conditions are not met.

Amounts that have not been paid to third parties may be returned as a credit balance. Registry/third-party fees and administrative costs are not refunded.

g) Statement of no warranty and Customer responsibility
The Company does not guarantee assignment, even if a name appears as available during the check. The Customer bears sole responsibility for checking third-party rights and for the accuracy/legality of the use of the name. For any third-party claim/damage resulting from a breach of the above, the Customer is obliged to indemnify the Company and pay every related expense of the Company.

h) Ethical registration by the Company
The Company may register domain names only for its own services/products or for trademark protection/security purposes (e.g. domain defenses), without using or affecting customer requests.

5.15 Abuse reporting procedure and enforcement measures

a) Scope - Definitions. For the purposes of this Article, “abuse” means in particular the use of a domain name or related DNS/mechanisms for phishing, malware, botnets, pharming, misleading practices, spam and/or inaccurate/false WHOIS details. The Company acts exclusively at domain name/registry/DNS level and is not obliged to assess or remove content hosted with third-party providers.

b) Reporting channel and requirements. Reports are submitted by ticket in the Client Area or to the email address abuse at konet.gr. On pain of not being examined, the following minimum content is required: (i) the full domain name, (ii) a description of the reported act, (iii) evidence (e.g. headers, URLs, screenshots, samples), (iv) related timestamps, (v) the identity and contact details of the reporter. The Company may request additional clarifications.

c) Report handling - Discretion. The Company assesses each report and is solely competent to judge whether abuse has occurred and which temporary or permanent measure is necessary, taking into account its seriousness and urgency. Failure to send an acknowledgment of receipt or failure to communicate does not constitute acceptance or rejection.

d) Escalation of measures. Where deemed appropriate, the Company may apply, by way of example and without limitation:
(i) a temporary Registrar/Client Hold and/or Registrar Lock,
(ii) deactivation or modification of nameservers/the DNS zone,
(iii) a request to verify or update WHOIS details within a set deadline,
(iv) referral of the case to the competent registry/registrar and/or the competent authorities,
(v) final deletion, where provided by registry regulations and/or law.
Reinstatement of a service following measures is subject to the prior full remedy of the violation and the sole judgment of the Company.

e) Special categories of cases.
(i) Phishing/malware/spam: temporary measures may be taken immediately to prevent harm.
(ii) Inaccurate/false WHOIS: the holder is asked to verify/update within a reasonable deadline. In the event of non-compliance, suspension or deletion is possible.
(iii) Rights disputes (trademarks/names): the Company does not resolve substantive disputes, and the interested party must turn to the appropriate mechanisms (e.g. registry procedures/UDRP/URS or before EETT for .GR/.ΕΛ) and/or the competent authorities.

f) Relationship with partner registrars/registries. For extensions served through a partner registrar, the Company forwards the report and follows the relevant procedures/policies of the registrar/registry. The final measures may be imposed by the third party, without liability on the part of the Company.

g) Abuse of the reporting procedure. Reports that are manifestly unfounded, made in bad faith, insufficiently documented or repetitive may be rejected without further action. The Company may take measures against abuse of the reporting channel.

h) Disclaimer - Authorities/registries. The Company is not liable for direct or indirect damages from temporary or permanent restriction/suspension/deletion measures taken following a complaint or a request of authorities/registries. The Company may cooperate with competent authorities and disclose strictly necessary data in accordance with the law.

Clarification
The Company operates as a provider of domain name registration and management and is not obliged to confirm the accuracy or legality of content associated with domain names. Reports must be fully documented, while further investigation and resolution of disputes fall within the competence of the competent authorities or courts.

5.16 Cooperation with Netim and acceptance of third-party terms

The Company operates as a domain name reseller through its cooperation with the accredited registrar Netim. All domain names registered through our Company (with the exception of .GR, .ΕΛ and all .CY) are subject to the regulations and terms of use of Netim, as well as the applicable regulations of the competent registries.

By registering or managing a domain name through our services:

• The Customer accepts and is bound by the terms and regulations of Netim, which are available at: Netim Terms of Use
• The Customer acknowledges that our Company acts as an intermediary and bears no liability for restrictions, amendments or requirements imposed by Netim or the competent registries.

The Company reserves the right to discontinue or refuse to provide domain name registration or management services that breach the above terms.

5.17 WHOIS Privacy / ID Protection Services

a) Definition and scope. The WHOIS Privacy / ID Protection service (the “Privacy Service”) provides, where supported by the competent Registry, replacement or masking of the publicly displayed WHOIS/RDAP details of the domain name through the use of a third-party provider's contact details or anonymized contact details. The Privacy Service does not alter the contractual relationship between the Customer and the Company, nor does it release the Customer from the obligation to maintain accurate underlying holder details.

b) Availability and conditions. The Privacy Service may not be available for all extensions or for all categories of registrants (e.g. legal persons, specific ccTLDs, premium/reserved names or where the Registry requires publication). Activation/provision is subject to: (i) the rules of the relevant Registry, (ii) the terms of any third-party privacy/proxy provider, (iii) the full and accurate declaration of the underlying details by the Customer.

c) Activation - deactivation - transfers/expiry. The Privacy Service may be requested at registration or later, if permitted by the Registry. Upon transfer of the domain name or expiry/non-renewal, the Privacy Service may be deactivated automatically or may require reactivation with the new registrar, in accordance with the applicable rules. Deactivation at the Customer's request results in the underlying details being displayed in WHOIS/RDAP.

d) Management of communications (forwarding). Where a forwarding mechanism (email/form) is provided, the Company and/or the third-party provider may filter, anonymize or reject messages (e.g. spam/malicious content). Successful forwarding does not guarantee final receipt by the Customer. The Customer must monitor the anonymized communication channels and keep their contact details up to date.

e) Accuracy of underlying details - verifications. Using the Privacy Service does not release the Customer from the obligation to provide complete, accurate and verifiable holder/contact details. The Company may request updating/documentation and may suspend or deactivate the Privacy Service and/or the domain name in the event of inaccurate/unverifiable details, in accordance with the Registry regulations and these terms.

f) Disclosure of underlying details - exceptions. Notwithstanding the Privacy Service, the underlying details may be disclosed to: (i) competent authorities, (ii) Registries/registrars, (iii) rights holders asserting substantiated claims (e.g. UDRP/URS or similar proceedings), (iv) in compliance with court/administrative orders or mandatory policies. The Company/the third-party provider retains discretion to set reasonable documentation requirements before any disclosure.

g) Prohibited uses - consequences. Using the Privacy Service for illegal or abusive activities, for misleading as to identity or for obstructing lawful service-of-process procedures is prohibited. In the event of a violation, the Company may, on the basis of these terms and the Registry rules, without notice: deactivate the Service, lift the privacy masking, impose restrictions (e.g. hold/lock) or take other measures as defined in 5.10.

h) Charges - non-refundable. The Privacy Service may be invoiced annually per domain name or per activation. Fees paid to third parties or to the Registry are not refunded. Unavailability or deactivation due to Registry rules, non-compliance or as defined in (e)–(g) does not give rise to any right to compensation.

i) Service limits - disclaimer of warranties. The Privacy Service does not guarantee complete anonymity, does not prevent third-party access to the data in the context of binding procedures/checks and does not ensure protection from unsolicited communications. Registry/ICANN policies or changes in law may require increased publication of specific fields. In such cases the Company will adjust the Service without liability for any consequences.

j) Third-party providers - acceptance of terms. Where the Privacy Service is provided through a partner provider and/or registrar, the Customer accepts the corresponding terms/policies. In the event of conflict, the Registry rules and mandatory policies prevail.

k) Relationship with the Privacy Policy. The processing of personal data in the context of the Privacy Service is governed by the Company's Privacy Policy and, where applicable, by the policies of the third-party privacy provider. The Customer is informed that any forwarding of communications or verifications may require the processing/transmission of the minimum necessary data in accordance with the law.

6. SSL Certificate Services (SSL Certificates)

6.1 Description of SSL and role of the Company/CA

SSL (Secure Sockets Layer) certificates provide secure communication and data encryption between a server and a “client” application (e.g. a web browser). They are used to protect sensitive data, such as passwords, payment details and personal information, and to ensure users' trust in your website.

Customer Obligations: For the responsibilities and obligations relating to the accuracy of information, technical requirements and management of the SSL certificate, refer to Article 6.6.

Role of the Company

• Intermediation: The Company acts as an intermediary between the Customer and the Certificate Authority (CA) that issues the SSL certificates.
• Process Support: We provide support for submitting and tracking applications, while the final decision on issuance rests exclusively with the Certificate Authority.

Limitations and Exclusions of Liability

• For limitations and exclusions of liability relating to the issuance of SSL certificates, refer to Article 6.6.
• The Customer acknowledges that using an SSL certificate for illegal or abusive purposes may lead to immediate revocation by the Certificate Authority, without a refund.

Support and Advisory Services

The Company offers limited support for the installation of SSL certificates. There may be additional charges for specialized technical services based on the price list in force from time to time.

6.2 Cancellations, refunds and activation terms

The process of issuing and using SSL certificates is subject to the terms and conditions of the Certificate Authority (CA). Refunds and cancellations are considered in accordance with the following terms:

Right of Cancellation

• Time Frame: The Customer may request cancellation and a refund within 14 days of submitting the order, provided that the SSL certificate has not been activated or issued.
• Activated Certificates: If the SSL certificate has been activated, no refund is possible, regardless of how long it has been used.

Cancellation Procedure

• The cancellation request must be submitted in writing through the Client Area of the Company's Website.
• The Customer must provide sufficient information confirming their identity and the order they wish to cancel.
• The Company reserves the right to request additional documents or information to process the request.

Refund Exclusions

• Offers and Discounts: SSL certificates purchased through special offers, discounts or bundled plans are non-refundable.
• Special Categories: SSL certificates that include multiple entries (SANs) or special categories (e.g. EV, Wildcard) are not eligible for a refund once the validation process has started.

Financial Consequences

• Credit Balance: Where the refund conditions are met, the Company refunds the amount exclusively as a credit balance to the Customer's account, which may be used for future services.
• Administrative Fees: In the event of cancellation, administrative fees may apply, which are deducted from the total refund amount.

Liability of the Company

For limitations of liability and exclusions, refer to Article 6.6.

6.3 Certificate renewal and notices

Ensuring the continuous operation of SSL certificates is the sole responsibility of the Customer. The Company provides information and tools to facilitate the renewal process, under the following terms:

Renewal Notices

• Scheduled Reminders: The Company sends multiple email reminders to the Customer before the expiry date of the SSL certificate, provided that the Customer's contact details are complete and up to date.
• Automatic and Manual Renewals: The Customer may choose between automatic renewal (where supported) and manual renewal through the Client Area of the Company's Website.

Renewal Procedure

For the Customer's obligations regarding certificate renewal, refer to Article 6.6.

Expiry Period and Loss of Certificate

• Expiry Status: If the SSL certificate is not renewed before its expiry date, it ceases to be active, adversely affecting the operation and security of the Customer's website.
• Renewals after Expiry: In some cases, a grace period for renewal may be provided, depending on the policy of the Certificate Authority. Any delay in renewal is borne exclusively by the Customer.

Special Conditions

• Different Policies for Each Category: Renewal terms may differ depending on the type of SSL certificate (e.g. EV, DV, OV). The Customer must stay informed about the requirements of the specific category of their certificate.
• Automatic Renewal: Where automatic renewal is available, the Customer must ensure that they have a sufficient credit balance or a valid payment method.

Liability of the Company

The Company bears no liability for renewal issues. For details, refer to Article 6.6.

6.4 SSL installation and limits of support/liability

The Company offers SSL Certificate installation services for an additional charge, in accordance with the applicable price list. Installation services are provided exclusively for:

• Company servers: Installation is carried out only on servers hosted on the Company's infrastructure.
• Certificates purchased through the Company: Installation applies exclusively to SSL Certificates purchased through the Company.

The Company does not offer installation services for certificates purchased from other sources or for servers outside its infrastructure.

SSL Certificate Management

The Customer bears sole responsibility for:

• The management and secure storage of the SSL certificate's private keys.
• The timely renewal of the certificate before its expiry.

Responsibility for the management and security of SSL certificates is set out in Article 6.6.

SSL Certificate Support

The Company provides SSL Certificates “as is” (as-is), without any commitment or obligation to provide technical support beyond the installation process.

Support is limited exclusively to the installation service, provided it has been selected and paid for by the Customer.

For the Customer's general obligations and support limitations, refer to Article 6.6.

Support Limitations

The Company does not offer support for:

• Troubleshooting problems that may arise after installation.
• The compatibility of certificates with third-party software or systems.
• Any modification or configuration required to activate or use the certificate.

The Customer assumes full responsibility for the further management and use of the SSL Certificate after installation is completed.

For more information about general support, see Article 6.6.

Cancellation and Refund

Installation is deemed complete upon successful performance of the service by the Company. The amount paid for the installation service is non-refundable, regardless of the circumstances.

Any cancellation or refund for the SSL Certificate itself is subject to the terms of the certificate provider. The Company does not guarantee that the Customer will be able to obtain a refund after placing their order.

Warning

Failure to use, or poor management of, the SSL certificate may affect the operation and security of the Customer's website. The Company bears no liability for problems arising from incorrect installation or use of the certificate.

6.5 Ownership, revocation by the CA and legal compliance

Once an SSL certificate has been issued, the Customer is recognized as the sole holder of the certificate. Responsibility for monitoring the validity of the certificate, renewing it in good time and complying with the applicable regulations and legal requirements rests exclusively with the Customer.

Cancellation and Suspension of Certificates

SSL certificates may be revoked or canceled by the Certificate Authority (CA) in the following cases:

• Use of the certificate for illegal purposes or activities that violate applicable legislation.
• Provision of false or inaccurate information during the application process.
• Non-compliance with the terms and policies of the Certificate Authority.

The revocation or cancellation of a certificate is carried out exclusively by the Certificate Authority, and the Company bears no liability for any losses or effects of this process.

Responsibility for Monitoring and Compatibility

For the monitoring and compatibility of the certificate, refer to Article 6.6.

Legal Compliance and Regulations

The Customer must ensure that the use of the certificate complies with all relevant laws, regulations and requirements, including those relating to data protection (such as the GDPR). The Company bears no liability for the Customer's failure to comply with their legal obligations.

6.6 Customer obligations and limitations of the Company's liability

The use, installation and management of SSL Certificates are subject to the following general terms and limitations:

Customer Obligations

The Customer bears sole responsibility for:

• Providing accurate and complete information when ordering the SSL certificate. Any incorrect or incomplete information may delay or prevent the issuance of the certificate.
• Submitting any required supporting documents to the Certificate Authority (CA), if requested, for the issuance or renewal of the certificate.
• Renewing the SSL certificate in good time before its expiry, to prevent downtime or reduced security of the website.
• Securely storing and managing the SSL certificate's private keys, and preventing unauthorized access.
• Ensuring that the server and the applications used are fully compatible with the SSL certificate.
• Complying with all relevant laws and regulations, including those relating to data protection (e.g. GDPR).

These obligations cover all processes, such as the issuance, renewal, installation and management of SSL certificates.

Limitations of the Company's Liability

The Company bears no liability for:

• Any delays, rejections or revocations by the Certificate Authority (CA).
• Any data loss, incompatibilities or technical issues caused by incorrect configuration or management by the Customer.
• The Customer's failure to comply with the laws and regulations governing the use of certificates.
• Any problems arising from late renewal or from failure to maintain the compatibility of the certificate.
• Decisions taken by the Certificate Authority (CA), such as the acceptance or rejection of applications.

For details about support and suspension of certificates, refer to Article 6.4.

Support Limitations

The Company provides support only for services expressly included within the scope of the agreement. Any additional support may be subject to additional charges, in accordance with the price list in force from time to time.

Support does not include:

• Troubleshooting problems arising after the installation of the certificate.
• Managing or configuring private keys belonging to the Customer.
• Compatibility with third-party software or services.
• Requests to the Certificate Authority (CA) beyond the initial submission.

Cancellation and Suspension of Certificates

The revocation or cancellation of an SSL certificate is carried out exclusively by the Certificate Authority (CA). The Company is not liable for damages or losses arising from such actions.

By accepting these terms, the Customer acknowledges that responsibility for the use and management of SSL Certificates rests solely with them.

7. Intellectual Property

7.1 Ownership of content & tools

All content provided by the Company, including texts, graphics, logos, designs, tools, software and any other material, is the exclusive intellectual property of the Company or its partners. It is protected by applicable Greek and international intellectual property law.

Ownership and Use

• All rights in the Company's content and tools remain its property, unless there is an express written agreement to the contrary.
• Customers receive a limited, non-exclusive and non-transferable license to use the Company's services and tools solely for the purposes described in these terms.

Usage Restrictions

The following are expressly prohibited without the prior written consent of the Company:

• Reproduction and Distribution: Copying, distributing, publishing or modifying any part of the content or tools.
• Reverse Engineering: Reverse engineering, decompiling or attempting to extract the source code of any software.
• Use of Branding: Using the Company's logos, trademarks or other distinctive marks without permission.

Reservation of Rights

The Company reserves the right to take legal action to protect its rights in the event of infringement. By accepting these terms, the Customer acknowledges that they do not acquire any intellectual property rights in the Company's content or tools.

7.2 Customer responsibility for content & compliance

Customers bear sole responsibility for the content they store, share or upload through the Company's services.

Content Legality Requirements

Content uploaded by Customers must:

• Not infringe the intellectual or industrial property rights of third parties.
• Fully comply with applicable legislation, including laws on data protection, intellectual property and trademarks.
• Not contain material that is offensive, illegal, misleading or harmful.

Customer Obligations

Customers must:

• Ensure that they hold all necessary rights and licenses for the content they use or upload.
• Protect private keys or other items relating to intellectual property rights.
• Regularly check the legality of their content to prevent infringements.

Complaint Handling

In the event of a complaint of copyright infringement relating to Customer content:

• The Company reserves the right to temporarily disable or remove the reported content.
• The Customer will be informed and given a reasonable period of time to resolve the complaint.
• Non-compliance may lead to termination of services and possible referral to the competent authorities.

Disclaimer

The Company disclaims any liability for:

• Actions of Customers that infringe the rights of third parties.
• Any legal dispute or damage arising from content uploaded by Customers.

By accepting these terms, the Customer acknowledges that they bear full responsibility for the legality of their content and their actions on the Company's services.

7.3 License to use services/software & restrictions

Customers receive a limited, non-exclusive, non-transferable and temporary license to use the tools, software and services provided by the Company, solely for the purposes defined in these Terms of Service.

Usage Restrictions

The license:

• Exclusive Purpose: Is limited solely to the Customer's personal or professional use, as defined in the terms of this agreement.
• Prohibition of Modification: Does not grant any right to modify, distribute, resell or create derivative works based on the tools or software provided.
• Time Limitation: Applies only for the duration of the Customer's active relationship or subscription with the Company.
• Prohibition of Reverse Engineering: Does not permit reverse engineering, decompiling or any attempt to extract the source code of the tools or software.

Prohibited Actions

Customers may not:

• Assign or transfer the license to third parties without the prior written consent of the Company.
• Incorporate the content, software or services of the Company into commercial applications or products without express approval.
• Use the services for unlawful, misleading or abusive purposes.

Intellectual Property

Any extension or customization of tools or services implemented by the Company on behalf of the Customer:

• Remains Property: It constitutes the intellectual property of the Company, unless there is an express written agreement for the transfer of rights.
• Use Only Within the Cooperation: It may be used exclusively within the framework of the agreement with the Company.
• Prohibition of Modification or Distribution: It may not be further modified, sold or distributed without the permission of the Company.

Complaints and Actions

In cases of a complaint regarding a breach of the above terms:

• The Company reserves the right to temporarily deactivate the service.
• The Customer will be notified in order to provide clarifications or supporting evidence.
• In cases of serious breaches, the Company may terminate the cooperation and escalate the matter to the competent authorities.

Disclaimer

The Company is not liable for:

• Any abusive use of the tools or services by customers.
• Damages or losses arising from unauthorized use, modification or distribution of the services provided.
• Legal claims related to the use of tools or services by customers.

By accepting these terms, the Customer agrees to fully comply with the conditions and restrictions of use described above.

8. Hosting/Website Hosting Services

8.1 Definition of service & scope

The Company provides website and application hosting services through advanced and certified infrastructure operating exclusively in partner data centers. Our hosting services include specialized equipment, high-speed networks, security technologies and comprehensive management software, designed to ensure the stability and security of data. The data centers are certified by their respective providers and meet the security and availability standards declared by those providers (for example ISO 27001/Tier III or higher).

Our customers access our services through the website https://konet.gr, for personal or professional use, in accordance with these Terms of Service and the applicable legal provisions. The detailed technical specifications, limits and features of each plan are described on the corresponding service pages of our website and form an integral part of the hosting contract. In the case of shared plans (shared/semi dedicated), the Customer accepts that resources are distributed among multiple accounts, while plans with dedicated resources (VPS/Cloud/Dedicated) are subject to special restrictions/limits defined per service.

Konet undertakes to provide a reliable and secure hosting environment that covers needs such as:

• Creating and displaying websites.
• Managing audiovisual material and electronic documents.
• Sending and receiving email.
• Storing and accessing data with advanced security measures.

Platform/infrastructure services (e.g. web server, database server, control panel) are provided as part of the hosting. The management/maintenance of the content and code of the Customer's applications (CMS, plugins, themes, custom code, third-party APIs) is the responsibility of the Customer, unless managed support has been agreed in writing.

The proper operation of the services depends on the correct DNS/Nameserver configuration of the domain name. When the nameservers recommended by the Company are used, the association is simplified. When custom nameservers/Cloudflare or third-party DNS are used, the configuration/updating of DNS is the sole responsibility of the Customer (particularly during transfers/upgrades), as is any special configuration.

Data transfer is carried out through modern internet protocols (HTTP/3, HTTPS, FTP, SSH) for the protection of our customers and the best user experience. The availability of specific protocols/versions may be adjusted for security/compatibility reasons. In any case, the current settings of each server apply.

Customer prerequisites/responsibilities: Use of the services requires basic technical knowledge of website/email/DNS management and basic security. The Company is not obliged to provide training beyond standard documentation/activation instructions. The Customer is responsible for the lawfulness, accuracy and updating of its content/data and for the compliance of its applications with the applicable security specifications.

GDPR roles: The Customer remains the Controller for the data hosted/processed through the services. The Company acts as Processor solely for the provision of hosting, in accordance with the applicable Data Processing Agreement (DPA) and the Privacy Policy. For Konet's privacy policy, see the Company's relevant page.

8.1.2 Definitions of hosting service terms

To facilitate the understanding of the hosting services, the following terms used to describe the services of the Company are clarified:

• Website hosting service: Includes any form of hosting, such as shared hosting, VPS hosting, semi dedicated hosting, reseller hosting, dedicated server hosting and managed hosting. Shared plans are subject to fair use policies and technical limits per account, while plans with dedicated resources are subject to the settings/limits stated on the page of each service.
• Server: The electronic equipment used for the storage and distribution of data.
• Web Applications: Software or applications that operate over the internet and are hosted on the servers of the Company. They include commercial, educational or personal uses.
• Control Panel: The service management software, such as cPanel, provided to customers for the simple and secure management of their hosting plans.
• Disk Space: Refers to the space available for storing files and data on a server. It includes terms such as "hard disk", "disk space" or "storage space". It is not intended for use as a repository/archive or for storing independent backups (see §§ 8.5, 8.9).
• Website: Any digital content hosted on our servers, including websites, applications and files.
• Email: The service of sending, receiving and managing messages over the internet.
• Backup: Includes the creation, storage and restoration (restore backup) of data. Backup services may include managed backup and storage of data on external servers under the supervision of the Company.
• Scheduled Backup: Automatic creation of backups at predefined intervals, with the ability to restore when needed.
• Database: A data structure such as MySQL or MS SQL, used for storing and managing information of websites and applications.
• Web Protocols: Protocols such as HTTP, HTTPS, FTP, SSH that ensure the smooth transmission of data.
• Mass Email: The sending of a large volume of email messages to many recipients, such as newsletters or updates. The use of this service is subject to the rules against unsolicited email (spam). Use is subject to the anti-spam policies and the relevant sending limits (see § 8.12).

8.2 Infrastructure maintenance/upgrades

The Company provides the hosting services as is and as available (as-is / as-available), to the maximum extent permitted by law, without express or implied warranties, and without additional obligations beyond ensuring the smooth operation of its infrastructure and technical support in cases of issues related to its equipment, software or network. Specific availability guarantees or credits are provided only if expressly agreed in a separate SLA.

The Company informs the Customer about the procedure for accessing the Control Panel and the use of the tools provided for managing the hosting services, and provides instructions for setting up email accounts and uploading files to the web. The technical support of the Company primarily concerns the infrastructure (hardware, server operating system, network, server control panel). It does not include development/correction of application code, configuration/upgrades of CMS or add-ons, SEO/advertising, DevOps tasks or third-party services, unless agreed in writing. Any additional work is provided for a fee based on the applicable price list (Admin Hands).

The Company undertakes to apply regular updates to the installed software and platforms of its servers, in order to maintain high levels of security and functionality. These updates include the latest available versions of tools such as cPanel, PHP, MySQL, as well as other software necessary for the optimal operation of the services. Konet may, at its absolute discretion, retire (deprecate) old or insecure versions of software/modules/protocols and change security settings or architecture, also in accordance with §8.8. The Customer is obliged to adapt its code/applications/add-ons in a timely manner so that they remain compatible.

All maintenance and upgrade work on the equipment and infrastructure is carried out, as far as possible, during periods of low activity, in order to minimize the impact on the services. In the case of scheduled upgrades, the Company sends prior notice to customers. As a rule, timely notice is given through an announcement in the Client Area, and the Customer is therefore obliged to check the announcements daily. In urgent cases or in matters of security/integrity, immediate action without prior notice is permitted. Nevertheless, the Company makes every possible effort to inform customers promptly. Maintenance work may temporarily restrict access/functions or affect scheduled backups.

The Company may apply automated or manual protection measures (for example WAF/Imunify360, IP/port blocking, rate-limiting, isolation of accounts or processes, temporary deactivation of scripts/services), where it deems this necessary for the security and stability of its infrastructure.

The Customer must cooperate in good faith, provide the required access details/authorizations in a timely manner and follow the instructions of the Company. Any delays or inability to intervene due to incomplete information do not give rise to any liability of the Company.

The Company bears no liability for any losses, damages or non-pecuniary harm that may arise from upgrades, nor for the consequences of the Customer's failure to adapt to new versions of software, programming languages or web applications applied on its servers. By way of example and without limitation, the Company is not liable for loss of profits/revenue, business interruption, loss of data, software/hardware damage or any indirect/consequential damages connected with maintenance, updates, configuration changes, errors/delays of third-party providers (e.g. data centers, upstream networks, third-party software/licenses). It is expressly agreed that no guarantee of uninterrupted operation is provided and that events of force majeure or circumstances beyond the control of the Company release it from any liability.

Notices are deemed lawfully delivered when sent to the Customer's registered email address or posted on the official information channels of the Company.

8.3 Acceptable use & prohibited activities

The Customer accepts and agrees that it will not use the website of the Company, the services provided or the servers of the Company for:

a. Harassing, stalking or causing harm to third parties in any way (including any form of cyberbullying, impersonation or attempt to defraud users).

b. Infringing the rights of third parties (intellectual/industrial property, trade secrets, trademarks, contractual confidentiality obligations, breach of software/data license terms and third-party API terms).

c. Actions that violate any applicable legislation, regulation or directive of the competent authorities, including, by way of example, consumer protection legislation, export/sanctions legislation, as well as electronic communications regulations

d. Content that is unlawful, dangerous, threatening, offensive, harassing, slanderous, defamatory, inappropriate, obscene, child sexual abuse or exploitation material, human trafficking and promotion of illegal or harmful substances, or any other material that violates privacy and intellectual property rights, promotes discrimination based on race, ethnicity, religion, sex or other personal characteristics, or is contrary to the accepted morals, customs and traditions of Greece, the principles and doctrine of the Orthodox Christian Faith and of the internet community, including racist, pornographic, religious or other immoral content, as well as serial or registration numbers of software, cracker utilities or instructions for spamming. Specifically for cases of child sexual abuse or exploitation material, human trafficking and promotion of illegal or harmful substances, a zero-tolerance policy applies, with immediate suspension of services and submission of relevant reports to the competent authorities.

e. Collecting, storing or processing personal data of other users without their lawful express consent, beyond the purpose for which they were obtained and in breach of personal data protection regulations.

f. Distributing or sending malicious software, viruses, programs or files intended to compromise the functionality of systems, networks or software, including, by way of example, exploit kits, command-and-control infrastructure, attempts to bypass security measures and "penetration tests" without the approval of the Company.

g. Transmitting, publishing or sending content protected by laws on intellectual property, trade secrets, confidentiality agreements or other legal or contractual obligations, without the appropriate license, including any form of scraping/crawling in breach of rights or of third-party robots/ToS rules.

h. Any action that endangers minors, causing mental, physical or moral harm.

i. Material contrary to applicable legislation, such as material that is inappropriate for persons under the age of 18, abusive, material that offends public sentiment or that infringes copyright, etc.

j. Party-political or directly political use.

k. References or links to locations on the Internet or elsewhere whose placement is prohibited by the Company.

l. Pages of any content that have been advertised in an improper manner on the Internet, e.g. Spamming.

m. Hidden files, i.e. pages and other files that are not referenced by any other page, with the exception of the Home page.

n. Malicious or abusive techniques that target or facilitate attacks (for example DDoS, brute-force, port scanning, relay/open proxy abuse, IP/SMTP spoofing, phishing).

o. Cryptocurrency mining (crypto-mining) or any automated process that consumes disproportionate system resources.

p. Use of the services of the Company for file sharing/peer-to-peer, distribution of "heavy" files unrelated to the operation of the website, or for operating streaming-type services, unless prior written approval of the Company has been obtained.

q. Sending, forwarding or facilitating unsolicited or bulk email (spam/UCE/UBE), as specifically provided also in §8.12.

r. Bypassing, altering or removing identification/logging data (e.g. headers, logs), or using identity-concealment techniques to bypass access controls.

s. Content or activity that violates sanctions regimes, export controls or other applicable economic or trade restrictions.

t. Publishing or promoting activities that violate the terms of use of third-party platforms and providers, where hosting them with the Company would constitute a breach of those terms. The Customer is solely responsible for complying with the terms/policies of third-party providers (APIs, platforms, data) and assumes every consequence of non-compliance.

u. Use of automated means or techniques for creating/falsifying content (e.g. deepfakes) for the purpose of deception, infringement of rights or violation of the law.

If you wish to place on your websites material that may be described by one of the above categories, then:

a) you must transfer its hosting to another provider before proceeding to publish the material that is contrary to the policy and terms of use of the Company, and

b) you must change the registrar of the domain name before proceeding to publish the material that is contrary to the policy and terms of use of the Company.

The Company reserves the right, at its absolute discretion, to temporarily suspend the operation of, or change the nameservers of, a website, and to remove content (such as texts, images or files) that violates these terms or that is deemed inappropriate or harmful to the Company or to third parties. If the content is contrary to the law, the Company may suspend or terminate the provision of the relevant service. Furthermore, the Company may apply automated or manual security measures, such as blocking of IPs/ports/protocols, isolation (quarantine) of accounts/processes, black-holing of routing, temporary deactivation of scripts or services and deletion of files, where it deems this necessary for the security and stability of its infrastructure.

In cases of serious violations, the Company may immediately and without notice discontinue the provision of the service and access to the website over the internet, without being liable for any losses or damages that may arise for the Customer or third parties. In addition, in the event of recurrence or multiple violations, the Company may, at its absolute discretion, proceed with the definitive termination of the contract and deletion of data, without further notice and without any obligation to pay compensation.

The Company may notify the Customer accordingly, giving the Customer the opportunity to withdraw the material in question. If the Customer does not comply within a reasonable period of time, the Company reserves the right to permanently deactivate the Customer's account, without further notice and without any obligation to pay compensation. The Company is not obliged to proactively monitor content or activities, but reserves the right to inspect/investigate and to cooperate with the competent authorities to the extent permitted or required by law, including by providing relevant information. The Customer is obliged to cooperate fully and to provide the necessary information without undue delay. In addition, the Company may comply with lawful requests/orders of competent authorities, including the provision of identification/logging data, without notice to the Customer and without liability for compensation.

The Customer bears sole responsibility for any claim/damage arising from a breach of this §8.3 and is obliged to compensate the Company for any actual loss and loss of profit, including reasonable costs of investigation, legal support and technical remediation.

8.4 Resource limits (CPU/RAM/IO/EP)

The Customer is obliged to use only the available storage space it has leased (virtual disk space) within the limits of the maximum capacity defined by the hosting plan it has selected. Storing data that exceeds these limits is expressly prohibited. The storage space concerns exclusively files that directly serve the operation of the hosted website/application (code, assets that are actually served, databases, email of the account). Using the space as a general file "warehouse" (e.g. archives/backup dumps, personal multimedia unrelated to the site, offline data) is prohibited.

Exceeding the available space may occur, for example, if the Customer uses caching software or abusively stores data in folders located outside the main directory of its account (home directory). In such cases (for example oversized cache/logs/tmp directories, storage of binaries/iso/archives or backups that are not served, excessively large mailboxes, bloated databases):

a. The Company reserves the right to notify the Customer to remove the excess material or to upgrade its plan to cover the increased storage needs. The Company may, at its absolute discretion, also proceed with the immediate deletion of temporary files or files obviously unrelated to the operation of the site in order to restore usage to the permitted limits, without any obligation to pay compensation.

b. If the Customer does not comply within a reasonable period of time set by the Company, the Company may restrict or suspend access to the hosting services until proper use of the storage space is restored. The Company may apply technical restrictions (e.g. I/O throttling, temporary isolation of the account, blocking the creation of new files).

c. In cases of repeated or serious violations, the Company reserves the right to terminate the Customer's account without compensation. In addition, the Company reserves the right to charge reasonable costs of investigation/remediation where the excess or abusive use has placed a burden on the infrastructure.

Storing data in areas of the system that do not belong to the Customer's account is considered abusive and is strictly prohibited. Such actions, apart from possibly exceeding the space, may affect the performance of the server and cause harm to the proper operation of the services. Likewise, using the space to host files that are not related to the website or are not intended to serve the public over the internet is presumed to be abuse.

Meters & proper use: The Company may apply additional meters beyond the total GB (e.g. number of files/inodes, database size, mailbox limits) and may set a proper use policy for services that may be described as "unmetered" or "unlimited". The measurements of the Company's infrastructure are final and constitute evidence.

The Company bears no liability for data loss or service interruptions resulting from non-compliance with the above terms. The Company has no obligation to recover/restore files deleted in the course of restoring usage to the limits, nor to pay any compensation arising from the above measures.

8.5 Use of disk space & prohibited backups/files

The Customer is obliged to use its account exclusively for the normal operation and hosting of its website or applications. Storing backups of any kind in the leased space of the hosting account is expressly prohibited, whether they consist of personal, business or any other kind of data. The prohibition includes, by way of example, compressed files and dumps (e.g. .zip, .tar.gz, .rar, .7z, .sql), disk images, database exports, multiple versions of content, copies of "/backup/" or "/backups/" directories, as well as backups created by add-ons/tools (e.g. CMS plugins) within the webroot, "/home/user/" or the mailboxes.

This prohibition includes, without limitation:

a. Backup files created by third-party software or tools that are stored in folders of the hosting account.

b. Backups of websites, databases or email that are not related to the daily operation of the hosted website.

c. Any other kind of backup intended for storage and not for immediate use. It is expressly clarified that email mailboxes do not constitute long-term archiving space and may not be used for keeping backups/archives.

Storing backups in the space of the hosting account:

a. May cause problems with the performance of the servers and negatively affect the operation of the services for other customers.

b. May lead to exceeding the available space or other resources of the hosting plan. It is also connected with the restrictions and measures of §§8.4, 8.11 and 8.17.

By way of exception, and only where required for technical reasons of transfer or support:

a. the temporary creation of an on-server copy is permitted, exclusively by the Company or with the express written permission of the Company,

b. the copy is kept in a non-publicly accessible path specified by the Company, with zero retention after the completion of the process,

c. any such temporary files are subject to automatic or manual deletion at the absolute discretion of the Company, without further notice and without any obligation to pay compensation.

If a breach of the above policy is found:

a. The Company reserves the right to detect, by automated means, files or folders identified as backups, to isolate them (quarantine) and/or to delete them immediately, without prior notice.

b. The Customer will be informed of the non-compliance and will be asked to remedy the situation immediately.

c. If the breach continues or if the backup material causes serious problems in the operation of the server, the Company may suspend or terminate the Customer's account at its absolute discretion, without notice, without being liable for any losses or damages and without any obligation to pay compensation. The Company may also impose reasonable charges for investigation/remediation/cleanup.

Furthermore, it is prohibited to use the hosting services as a file synchronization repository (e.g. drive/sync, seedbox, peer-to-peer, bulk distribution or streaming services) or for keeping multimedia that does not directly serve the functionality of the website.

Any backup solution provided by the Company (e.g. managed/remote backup) is governed by separate terms/plans and does not imply permission to store backups within the hosted account. The Company recommends the use of specialized backup storage and management services outside the hosting space, in order to ensure the security and availability of the Customer's data. The Customer remains solely responsible for taking and keeping adequate external backups and is liable for any consequence of failing to comply with this paragraph.

8.6 Inode limits & file management

The hosting space provided by the Company, including access via FTP, is intended exclusively for the personal or professional use of the Customer. Disclosing access details, such as the password, to third parties is strictly prohibited. Where the relevant functionality is available, the Customer must use named sub-accounts/access roles (e.g. cPanel users, SSH keys, API tokens) instead of sharing credentials. The creation, maintenance and revocation of such sub-accounts is the sole responsibility of the Customer.

To protect its account and data, the Customer is obliged to take appropriate security measures, such as:

• Changing passwords regularly.
• Using complex passwords that are not easy to guess.
• Enabling additional security mechanisms, such as two-factor authentication (2FA).
• Rotating/revoking access keys (SSH keys, API tokens, application passwords), disabling unused credentials and periodically reviewing permissions.
• Using password managers, unique passwords per service, and avoiding storing credentials in code/repositories.
• Applying the principle of least privilege, logging/monitoring access by third parties (e.g. partners/contractors) and revoking access immediately when the cooperation ends.
• Where provided, using lists of allowed addresses (IP whitelisting) and restricting protocols/ports.

The Customer bears full and sole responsibility for all actions carried out through its account, regardless of whether they were carried out by the Customer or by third parties who obtained unauthorized access. The access/event records (system & application logs) of the Company's infrastructure are presumed accurate and may be used as evidence.

In the event of a breach of the security of the account or suspicion of malicious use, the Customer is obliged:

a. To inform the Company immediately so that appropriate measures can be taken.

b. To change the passwords and ensure that no further unauthorized actions take place.

c. To rotate/revoke without delay all relevant credentials (SSH keys, API tokens, application passwords) and to check/clean end devices of malicious software.

d. To make available to the Company the necessary information/logs for the investigation of the incident.

The Company may, at its absolute discretion, impose and/or make mandatory the activation of 2FA, the rotation of passwords/keys, the temporary blocking of access (IPs/ports/protocols), the isolation (quarantine) of accounts/processes, the revocation of keys/API tokens and forced password resets, with or without notice, where it deems this necessary for the security and stability of its infrastructure, without any obligation to pay compensation.

For the purposes of identity verification and prevention of fraudulent account recovery, the Company may request appropriate proof of identity before reactivating or reissuing credentials.

The Company reserves the right to temporarily suspend or terminate the account in cases where the above terms are violated or if a risk to the security of the server or the data of other customers is identified. In addition, the Company may impose reasonable charges for the investigation/remediation of security incidents caused by acts or omissions of the Customer.

The Customer accepts and agrees that the Company bears no liability for any damage, data loss or other consequences arising from inadequate protection or unauthorized use of its account. In particular, the Company is not liable for damages caused by phishing, key-loggers/malicious software on the Customer's equipment, SIM-swap, social engineering, vulnerabilities of third-party add-ons/applications or other causes outside its sphere of control. The Company will never ask for passwords by email/telephone. Any such request is an indication of fraud.

The Company may at any time modify the minimum access security requirements (e.g. password complexity, 2FA, permitted protocols), enforce them immediately and require the Customer's compliance within a reasonable deadline, without further notice and without any obligation to pay compensation.

8.7 Account security - passwords, access, Customer responsibility

The Company makes every possible effort to ensure the security of its hosting accounts and servers, providing advanced protection systems and security tools in the web hosting plans it offers. However, the Customer acknowledges and agrees that:

a. No security system is completely impenetrable. Despite the application of advanced protection measures, accounts or servers may become the target of malicious software, hacking attacks or other threats. The security measures of the Company primarily protect the infrastructure level. The security of the Customer's code/applications/content remains the Customer's responsibility.

b. The Company bears no liability whatsoever for any damage, data loss or malfunction resulting from security attacks, such as infection by malicious software, unauthorized access or other similar circumstances, including, by way of example, incidents caused by vulnerabilities of third-party software (e.g. themes/plugins/CMS), zero-day exploits, configuration errors of the Customer or causes outside the sphere of control of the Company, to the extent permitted by law.

c. The Customer is responsible for strengthening the security of its account, through:

i. Regularly updating passwords.

ii. Installing security updates for the applications and software it uses.

iii. Using additional protection systems, such as firewalls, malware detection software and two-factor authentication (2FA), where provided.

iv. Periodically scanning/hardening applications, removing unused add-ons/accounts, and applying the principle of least privilege.

v. Ensuring encryption in transit and, where required by the nature of the data, at rest, on the part of the Customer or through additional services.

vi. Complying with its own regulatory obligations (e.g. PCI-DSS for payments, specific GDPR obligations at application/data level), unless otherwise expressly agreed in a separate contract (e.g. DPA/Managed Security).

d. If the Customer's account or server becomes the target of an attack or is infected by malicious software, the Company bears no liability for remedying the damage. Any technical assistance/remediation is provided, where feasible, exclusively as an additional, paid incident response/cleanup service, in accordance with the price list in force at the time.

e. The Customer is obliged to inform the Company immediately in case of a suspected security breach, so that appropriate protection or remediation measures can be taken. The notification must be made without undue delay and in any case within twenty-four (24) hours from the moment the Customer became aware or should reasonably have become aware of the incident. The Customer is obliged to provide any relevant information/log that is reasonably requested.

f. The liability of the Company is limited to providing the best possible protection measures, in accordance with the technology available at the given time. The Company may, at its absolute discretion, modify, upgrade or replace its security measures at any time, with or without notice, and impose new minimum compliance requirements on the Customer with immediate effect, without any obligation to pay compensation.

The Company reserves the right, at its absolute discretion, to apply automated or manual immediate defense measures, including isolation (quarantine) of accounts/processes/files, blocking of IPs/ports/protocols, temporary deactivation of services or scripts, forced reset of passwords/keys, black-holing of routing and any other necessary technical measure for the protection of its infrastructure and of other customers, without further notice and without any obligation to pay compensation.

The Company is not obliged to proactively monitor the content or activity of the Customer. However, it reserves the right to investigate suspicious incidents, to keep and use logs as evidence and to cooperate with the competent authorities to the extent permitted or required by law, including by providing relevant data.

Any penetration test, vulnerability scan or similar action on the infrastructure of the Company is permitted only with the prior written approval of the Company. Unauthorized tests constitute a breach of the terms and may result in immediate suspension or termination of services, without any obligation to pay compensation.

By accepting these terms, the Customer acknowledges that security is a shared responsibility and that the Company does not guarantee complete protection against every possible threat. The Customer bears sole responsibility for any claim/damage arising from failure to comply with this §8.7 and is obliged to compensate the Company for any actual loss and loss of profit, including reasonable costs of investigation, legal support and technical remediation.

8.8 Technology changes & platform migrations

The Company reserves the right, at its absolute discretion, to make changes to technology, equipment or infrastructure related to the provision of website hosting services. These changes may include, by way of example:

a. Technology upgrades: Installation of newer or improved systems, software or equipment for better customer support and to ensure high levels of performance and security. The Company may modify and/or disable functions, modules and extensions (e.g. PHP versions/extensions, web server rules, mail/security filters), apply patches and security settings, and renew TLS certificates without notice when security or proper operation so requires.

b. Infrastructure transfers: Possible transfer of services or data to different servers or data centers, in order to ensure the stability, security or optimization of the service provided. The Company may change IP ranges, nameservers, routing, storage backends and other parameters, and may discontinue or replace third-party providers/technologies (e.g. control panel, web/email/security stack).

c. Changes to service parameters: Modification of technical features or settings, with the aim of adapting the services to the current or future needs of customers. The Company may impose minimum technical specifications or withdraw support for old versions (EOL), requiring the Customer to upgrade applications/code/software frameworks.

d. Continuous improvement: Technology changes aim to provide the best possible services and are part of the Company's commitment to the continuous development and improvement of its hosting services. The Company may apply temporary or permanent performance optimization settings (e.g. rate limiting, caching changes, WAF/IPS adjustments) when it deems appropriate.

The Company may carry out the above changes without prior notice, especially in cases of urgent need or to ensure the proper operation of its services. Where feasible, notice may be given with a reasonable warning period, without this constituting an obligation.

The Customer agrees that the Company bears no liability whatsoever and is not obliged to pay compensation for any temporary interruptions, data loss or other consequences that may arise from these changes, and that no credits/discounts or SLA credits are owed. Any downtime caused by the above changes or by related security/optimization measures is expressly excluded from any service level (SLA), if one exists.

The Customer is obliged, at its own expense, to adapt its content, applications and settings in a timely manner (e.g. CMS/plugin/theme versions, code compatibility with new versions of PHP/DB engines, DNS/SPF/DKIM/DMARC/SMTP settings, TLS/cipher suite requirements, retirement of old protocols) so that they remain compatible with the technical parameters of the Company in force at the time. The Company does not guarantee backward compatibility and is not obliged to grant temporary "exceptions" or to retain legacy settings.

For reasons of security and stability, the Company may apply automated or manual measures, such as blocking of IPs/ports/protocols, isolation (quarantine) of accounts/processes, black-holing of routing, temporary deactivation of scripts/services, modification or enforcement of WAF/IPS/antimalware rules and rate limiting settings, without further notice and without any obligation to pay compensation.

By accepting these terms, the Customer acknowledges and agrees that these changes are necessary to maintain the quality and security of the services and do not constitute grounds for a claim or for termination without charge, and that the Company is not liable for any losses or damages that may arise. The Company reserves the right to determine, on a case-by-case basis and at its absolute discretion, the reasonable framework for adaptation.

8.9 Backups - policy & disclaimer

The Company provides no guarantee for the retention or integrity of the data stored in your account. Although we offer backup systems, we recommend that our customers keep their own backups of all files and data located in the hosting space they have leased (virtual disk space). Any backups kept by the Company are a disaster recovery tool and are provided "as is", without any guarantee of availability, completeness or currency, and do not constitute a contractual obligation or part of an SLA.

The backups you keep of your files and data may not be stored in your hosting account. It is the Customer's responsibility to ensure that its data is stored on external media or in alternative secure storage locations. By way of exception, only the temporary hosting of backup files is permitted, exclusively for the purposes of an immediate restore and for the strictly necessary period of time, with immediate deletion upon completion. Otherwise §8.5 applies.

Specific terms:

• The Company may, at its absolute discretion, change/discontinue its backup retention policy (cycles/frequency/medium/space) without notice in urgent cases of security or operation.
• Restores are carried out upon request via ticket, provided that a backup is available and the restore is technically feasible. They may be subject to a charge, may cause additional downtime and are not covered by SLA times/credits.
• Data such as large volumes of temporary files, cache, logs, multimedia files/third-party backups, mailboxes above reasonable limits, encrypted archives without available keys, as well as data that does not belong to the permitted space of the account, may be excluded from the Company's backups.
• The Company is not obliged to perform "selective" recovery (e.g. individual emails/DB rows) or recovery of earlier versions beyond the available snapshots.
• The Company does not provide expert examination services (digital forensics) and does not issue certificates of integrity/chain of custody for the data or the backups.
• The Company's backups may be encrypted/not directly accessible by the Customer. Access is provided only through the restore process.
• In incidents of force majeure, cyberattack, infrastructure failure, terrorist attacks, extreme weather events, power outages, software failure or Customer error, the Company bears no liability for the unavailability/loss of backups or failure of a restore.

By accepting these terms, the Customer understands and accepts that the Company bears no liability whatsoever for any data loss arising from the lack of backups on the part of the Customer and/or from the unavailability, incomplete or failed restore of a Company backup, without further notice and without any obligation to pay compensation. The Customer must maintain, at its own expense, an independent, regular and tested ("tested restore") backup policy outside the infrastructure of the Company.

8.10 SSL/TLS certificates & AutoSSL - prerequisites/limitations

The Company bears no liability whatsoever for any damage or loss that may be caused to the computer, the network of the Customer or any other equipment connected with the use of the hosting services it provides. The services are provided "as is" and "as available", without any guarantee of compatibility, fitness for a particular purpose or uninterrupted availability.

The services of the Company are provided as is, and the Company cannot be held responsible for incidents such as data loss, system failures, malware infections or other malfunctions arising from the use of or connection to its servers. By way of example and without limitation, the Company is not liable for issues caused by:

a. incompatibilities/defects of third-party software, add-ons/themes, APIs and PHP/MySQL/OS updates,

b. exceeding resources or incorrect settings by the Customer or its partners,

c. third-party providers (network/electricity/IX/Data Center/CDN),

d. malicious actions of third parties (DDoS, brute-force, malware, phishing),

e. events of force majeure or events beyond the reasonable control of the Company.

By accepting these terms, the Customer acknowledges and accepts that it is solely responsible for ensuring the security and protection of its equipment and data when using our services. The Customer takes care of updating operating systems/applications, using up-to-date antivirus/EDR and firewalls, a strong password/2FA policy, encryption where appropriate, as well as adequate backups outside our infrastructure (see §8.5-§8.9).

To the maximum extent permitted by applicable law, the Company bears no liability for direct, indirect, special or consequential damages, loss of profits, loss of reputation, loss of data or business interruption. Any total and aggregate liability of ours, if and to the extent it arises, is limited to the amount of the fees paid by the Customer for the relevant service during the last three (3) calendar months.

8.11 Running tasks - cron/daemons/long-running processes

The resources of the Company's servers are made available exclusively for use within the accounts of our customers and are intended exclusively to support the websites and applications hosted on our servers. An exception is permitted only where there is an express reseller (Reseller) contract and exclusively within its terms.

Making available or using the server's resources for external purposes is strictly prohibited, such as pulling graphics, texts or other files from our servers for use on third-party websites (hotlinking). This includes, by way of example and without limitation, activities such as participation in banner exchange programs, providing data to external websites or any other unauthorized use of resources. "Hotlinking" means any direct loading of files (e.g. images, videos, CSS/JS files, downloads) from third-party domains to your account. Hotlinking is prohibited unless express prior written approval of the Company has been obtained.

The services may not be used as a CDN/object storage, public repository or mirror for third-party applications/mobile apps, proxy/VPN/open relay/exit node services, image/file hosting for third-party domains, public APIs that cause disproportionate resource consumption, nor for streaming/file sharing functions for purposes unrelated to the relevant website. Connection to third-party CDNs (e.g. reverse proxy) is permitted exclusively for content of the Customer's own domain/brand and provided that these terms or the rights of third parties are not violated.

The Company reserves the right to take immediate action to ensure the proper operation of its servers, including restricting or discontinuing the service, in cases of abuse of resources. Example measures: imposing limits/rates (rate-limit), blocking referrers/IPs/ports/protocols, enabling/enforcing WAF/LSCache rules, isolation (quarantine) of accounts or processes, temporary deactivation of scripts, changing security settings/rules and black-holing of routing, all at the absolute discretion of the Company, without further notice and without any obligation to pay compensation. The Company may request the immediate removal of the causes of abuse and/or a plan upgrade. Failure to comply within the deadline set may result in suspension or termination of the contract. Any additional cost of traffic/resources or technical actions is borne by the Customer in accordance with the price list in force at the time.

8.12 Anti-spam policy & acceptable use of email

The Company follows a strict acceptable use policy regarding the content and lawfulness of email. The Customer must comply with the applicable law on electronic communications and data protection, including lawful consent, transparency of the sender's identity and the existence of a clearly visible mechanism for immediate unsubscription where required.

It is prohibited to send messages that:

• are of a commercial/advertising nature without the prior valid consent of the recipients, which must be documented and provable, and which the Customer is obliged to show to the Company immediately upon its request, or in breach of their legitimate expectations,
• are misleading or fraudulent (e.g. phishing, social engineering, abusive concealment/falsification of identification data at content level),
• contain material that infringes the rights of third parties (intellectual/industrial property, trade secrets, personal data) or violates the law or judicial/administrative decisions,
• are offensive, slanderous, defamatory, threatening or encourage unlawful acts,
• are based on purchased/rented/"scraped" or unverified recipient lists, or are addressed to persons who have requested to unsubscribe/have been flagged as bounces.

Sender obligations:

• Keeping evidence of consent (date/method of collection, information policy) and maintaining compliance records.
• Acting immediately on unsubscribe requests, without delay or additional requirements.
• Regularly cleaning lists of invalid/inactive addresses and handling complaints (abuse reports).

The Company may, at its absolute discretion, assess the sending activity and, where it considers that this provision is being violated, immediately apply measures including, by way of example, blocks, quarantine/non-delivery of messages, and temporary or permanent suspension of the account, without notice and without any obligation to pay compensation. In the event of damages/sanctions/third-party claims due to a violation, the Customer is solely liable for every consequence and cost (including reasonable costs of investigation and legal support).

This §8.12 governs exclusively matters of content, consent and acceptable use. The operational sending limits, technical settings (e.g. authentication/alignment policies) and campaign rules are set out in §8.20, while filtering/routing through anti-spam services is described in §8.21.

8.13 Restriction/suspension/termination measures

The Company reserves the right to immediately suspend, without prior notice, access to a Customer's website, if it causes problems or interference with the hosting services of other customers served by the same server.

In such a case, the Customer will be informed as soon as possible, and the Company will make every possible effort to cooperate with the Customer in order to identify and address the cause of the interruption.

The Customer understands and accepts that the Company bears no liability and is not obliged to pay compensation for any damage, data loss or other consequences arising from such an interruption. The suspension of the service is a measure to protect the overall stability and performance of the system, which serves all customers.

The Company may, at its absolute discretion, instead of a full suspension, impose targeted restriction and/or isolation measures, such as, by way of example, temporary throttling/rate-limit, blocking of ports/IPs/protocols, black-holing/null-route, isolation (quarantine) of accounts or processes, deactivation of specific scripts/cron jobs or services (e.g. PHP, MySQL, SMTP, FTP), activation of additional WAF/security rules or temporary change of nameservers.

Example grounds for activating the above measures include, without limitation: excessive resource consumption (CPU/RAM/Disk I/O/Entry Processes/queries), malicious or vulnerable processes exploited in attacks (DDoS/reflector/brute-force/scan), an extensive mail queue due to spam/backscatter, activity of malware/shells/compromised plugins, and incorrect settings that cause instability or risk to the server.

The Customer is obliged to cooperate fully and without undue delay with the Company to remove the cause, to apply the hardening/remediation instructions and to complete the required actions within the deadline set by the Company. Non-compliance results in the continuation and/or escalation of the measures, up to and including the permanent termination of the account, without further notice and without any obligation to pay compensation.

The Company is not obliged to maintain or immediately restore availability, nor to provide temporary solutions (workarounds). No credits, refunds or SLA credits are given for the period of restriction/suspension. The Company may charge a reasonable cost for inspection/investigation/remediation and cleanup (e.g. malware removal, debugging of settings), particularly where the cause lies in the code, settings or management of the Customer.

The Company may remove or clean files that are presumed to be infected/malicious or that cause instability, restrict access to logs/files in order to safeguard the integrity of the systems, and cooperate with the competent authorities, to the extent permitted or required by law.

In the event of recurrence or a particularly serious violation, the Company may permanently terminate the service and refuse to provide new services, in order to protect its infrastructure and its customers.

8.14 Intellectual property & unlawful content (removal)

The Customer undertakes to use the space provided exclusively for files directly related to the operation of its website. It is not permitted to upload, download or store files that do not directly serve the functionality of the website or application hosted in its account. "Unrelated" or "unnecessary" files means, by way of example, multimedia libraries intended for distribution/download by the public, personal archives (.zip/.rar/.7z, disk images, installers), data dumps, temporary or redundant logs beyond a reasonable retention period, files that are not called/referenced by the code of the website (orphaned assets), staging copies/build artifacts, as well as any content that turns the account into a file warehouse or CDN. This provision applies in addition to §§ 8.5 and 8.11.

The Company reserves the right to remove immediately, without prior notice, files that are not necessary for the operation of the Customer's website. This action ensures that the available space remains within the defined limits and that the overall operation of the server, which also serves other customers, remains uninterrupted. Furthermore, the Company may, at its absolute discretion and to the maximum extent permitted by law:

a. apply automated or manual MIME type/signature checks, heuristics for detecting "orphaned"/unrelated files and restrictions per file type,

b. set/modify limits per folder and/or per type of content,

c. move content to a non-publicly accessible quarantine zone or proceed with permanent deletion,

d. restrict or block protocols/functions (e.g. FTP/SFTP/HTTP uploads) that abuse the space.

These measures may be taken without notice and without any obligation to pay compensation or provide a credit.

By way of exception, and only with the prior written approval of the Company, it is possible to host high-volume files (e.g. for streaming/download), under special service terms, technical restrictions and additional charges. The Company may revoke the approval at any time if the stability/security of the infrastructure is affected or these terms are violated.

The Customer is obliged:

a. to keep its files optimized (for example, compression/clearing of cache, avoiding duplicates),

b. to delete temporary/obsolete files and oversized logs at reasonable intervals,

c. to adopt suitable third-party solutions for distributing large files (CDN/object storage), where required.

Following a relevant request of the Company, the Customer must comply within 24 hours by removing the unrelated files or upgrading its plan. Non-compliance may result in restriction, suspension or termination of the service, without refund or compensation.

The Company may charge a reasonable cost for the investigation, cleanup, restoration of resources and technical interventions required due to a breach of this §8.14. The Customer is fully liable and shall indemnify the Company for any damage/third-party cost arising from a breach of this provision.

File checks/scans by the Company are intended exclusively to ensure security/compliance and do not constitute proactive monitoring of content. The Company may cooperate with the competent authorities to the extent permitted or required by law.

8.14.1 Notice & Takedown procedure (content / copyright)

The Customer bears sole and full responsibility for all content hosted in its account, including, by way of example, texts, images, videos, data and applications. The Company, its partner data centers and its other partners bear no liability for any infringement of intellectual property or other rights of third parties, nor can they be held liable by judicial or administrative authorities. Liability is to be sought solely and exclusively from the Customer through legal channels.

If a report of infringement of rights or of unlawful content is submitted to the Company, to its partner data centers or to a partner of the Company, the Company is entitled to remove or disable the content in question immediately within twenty-four (24) hours, regardless of whether or not the Customer is its creator or lawful owner. The Customer is obliged, within seven (7) days, to prove with valid and sufficient evidence that it holds the rights or that it does not infringe the lawful rights of third parties. If the proof is deemed sufficient, the Company may restore the content.

The Company is not liable for any damages, interruptions, loss of data or revenue arising from the temporary or permanent removal of content, nor is it obliged to pay any monetary compensation or provide any credit. By accepting these Terms of Service, the Customer unreservedly accepts this mechanism and consents to its application.

8.15 Application security & permissions

The Customer bears full responsibility for ensuring the security of the code and applications installed in its account. This includes the appropriate configuration of access permissions for folders and files, regardless of their method of installation.

The Customer must:

• Ensure that its code is secure, without vulnerabilities that can be exploited for malicious actions.
• Apply all the recommended security settings provided by its applications.
• Use the appropriate access levels to protect its folders and files.
• Regularly monitor the reliability of its applications and ensure that all security updates and upgrades are applied in a timely manner.
• Keep CMS, plugins and themes up to date and avoid versions that have reached end of life (EOL) or are no longer supported. "Nulled"/pirated software is prohibited.
• Immediately remove abandoned add-ons/themes and limit administrative accounts to what is strictly necessary. Enable 2FA where provided and use strong, unique passwords.
• Ensure correct configuration (for example: disabling directory listing, appropriate file/folder permissions, not storing credentials/secrets in the webroot, protecting configuration files, using secure connections to databases).
• Take immediate action on critical vulnerabilities disclosed in the industry or by the Company. Indicative compliance deadline for critical fixes: within 72 hours of the disclosure.
• Adopt reasonable application-level technical defenses (e.g. limiting login attempts, CAPTCHA on forms, basic HTTP security headers), in a manner compatible with the platform.

Carrying out security audits, vulnerability scanning, penetration testing or other stress tests on the infrastructure of the Company is strictly prohibited without prior written authorization. Unauthorized tests are considered a breach of the Terms of Service and may result in the immediate suspension or termination of the contract. The Company reserves the right to claim full compensation for any actual loss or loss of profit, including reasonable costs of investigation and legal support, and to take legal action against the responsible party for any damage or threat arising from such actions.

The Company has an official responsible vulnerability disclosure channel (responsible disclosure) via abuse at konet dot gr and/or by submitting a ticket in the Client Area under the relevant "Support" category. Any disclosure must be made in a manner that does not compromise data or the availability of services.

In the event of suspected or established compromise/infection/abuse of an account, the Company may, at its absolute discretion, place the account or parts of it in quarantine, temporarily deactivate scripts/add-ons, apply IP/port/protocol blocks or take other immediate protective technical actions, without notice and without any obligation to pay compensation or provide a credit.

Server-level protection is provided through Imunify360 (including OSSEC intrusion detection modules) on a best-effort basis. This service is limited to detection/prevention mechanisms and automated cleanup of basic infections. It does not include fixing the Customer's custom applications, code or databases, for which the Customer bears sole responsibility.

Application-level remediation (e.g. code cleanup, database repair, reconfiguration of CMS/plugins) is not included in the standard hosting services. It is provided only upon request and for a fee in accordance with the price list in force at the time.

The Company may impose minimum mandatory versions/settings (e.g. PHP upgrade, disabling insecure functions) for reasons of security and stability. The Customer accepts that any incompatibilities/malfunctions arising from these upgrades do not give rise to any liability or obligation of the Company to pay compensation.

In the event of blacklisting, listing on anti-abuse lists or blocking due to acts/omissions of the Customer (e.g. sending spam from a compromised site), the Customer bears the cost of investigation, delisting, restoration of IP/domain reputation and any related technical work.

Failure to comply with these obligations may lead to security problems for which the Company bears no liability whatsoever. The Customer bears sole responsibility and is obliged to compensate the Company for any actual loss or loss of profit arising from related breaches, including reasonable costs of investigation, legal support and technical remediation.

8.16 Temporary "Under Construction" page

Upon the activation of each web hosting account, an "Under Construction" page is automatically created, which serves as a temporary indication that the hosting account has been activated successfully and/or as a default "placeholder"/"default index" page for empty site folders.

This page is predefined and displays only the message "Under Construction". The Customer may remove or replace the "Under Construction" page at any time, once it has access to its web hosting account. The page may include minimal marking/branding of the Company, informational content or links to Konet services. Its template/content is the intellectual property of Konet and no license of use is granted beyond its temporary display.

The existence of this page does not restrict or affect the functionality of the account and it can be fully customized according to the preferences of the Customer. The Company may, at its absolute discretion and without notice, display/redisplay the "Under Construction" page in cases where there is no active content, incorrect DNS settings, a transfer, a suspension or for reasons of security/maintenance, without any obligation to pay compensation or provide a credit.

Efforts are made to serve the page with appropriate directives (e.g. noindex/nofollow) where technically feasible. However, no guarantee is given that it will not be indexed/stored by third parties (search engines, caches, archives). The Customer bears sole responsibility for any additional settings (robots.txt, meta tags, webmaster tools) and accepts that the Company bears no liability for effects on SEO/reputation/traffic due to the display of the "Under Construction" page.

For operational monitoring/security purposes, aggregate/anonymous technical traffic data of the page may be recorded, in accordance with Konet's Privacy Policy. No collection of personal data is sought beyond what is strictly necessary for the operation of the service.

The display of the "Under Construction" page does not constitute approval, promotion or presentation of the Customer or its content by the Company. Before any campaign or production website, the Customer must remove/replace the page and verify the correct public display of its website.

8.17 System protection & email/SMTP filtering/checks

The Company reserves the right to set and dynamically adjust limits and technical control measures on the number and/or volume of messages sent or received through its services, at its absolute discretion, per service, server, IP, domain name or account. These measures are applied to ensure the stability, security and quality of email delivery for all customers. The numerical limits in force at any time (rates/parameters) are set out in §8.20 and may change without notice.

The Company may restrict, delay, reject, quarantine or delete communications that are considered harmful, unsolicited or contrary to the terms of use and/or its legitimate interests. Processing/filtering may be carried out automatically and/or manually (antivirus/antispam, reputation checks, greylisting, content/attachment filtering), with the possibility of temporarily or permanently blocking ports/protocols, IPs or entire address ranges/zones, without further notice and without any obligation to pay compensation.

Example measures that may be taken include:

a) throttling/tarpitting and queue management (queueing/queue purge),

b) isolation (quarantine) of accounts/processes or temporary deactivation of IMAP/POP/SMTP/Webmail services,

c) blocking or tightening checks per TLD/geographic region or to/from specific providers,

d) blocking based on RBLs/local reputation policies,

e) filtering/rejecting high-risk attachments (e.g. executables, password-protected archives),

f) forcing password changes, enabling 2FA or temporarily disabling access in case of suspected compromise,

g) modifying flows/routing through third-party filters/infrastructure (see §8.21).

The Customer is obliged to cooperate fully with every check, to provide the necessary information without undue delay and to take the corrective actions indicated by the Company. Failure to comply within the reasonable deadline set may result in suspension or termination of the service, without a refund. The Company is not obliged to proactively monitor content (see §8.12), but reserves the right to investigate/inspect, as well as to cooperate with the competent authorities to the extent permitted or required by law.

In addition, the Customer is obliged to implement proper SMTP authentication in all contact, registration and order forms or any other application hosted in its account that sends email through the servers of the Company. Failure to use, or improper use of, SMTP authentication may cause rejections, delays or blocking of messages. The Customer bears sole responsibility for any problem, damage or burden to the Company arising from misuse or lack of authentication, and is obliged to fully make good any related damages. The Company reserves the right to suspend or discontinue the service in the event of a breach. If the Customer does not know how to configure this, it is the Customer's own responsibility to contact the technical support provider of its website.

The Company does not guarantee the delivery of messages or their acceptance by third-party providers/recipients, who apply their own policies and filters. Delays, losses or blocks due to filters, IP/domain reputation or third-party settings do not give rise to any liability for compensation. Technical logs and statistics may be kept for security/operational purposes, in accordance with the Privacy Policy.

Matters of content/consent are governed by §8.12. The numerical sending limits and campaign rules are set out in §8.20. Routing/filtering through antispam services is described in §8.21.

8.18 SSH access - prerequisites & restrictions

SSH access is provided exclusively upon a written request (a ticket from the Client Area) and only if the Customer has a static IP address registered in its name. The Company may, at its absolute discretion, refuse to provide it, impose restrictions or revoke access at any time, without notice and without any obligation to pay compensation. Activation may be accompanied by technical conditions, such as a jailshell/chroot environment, a whitelist of specific commands, access hours, resource limits and file transfer restrictions. Access is permitted exclusively from the declared static IP addresses. Requests from other addresses are rejected. The Company may require authentication with an SSH key, disable password logins and enforce 2FA where available.

Once SSH access is activated:

• The Customer fully acknowledges and accepts the risks associated with the use of SSH.
• The Customer assumes sole responsibility for any damage or loss arising from the use of SSH access, including security issues or incorrect settings.
• The Company has no obligation to provide technical support regarding the use of SSH or for actions within the shell. If assistance is requested, it is provided only for a fee in accordance with the price list in force at the time.
• No root/sudo access is provided. Any attempt at privilege escalation, the installation/execution of sniffers, scanners or packet-capture tools, the use of compilers where not permitted, as well as any action to bypass the security policies of the platform, are prohibited.
• Port forwarding/reverse tunneling, proxy/VPN exit nodes, TOR relays, background daemons and long-running processes that consume disproportionate resources, cryptocurrency mining (crypto-mining) and any automation that burdens shared resources are prohibited. Cron jobs with a frequency of less than 15 minutes are prohibited.
• The Company may apply geographic and/or network filters, whitelisting of the declared static IPs, session duration/inactivity limits and automatic termination (idle timeout) without notice.
• For reasons of security and compliance, the Company may record access events (logs) and retain them for a reasonable period of time in accordance with the applicable legislation and the Privacy Policy.

SSH access is provided for a maximum period of 180 days and is automatically discontinued upon its expiry. Renewal takes place only upon a new request and may be refused. In case of suspected abuse, breach or risk to the infrastructure, the Company may apply immediate deactivation, blocking of ports/IPs/protocols, account quarantine, throttling or other measures without further notice and without any obligation to pay compensation.

The Customer bears exclusively the risk and responsibility for every consequence of the use of SSH, including any investigation, remediation or restore work that may be invoiced. The use of SSH is subject to the general rules of acceptable use (§8.3), security (§8.7), proper use of resources (§8.11) and email protection/flow (§8.17).

8.19 Mailboxes - quotas, retention & automatic cleanups

The email service is not a permanent storage space. Messages and attachments must be archived locally by the Customer. A default maximum storage limit of 5 GB applies to each mailbox. By way of exception, the limit may be increased up to 10 GB per mailbox exclusively upon written request and for an additional charge, at the absolute discretion of the Company. In addition, each plan may include a maximum number of mailboxes and/or total email storage limits, as announced on the page of the respective plan. These limits prevail.

The quota is calculated cumulatively for all folders of the mailbox (Inbox, Sent, Drafts, Junk/Spam, Trash, Archive, etc.). The POP3 option "leave a copy on the server" is subject to the same limits and does not bypass them. The Company may change technical limits/policies for reasons of security and performance, without further notice and without any obligation to pay compensation.

The Company may, without notice, apply automated "cleanup" and optimization policies (for example: emptying of Spam/Junk/Trash folders, compression/deletion of temporary files and logs) and reject new incoming/outgoing messages when the mailbox and/or the total plan limit has been reached. As a retention policy, messages remaining in the Spam/Junk folder are automatically moved to the Trash folder after 14 days, while the Trash folder is permanently emptied after 30 days. The above time limits may be revised for reasons of security and performance, at the absolute discretion of the Company. Any quota notifications are provided for information only, and failure to receive them does not give rise to any liability.

For reasons of performance and proper use of resources, the Company strongly recommends the use of POP3 with local storage and periodic deletion from the server. The use of IMAP is permitted but is subject to technical restrictions (e.g. maximum number of simultaneous connections, inactivity/IDLE times, folder/message limits) determined at the discretion of the Company. In cases of disproportionate resource consumption or degradation of services, the Company may restrict and/or temporarily disable IMAP connections, without any liability for any losses or delays.

The use of mailboxes as general storage space is prohibited (e.g. storing files/backups, files that are not email messages or that do not serve the normal operation of email). The Company may remove such material and impose restrictions and/or management/remediation fees, where required for the proper operation of the platform.

Additional technical limits per message apply (message/attachment size, number/type of links, accepted file types), as well as filtering policies (antivirus/antispam, reputation), which may change for reasons of security and stability. Non-delivery or delay due to quota, third-party filtering (providers/recipients), network conditions or security policies does not give rise to any liability of the Company for compensation.

In the event of expiry, suspension or termination of the service, the mailboxes and their content may be permanently deleted without the possibility of recovery and without any obligation to pay compensation. The Customer must take care in good time to export/archive its email. Compliance with any legal/regulatory obligations to retain email is the sole responsibility of the Customer.

Related terms: see also §8.12 (anti-spam/acceptable use of email) and §8.17 (sending restrictions/system protection), which apply in addition, as well as §8.9 (backups).

8.20 Outgoing email limits & campaigns/newsletters

Each hosting plan is subject to an hourly limit on sending messages through the SMTP servers of the Company, as stated from time to time on the page of the plan. The Company may, at its absolute discretion, set additional daily/per-mailbox and/or per-account limits. In addition, each message may not be addressed to more than fifty (50) recipients in total (To/CC/BCC). If the above limits are exceeded, messages may be rejected, queued or delayed, and the Company reserves the right to proceed immediately, at its absolute discretion, with the temporary or permanent suspension of the relevant account, without notice and without any liability for compensation for losses or non-delivery of email.

Newsletters, mass campaigns or bulk sending are not permitted from the sending infrastructure of the Company. The use of purchased, rented or collected (scraped) recipient lists is expressly prohibited, as is any form of "cold outreach" or unsolicited commercial communication through the infrastructure of the Company. Campaigns require the use of specialized third-party services (email marketing/transactional providers), with the Customer bearing sole responsibility for compliance (lawful consent, easy unsubscription, handling of bounces/complaints). The prohibition does not cover reasonable transactional notifications (e.g. order confirmation, password reset), which are nevertheless subject to the rate limits of the plan.

The Customer is obliged to ensure correct sending authentication with SPF, DKIM and DMARC in alignment with the sender/responder domain. The Company may provide indicative DNS records, but the responsibility for creating, ensuring the accuracy of and maintaining the records lies solely with the Customer. Rejections/filtering by third parties (ISPs, anti-spam lists, DMARC, reputation systems) due to inadequate authentication or sending practices do not give rise to any liability of the Company.

Excessive levels are considered to be, for example, failure rates (hard bounces) above five percent (5%) within a period of 24 hours or spam complaint rates above zero point one percent (0,1%) within the same period. If the above indicators are exceeded, the Company may impose a temporary restriction on sending (throttling), suspension of the account or a requirement to clean the recipient list before reactivation.

It is prohibited to bypass limits by splitting sends, using multiple mailboxes, external scripts or third-party SMTP used on behalf of the infrastructure of the Company. Spoofing, open-relay behavior or SMTP abuse constitute a serious violation and result in immediate restriction or suspension, without notice and without any obligation to pay compensation.

To protect the reputation of the networks, the Company may require the mandatory use of ports 587/465 with TLS/SSL and SMTP AUTH, block outgoing traffic from/to specific ports (for example 25), apply throttling/greylisting/additional filtering, dynamically modify limits and temporarily disable sending with excessive bounce or complaint rates. The listing of IPs/domains on blocklists (RBLs) or the degradation of reputation due to the Customer's practices is not the responsibility of the Company. Delisting/remediation is the responsibility of the Customer and no timeframe is guaranteed. Where appropriate, a dedicated IP may be offered for an additional charge and with justification, without a guarantee of delivery.

In shared hosting, if the shared IP is listed on RBLs as a result of acts or omissions of a specific Customer, the Company may impose on that Customer reasonable charges for remediation/incident handling (for example: technical time for investigation/cleanup, delisting requests, reallocation/replacement of the IP, communication with third-party providers, additional filters/measures), as well as any related charges or damages incurred. The Company may require an advance payment and/or a deposit for the continuation of the service. The above are cumulative with the provided suspension/termination measures and are without prejudice to any other right of the Company.

The Company may block types of attachments (e.g. executables, encrypted/password-protected files), restrict message/attachment sizes and record technical metadata (headers, timestamps, IPs) exclusively for purposes of security/combating abuse, without proactive supervision of content. Non-delivery/delay due to limits, third-party filtering, network conditions or security policies does not constitute grounds for compensation.

The provisions of this section apply in addition to §8.12 (anti-spam), §8.17 (system protection/sending restrictions) and §8.19 (quotas/retention). In the event of a breach, the Company may take any appropriate measure, including the immediate suspension or termination of the service, without further notice and without any obligation to pay compensation.

8.21 Email filtering (SpamExperts/SpamAssassin) - terms of use

The Company offers incoming and/or outgoing email filtering services through the provider SpamExperts on selected plans. Where it is not included, it is available as an add-on service. Some plans include only incoming protection, others both flows. On plans without SpamExperts, cPanel SpamAssassin is provided "as is" (as-is), without any obligation of support by the Company.

Upon activation of the service, a dedicated SpamExperts control panel is provided (on the provider's infrastructure), accessible through the Client Area at konet.gr and/or through cPanel. From there it is possible to view/recover quarantined messages, manage allow/deny lists and basic settings, according to the features of the respective plan. The availability/responsiveness of the panel depends on the third-party provider, and any discontinuities or limitations do not give rise to any liability of the Company.

Upon activation of SpamExperts, incoming and/or outgoing email is routed through the provider's systems for filtering/scoring/quarantine. Headers/subject may be modified, messages may be tagged or blocked/quarantined/rejected, at the discretion of the filters. The Customer is obliged to correctly apply the required DNS/SMTP settings (e.g. MX, smart-host/SMTP relay, SPF/DKIM/DMARC) in accordance with the instructions of the Company. Delays/rejections due to incorrect settings are not the responsibility of the Company.

For SpamExperts, the Company provides basic configuration/diagnostic support (quarantine access, allow/deny lists, log review). Advanced settings, rule customizations, bulk list imports or remediation actions may be charged extra. SpamAssassin is used solely at the Customer's own responsibility and without configuration/optimization support.

The Customer accepts that no filtering system is infallible. Legitimate messages may be classified as unsolicited (false positives) and vice versa. The Customer must regularly check the quarantine/logs, configure the whitelist/blacklist and recover any messages in good time. Quarantine/log data is retained for a limited period of time set by the provider and is then permanently deleted. Failure to recover messages within that period does not give rise to any liability or obligation of the Company to pay compensation. The service is neither an archiving mechanism nor a guarantee of email delivery.

When outgoing filtering is used, sending is carried out through an authenticated relay (smart-host) with mandatory SPF/DKIM/DMARC alignment. Policy violations (e.g. spam bursts, phishing, malicious attachments, alignment deception) may result in immediate blocking/quarantine of the flow, rate restrictions and/or suspension of the account, without notice and without any obligation to pay compensation, cumulatively with any other measure under these terms. For campaigns/bulk sending, §8.20 applies.

The Company reserves the right to modify, replace or discontinue the third-party anti-spam provider at any time and/or to temporarily bypass the routing for reasons of service continuity, at its absolute discretion and without further notice, without any obligation to pay compensation for delays/slippages/incompatibilities during the transition.

For the operation of the filtering, sender/recipient data, technical metadata (IPs, headers, timestamps), content/attachments (for detection/scoring) and logging/quarantine events are processed. The Customer is the Controller of its email data and authorizes the Company to use the provider SpamExperts as a sub-processor. The Company ensures appropriate contractual terms with the sub-processor. The Customer must have a lawful basis for processing and comply with its obligations to inform data subjects. International transfers may take place in accordance with the provider's policy, and the Customer accepts them to the extent that they are lawfully necessary for the operation of the service.

The service is subject to volume/rate/account limits set by the plan and/or the commercial offer in force at the time. Misuse or breach of these terms may lead to the immediate suspension or termination of the service, without further notice and without any obligation to pay compensation.

8.22 Open-source applications & Softaculous - responsibility & limitations

Open-source applications and/or automatic installations made available through Control Panel tools (e.g. Softaculous) are provided "as is" (as-is), without any guarantee of functionality, security, compatibility or availability of support. The Company does not undertake, within the scope of the hosting service, the configuration, customization, debugging, upgrading or repair of such applications.

The Customer bears sole responsibility for:

• timely updates to the core, themes, extensions/plugins and libraries,
• correct configuration of permissions/security parameters and use of strong credentials,
• lawful licensing ("nulled/cracked" versions are prohibited),
• compatibility with the PHP/DB/Web Server versions applied on our infrastructure at any given time.

Softaculous is provided solely as a convenience tool. The available versions/packages and its automations (install/upgrade/clone/staging) may differ from the official versions of the projects. Installation/upgrade failures, incompatibilities or data loss arising from its use are not the responsibility of the Company (see also §8.9). Enabling backups from within Softaculous is expressly prohibited, while the use of "staging/clone" consumes resources (disk space/databases/files) of the plan and is subject to the limits/policies of §8.4–8.5. Backup files created by Softaculous may not be stored in the hosting space (see §8.5) and are deleted immediately, without notice, as soon as they are detected.

The Company may, at its absolute discretion and without prior notice, take immediate technical measures to protect the infrastructure/other customers, such as deactivating or removing vulnerable themes/plugins/versions, quarantining or deleting infected files, enforcing WAF/ModSecurity rules, restricting/disabling cron or outgoing SMTP, blocking dangerous PHP functions, and isolating the account. Any malfunction of the website due to these measures does not give rise to any liability or obligation of the Company to pay compensation.

If illegal copies or serious vulnerabilities are found that are not addressed immediately, the Company may suspend and/or terminate the service without notice and without any obligation to pay compensation, requiring immediate remediation. The Customer is obliged to compensate us for any damage arising from a related incident, including reasonable costs of investigation/cleanup, technical support, legal assistance and countermeasures.

Related violations that lead to spam/phishing or other abuse (see §8.12, §8.20) cumulatively trigger the corresponding clauses on suspension, charging for remediation work and compensation.

8.23 Supported technical environments & compatibility

The Company defines and supports specific technical environments (for example: PHP/Node/Python versions, MySQL/MariaDB, web server, OpenSSL/cURL, libraries/extensions, TLS/SSL protocols and security policies). The Company reserves the right, at its absolute discretion, to upgrade, modify or withdraw any version, setting and/or module, to change security defaults (e.g. disable_functions, memory_limit, max_execution_time) or to end the availability of obsolete (EOL) components, without any obligation to retain older versions, without further notice and without any obligation to pay compensation.

The Customer accepts that application/network-level security policies (WAF/mod_security, anti-bot, rate-limits) may affect the behavior of applications. Requests for whitelisting/relaxation of checks are accepted only at the absolute discretion of the Company.

The Customer bears sole responsibility for ensuring that its code, CMS, plugins/themes, libraries and dependencies (composer/npm/pip, etc.) remain compatible with the supported environments, for applying security updates/fixes in a timely manner, for removing unsupported or vulnerable add-ons and for carrying out the necessary tests/migrations (staging, rollback plan) before any change. The Company is not obliged to provide development services, fixing of incompatibilities or code customization. Any assistance is provided only for a fee, without any guarantee of result or of remediation time. For widely used platforms, the Company may selectively enable auto-updates of the core/themes/add-ons for security reasons, without any obligation of prior notice.

In the event of critical security issues or incompatibilities that endanger the infrastructure or third parties, applications/plugins/themes may be deactivated immediately, the account may be placed in quarantine/maintenance or mandatory upgrades may be imposed (e.g. migration to a newer PHP), without notice and without any obligation to pay compensation. The Customer is obliged to cooperate and comply without undue delay. In case of non-compliance, the provisions of §8.3 and §8.13 (restriction/suspension/termination) apply.

By way of exception and only where technically feasible, an environment with an older version or isolation (isolation/container) may be offered temporarily for an additional charge and under strict restrictions. The Company may refuse any downgrade or the retention of "legacy" versions in the shared environment. Any options for multiple versions of languages/engines (e.g. Multi-PHP or PHP Selector) are provided where technically available, without any commitment to retain a specific version.

The Company makes reasonable efforts to give notice of scheduled compatibility changes through the website/Client Area/email, where feasible. In urgent security matters, actions may be applied immediately and without prior notice. Rollback to earlier versions is neither guaranteed nor provided as an obligation.

The Customer must keep valid licenses for third-party software/add-ons. Invalidity or breach of license terms may lead to the immediate deactivation of the relevant components. The Company is not liable for malfunctions caused by changes/incompatibilities of third-party services (e.g. payment providers, APIs, gateways, external modules).

Before significant updates/changes, the Customer must take and verify adequate backups. See also §8.9 for limitations/disclaimer of liability regarding backup/restore. Any damage/downtime caused by inadequate updates, incompatibilities or non-compliance with the above is borne solely by the Customer, who is obliged to compensate the Company for any actual loss/loss of profit (including reasonable costs of investigation/remediation). Continued use of the service after compatibility changes constitutes acceptance of the changes.

Related terms: §8.2 (infrastructure maintenance/upgrades), §8.8 (technology changes), §8.15 (code security/permissions), §8.22 (open-source/Softaculous).

8.24 Service lifecycle (activation-expiry-suspension-deletion)

The provision of hosting services follows a standardized lifecycle (activation, term, expiry, suspension, deletion) defined by the Company, with the security and stability of the infrastructure as the guiding principle. The Company may, at its absolute discretion, adjust procedures/timings and take immediate technical measures (restrictions, quarantine, blocks, parameter changes), without further notice and without any obligation to pay compensation.

8.24.1 Activation. The provision of the service begins after confirmation of the order and clearance of payment, as well as any identity verification/anti-fraud checks that the Company deems appropriate. The Company may refuse or delay activation at its absolute discretion, without any obligation to give reasons or pay compensation, particularly in cases of risk to security or to the lawfulness of use. Upon activation, a temporary "Under Construction" page may be displayed (see §8.16).

8.24.2 Term - renewal. The services are provided in advance for the agreed period. Expiry occurs at the end of the prepaid period, unless a timely renewal has taken place. Any expiry notifications are sent for information only. Failure to receive/read a notification does not release the Customer from its obligations. Any automatic renewals apply only if enabled by the Customer and are not guaranteed to succeed (e.g. payment failure). Partially unused periods are not refunded.

8.24.3 Suspension due to expiry or outstanding debt. Upon expiry and/or failure to pay on time, the service may be suspended immediately without notice and without any obligation to pay compensation. During suspension, HTTP/HTTPS/FTP/SSH/Email access may be disabled, nameservers may be changed, outgoing email may be discontinued and message queues may be rejected and/or deleted. The Company may impose reactivation/administration fees.

8.24.4 Grace period - quarantine. After expiry, the Company may, at its absolute discretion, provide a grace period of 14 days and/or place the service in a quarantine state with possibly limited functionality. The duration of the grace/quarantine period cannot be modified. The Company may decline to provide it and proceed immediately to deletion/termination, without further notice and without any obligation to pay compensation, if the Customer has violated the Terms of Service of its services and/or if, during the agreed period, the Customer, at the absolute discretion of the Company, endangered its infrastructure. Upon the expiry of the grace period without action, if there is no settlement or compliance, the contract is deemed terminated by operation of law and the service proceeds to permanent deletion as set out in §8.24.5.

8.24.5 Permanent discontinuation - data deletion. Upon permanent discontinuation, the data is removed from the active production systems. The Company may, for technical/operational restore purposes, keep a backup for up to 3 months from the discontinuation. The existence/completeness/usefulness of this backup is not guaranteed and it may expire earlier for reasons of security/compliance. This backup does not replace the Customer's obligation to keep its own backups and does not constitute an archive of the Customer. After the above period has elapsed, any remaining backup is permanently deleted, without the possibility of recovery. Permanent deletion entails the termination of the contract and the loss of any access or claim. After the grace period has elapsed, deletion takes place regardless of the existence of backups, without any obligation of further notice.

8.24.6 Reactivation - restore. Reactivation after suspension or discontinuation is subject to full payment, availability of resources and technical feasibility. If the above backup exists (see §8.24.5), the Company may offer a restore for a fee (for example: time-based charge, handling fees), without any guarantee of success or data integrity. In addition to payment, the Company may require the payment of a reactivation fee (reconnection fee) as well as, at its absolute discretion, an advance payment and/or a deposit for the continuation of the service.

8.24.7 Plan and billing changes. During the current period, only plan upgrades are permitted. Downgrades are not carried out before the end of the period.

In the event of an upgrade, the charge is calculated on the basis of the remaining period until the expiry of the current subscription. The cost of this period for the new, upgraded plan is offset against the credit balance arising from the previous plan. The Customer pays the difference, if the debit balance is greater than the credit balance. The above calculation constitutes a pro rata (proportional) calculation of the charge.

If the credit balance exceeds or is equal to the debit balance arising from the upgrade, the upgrade is not carried out.

A change of billing period takes place only if the debit balance arising from the upgrade is greater than the credit balance. The new period starts on the basis of the upgraded plan. The new expiry date after the upgrade is the expiry of the period of the new plan selected.

8.24.8 Retained legal obligations. After discontinuation, the Company may retain limited technical/accounting data (e.g. security logs, invoicing) for as long as required by law and/or for providing the restore option under §8.24.5 within up to 3 months. This data is not available for other purposes and does not constitute an archiving service.

8.24.9 Procedure changes - priority of stability. The Company is entitled to revise at any time the timelines/procedures for activation, expiry, suspension and deletion and to take immediate measures to protect the infrastructure (e.g. blocks, restrictions, quarantine), without further notice and without any obligation to pay compensation, where this is required for security/stability or compliance with the law.

8.24.10 Payment default - chargebacks. In the event of a payment dispute or a reversal of a transaction (chargeback), the Company may immediately suspend and/or terminate every service provided to the Customer and every related commercial relationship (including reseller relationships and referral/affiliate programs), and may impose administration/investigation fees, request an advance payment/deposit for any reactivation and block future orders, without any obligation to pay compensation.

8.24.11 Dependent/supplementary benefits. Any supplementary or promotional benefits (e.g. SSL, dedicated IPs, transfers) cease automatically upon the discontinuation or downgrade of the main plan. The Company may adjust charges if their retention is required on a standalone basis.

8.24.12 Obligation to keep details up to date. The Customer must keep its contact and billing details up to date. Problems with the delivery of notifications (e.g. spam filters, inactive email addresses) do not suspend the progress of the lifecycle and do not give rise to any liability of the Company.

8.24.13 Management of nameservers during upgrades/transfers. During the upgrade or migration of infrastructure, the Company may require changes to nameservers and/or other DNS parameters for correct routing.

a) Where the domain names are managed/registered by the Company, the Customer expressly authorizes and consents to the Company automatically making the necessary nameserver/DNS changes. This action may cause temporary changes during the propagation period, without any obligation to pay compensation, which the Customer, by accepting these Terms of Service, declares that it understands and accepts.

b) Where the domain names are not managed/registered by the Company, the Customer is obliged to make the required nameserver/DNS changes itself within the time period set by the Company. Non-compliance or late implementation is the sole responsibility of the Customer and does not give rise to any liability of the Company for any interruptions, losses or malfunctions. The Company may set technical prerequisites (e.g. TTLs, zones/records) and request proof of completion.

c) The Company may apply temporary measures (e.g. alternative IPs, quarantine, changing nameservers to default) to protect the infrastructure and complete the work, without further notice and without any obligation to pay compensation.

8.24.14 Change of nameservers and non-use of services. If the Customer, during the active hosting period, changes the nameservers and does not use any of the services provided (e.g. website hosting, email), the Company may, for reasons of security and optimal resource management, delete the hosting account from the active systems within seven (7) days. The Customer is informed of the deletion by electronic notification.

The Company may, at its absolute discretion, keep a backup of the account exclusively for restore purposes, until the end of the hosting period. The restore is carried out only if the Customer reactivates at least one of the services of the account (e.g. website, email), in accordance with the applicable procedures and charges. After the end of the hosting period, the backup is permanently deleted without the possibility of recovery.

8.24.15 Technical changes during upgrade or migration. The Company may, in the context of an upgrade or migration, modify IPs, nameservers, software versions/parameters and reallocate resources. The Customer must adjust DNS, nameservers, applications and third-party integrations in accordance with the instructions and within the time windows set by the Company.

Failure or delay by the Customer in implementing the required changes (for example change of nameservers/DNS) resulting in interruption, delay or failure of operation (e.g. website, email, APIs, SEO) is the sole responsibility of the Customer. The Company bears no liability whatsoever and has no obligation to pay compensation for any losses, damages or indirect consequences.

8.24.16 Data export after expiry. Upon request of the Customer, the Company may, at its absolute discretion and where technically feasible, provide assisted data export and/or migration services to an external environment. This service is provided exclusively as an additional benefit, does not constitute a contractual obligation and may be invoiced with special fees (for example: time-based charge, handling fees, storage/transfer costs). The success, completeness and integrity of the export are not guaranteed and depend on the availability of backups, technical compatibility and the timing of the request. Any liability of the Company is limited to the charge paid for this service.

8.25 Website & email transfers/migrations - terms

"Transfer" means any work of copying/migrating files, databases, email accounts, settings and related items from a third-party provider or system to the servers of the Company, as well as the adjustment of basic parameters (e.g. DNS) for proper operation. The service is provided "as is", without any guarantee of completion within a specific time or of the possibility of full replication/functionality, and without any guarantee of success.

8.25.1 The Company carries out transfers only if the Customer provides, within 3 months, complete and valid access details for the required services/systems (for example: source control panel such as cPanel/Plesk, FTP/SFTP/SSH, database access, CMS administrative access, domain registrar details for nameserver changes, IP whitelisting, Authorization Code/EPP Code for a change of registrar). Incomplete or incorrect details, security restrictions (firewalls, 2FA without cooperation) or technical obstacles at the source may delay, limit or cancel the work without liability of the Company. Any free transfers do not apply to Lite Web Hosting plans or to VPS or Dedicated Servers services.

8.25.2 During the transfer, the Customer must refrain from changes to content/code/databases ("content freeze") until completion and confirmation of operation. Changes made at the source after the start of the process may not be transferred. The Company is not liable for data inconsistencies due to the lack of a "content freeze".

8.25.3 The Company may, at its absolute discretion, set reasonable technical limits/exclusions regarding data volume, number of inodes/files, size/number of databases, number/volume of mailboxes and file types (e.g. logs, temporary files/caches, standalone backups and bulky media are excluded). Transfers from non-standard environments, custom platforms or old/incompatible application versions are carried out on a "best effort" basis and may require additional chargeable adaptation work.

8.25.4 The Company may refuse or suspend a transfer if malicious/infected code, compromised accounts or unlawfully acquired/infringing content is detected. Any required cleanup/security hardening, CMS/plugin/theme updates and related actions are provided, if undertaken, for an additional charge.

8.25.5 The responsibility for verifying functionality after the transfer lies solely with the Customer (frontend/back office, forms, payments, APIs, cron jobs, SEO/redirects, HTTPS mixed content, email flows/forms, webhooks). Implied use/failure to raise objections within 72 hours of the completion notice constitutes acceptance. Subsequent changes/fixes are considered new, separate work.

8.25.6 The Company does not guarantee the retention of third-party settings/credentials (e.g. payment keys, licensing, external integrations), SEO indexing/rankings, historical statistics/analytics, sessions, shopping carts/pending orders, DNS records, nor the continued operation of add-ons/themes/extensions that require special licenses or versions. The Customer takes care of renewing/transferring licenses and providing the relevant keys/secrets.

8.25.7 The transfer of email accounts concerns the creation of the same mailboxes and, where feasible, the synchronization of messages. Differences in folders, labels, filters, rules or contacts/calendars may not be transferred. The Customer is responsible for keeping local copies/archives before the start. The SPF/DKIM/DMARC/MX settings are aligned based on the instructions of the Company. Rejections/delays by third parties do not give rise to any liability for compensation. Each mailbox is transferred only if its total size at the source (including all folders/subfolders and attachments) does not exceed the maximum permitted limit per mailbox of the selected hosting plan. If the size exceeds the limit, the Customer must, before the start of the process, either reduce the size appropriately (e.g. local archiving/deletion), or upgrade to a plan with a higher limit, or request in writing an exceptional increase where available for an additional charge. The Company is entitled to refuse, limit or discontinue the transfer if it would lead to exceeding quotas or to a breach of the email retention/cleanup policies (see §8.19), without liability for any loss or non-delivery of messages. A partial transfer (e.g. excluding Spam/Trash/Archive folders or attachments above a certain size) may be carried out only with the express acceptance of the Customer. Example: a 10 GB mailbox at a third-party provider is not transferred to a plan with a maximum of 2 GB per mailbox.

8.25.8 Where the domains are managed/registered by the Company, the Customer authorizes the necessary nameserver/DNS changes. Otherwise, the Customer must carry out the changes itself within the time windows set by the Company. Delays/omissions of the Customer do not establish any liability of the Company for downtime or losses (see also §8.24.13).

8.25.9 Time references are estimates and may be modified without notice due to third parties/networks/workload. During the switchover (cutover), brief interruptions or behaviors due to propagation may occur. The Company may impose off-peak "work windows".

8.25.10 The transfer is a separate service charged on the basis of an estimate and/or an hourly cost, depending on the volume, complexity, systems, the need for urgent handling (outside business hours/holidays) and any repetitions due to changes at the source. Free transfers may be offered only where expressly provided for in a commercial offer/plan page, with a specific scope/limits. Lite Web Hosting plans, as well as VPS and Dedicated Servers services, are expressly excluded from any free transfer offer. For the above services, the transfer is provided, if undertaken, exclusively for a charge based on a quote. Work outside the scope (e.g. malware cleanup, application upgrades, fixing incompatibilities, SSL reissue, code/SQL adjustments, data transformations, repeated attempts due to incomplete details) is charged additionally. An advance payment may be required.

8.25.11 If the Customer requests a free website transfer, it expressly accepts that, upon the start of the transfer work, it waives any withdrawal policy and/or money-back guarantee that would apply to the corresponding hosting subscription. The waiver applies regardless of the extent of the work or whether the transfer is completed, provided that the non-completion is not attributable to the fault of the Company.

8.25.12 The Company is not liable for loss/corruption of data, delays or malfunctions caused by limitations/errors of the source, incompatibilities of applications/versions, third-party policies (e.g. email/antispam providers, payment gateways, CDNs) or acts/omissions of the Customer. Before any work, the Customer is obliged to have complete and recent backups outside the infrastructure of the Company. Failure to do so does not give rise to any obligation of the Company to pay compensation.

8.25.13 The Customer declares that it is legally entitled to transfer the data and acts as Controller for any personal data. The Company acts as Processor for the technical purposes of the migration, in accordance with the applicable data protection policy and the processing terms in force. The Customer must inform its users and comply with its legal obligations.

8.25.14 The Company may, at its absolute discretion, refuse, suspend or discontinue a transfer and/or the related hosting service in the event of a breach of terms, a security risk or lack of cooperation by the Customer, without further notice and without any obligation to pay compensation.

8.25.15 DNS modifications, performance optimizations, software version changes, database restructuring or fixing of errors that arise after acceptance (§8.25.5) are treated as separate services with a corresponding charge.

8.25.16 In cases where bulk synchronization of historical email or conversion of mailbox formats is required, the Company may propose alternative methods (for example: local archiving/export, transfer limited to a time horizon). Partial or gradual transfer of messages does not constitute defective performance.

8.25.17 The transfer is presumed completed when the basic availability checks (website loading, database connection, basic flows) succeed and the minimum DNS/SSL/email settings declared by the Company have been applied. Any pending third-party matters (e.g. propagation, reindexing, cache warm-up) do not prevent delivery.

8.26 Incident management & remediation charges

In every incident arising from the use of the services in breach of these terms and/or that requires additional technical, operational or legal handling on the part of the Company, the Company may, at its absolute discretion, carry out investigation, containment/suppression, remediation and preventive measures and charge the Customer every related cost, without further notice and without any obligation to pay compensation. "Incident" means, by way of example (and without limitation), any event that exceeds normal/ordinary technical support, such as:

a. Sending unsolicited email/malicious content (spam, phishing, malware), listing of IPs/domains on RBLs/blacklists, increased bounce/complaint rates, backscatter. This includes investigation time, delisting requests, reallocation/replacement of IPs, additional filtering and communication with third parties. (Related to §8.12, §8.17, §8.20, §8.21).

b. Compromise/infection of accounts (defacement, backdoors, web-shells, botnets) or abuse of resources (DoS/DDoS from/to an account, brute-force, port scans), requiring isolation (quarantine), restoration of settings, deactivation of scripts, reinstallation or migration.

c. Exceeding or abusive use of resources (CPU/RAM/IO/EP, inodes, disk/traffic, IMAP connections, SMTP queues) that results in degradation of services or harm to other customers and requires throttling, configuration/optimization, a plan upgrade or an emergency transfer to other infrastructure. (See also §8.4, §8.5, §8.11, §8.19).

d. Unlawful or infringing content or content that affects the rights of third parties (intellectual/industrial property, personal data), including removal requests/complaints (e.g. notices from rights holders, authorities, providers) and the response actions. (See also §8.3).

e. Incorrect settings of the Customer (DNS/MX/SPF/DKIM/DMARC, cron scripts, redirects, auto-responders, open relays/proxies) that cause loops, floods, delivery failures or burdens on systems.

f. Requests for recovery/export/review of logs beyond the ordinary, technical expert examinations/forensics, legal/regulatory investigation obligations, including cooperation with competent authorities, to the extent permitted or required by law.

g. Recoveries from backups, where required due to acts/omissions of the Customer (deletions, malicious alteration, application failures), under the terms of §8.9 and §8.19.

Unless otherwise expressly provided in a commercial offer, the Company may charge:

• technician hourly rates (business hours/outside business hours/holidays with a surcharge) according to the price list in force at the time, with a minimum charge per incident,
• third-party costs (e.g. anti-abuse/anti-malware tools, RBL delisting fees, dedicated IPs, CDN/mitigation, additional bandwidth/traffic, external consultants/lawyers),
• operational remediation costs (migrations, reconfiguration of services, DNS/nameserver changes, reissue/configuration of certificates, etc.).

The measurements/records (logs) of the Company and its partner providers sufficiently document the scope of the incident and may be used to calculate the charge, even by estimate where an exact valuation is not practically feasible.

Investigation/remediation costs are immediately due. The Company may:

(i) request an advance payment/deposit for the continuation of services,

(ii) set them off against any credits,

(iii) suspend and/or terminate services until payment in full,

(iv) impose default interest and collection costs (including the fees of a lawyer/agent).

Following a chargeback or refusal to pay related charges, the Company may immediately suspend every service of the Customer and every commercial relationship (including a reseller or referral partner relationship), as also provided in §8.24.10.

The Customer is obliged to indemnify, defend and hold harmless the Company, its officers, employees and partners from every claim, damage, fine, charge or third-party cost (including reasonable legal/technical fees) caused by an act or omission of the Customer or by the use of its services in breach of the terms, the law or the rights of third parties. In the event of damage to the infrastructure/services of other customers caused by actions of the Customer, the Customer is fully liable for covering the damage and the related remediation costs.

Where the Company acts as processor, every administrative/technical/legal compliance cost arising from a security incident attributable to the Customer (e.g. breach notifications, risk assessments, additional measures) is borne by the Customer.

The taking of measures by the Company in relation to an incident does not constitute an acceptance of liability or an undertaking of permanent remediation. The Company may permanently delete malicious/unlawful material, modify security settings and impose preventive restrictions (e.g. throttling, quarantine, deactivation of functions), where it deems this necessary for the security and stability of its infrastructure. The provisions of this section apply cumulatively with every other right or measure provided for in these terms.

8.27 Hosting availability & force majeure - no SLA/credits

The hosting services are provided through infrastructure and networks that interact with the public Internet and third-party systems. Continuous and uninterrupted operation depends on factors outside the direct control of the Company. Therefore, no contractual availability guarantee is provided and the following special terms apply.

8.27.1 The Company is not bound by any specific level of availability (SLA), response time or restoration time, and does not owe service credits, refunds or compensation for interruptions/degradations/delays. The restoration time depends on the nature of the incident and may be affected by third parties. The general limitations of liability of the terms apply in addition (see also §2, §8.2).

8.27.2 The public Internet, network/interconnection providers (ISPs, carriers, peering, IXPs), DNS/CDN services, email/anti-spam providers and third-party platforms are not under the control of the Company. Congestion, packet loss, routing changes, filtering by third parties (e.g. blacklists/anti-spam), policy restrictions or technical barriers of third parties do not give rise to any liability of the Company for compensation.

8.27.3 The Company may carry out scheduled or emergency maintenance/upgrade work, which may cause temporary interruptions or degradation of services. For scheduled work, efforts are made to give timely notice. There is no obligation to pay compensation for effects arising from such work (see also §8.2, §8.8).

8.27.4 In incidents of malicious activity (for example: DDoS, exploitation of vulnerabilities, spam/phishing waves), the Company may, at its absolute discretion, apply mitigation/protection measures (e.g. blocking of ports/IPs/networks, traffic shaping, black-holing, isolation of services/accounts, quarantine). Any temporary inability to access or degradation resulting from these measures does not establish liability.

8.27.5 Where the hosting services depend on third parties (for example: data centers, anti-spam/anti-virus providers, SSL certificate issuers, registries/naming mechanisms, software/platform providers), discontinuities, policy changes, technical problems or limitations of these third parties are not the responsibility of the Company and do not constitute grounds for compensation (see also §8.21).

8.27.6 The Company is not liable for interruptions/degradation of services caused by events of force majeure or other exceptional events beyond its control, such as, by way of example: natural disasters, fires, floods, earthquakes, extreme weather events, extensive failures/outages of power supply or telecommunications providers, wars/hostilities, terrorist acts, civil unrest/strikes, epidemics/pandemics, governmental/regulatory acts or sanctions, supply crises, suspended international transfers, mass cyberattacks, serious security incidents at critical suppliers (e.g. control panel/software vendors, registries/TLDs), global vulnerabilities/zero-day exploits or cryptographic failures. In all the above cases, no compensation is owed.

8.27.7 The Company is not liable for indirect or consequential losses of any kind (such as loss of profits, data, customers or reputation, effects on SEO/rankings, third-party penalty clauses/fines or losses due to cache/CDN), arising from incidents covered by these terms (see also §2).

8.27.8 When technically feasible, the Company may post status updates in the Client Area and/or other information channels. Failure to receive, or late receipt of, a notification does not establish any liability or obligation to pay compensation.

8.27.9 The Customer must provide for its own business continuity (for example: external backups, backup MX/SMTP where appropriate, alternative communication channels, appropriate scaling of resources, use of specialized/high-availability solutions for critical operations). Relying on a shared hosting environment alone for critical processes is the sole responsibility of the Customer.

8.27.10 In large-scale incidents, the Company may prioritize remediation work, giving priority to the stability of the network/infrastructure over individual accounts/services. The choice and order of actions are at its absolute discretion, without any obligation to pay compensation.

8.27.11 The above apply cumulatively with the general limitations of liability and the clauses of §2, §8.2, §8.8 and other relevant terms. Any tolerance or temporary deviation does not constitute a waiver of the rights of the Company and does not create a precedent.

8.28 DNS & nameservers - management, responsibilities, limitations

Naming services (DNS) and nameservers are a critical element in the operation of websites, email and related services. The correct configuration/maintenance of DNS zones and compliance with the deadlines for changes/transfers are necessary for availability. The Company may request specific settings/actions and may make technical changes when required for security and/or smooth operation, as specifically set out below.

8.28.1 Where the domain name is managed/registered by the Company, the Company may set/change the nameservers required for the provision of the service, particularly in the context of an upgrade/migration or the application of security measures, without further notice and without any obligation to pay compensation. The Customer gives its prior consent to such changes. Where the domain is not managed by the Company, the Customer is obliged to make all required nameserver/record changes itself, within the deadlines set by the Company. Any delays or omissions are not the responsibility of the Company (see also §8.24.7).

8.28.2 The Company provides DNS management tools for basic records (A/AAAA, CNAME, MX, TXT, SRV, CAA where supported). The responsibility for the content, correctness and updating of the records lies solely with the Customer. The Company may provide indicative values/instructions, but is not obliged to design DNS architectures, support complex zones (GeoDNS, weighted/health-checks, DNS flattening) or manage settings of third-party services, unless this has been expressly agreed and invoiced.

8.28.3 Propagation and cache times depend on third-party recursive resolvers, ISPs and device settings and are not under the control of the Company. The Company may, particularly during migrations/maintenance, adjust TTLs and/or temporary records for a smooth switchover. Propagation delays/inconsistencies do not establish any liability for compensation.

8.28.4 When the Customer chooses third-party DNS providers or content intermediaries (CDN/proxy/WAF), it assumes full responsibility for:
a) correct routing to the origin endpoints of the Company,
b) SSL/TLS compatibility (termination/re-encryption, SNI, protocols),
c) security/filtering rules that may block legitimate traffic,
d) the effects of caching/aggressive optimizations and
e) maintaining the required records (MX/SPF/DKIM/DMARC/CAA).
Availability/performance/delivery issues caused by a third-party provider are not the responsibility of the Company. If third-party settings cause risk or instability, the Company may request a return to its nameservers or the removal/modification of the settings. Non-compliance may result in restrictions/suspension at its absolute discretion (see also §8.27).

8.28.5 Enabling DNSSEC is supported where technically available. The correct publication/maintenance of DS records and the maintenance of the keys are the responsibility of the Customer. During transfers/nameserver changes, temporary deactivation of DNSSEC may be required to avoid resolution failures. CAA settings that restrict certificate issuance may prevent SSL renewal/issuance. The responsibility lies with the Customer. Issuance/renewal failures due to DNSSEC/CAA do not give rise to any liability of the Company.

8.28.6 The correct operation of email requires accurate MX records and aligned SPF/DKIM/DMARC authentication. The Company may provide indicative templates or entries relating to its own services (e.g. relay/filtering under §8.21), but the Customer bears the responsibility for maintenance/testing/upkeep, especially when using external email providers. Non-delivery/degradation due to incorrect DNS is not the responsibility of the Company (see also §8.19, §8.20, §8.21).

8.28.7 Reverse DNS (PTR) settings are available only for dedicated IPs provided by the Company and upon justification of use where required. PTR on shared IPs is not supported. PTR changes may be subject to third-party procedures and delays that the Company does not control.

8.28.8 The creation of private nameservers (ns1/ns2 under the Customer's domain) requires the correct publication of glue records at the registrar and the continuous updating of the corresponding A/AAAA records. Incorrect or outdated addresses lead to loss of services without liability of the Company. The Company may refuse private NS in scenarios that cause risk/instability.

8.28.9 In cases of urgent need (security, compliance, prevention of abuse or protection of infrastructure), the Company may insert temporary records, redirect to an information/suspension page or make other necessary modifications to the DNS zone served by its nameservers, at its absolute discretion, without prior notice and without any obligation to pay compensation. Where the domain is managed by another registrar, the Customer is obliged to implement the instructions without undue delay.

8.28.10 DNS changes requested by the Customer are carried out after identification (through the Client Area/ticket) and according to the prioritization of technical support. Complex configurations, bulk zone transfers, special third-party scenarios or work outside business hours may be invoiced in accordance with the price list in force at the time. The Company does not guarantee specific implementation times.

8.28.11 The operation of DNS involves technical metadata (e.g. IPs, timestamps, logs). When the Customer uses third-party DNS/CDN providers, the Customer bears the responsibility for informing users/privacy policies and for any international transfers lawfully carried out by those third parties. The Company may keep limited technical logs for security/compliance purposes, in accordance with the law.

8.28.12 These terms apply in addition to §8.24.7 (migrations/nameserver changes), §8.21 (email filtering), §8.27 (availability/force majeure) and the general limitations of liability. Any non-compliance of the Customer with DNS instructions may lead to the restriction or suspension of services at the absolute discretion of the Company, without further notice and without any obligation to pay compensation.

8.29 Reseller Hosting - special terms

These terms apply in addition to the other hosting terms in the case of the purchase/use of a Reseller Hosting plan. The "Reseller" provides hosting services to end customers through the infrastructure of the Company (for example: cPanel/WHM), remains solely responsible for the relationship with them and their support, and must ensure that all its end customers comply with these Terms (particularly §§ 8.1–8.28 and the Acceptable Use Policy). The features/limits of each Reseller plan are set out on the respective product page and prevail as special terms.

8.29.1 The Reseller acts in its own name and on its own behalf. It is prohibited from presenting the Company as a contracting party to its end customers or from using the trademarks/name of the Company without written permission. The provision of "white-label" services or private nameservers, where available, does not create a corporate/agency relationship.

8.29.2 The Company provides technical support exclusively to the Reseller (authorized persons/accounts) and not to its end customers. The Reseller must provide 1st level support (L1) to its end customers, including handling requests, basic settings and initial diagnosis. The Company provides the Reseller with 2nd level support (L2), which concerns the hosting infrastructure, the systems and the services of the server. The Reseller is obliged to collect, filter and forward to the Company only requests related to the infrastructure, after its own initial assessment. Where 3rd level support (L3) is required, i.e. specialized technical intervention or the involvement of third-party suppliers/vendors (e.g. cPanel, LiteSpeed, CloudLinux, Imunify360), the Company may impose an additional charge on the Reseller for the time and resources to be allocated. Notification and confirmation of the relevant charge precede the provision of L3 support, unless it concerns urgent security work.

8.29.3 The Reseller bears sole and full responsibility for every act/omission of its end customers, their content, applications, DNS/email settings, and compliance with the law and the policies of the Company (e.g. anti-spam, sending limits, server resources). The Company is entitled, at its absolute discretion, to suspend/restrict any end customer account and/or the reseller account as a whole in the event of a breach, without notice and without any obligation to pay compensation.

8.29.4 The Reseller ensures the correct registration/renewal of the domain names of its end customers and the proper operation of the nameservers/DNS zones. In the event of expiry/failure of a domain or nameserver of the Reseller, the Company may make necessary routing changes or temporary interventions for the stability of the platform, without liability for any consequences. (See also § 8.28 in this regard).

8.29.5 All limits (e.g. space/traffic, inodes, CPU/RAM/IO, databases, mailboxes, sending limits) apply per account and per plan, as described on the product pages and/or in relevant announcements of the Company. Exceeding or circumventing the limits, using multiple accounts to avoid restrictions, as well as the practice of overselling (granting end customers more resources than those demonstrably allocated to the Reseller by the Company) are expressly prohibited. In every such case, the Company may, at its absolute discretion, apply measures (for example: throttling, quarantine, temporary or permanent suspension of services) without prior notice and without any liability for losses, delays or compensation.

8.29.6 The policies of §§ 8.12, 8.17–8.21 apply mandatorily to the end customers of the Reseller as well. The Reseller is responsible for enforcing lawful recipient lists, correct authentication (SPF/DKIM/DMARC) and sending restrictions. If an incident of spam, IP blacklisting, phishing, malicious software or any other form of abuse arises from an end customer, the Company notifies the Reseller, who is obliged to take measures within 24 hours of the notification. If the Reseller does not respond within the above deadline or the incident recurs, the Company may, at its absolute discretion, immediately suspend the relevant account and/or the entire reseller account, and impose reasonable remediation/incident handling charges, without any obligation to pay compensation.

8.29.7 The Reseller must keep its own backups of the accounts of its end customers outside the infrastructure. Any backup services offered by the Company are an additional facility/convenience and do not constitute a guarantee or obligation of retention/recovery. Restores/remediation work may be invoiced. (See also the general backup terms in this regard).

8.29.8 The Reseller takes care of the security of code, CMS, add-ons/themes, passwords and access policies (e.g. 2FA) for all accounts it manages. The Company may immediately deactivate vulnerable plugins/themes/versions or isolate accounts in quarantine where it deems this necessary for stability/security, without prior notice and without any obligation to pay compensation.

8.29.9 The Reseller is independently the Controller for the data of its end customers. The Company acts as Processor only for the hosting infrastructure. The Reseller ensures a lawful basis for processing, informs data subjects, takes care of third-party DNS/anti-spam settings (e.g. filters) and, where required, concludes any supplementary processing agreements with the Company and with third-party providers it chooses.

8.29.10 Invoicing/collection from end customers is the responsibility of the Reseller. Cancellations/chargebacks between the Reseller and its end customers do not bind the Company. In the event of an outstanding financial balance or a chargeback to the Company, the Company may immediately suspend every related service of the Reseller (and related sub-accounts), impose reconnection fees or terminate the contract, without further notice and without any obligation to pay compensation.

8.29.11 At its absolute discretion, the Company may impose preventive and/or corrective measures at account/plan/server level (for example: throttling, blocking of IPs/ports/protocols, black-holing, quarantine, deactivation of services, nameserver changes, temporary or permanent suspension). The measures may be applied without notice, particularly in cases of risk to security/stability or breach of the law/terms, and do not establish any obligation to pay compensation.

8.29.12 Upon expiry/termination of the Reseller account, the sub-accounts of end customers are suspended and/or deleted in accordance with the applicable lifecycles (§ 8.24). The Company may, at its absolute discretion, offer selected end customers the possibility of continuing services directly with the Company under new terms. Any acceptance/refusal does not give rise to any liability towards the Reseller.

8.29.13 In the event of a conflict between the general terms and the specific features/limits stated on the Reseller plan page, the specific features prevail. The Company may modify technical parameters/limits for reasons of security/stability/infrastructure upgrade, effective from publication and/or notification in the Control Panel, without liability for compensation.

8.29.14 Access details and communication with end customers. The Company has a commercial relationship exclusively with the Reseller and not with its end customers. For every request, content issue, rights, credentials, account information or other claims raised by an end customer, the Company refers exclusively to the Reseller.

The Reseller bears full and sole responsibility towards its end customers for the provision of information, service, support, the accuracy and lawfulness of the content, as well as for every right or obligation arising from that relationship. The Company assumes no liability whatsoever, direct or indirect, towards the end customers of the Reseller, nor is it considered a contracting party to their relationship.

8.30 Support levels (L1/L2/L3)

The Company provides customers of hosting services with 1st level (L1) and 2nd level (L2) technical support, depending on the type and features of each plan.

a) 1st level support (L1). Includes basic guidance, routine requests, usage questions, changes to settings through the available management tools and initial diagnosis of problems.

b) 2nd level support (L2). Includes technical investigation and interventions concerning the hosting infrastructure, the server environment and the services of the Company. L2 requests are examined exclusively after an initial assessment/filtering by the Company, based on the information provided by the Customer.

c) 3rd level support (L3). Includes specialized technical interventions, analysis or correction of code, as well as requests that require the involvement of third-party suppliers or vendors (for example: cPanel, LiteSpeed, CloudLinux, Imunify360). L3 support is not provided as part of the standard hosting services and may be offered only under a special agreement and for an additional charge.

d) Managed services. For Managed plans (Managed WordPress, Managed WooCommerce, Managed VPS, Managed Dedicated), the Company provides L1 and L2 support within the scope of the agreed features. L3 support for these services is provided only under a special agreement and for an additional charge.

9. Support

9.1 Scope of support - what is/is not covered

Support includes providing assistance to customers in resolving problems related exclusively to the services provided by the Company. It does not include the free provision of know-how for building or maintaining websites, programming or using computer software.

9.2 Support procedure & channels (tickets/email/telephone)

a) Before contacting the Company, the Customer is asked to consult the support resources provided, such as the Knowledge Base and frequently asked questions at help.konet.gr and in the Client Area, and the articles on the Company's Blog at blog.konet.gr.

b) If the issue cannot be resolved through the above resources, the Customer must inform the Company by submitting a ticket through the Client Area. If submitting a ticket through the Client Area is not possible for technical reasons, only then may the Customer also use the other approved communication channels with the Company, which, in order of priority, are the support email address support (at) konet (dot) gr and the contact telephone number 2310 501 800.

c) After submitting the ticket through the Client Area, the Customer receives a unique reference number certifying receipt of the ticket by the support system of the Company.

The Customer must:

• Provide its full name and a detailed description of the problem.
• State the relevant domain, folders, email accounts or other information required for investigating the issue.
• Clearly describe the steps that lead to the problem and quote any error messages.
• Provide passwords, where necessary, for access to services that are experiencing problems.
• Not send multiple tickets on the same matter or make repeated calls, as this may slow down the processing of its ticket.
• State the actual priority status of its ticket.

The Customer must cooperate fully with the support staff, carefully following the instructions provided.

9.3 Limits for third-party applications & indicative exclusions

The support of the Company covers exclusively matters concerning the functionality of the infrastructure, equipment and software that the Company itself installs. These include matters of network, servers and management software provided through the Client Area.

The Company is not obliged to provide support for third-party applications installed by the Customer, such as WordPress, Joomla or other CMS, unless the problem is directly related to the services of the Company. Likewise, the Company is not obliged to provide support for setting up the Customer's email addresses in email clients on its local systems. By way of example, the Company is not liable for:

• Errors arising from outdated or compromised applications.
• Incompatibilities due to software upgrades on its servers.
• Problems caused by mishandling or neglect by the Customer.

If the Customer wishes to receive support for problems that do not fall within the responsibilities of the Company, this may be provided at the discretion of the Company, where time is available, and for a fee in accordance with its price list. The Company does not guarantee the resolution of such issues.

9.4 Support hours

The Company provides support within the following hours:

a) Routine support matters (non-critical):
Monday to Friday: 09:00–18:00
Saturday: 10:00–15:00
Sunday and holidays of the Orthodox Church: closed.
From Holy Thursday through Easter Sunday: closed.

b) Critical or urgent matters (critical issues):
For issues concerning exclusively the functionality of the infrastructure, equipment and software installed by the Company (for example: server outage, network interruption, malfunction of management software provided through the Client Area), support is provided in writing (via email or ticket) seven (7) days a week, three hundred sixty-five (365) days a year, from 07:00 to 00:00.

The Company reserves the right to modify the above hours at its absolute discretion, informing customers accordingly through the Client Area and/or by an announcement on its website.

10. Payments, Invoicing & Financial Terms

10.1 Currency, Price Display & VAT

a) All charges, payments and refunds are made exclusively in euros (EUR).

b) The prices displayed on the website do not include VAT. VAT is calculated in the shopping cart, based on the Customer's details and the applicable tax legislation.

c) When creating an account, the Customer must declare its Tax ID (VAT No.) and, where required, provide a valid VIES number for cross-border transactions.

d) Each account may receive only one type of billing document (Receipt or Invoice). A change of the type of billing document is permitted only upon timely written notice to the accounting department through the Client Area.

e) In the event of a significant drop in the exchange rate of the euro against the dollar or another international currency, the Company reserves the right to adjust prices for future cycles.

f) Obvious typographical or accounting errors in prices do not bind the Company. In such cases, correction/re-invoicing is permitted.

10.2 Billing Statements (Pro Forma Invoices), Invoices & Issuance

a) Definition & nature. The "Billing Statement" (pro forma invoice) is issued for new orders and/or upcoming renewals. It is not a tax document and does not create an obligation of the Company to invoice.

b) Prepayment & activation. Activation/submission of requests (e.g. renewal) takes place only after the final collection of the amount of the Billing Statement. For bank deposits/wire transfers, matching takes place after the funds are credited and the details are checked.

c) Issuance of the billing document. The Company issues an Invoice/Receipt after final collection and makes it available electronically (PDF) in the Client Area and/or at the billing email address. Failure to receive the email does not release the Customer from its obligations. Delivery is presumed once the document is made available in the Client Area.

d) Accuracy of details. The tax details for invoicing are provided exclusively by the Customer, who is responsible for their accuracy. After issuance, changes are made only as permitted by law (e.g. issuance of a credit note where permitted).

e) Validity & adjustments. Billing Statements may have a validity period. After expiry, or in the event of changes in third-party costs, a new Statement is issued with updated prices. Late payment does not secure the original price.

f) Archiving. The Company archives Billing Statements and billing documents electronically as required by law. The Customer must keep copies for its own use/compliance.

10.3 Payment Methods & Third-Party Charges

a) Accepted methods. Payments are accepted via Stripe (including subscription charges), Alpha Bank (one-time card payments), PayPal (including subscriptions, where offered), bank deposit/wire transfer and IRIS. Availability may vary by service/country/transaction risk assessment.

b) Cards (Alpha Bank). Card payments are carried out in the secure environment of the provider. Activation of the service requires final approval/clearance by the payment provider.

c) Stripe / PayPal (subscriptions). By activating a subscription charge, the Customer consents to recurring charges based on the selected cycle. Card details are not stored by the Company. They are kept by the payment provider.

d) Bank deposit/IRIS. A payment is matched only after it is credited to the Company's account. The Customer must state the Billing Statement number in the payment reference. IRIS confirmation is manual and may take up to 1 business day.

e) Security checks. The Company may request verification of identity/payment method and may temporarily suspend activation for higher-risk transactions. Failure to provide the requested documents within a reasonable time may lead to the cancellation of the order.

10.4 Prepayment, Service Activation & Automatic Renewals (Auto-Renew/Subscriptions)

a) Activation. Services that support auto-renew or subscriptions are activated only with the express consent of the Customer during the order or later through the Client Area.

b) Deactivation. The Customer may at any time deactivate auto-renew or cancel the subscription before the next scheduled billing through the Client Area. Failure to deactivate before the next billing results in the normal charge for the next cycle.

c) Notifications. The Company may send advance notices of upcoming charges or expiries. The sending/receipt of notifications is not guaranteed and does not release the Customer from the obligation to manage its settings in good time.

d) Plan changes. Changes of cycle or plan on an active subscription apply from the next cycle, unless otherwise specified during the change process.

e) Payment data. Card/account details are not stored by the Company. They are kept by the respective payment provider under its own security regime.

10.5 Billing Cycles, Renewal & Grace Periods

a) Billing cycles. Services are offered in monthly, quarterly, semi-annual, annual or other available billing cycles, as shown during the order. Each order is prepaid on the same day it is submitted.

b) Start & expiry. The cycle starts on the activation date and expires on the corresponding date of the next cycle. The expiry date is the payment deadline for the next period.

c) Grace period for infrastructure services. For hosting, email, VPS and Dedicated services, a grace period of fourteen (14) calendar days after expiry applies, exclusively for payment. The service may be technically restricted during the grace period.

d) Exceptions. The provisions of this section do not concern domain names or other services governed by the regulations of third-party bodies with different deadlines.

e) Prices & validity of statements. If third-party costs change or the validity of a statement expires, a new statement with updated prices may be required.

10.6 Payment Delays, Suspensions & Reconnections

a) Start of delay. A claim is considered overdue if it has not been paid by the expiry date stated on the corresponding statement or in the service account.

b) Suspension of services. Upon expiry of the applicable grace period, the Company may partially or fully suspend the service and/or restrict access solely for the purpose of payment or downloading copies, where technically feasible.

c) Termination & data deletion. If the debt remains unpaid after suspension, the service may be terminated and the data permanently deleted in the course of the normal operation of the systems, without further notice.

d) Reconnection. The service is restored only after full payment of the amounts owed and payment of any reconnection or recovery work fees. Data recovery is not guaranteed. Where technically possible, it may be invoiced separately.

e) Notifications. The Company may send reminders of debts or suspensions. Their delivery is not guaranteed and the responsibility for monitoring deadlines lies with the Customer.

f) Partial payments & order of allocation. Partial payments do not cure the default. The Company may allocate amounts as a priority to older debts or fees before reconnection.

g) Payment reversals. A reversal/dispute of a payment is treated as an unpaid debt and may result in the immediate suspension of the related services until final resolution.

10.7 Refunds & Credits

a) Statutory right of withdrawal. The right of withdrawal within fourteen (14) calendar days applies exclusively to customers who are consumers, i.e. natural persons acting outside the scope of their professional, commercial or business activity. This right does not apply to legal entities or to natural persons who obtain the services for professional/business purposes.

b) Exceptions. Withdrawal is not permitted for:
– domain names, after the request has been forwarded to the Registry,
– SSL certificates,
– services fully performed with the consent of the Customer,
– services with immediate commencement (e.g. VPS/Dedicated).

c) Refund method. Refunds are made to the same payment method, unless a credit is agreed. Credit balances cannot be redeemed for cash.

d) Non-refundable fees. Third-party fees (e.g. registries, licenses, banks) and activation fees are not refunded.

10.8 Payment Reversals/Disputes (Chargebacks/Claims) & Anti-Fraud Checks

a) Notification. In the event of a reversal/dispute of a payment (chargeback), the Customer must inform the Company immediately and cooperate to resolve it.

b) Suspension of services. During a chargeback, the Company may suspend the related services until the matter is settled.

c) Costs & charges. If the chargeback is rejected and found to be unfounded, the Customer is liable for any bank/provider fees and for any damage suffered by the Company.

d) Cancellation of services. Repeated chargebacks or misuse of the procedure may lead to the permanent termination of the cooperation.

10.9 Billing Corrections & Invoice Discrepancies

a) Invoicing errors. In the event of obvious or material errors (e.g. typographical errors, incorrect tax calculation), the Company is entitled to issue a corrective billing document (credit/debit note) in accordance with the law.

b) Obligation to cooperate. The Customer is obliged to provide corrected tax details and to cooperate for the correct reissue.

c) Limits. A correction does not entail any obligation to pay compensation beyond the corrected amount.

10.10 Adjustments of Prices, Taxes & Third-Party Fees

a) Right of adjustment. The Company reserves the right to change the prices of its services at any time, due to changes in third-party costs (e.g. registries, software providers, transaction costs) and/or due to internal pricing policy.

b) Effective date. New prices apply to future cycles or new orders. They are not applied retroactively to periods already paid.

c) Notification. The Customer is informed of the changes a reasonable time before the next renewal through the Client Area or by email, where feasible.

d) Special cases. For services that depend on third parties, any increases/decreases are applied automatically upon renewal, in accordance with the applicable regulations.

10.11 Discontinuation of Service by the Customer (Cancellations)

a) Method of submission. Cancellation is made exclusively via a ticket from the Client Area, clearly stating the service. The Company may request identity verification.

b) Timing.
– At the end of the cycle: the service remains active until expiry, without a refund for the unused period.
– Immediately: the Customer may request immediate cessation, without a pro rata refund.

c) Data & backups. After cancellation, the data may be permanently deleted in the course of normal operation. Taking backups before cancellation is the sole responsibility of the Customer.

d) Consequences. Any outstanding debts are paid before final termination. Cancellation does not affect the validity of registered domains or other services governed by third-party regulations.

10.12 Third-Party Fees & Commissions, Withholdings, Exchange Rates, Set-Off & Collection

a) Net payments. Payments must be remitted to the Company net, without withholdings or third-party charges (banks, payment providers, wire transfers).

b) Tax withholdings. If the Customer is obliged to withhold tax, it must pay an additional amount (gross-up) so that the Company receives the agreed net amount.

c) Exchange rates. All transactions are made in EUR. Payments in another currency are subject to exchange rates/charges borne solely by the Customer.

d) Reprocessing costs. Costs of tracing deposits without a correct payment reference, recalls of wire transfers or reissuing billing documents due to errors of the Customer are borne solely by the Customer.

e) Set-off. The Company may set off credit balances against overdue debts. The Customer is not entitled to set-off without written consent or a final court judgment.

f) Assignment of collection. The Company may assign collection to third parties (collection agencies/legal advisors). The related collection costs are borne by the defaulting Customer, in accordance with the law.

11. Amendment of the Terms of Service, Conditions and Rules

The Company reserves the right to change the terms and conditions governing its website at any time. We therefore ask the users of our website and our customers to visit it frequently to stay informed of any changes. We also reserve every right to change the content and presentation of our pages whenever we deem it appropriate or necessary. If we decide to change the Terms of Service, Conditions and Rules, we will publish these changes on this page and will update the amendment date of the Terms of Service, Conditions and Rules below.

The Terms of Service, Conditions and Rules were last updated on 21/02/2026.

You can view the previous terms of service here for a limited period of time.