HOSTING & INFRASTRUCTURE POLICY #

Effective Date: 01 February 2026

Applicable To: All clients, partners, licensees, and white-label operators under the Xdemór Infrastructure

1. Legal Status and Application #

This Hosting & Infrastructure Policy (“Policy”) governs hosting, infrastructure, managed hosting, assisted hosting, technical infrastructure, service environments, server-related configuration, access layers, support layers, and related services provided by The Xdemór Group Limited (“Xdemór”) in connection with its Services.

This Policy applies to services provided directly by Xdemór or through its affiliated, operational, functional, or service brands, including Fludnox, Xdorable, Services Support, Backline Support, Geometry Plane, and any other Xdemór-operated or Xdemór-controlled service environment.

This Policy applies to all clients, partners, licensees, resellers, white-label operators, and authorised users of Xdemór infrastructure unless expressly agreed otherwise in a written Individual Agreement.

1.1 Managed Service Role #

Xdemór provides hosting and infrastructure services as a managed service provider and contractual service interface toward the Client.

The Services may be delivered using a combination of Xdemór-controlled systems, third-party hosting providers, cloud infrastructure, data centres, DNS providers, CDN providers, email providers, security providers, software vendors, licensed platforms, automation tools, and other infrastructure components.

Unless expressly agreed otherwise in writing, the Client contracts with Xdemór for the managed service layer, service configuration, access, support, and operational delivery — not for ownership, direct control, or direct contractual access to the underlying third-party infrastructure.

1.2 Upstream Provider Dependency #

The Client acknowledges that the Services may depend on upstream providers, third-party platforms, software vendors, infrastructure networks, server environments, data centre providers, registrars, DNS providers, email providers, CDN providers, security providers, and other external systems.

Such upstream providers may impose their own terms, acceptable use rules, technical limits, export controls, suspension rights, maintenance windows, data handling requirements, fair use limits, security controls, and service restrictions.

Xdemór cannot override any mandatory rule, restriction, suspension, enforcement action, technical limitation, outage, pricing change, service discontinuation, or policy change imposed by an upstream provider, platform, registrar, registry, authority, or applicable law.

1.3 Internal Implementation #

The underlying infrastructure providers, server locations, hosting environments, platforms, software, panels, dashboards, networks, routing arrangements, security layers, backup systems, automation tools, and operational methods used to deliver the Services are internal implementation details of Xdemór’s managed service layer.

They do not form part of the Client’s contractual deliverable unless expressly included in an Individual Agreement, Order Form, Proposal, Statement of Work, or written service confirmation.

Xdemór may modify, replace, reconfigure, migrate, upgrade, downgrade, suspend, or discontinue any internal implementation detail where necessary for operational, security, compliance, risk-control, supplier, performance, cost, or service-management reasons, subject to the Terms of Service and this Policy.

1.4 Incorporation into Terms #

This Policy is incorporated by reference into the Xdemór Terms of Service pursuant to Clause 8.10 (Policy Incorporation and Amendment).

The Services are governed by the Terms of Service, this Policy, any applicable service-specific policies, any applicable Individual Agreement, and any mandatory third-party or upstream provider rules relevant to the service being supplied.

1.5 Order of Precedence #

In the event of conflict, the following order of precedence applies, to the extent legally permitted:

(a) mandatory applicable law, court orders, regulator requirements, law enforcement obligations, and binding legal process;

(b) mandatory upstream provider, platform, registrar, registry, data centre, hosting, DNS, CDN, email, security, software, or infrastructure rules that directly affect the relevant Service;

(d) signed Individual Agreement, Proposal, Order Form, Statement of Work, or Annex, but only where it does not conflict with mandatory law or mandatory third-party rules;

(e) Xdemór Terms of Service;

(f) this Hosting & Infrastructure Policy;

(g) service-specific or product-specific policies;

(h) operational notices, support instructions, service documentation, or technical guidance issued by Xdemór.

1.6 No Direct Third-Party Rights #

Nothing in this Policy creates a direct contractual relationship between the Client and any upstream provider used by Xdemór unless the Client separately contracts with that provider.

Nothing in this Policy grants the Client any right to access, control, audit, demand disclosure of, or directly enforce rights against Xdemór’s upstream providers, supplier accounts, server accounts, platform accounts, infrastructure contracts, configuration systems, internal dashboards, or implementation arrangements.

1.7 Relationship with Domain Services #

Domain name registration, registrant status, registrar control, domain transfer, WHOIS data, domain expiry, and registry enforcement are governed by the Domain Names Policy and applicable registrar, registry, ICANN, ccTLD, and legal rules.

Where hosting or infrastructure services depend on domain configuration, DNS, SSL, email routing, or registrar settings, those components may also be affected by the Domain Names Policy and applicable third-party rules.

2. Nature of the Hosting Infrastructure Services #

2.1 Managed Hosting Infrastructure Layer #

Xdemór provides hosting and infrastructure services as a managed hosting infrastructure layer and hosting solutions provider.

The purpose of the Services is to enable, support, configure, maintain, and manage hosted environments for websites, applications, portals, dashboards, landing pages, microsites, email-related configuration, technical integrations, and related digital service delivery.

The Services may include technical assembly, provider selection, configuration, deployment, monitoring, support coordination, performance management, security controls, infrastructure routing, operational troubleshooting, and ongoing service administration, depending on the applicable service plan or written agreement.

2.2 Service Output, Not Infrastructure Ownership #

The Client receives access to and use of the service output, hosted environment, functionality, or managed configuration made available by Xdemór.

Unless expressly agreed otherwise in writing, the Client does not receive ownership, assignment, transfer, tenancy, leasehold, administrative control, root access, supplier account access, source control, infrastructure ownership, server ownership, software ownership, or direct contractual rights over any underlying infrastructure, systems, platforms, networks, panels, software, automation, supplier accounts, or third-party services used to deliver the Services.

Payments for hosting, infrastructure, setup, support, maintenance, configuration, migration, optimisation, or managed service delivery do not transfer ownership of the underlying infrastructure or implementation.

2.3 Managed Assembly and Operational Control #

The Client acknowledges that Xdemór’s value lies in the managed assembly, configuration, orchestration, support, and operational control of multiple technical components.

Such components may include, without limitation:

(a) hosting providers;

(b) cloud infrastructure providers;

(d) control panels;

(e) DNS providers;

(f) CDN providers;

(g) SSL/TLS certificate systems;

(h) email routing or mailbox providers;

(i) backup systems;

(j) monitoring tools;

(k) security tools;

(l) licensed software;

(m) automation systems;

(n) technical support workflows.

The selection, combination, replacement, configuration, and management of these components form part of Xdemór’s managed service layer and operational methodology.

2.4 Hosted Service Environment #

The Services are provided as hosted service environments, not as standalone infrastructure assets.

A hosted service environment may be shared, isolated, reseller-based, cloud-based, containerised, panel-based, white-label, dedicated, hybrid, or otherwise configured depending on the applicable service scope, technical requirements, commercial plan, provider availability, and operational judgement of Xdemór.

Unless expressly agreed in writing, the Client is not entitled to dictate or retain any specific server, provider, data centre, location, IP address, control panel, software stack, backup system, CDN, DNS provider, security provider, or infrastructure configuration.

2.5 Third-Party Infrastructure and Provider Dependency #

The Client acknowledges that hosting and infrastructure services may depend on third-party providers and upstream infrastructure.

Such providers may impose technical limits, fair use restrictions, maintenance windows, acceptable use rules, data location limitations, security controls, suspension rights, service changes, pricing changes, resource limits, export controls, provider migrations, platform restrictions, and enforcement actions.

Xdemór is responsible for managing the Services within the scope of the applicable service plan, but does not guarantee uninterrupted availability, provider continuity, identical infrastructure, permanent location, permanent IP address, unchanged supplier stack, or permanent technical configuration unless expressly agreed in writing.

2.6 No Entitlement to Internal Implementation #

The Client is not entitled to receive, copy, audit, export, replicate, reverse engineer, reconstruct, or demand disclosure of Xdemór’s internal implementation, including:

(a) infrastructure architecture;

(b) server configuration;

(d) control panel configuration;

(e) routing logic;

(f) security rules;

(g) caching strategy;

(h) CDN setup;

(i) backup logic;

(j) automation workflows;

(k) monitoring processes;

(l) diagnostic methodology;

(m) operational playbooks;

(n) performance optimisation methods;

(o) internal support processes.

The Client may receive reasonable access, reports, credentials, records, or technical information only to the extent required for the agreed service output, lawful use of the Services, or agreed migration/export obligations.

2.7 No Standalone Hosting Resale Unless Authorised #

The Services may be used by resellers, agencies, partners, or white-label operators only where such use is expressly permitted under the applicable agreement.

No Client may represent Xdemór’s infrastructure, hosting environments, provider relationships, configurations, systems, or managed service methodology as its own proprietary infrastructure unless expressly authorised in writing.

Where white-label or reseller use is permitted, the Client remains responsible for its own end clients, representations, pricing, support promises, legal notices, acceptable use compliance, and service expectations.

2.8 Scope Depends on the Applicable Service Plan #

The precise nature, level, limits, support scope, included features, backup arrangements, migration assistance, security controls, monitoring, response times, resource allocation, and service commitments depend on the applicable service plan, Individual Agreement, Proposal, Order Form, Statement of Work, Annex, or written service confirmation.

Any service, feature, support obligation, recovery obligation, performance commitment, migration commitment, security service, backup service, DDoS mitigation, uptime guarantee, or custom infrastructure requirement not expressly included is out of scope by default.

3. Scope of Services #

3.1 General Scope #

Hosting & Infrastructure Services may include, depending on the applicable service plan, Individual Agreement, Proposal, Order Form, Statement of Work, Annex, or written service confirmation:

(a) web hosting;

(b) application hosting;

(d) white-label hosting services under the Fludnox brand or other Xdemór service brands;

(e) server, hosting panel, or environment configuration;

(f) DNS-related technical configuration where connected to hosting delivery;

(g) SSL/TLS configuration or assistance;

(h) website, portal, dashboard, landing page, microsite, or e-commerce hosting support;

(i) content delivery, caching, routing, proxying, or offload services;

(j) email-related hosting configuration, including MX, SPF, DKIM, DMARC, mailbox, forwarding, or routing assistance where included;

(k) basic monitoring, security controls, performance checks, or optimisation measures where included;

(l) backup configuration, backup restoration assistance, or recovery support where included;

(m) migration assistance from or to another provider where included;

(n) access to hosting dashboards, control panels, client portals, technical interfaces, support channels, or reporting views made available by Xdemór.

The precise scope of the Services depends strictly on the applicable service plan and written commercial terms.

3.2 Express Inclusion Required #

A service, feature, support obligation, technical action, recovery obligation, monitoring duty, performance commitment, security commitment, migration task, backup task, emergency response, or infrastructure change is included only where expressly stated in the applicable service plan or written agreement.

Any service or functionality not expressly included is out of scope by default.

3.3 Services Not Included by Default #

Unless expressly agreed in writing, Hosting & Infrastructure Services do not include:

(a) dedicated server administration;

(b) root access, SSH access, database administration, or privileged system access;

(d) DDoS mitigation or guaranteed protection against denial-of-service attacks;

(e) malware removal, forensic investigation, blacklist removal, spam cleanup, or reputation repair;

(f) guaranteed email deliverability, inbox placement, sender reputation, or spam-filter avoidance;

(g) custom backup architecture, guaranteed backup completeness, guaranteed backup frequency, or guaranteed disaster recovery;

(h) emergency recovery outside the agreed support scope;

(i) full website rebuild, redesign, development, debugging, plugin repair, theme repair, or code-level development;

(j) third-party software licensing, plugin licensing, theme licensing, API licensing, or renewal of external software unless expressly included;

(k) SEO performance, search ranking protection, traffic preservation, analytics continuity, or advertising platform continuity;

(l) legal, compliance, data protection, PCI, medical, financial, or regulated-industry compliance configuration unless expressly agreed;

(m) load testing, penetration testing, vulnerability scanning, security audits, or compliance audits;

(n) data archiving, file storage, media storage, video encoding, transcoding, crawling, scraping, batch processing, or backup storage use;

(o) guaranteed migration of emails, DNS records, domains, databases, historical logs, analytics data, or third-party platform data;

(p) support for custom scripts, unsupported software, abandoned plugins, insecure code, nulled software, pirated software, or unlicensed components.

3.4 Hosting Use Purpose #

Unless expressly agreed otherwise in writing, hosting environments are intended for ordinary website, application, portal, landing page, dashboard, e-commerce, and related business hosting purposes.

The Services must not be used as general-purpose computing, file storage, backup storage, archive storage, video processing, bulk email sending, scraping, crawling, proxying, tunnelling, cryptocurrency mining, high-volume automation, bot operation, or any other non-standard infrastructure workload.

Xdemór may suspend, restrict, throttle, migrate, require optimisation, require upgrade, or terminate any hosting environment that exceeds the intended use of the applicable service plan or creates risk to infrastructure stability, security, provider compliance, IP reputation, or other clients.

3.5 Managed and Assisted Services #

Where a service is described as “managed”, “assisted”, “supported”, “configured”, “maintained”, or similar, this means that Xdemór provides operational support within the agreed service scope.

It does not mean that Xdemór assumes unlimited responsibility for:

(a) the Client’s website code;

(b) the Client’s content;

(d) user errors;

(e) unauthorised changes;

(f) weak passwords or compromised credentials;

(g) outdated software;

(h) third-party platform changes;

(i) registrar, DNS, email, CDN, certificate authority, advertising platform, analytics platform, or payment provider actions;

(j) business losses arising from downtime, configuration changes, migration, suspension, security events, or provider action.

3.6 Migration Assistance #

Where migration assistance is included, it is provided on a reasonable-efforts basis unless expressly agreed otherwise in writing.

Xdemór may assist with moving website files, databases, hosting configuration, DNS records, email configuration, or other technical components where technically possible and within scope.

Migration assistance does not guarantee:

(a) zero downtime;

(b) full data integrity;

(d) identical configuration;

(e) successful email migration;

(f) successful DNS migration;

(g) successful domain transfer;

(h) successful third-party integration;

(i) compatibility of legacy software, plugins, themes, scripts, or databases;

(j) preservation of SEO rankings, analytics continuity, advertising tracking, email deliverability, or historical logs.

The Client remains responsible for reviewing and confirming that migrated services operate correctly after migration.

3.7 Backup and Recovery Scope #

Backup, recovery, and restoration services are included only where expressly stated in the applicable service plan or written agreement.

Where backups are provided, they are provided as a risk-reduction measure and not as a guarantee of complete, current, restorable, or uninterrupted data availability.

Xdemór may exclude temporary files, cache files, logs, generated files, large media files, third-party backups, system backups, duplicate archives, or files considered non-essential to ordinary service operation.

The Client remains responsible for maintaining its own independent backups of websites, files, databases, emails, media, business records, and critical data unless a specific managed backup service has been agreed in writing.

3.8 Security and Performance Scope #

Where security controls or performance optimisation are included, they are limited to reasonable operational measures within the agreed service scope.

Xdemór does not guarantee that any hosting environment, website, application, email system, DNS setup, SSL configuration, CDN setup, or security layer will be immune from hacking, malware, spam, phishing, DDoS attacks, credential compromise, software vulnerabilities, plugin conflicts, data loss, downtime, performance degradation, blacklist events, or third-party enforcement.

Performance optimisation does not guarantee specific loading speeds, Core Web Vitals scores, SEO rankings, conversion rates, advertising results, uptime, or business outcomes unless expressly agreed in writing.

3.9 Access to Dashboards, Panels, and Interfaces #

Xdemór may provide access to dashboards, control panels, client portals, hosting panels, reporting interfaces, or technical views at its discretion and according to the applicable service plan.

Such access is a service interface only and does not grant ownership, administrative control, root access, supplier account access, infrastructure control, database control, internal system access, or entitlement to the underlying platform.

Xdemór may modify, restrict, replace, suspend, or remove access to any dashboard, panel, portal, or interface for security, operational, billing, compliance, abuse-prevention, supplier, or risk-control reasons.

3.10 Scope Changes and Additional Work #

Any work outside the agreed service scope may be refused, deferred, quoted separately, or treated as additional billable work.

Additional work may include, without limitation:

(a) emergency recovery;

(b) malware cleanup;

(d) DNS repair;

(e) email repair;

(f) plugin or theme repair;

(g) website debugging;

(h) performance optimisation;

(i) restore attempts;

(j) third-party support coordination;

(k) configuration reconstruction;

(l) client-caused issue remediation;

(m) recovery after unauthorised changes;

(n) audit, investigation, or technical diagnosis outside the agreed plan.

Xdemór may require upfront payment, deposit, revised pricing, or a new written scope before commencing any additional work.

4. Infrastructure, Software, and Implementation #

4.1 Delivery Through Combined Infrastructure #

The Services are delivered through a managed combination of infrastructure, software, platforms, configurations, provider relationships, and operational processes selected, configured, and managed by Xdemór.

This may include, without limitation:

(a) third-party hosting providers;

(b) cloud infrastructure providers;

(d) server operating systems;

(e) hosting control panels;

(f) DNS providers;

(g) CDN providers;

(h) SSL/TLS certificate systems;

(i) email providers or email routing systems;

(j) backup systems;

(k) monitoring tools;

(l) security tools;

(m) licensed software;

(n) automation tools;

(o) Xdemór-defined configurations, standards, operational methods, and service processes.

4.2 Internal Implementation Details #

Underlying infrastructure providers, platforms, data centres, networks, software vendors, control panels, routing arrangements, backup systems, security tools, automation tools, and service processes constitute internal implementation details of Xdemór’s managed service layer.

They do not form part of the contractual deliverable unless expressly identified in an Individual Agreement, Proposal, Order Form, Statement of Work, Annex, or written service confirmation.

The Client contracts for the managed service output, not for any specific supplier, software stack, server location, IP address, panel, account, licence, route, configuration, or internal delivery method.

4.3 Right to Modify or Replace Implementation #

Xdemór may modify, upgrade, downgrade, migrate, replace, reconfigure, suspend, or discontinue any internal implementation detail where Xdemór reasonably considers this necessary or appropriate for:

(a) operational efficiency;

(b) service stability;

(d) compliance;

(e) supplier changes;

(f) infrastructure availability;

(g) cost control;

(h) performance management;

(i) abuse prevention;

(j) risk control;

(k) technical compatibility;

(l) provider discontinuation;

(m) supportability;

(n) platform maintenance;

(o) service improvement.

Such changes may include moving services between providers, environments, servers, IP addresses, regions, data centres, panels, software versions, backup systems, CDN providers, DNS providers, email providers, security systems, or other technical components.

4.4 No Entitlement to Specific Provider or Stack #

Unless expressly agreed in writing, the Client is not entitled to require, retain, reject, audit, or control any specific:

(a) upstream provider;

(b) server;

(d) data centre;

(e) geographic location;

(f) control panel;

(g) operating system;

(h) software version;

(i) database version;

(j) DNS provider;

(k) CDN provider;

(l) backup provider;

(m) email provider;

(n) security provider;

(o) monitoring tool;

(p) automation system;

(q) technical architecture.

Xdemór may use its operational judgement to determine the appropriate infrastructure stack for the relevant service.

4.5 Provider, Location, and Environment Changes #

The Client acknowledges that upstream providers, server environments, data centre locations, IP addresses, software stacks, and hosting platforms may change over time.

Where commercially reasonable, Xdemór will aim to maintain equivalent service output after such changes. However, Xdemór does not guarantee that the technical environment, performance characteristics, IP address, location, latency, panel behaviour, software compatibility, routing, or provider features will remain identical.

Any requirement for a fixed provider, fixed country, fixed server, fixed IP address, fixed stack, fixed software version, fixed storage location, or dedicated environment must be expressly agreed in writing.

4.6 Software and Licensing #

The Services may rely on licensed software, open-source software, commercial software, third-party plugins, control panels, APIs, integrations, operating systems, server tools, and other software components.

Unless expressly agreed in writing:

(a) Xdemór does not transfer any software licence to the Client;

(b) Xdemór does not grant the Client ownership of any software, platform, panel, tool, or integration used to deliver the Services;

(c) the Client is responsible for any third-party software, plugin, theme, API, licence, subscription, renewal, or account that belongs to, is supplied by, or is required for the Client’s own website, application, content, or business process;

(d) Xdemór may refuse to install, maintain, support, or continue using unsupported, insecure, abandoned, pirated, nulled, unlicensed, incompatible, or non-compliant software.

4.7 Third-Party Terms and Restrictions #

The Client acknowledges that upstream providers and software vendors may impose their own terms, acceptable use policies, licence restrictions, export controls, fair use limits, security requirements, data location conditions, suspension rights, maintenance windows, pricing changes, and service restrictions.

The Client must not use the Services in a way that causes Xdemór to breach, or creates risk of breach of, any upstream provider or software vendor terms.

Where an upstream provider, software vendor, authority, or platform requires a change, restriction, suspension, migration, removal, or discontinuation, Xdemór may take the necessary action without liability to the Client.

4.8 Client-Installed or Client-Requested Components #

Where the Client installs, requests, supplies, approves, or requires any software, script, plugin, theme, integration, API, database, automation, codebase, tracking tool, or third-party component, the Client remains responsible for:

(a) licence compliance;

(b) security;

(d) updates;

(e) renewals;

(f) vendor support;

(g) lawful use;

(h) data protection implications;

(i) performance impact;

(j) conflicts with the hosting environment;

(k) damage, downtime, data loss, or security issues caused by that component.

Xdemór may disable, remove, isolate, or refuse support for any Client-installed or Client-requested component that creates security, stability, legal, licensing, performance, abuse, compatibility, or provider compliance risk.

4.9 No Disclosure of Internal Implementation #

The Client is not entitled to receive or access:

(a) supplier account details;

(b) server root access;

(d) infrastructure diagrams;

(e) automation workflows;

(f) deployment logic;

(g) security rules;

(h) monitoring configurations;

(i) backup architecture;

(j) provider contracts;

(k) internal documentation;

(l) operational playbooks;

(m) commercial supplier terms;

(n) proprietary configuration standards.

Xdemór may provide limited technical information only where necessary for normal service use, support, lawful operation, or agreed migration/export obligations.

4.10 Implementation Changes Are Not Ownership Changes #

Any change, replacement, migration, upgrade, downgrade, or reconfiguration of the infrastructure, software, provider, panel, server, stack, or implementation method does not transfer ownership or control of any underlying system to the Client.

Such changes shall not be treated as a breach of contract, service downgrade, or material change where the managed service output remains substantially consistent with the applicable service scope or where the change is required for security, compliance, provider, maintenance, abuse-prevention, or risk-control reasons.

4.11 Technical Compatibility #

Xdemór does not guarantee that any Client website, application, plugin, theme, script, integration, database, workflow, or third-party service will remain compatible with all future infrastructure, provider, software, PHP, database, panel, security, CDN, email, or hosting environment changes.

Compatibility work, debugging, refactoring, upgrade work, plugin repair, theme repair, code changes, or third-party integration repair may be treated as additional billable work unless expressly included in the applicable service scope.

5.Intellectual Property, Client Data, and Infrastructure Rights #

5.1 Client Data and Client Content #

The Client retains all rights, title, and interest in its own data, website content, files, databases, media, business records, customer data, uploaded materials, and other content submitted to, hosted on, stored within, transmitted through, or processed by the Services (“Client Data”).

Nothing in this Policy transfers ownership of Client Data to Xdemór.

The Client grants Xdemór a limited, non-exclusive, worldwide licence to host, store, process, transmit, cache, reproduce, back up, restore, migrate, secure, scan, monitor, troubleshoot, display, and otherwise technically handle Client Data solely to the extent necessary to provide, maintain, secure, support, improve, migrate, suspend, terminate, or comply with legal obligations relating to the Services.

The Client is responsible for ensuring that it has all necessary rights, permissions, licences, consents, and legal bases to upload, store, publish, process, transmit, or otherwise use Client Data through the Services.

5.2 Hosted Copies, Logs, Backups, and Operational Data #

Technical copies of Client Data may be created as part of ordinary hosting, caching, backup, security, monitoring, migration, troubleshooting, logging, or disaster-recovery processes.

Such technical copies do not transfer ownership of Client Data to Xdemór.

Xdemór may generate, retain, analyse, and use technical logs, system records, performance data, resource usage data, security events, access logs, error logs, diagnostic information, infrastructure metrics, service metadata, and operational records for the purposes of service delivery, billing, security, compliance, abuse prevention, troubleshooting, performance management, infrastructure planning, and risk control.

Where such data contains personal data, it shall be handled in accordance with the applicable Privacy Policy, Data Processing Agreement, and data protection law.

5.3 Xdemór Infrastructure and Service Rights #

Except for Client Data, no ownership, title, licence, assignment, transfer, or proprietary right in the Services is granted to the Client unless expressly agreed in writing.

Xdemór retains all rights, title, and interest in and to the Services and the managed service layer, including without limitation:

(a) hosting environments;

(b) infrastructure architecture;

(d) DNS, CDN, routing, caching, and proxy configurations;

(e) SSL/TLS configuration methods;

(f) email routing and deliverability configuration methods;

(g) security rules, firewall logic, monitoring logic, and abuse-prevention systems;

(h) backup architecture and restoration workflows;

(i) automation workflows;

(j) dashboards, panels, portals, reporting views, and service interfaces;

(k) deployment standards;

(l) diagnostic methods;

(m) operational playbooks;

(n) support processes;

(o) service templates;

(p) configuration standards;

(q) supplier selection logic;

(r) implementation methodology;

(s) technical know-how, commercial know-how, and operational know-how.

5.4 Service Output Does Not Transfer Implementation #

The Client receives access to and use of the service output made available under the applicable service plan.

Access to a hosted website, application, portal, dashboard, control panel, mailbox, DNS setting, report, backup, migration file, support response, configuration, or technical environment does not transfer ownership of the underlying systems, configuration logic, infrastructure design, automation, service methodology, supplier setup, or operational process used to deliver it.

Payment for hosting, infrastructure, setup, support, maintenance, optimisation, migration, recovery, or managed services does not create any ownership, co-ownership, escrow right, source access right, supplier access right, audit right, replication right, or transfer right in Xdemór’s infrastructure or service methodology.

5.5 Third-Party Software and Licences #

The Services may rely on third-party software, open-source software, commercial software, plugins, themes, APIs, integrations, control panels, server tools, operating systems, security tools, backup tools, and other licensed components.

Unless expressly agreed in writing:

(a) Xdemór does not transfer any third-party software licence to the Client;

(b) Xdemór does not guarantee that any third-party software will remain available, supported, compatible, secure, or commercially unchanged;

(c) the Client remains responsible for any software, plugin, theme, API, integration, licence, subscription, account, renewal, or vendor relationship that belongs to or is required specifically for the Client’s own website, application, content, business process, or third-party service;

(d) Xdemór may refuse to install, support, renew, maintain, or continue using software that is unsupported, insecure, abandoned, incompatible, unlawful, pirated, nulled, unlicensed, or in breach of third-party terms.

5.6 Restrictions on Use of Xdemór Services #

The Client shall not, directly or indirectly:

(a) copy, modify, reproduce, reverse engineer, decompile, disassemble, derive, reconstruct, or create derivative works from the Services or any part of Xdemór’s managed service layer;

(b) attempt to obtain source code, internal logic, supplier account details, infrastructure design, automation scripts, security rules, monitoring configuration, deployment logic, or operational methodology;

(c) bypass, disable, interfere with, or circumvent usage limits, security controls, technical restrictions, access controls, billing controls, or provider limitations;

(d) resell, sublicense, white-label, rent, lease, share, assign, or make the Services available to third parties unless expressly authorised in writing;

(e) represent Xdemór’s infrastructure, service layer, configuration, dashboards, systems, processes, or methodology as the Client’s own proprietary infrastructure;

(f) use access to the Services, support communications, screenshots, configuration data, migration materials, diagnostics, or technical explanations to replicate, substitute, or bypass Xdemór’s managed infrastructure layer;

(g) remove, obscure, alter, or misrepresent any ownership, service, technical, legal, security, or provider notices connected with the Services.

5.7 Client-Created Materials and Separate Deliverables #

This Policy does not determine ownership of website designs, development deliverables, creative materials, written content, branding assets, code deliverables, marketing materials, or other separately commissioned works where those matters are governed by a Website & Web Development Policy, Individual Agreement, Proposal, Statement of Work, Annex, or separate IP assignment clause.

Where a separate written agreement expressly transfers ownership of a specific deliverable to the Client, that transfer applies only to the identified deliverable and does not transfer ownership of Xdemór’s hosting infrastructure, service layer, reusable components, templates, configurations, workflows, automation, dashboards, operational methods, supplier setup, or underlying implementation.

5.8 Feedback and Service Improvements #

If the Client provides suggestions, feedback, requests, comments, ideas, bug reports, improvement proposals, workflow recommendations, or operational observations relating to the Services, Xdemór may use them to improve, modify, develop, or commercialise its Services without restriction, obligation, attribution, compensation, or ownership transfer, unless expressly agreed otherwise in writing.

This does not grant Xdemór ownership of Client Data, confidential business content, or separately assigned Client materials.

5.9 Survival #

The provisions of this Section survive suspension, termination, expiry, migration, transfer, service discontinuation, Final Lock, and the end of any commercial relationship between the Client and Xdemór.

6. Anti-Circumvention and Misuse of Services Protection #

6.1 Anti-Circumvention #

The Client shall not, directly or indirectly, use access to the Services to circumvent, bypass, replicate, substitute, reconstruct, or materially reduce reliance on Xdemór’s managed hosting infrastructure layer in breach of the Terms of Service or this Policy.

Prohibited conduct includes, without limitation: #

(a) extracting, copying, reconstructing, reverse engineering, deriving, or reproducing Xdemór’s non-public infrastructure architecture, hosting configuration, routing logic, deployment standards, security rules, caching strategy, backup logic, automation workflows, monitoring setup, diagnostic methods, support processes, operational playbooks, or managed service methodology;

(b) using access credentials, dashboards, hosting panels, DNS records, server details, support communications, screenshots, audit findings, migration information, configuration data, or technical explanations obtained through Xdemór to recreate or imitate Xdemór’s managed service layer;

(c) using any migration, export, support, audit, recovery, backup, diagnostic, or handover request as a pretext to obtain proprietary configuration, internal implementation details, supplier account structure, automation logic, security methodology, or operational know-how;

(d) inducing, instructing, or assisting any third party, contractor, agency, developer, platform, provider, reseller, end client, or competitor to replicate, interfere with, bypass, substitute, or reconstruct Xdemór’s managed hosting environment or service delivery methods;

(e) attempting to reproduce the functional outcome of the Services through parallel, substitute, or derivative infrastructure using non-public information, configurations, access, processes, or operational knowledge obtained through the Services.

Nothing in this Section prevents the Client from independently procuring hosting, DNS, email, CDN, security, backup, development, or infrastructure services in the open market, provided such procurement does not rely on, derive from, replicate, misuse, or exploit Xdemór’s non-public configurations, operational framework, automation, supplier setup, or proprietary service methodology.

6.2 Misuse of Services #

The Client shall not use, permit, enable, or facilitate use of the Services for:

(a) illegal, fraudulent, deceptive, abusive, or misleading activity;

(b) malware, viruses, botnets, phishing, credential harvesting, spoofing, impersonation, or security attacks;

(c) spam, unsolicited bulk email, mail bombing, abusive forwarding, or practices that damage email deliverability, IP reputation, domain reputation, or provider standing;

(d) unauthorised access, hacking, password attacks, brute force activity, port scanning, vulnerability scanning, network probing, denial-of-service activity, packet flooding, or interference with systems or networks;

(e) open proxy services, traffic relaying, tunnelling, scraping, crawling, unauthorised automation, bot operations, cryptocurrency mining, file dumping, warez, piracy, or unlawful content distribution;

(f) excessive resource usage, abusive scripts, insecure code, unsupported scripts, abandoned plugins, nulled software, pirated software, unlicensed software, or any workload inconsistent with ordinary hosting use;

(g) storing, transmitting, publishing, or linking to content that infringes intellectual property rights, privacy rights, publicity rights, confidentiality obligations, or other third-party rights;

(h) activity that violates upstream provider terms, acceptable use policies, platform rules, registrar rules, registry rules, payment provider rules, email provider rules, CDN provider rules, security provider rules, or applicable law;

(i) any activity likely to cause suspension, blacklisting, provider enforcement, platform restriction, domain lock, IP reputation damage, security risk, legal claim, regulatory action, or harm to Xdemór, its providers, other clients, or service environments.

6.3 Unauthorised Access and Configuration Changes #

The Client shall not, without written authority: #

(a) access, attempt to access, modify, copy, export, disclose, or interfere with systems, accounts, dashboards, panels, APIs, credentials, databases, servers, DNS zones, backup systems, monitoring tools, security tools, or supplier accounts not expressly made available to the Client;

(b) alter hosting configurations, DNS records, email routing, SSL/TLS settings, CDN settings, cache rules, security settings, redirects, database settings, server settings, or application settings in a way that creates security, stability, deliverability, compliance, or operational risk;

(c) share credentials, access links, panel access, API keys, backup files, migration files, configuration data, or technical information with unauthorised third parties;

(d) bypass, disable, interfere with, or circumvent security controls, usage limits, access restrictions, billing controls, provider restrictions, or technical safeguards;

(e) attempt to obtain root access, supplier account access, server-level access, internal documentation, automation scripts, or infrastructure control unless expressly agreed in writing.

6.4 White-Label, Reseller, and End-Client Misuse #

Where the Client acts as a reseller, agency, white-label operator, intermediary, or service provider to its own clients or end users, the Client shall not:

(a) represent Xdemór’s infrastructure, systems, hosting environments, provider relationships, configurations, dashboards, support processes, or managed service methodology as its own proprietary infrastructure unless expressly authorised in writing;

(b) make service promises, uptime promises, backup promises, security promises, migration promises, ownership promises, or support promises to end clients that exceed the Client’s own rights under the Terms, this Policy, and the applicable service scope;

(c) conceal required information from end clients where such concealment creates legal, billing, ownership, data protection, operational, compliance, or support risk;

(d) allow end clients, contractors, developers, or third parties to misuse, overload, reverse engineer, interfere with, or attempt to replicate Xdemór-managed services.

The Client remains solely responsible for all claims, representations, omissions, disputes, complaints, losses, and liabilities arising from its relationship with end clients, sub-users, contractors, or third-party operators.

6.5 Protective and Enforcement Measures #

Any breach, suspected breach, or risk of breach of this Section may constitute a material breach of the Terms of Service and may result in one or more of the following measures:

(a) immediate suspension or restriction of Services;

(b) disabling or limiting hosting, dashboards, panels, DNS, email, CDN, SSL, backups, redirects, databases, integrations, support, or access credentials;

(c) isolation, throttling, migration, removal, quarantine, or deletion of abusive scripts, files, software, traffic, accounts, or configurations;

(d) refusal of migration, export, handover, recovery, restoration, or reinstatement assistance where legally and contractually permitted;

(e) requirement for upgrade, optimisation, remediation, identity verification, deposit, advance payment, revised pricing, or High-Risk classification;

(f) escalation, termination, or Final Lock under the Terms of Service;

(g) notification to upstream providers, hosting providers, DNS providers, email providers, CDN providers, security providers, payment providers, registrars, regulators, law enforcement, affected third parties, or other competent authorities where necessary.

Xdemór may take preventive or protective action where it reasonably considers that abuse, misuse, circumvention, fraud, unauthorised access, infrastructure risk, reputational harm, non-payment, provider enforcement risk, or legal/compliance risk has occurred or is likely to occur.

6.6 No Waiver of Third-Party Enforcement #

Nothing in this Section limits the independent right of any upstream provider, hosting provider, cloud provider, data centre, DNS provider, email provider, CDN provider, software vendor, registrar, registry operator, payment provider, regulator, court, law enforcement authority, or other competent authority to suspend, restrict, remove, lock, delete, disclose, reject, terminate, or otherwise enforce against any service, content, account, domain, traffic, or configuration.

Xdemór shall not be liable for any loss, interruption, suspension, deletion, restriction, failed recovery, failed migration, blacklist event, provider enforcement action, platform restriction, legal process, or loss of use arising from abuse, suspected abuse, misuse, third-party policy enforcement, legal process, or the Client’s conduct.

6.7 Survival #

The obligations in this Section survive suspension, termination, migration, expiry, service discontinuation, Final Lock, and the end of any commercial relationship between the Client and Xdemór.

7. Availability, Performance, and No SLA #

7.1 General Availability Position #

The Services are provided on an “as is” and “as available” basis.

Xdemór will use reasonable operational efforts to manage hosting and infrastructure services within the applicable service scope, but does not guarantee uninterrupted availability, error-free operation, continuous access, specific performance levels, specific response times, specific recovery times, or specific business outcomes unless expressly agreed in writing.

7.2 No SLA Unless Expressly Agreed #

No service level agreement, uptime guarantee, performance guarantee, response-time guarantee, recovery-time guarantee, support-time guarantee, service credit, compensation right, or financial remedy applies unless expressly stated in an Individual Agreement, Order Form, Proposal, SLA, Annex, or written service confirmation.

Any SLA, if agreed, applies only to the specific service, metric, period, exclusions, and remedy expressly stated in that document.

Marketing statements, support messages, service descriptions, dashboard indicators, status updates, or general references to reliability shall not constitute an SLA or performance guarantee.

7.3 Availability Depends on Multiple Factors #

Availability, performance, and continuity may depend on factors outside Xdemór’s direct control, including:

(a) upstream hosting providers;

(b) cloud infrastructure providers;

(d) DNS providers;

(e) CDN providers;

(f) email providers;

(g) SSL/TLS certificate authorities;

(h) registrars and registry operators;

(i) software vendors;

(j) control panel providers;

(k) payment providers;

(l) third-party APIs and integrations;

(m) Client websites, applications, plugins, themes, scripts, databases, or custom code;

(n) Client-side configuration, credentials, devices, networks, browsers, accounts, or user actions;

(o) internet routing, DNS propagation, blacklist events, security events, legal process, provider enforcement, or platform restrictions.

Xdemór is not liable for unavailability, degraded performance, failed delivery, delay, interruption, failed validation, failed email delivery, broken integration, or loss of functionality caused by such factors.

7.4 Maintenance, Updates, and Technical Changes #

Xdemór may perform planned, emergency, corrective, preventative, security, compliance, supplier-driven, or risk-control maintenance at any time.

Maintenance may include, without limitation:

(a) server updates;

(b) software updates;

(d) security patching;

(e) infrastructure migration;

(f) provider migration;

(g) DNS, CDN, routing, or cache changes;

(h) SSL/TLS updates;

(i) backup system changes;

(j) database maintenance;

(k) email system maintenance;

(l) security isolation or abuse containment;

(m) emergency remediation.

Where commercially reasonable, Xdemór may provide advance notice of planned maintenance through available communication channels or service status notices. However, advance notice may not be provided where maintenance is urgent, security-related, supplier-driven, compliance-driven, or necessary to protect infrastructure, data, providers, or other clients.

7.5 Upstream Provider and Platform Outages #

The Client acknowledges that upstream providers may experience outages, maintenance, network issues, hardware failures, software failures, data centre incidents, routing issues, provider migrations, service discontinuation, suspension, account restrictions, or other operational events.

Xdemór shall not be liable for outages, service degradation, downtime, data loss, failed backups, delayed recovery, IP changes, location changes, routing changes, or reduced functionality caused by upstream provider action, inaction, outage, maintenance, limitation, enforcement, or failure.

Where an upstream issue occurs, Xdemór’s responsibility is limited to reasonable coordination, escalation, mitigation, or workaround efforts within the applicable service scope.

7.6 Performance Is Not Guaranteed #

Xdemór does not guarantee any specific:

(a) loading speed;

(b) Core Web Vitals score;

(d) server response time;

(e) uptime percentage;

(f) bandwidth level;

(g) storage speed;

(h) database speed;

(i) email delivery speed;

(j) inbox placement;

(k) SEO ranking;

(l) advertising performance;

(m) conversion rate;

(n) analytics continuity;

(o) user experience metric;

(p) revenue result.

Performance may vary depending on traffic, website code, plugins, scripts, database condition, media size, caching, DNS, CDN, third-party scripts, theme quality, software updates, upstream provider behaviour, browser behaviour, user location, and Client-side changes.

7.7 Security and Risk-Control Actions #

Xdemór may suspend, restrict, throttle, isolate, disable, migrate, reconfigure, block, remove, or otherwise intervene in any service environment where Xdemór reasonably considers this necessary for:

(a) security protection;

(b) abuse prevention;

(d) spam prevention;

(e) phishing prevention;

(f) DDoS response;

(g) provider compliance;

(h) legal or regulatory compliance;

(i) protection of IP reputation, domain reputation, server reputation, or platform reputation;

(j) protection of other clients;

(k) infrastructure stability;

(l) prevention of data exposure, unauthorised access, or operational harm.

Such action shall not constitute breach, downtime, service failure, or SLA breach where taken in good faith for operational, security, compliance, or risk-control reasons.

7.8 Resource Limits and Fair Use #

Availability and performance are subject to service limits, plan restrictions, fair use rules, provider limits, storage limits, bandwidth limits, CPU limits, memory limits, inode limits, process limits, database limits, email limits, API limits, backup limits, and other technical restrictions.

Use described as “unlimited” by any provider, package, panel, or service description remains subject to fair use, technical feasibility, infrastructure stability, provider restrictions, and this Policy.

Xdemór may require optimisation, upgrade, migration, throttling, suspension, or termination where usage exceeds ordinary service expectations or creates risk to performance, security, provider compliance, or other clients.

7.9 Service Interruptions Caused by the Client #

Xdemór shall not be responsible for downtime, degraded performance, failed delivery, data loss, broken functionality, security compromise, failed email delivery, failed DNS resolution, SSL failure, failed backups, or loss of access caused by:

(a) Client-side changes;

(b) incorrect DNS changes;

(d) expired licences;

(e) unpaid invoices;

(f) weak passwords;

(g) compromised credentials;

(h) outdated software;

(i) unsupported plugins, themes, scripts, or integrations;

(j) third-party developer actions;

(k) unauthorised access sharing;

(l) excessive traffic;

(m) malware introduced through Client systems;

(n) Client failure to follow instructions;

(o) late response to support, verification, renewal, or security requests.

Recovery from Client-caused interruptions may be treated as additional billable work unless expressly included in the applicable service scope.

7.10 No Automatic Credits, Refunds, or Compensation #

Unless expressly agreed in writing, downtime, degraded performance, interruption, maintenance, suspension, provider outage, failed migration, failed backup, failed recovery, failed email delivery, DNS delay, SSL issue, or temporary service unavailability does not entitle the Client to any refund, credit, set-off, compensation, extension, or payment reduction.

Any service credit or financial remedy must be expressly agreed in a written SLA or Individual Agreement.

7.11 Status Notices and Incident Communication #

Xdemór may provide service notices, incident updates, maintenance notices, or status communications through email, support channels, status pages, dashboards, client portals, or other communication methods.

Such notices are provided for operational transparency and do not create any additional warranty, SLA, admission of liability, or compensation right.

Failure to provide notice shall not constitute breach where the issue is urgent, security-related, supplier-driven, caused by the Client, caused by a third party, or outside Xdemór’s reasonable control.

8. Acceptable Use, Resource Controls, and Risk Controls #

8.1 General Acceptable Use #

The Client must use the Services in compliance with: #

(a) this Policy;

(b) the Xdemór Terms of Service;

(d) any applicable Individual Agreement, Proposal, Order Form, Statement of Work, Annex, or written service confirmation;

(e) all applicable laws, regulations, court orders, regulatory requirements, and legal obligations;

(f) all applicable upstream provider, hosting provider, DNS provider, email provider, CDN provider, registrar, registry, software vendor, payment provider, and platform rules.

The Client is responsible for all activity occurring through its websites, applications, accounts, users, contractors, sub-users, end clients, credentials, scripts, files, databases, domains, email services, and hosted environments, whether authorised by the Client or not.

8.2 Prohibited Hosting Activity #

The Client must not use, permit, enable, or facilitate use of the Services for: #

(a) illegal, fraudulent, deceptive, abusive, misleading, or harmful activity;

(b) malware, viruses, worms, trojans, ransomware, botnets, credential harvesting, phishing, spoofing, impersonation, or security attacks;

(c) spam, unsolicited bulk email, mail bombing, abusive forwarding, open relay, spoofed headers, or practices damaging IP reputation, domain reputation, email deliverability, provider standing, or network integrity;

(d) denial-of-service activity, packet flooding, packet corruption, port scanning, vulnerability scanning, brute force activity, unauthorised penetration testing, network probing, or unauthorised access attempts;

(e) open proxy services, traffic relaying, tunnelling, anonymisation services, VPN-like resale, unauthorised scraping, crawling, spidering, bot operation, or automated traffic generation;

(f) cryptocurrency mining, high-volume computation, video encoding, video transcoding, batch processing, file dumping, public archive storage, backup storage, mirror hosting, warez, piracy, torrent tracking, or non-standard infrastructure workloads;

(g) storage, publication, distribution, or linking to content that infringes copyright, trademarks, trade secrets, privacy rights, publicity rights, confidentiality obligations, or other third-party rights;

(h) content or activity that is unlawful, defamatory, obscene, threatening, abusive, hateful, exploitative, or otherwise prohibited by applicable law or upstream provider rules;

(i) unauthorised commercial resale, sublicensing, white-label resale, or third-party access to the Services outside the permitted service scope;

(j) any activity likely to cause blacklisting, provider suspension, registrar enforcement, registry action, email filtering, CDN restriction, platform ban, payment provider review, legal claim, regulatory action, reputational harm, or infrastructure instability.

8.3 Resource Usage and Fair Use #

The Client must use the Services within the limits of the applicable service plan, technical environment, upstream provider restrictions, and ordinary hosting use.

The Client must not create excessive or abnormal use of:

(a) CPU;

(b) memory;

(d) bandwidth;

(e) inodes;

(f) database resources;

(g) email sending limits;

(h) API calls;

(i) backup storage;

(j) file count;

(k) concurrent processes;

(l) cron jobs;

(m) traffic volume;

(n) CDN usage;

(o) support resources.

Any “unlimited” or high-allowance feature remains subject to fair use, provider restrictions, infrastructure stability, reasonable business use, and this Policy.

Xdemór may require the Client to optimise, reduce usage, remove files, disable scripts, upgrade to a higher plan, migrate to a more suitable environment, or pay additional fees where usage exceeds ordinary service expectations or creates risk to infrastructure, providers, or other clients.

8.4 Client Responsibility for Scripts, Software, and Content #

The Client is responsible for all scripts, software, plugins, themes, applications, integrations, files, media, databases, content, users, and processes operating within or connected to its service environment.

The Client must ensure that all software and content is:

(a) lawful;

(b) properly licensed;

(d) updated;

(e) compatible with the hosting environment;

(f) free from malware or abusive behaviour;

(g) compliant with applicable provider rules and legal requirements.

Xdemór may disable, remove, quarantine, suspend, isolate, or refuse support for any script, software, plugin, theme, file, account, database, process, or integration that creates security, stability, performance, licensing, legal, abuse, or provider-compliance risk.

8.5 Email, Messaging, and Deliverability Controls #

Where email, forwarding, mailbox, SMTP, transactional email, or DNS-based email authentication is provided or configured, the Client must not use the Services for spam, unsolicited bulk email, abusive mailing, spoofing, phishing, mail bombing, open relay, purchased lists, scraped lists, or deceptive sender practices.

Xdemór does not guarantee inbox placement, sender reputation, email deliverability, non-blacklisting, spam-filter avoidance, or uninterrupted email sending.

Xdemór may suspend, throttle, restrict, disable, reroute, or remove email-related services where necessary to protect deliverability, IP reputation, domain reputation, provider compliance, security, or other clients.

8.6 Security and Abuse Response #

Xdemór may take immediate protective action where it reasonably considers that the Services, infrastructure, upstream providers, other clients, third parties, data, security, reputation, legal compliance, or service continuity are at risk.

Protective action may include:

(a) suspension or restriction of Services;

(b) disabling websites, scripts, plugins, themes, accounts, files, databases, mailboxes, DNS records, redirects, or integrations;

(d) isolating or migrating environments;

(e) throttling resource usage;

(f) removing malware, abusive files, spam scripts, phishing pages, or harmful content;

(g) revoking access credentials;

(h) requiring password resets, identity verification, security remediation, or software updates;

(i) notifying upstream providers, platforms, affected parties, regulators, law enforcement, or competent authorities where necessary.

Such action may be taken without prior notice where the issue is urgent, security-related, abuse-related, provider-driven, compliance-driven, or necessary to protect infrastructure, Xdemór, other clients, or third parties.

8.7 Upstream Provider and Platform Compliance #

The Client must not use the Services in any way that causes, or may cause, Xdemór to breach the terms, acceptable use policies, resource limits, security rules, export controls, platform rules, or compliance requirements of any upstream provider, software vendor, registrar, registry, DNS provider, email provider, CDN provider, payment provider, data centre, or infrastructure supplier.

If an upstream provider, platform, authority, or supplier requires suspension, restriction, removal, migration, disclosure, investigation, or enforcement, Xdemór may comply without liability to the Client.

Xdemór is not required to continue providing any Service where doing so would expose Xdemór to provider suspension, legal risk, payment risk, platform enforcement, security risk, reputational harm, or operational instability.

8.8 White-Label, Reseller, and End-User Responsibility #

Where the Client uses the Services for white-label, reseller, agency, partner, or end-client purposes, the Client remains fully responsible for:

(a) the conduct of its own clients, users, sub-users, contractors, staff, and representatives;

(b) all content, websites, domains, email activity, data, scripts, and accounts operated under its service environment;

(d) providing accurate service representations to end users;

(e) handling end-user disputes, complaints, notices, and claims;

(f) preventing misuse, abuse, illegal content, spam, malware, and provider-risk activity.

Xdemór may suspend, restrict, isolate, or terminate any service environment affected by end-user misuse, even where the immediate breach was caused by the Client’s own customer, contractor, developer, user, or sub-user.

8.9 No Duty to Host Harmful or Risky Content #

Xdemór is not obliged to host, transmit, store, process, support, restore, migrate, or continue any content, service, website, account, file, database, script, application, or configuration that Xdemór reasonably considers unlawful, abusive, harmful, insecure, provider-risky, reputationally damaging, technically unstable, commercially unsuitable, or outside the intended use of the Services.

8.10 Enforcement and Consequences #

Breach, suspected breach, or risk of breach of this Section may result in one or more of the following:

(a) warning;

(b) suspension;

(d) throttling;

(e) removal or disabling of content, files, scripts, accounts, email, DNS, databases, or integrations;

(f) forced upgrade, migration, optimisation, or remediation;

(g) additional charges for investigation, recovery, cleanup, migration, support, or remediation;

(h) High-Risk classification;

(i) requirement for advance payment, deposit, or revised commercial terms;

(j) refusal of support, migration, export, restoration, or reinstatement where legally and contractually permitted;

(k) termination;

(l) Final Lock under the Terms of Service;

(m) notification to providers, platforms, authorities, regulators, law enforcement, or affected third parties where necessary.

Xdemór may determine the appropriate enforcement measure based on risk, urgency, provider requirements, legal exposure, client history, technical impact, and operational judgement.

8.11 No Liability for Enforcement #

Xdemór shall not be liable for loss, downtime, data loss, email interruption, traffic loss, revenue loss, reputational harm, failed delivery, failed migration, failed recovery, loss of access, provider action, platform restriction, or business interruption arising from enforcement action taken in good faith under this Section, under the Terms of Service, or under upstream provider, legal, security, or compliance requirements.

9. Data Protection #

Where personal data is processed in connection with the Services, the Client acts as Data Controller and Xdemór acts as Data Processor, unless expressly agreed otherwise in a written data protection agreement.

All processing of personal data is governed by the applicable Data Processing Agreement, Privacy Policy, and any mandatory data protection law.

The Client is responsible for ensuring that it has a lawful basis, required notices, permissions, consents, and instructions for any personal data, customer data, employee data, end-user data, analytics data, website data, email data, or third-party data submitted to or processed through the Services.

Xdemór may process technical logs, access logs, security logs, backup data, usage data, support data, diagnostic data, and infrastructure metadata where necessary for service delivery, security, troubleshooting, billing, compliance, abuse prevention, or legal obligations.

Where upstream providers, hosting providers, software vendors, data centres, DNS providers, email providers, CDN providers, security providers, or other subprocessors are used, such processing remains subject to the applicable Data Processing Agreement and subprocessor framework.

10. Migration, Termination, and Exit #

Upon termination of the Services, the Client may request export of Client Data in accordance with the Terms of Service, the Data Processing Agreement, this Policy, and any applicable handover or migration procedure.

Any export, handover, migration, release, or continuation of access is subject to:

(a) full settlement of all outstanding amounts;

(b) identity, authority, and security verification;

(d) upstream provider restrictions;

(e) legal, compliance, and data protection requirements;

(f) the applicable service scope.

Unless expressly agreed in writing, Xdemór is not required to provide:

(a) system configurations;

(b) server configurations;

(d) root access;

(e) internal documentation;

(f) automation scripts;

(g) operational playbooks;

(h) service logic;

(i) infrastructure diagrams;

(j) security rules;

(k) dashboards, tooling, or backend systems used to deliver the Services.

Migration assistance, where provided, is offered on a reasonable-efforts basis only and does not guarantee zero downtime, full data integrity, identical performance, identical configuration, successful email migration, successful DNS migration, successful third-party integration, or equivalent service behaviour after migration.

Following termination, suspension, expiry, or Final Lock, Xdemór may disable access, stop service delivery, remove environments, delete data, release resources, reassign infrastructure, or cease support in accordance with the Terms of Service, this Policy, the Data Processing Agreement, and applicable law.

11. Limitation of Liability #

To the maximum extent permitted by law, Xdemór shall not be liable for:

(a) infrastructure-level outages or failures;

(b) upstream provider, hosting provider, DNS provider, email provider, CDN provider, registrar, registry, software vendor, payment provider, platform, or third-party action or inaction;

(d) data loss outside expressly agreed backup or recovery services;

(e) incomplete, unavailable, outdated, corrupted, or failed backups;

(f) failed migration, failed restoration, failed recovery, failed email delivery, failed DNS propagation, failed SSL validation, or failed third-party integration;

(g) Client-side changes, unauthorised access, weak passwords, compromised credentials, outdated software, insecure plugins, unsupported themes, custom code, or third-party developer actions;

(h) loss of traffic, SEO rankings, advertising performance, analytics continuity, revenue, profit, goodwill, reputation, customers, contracts, or business opportunity;

(i) indirect, incidental, special, punitive, consequential, or economic losses.

Nothing in this Policy limits liability where such limitation is prohibited by mandatory applicable law.

Liability is limited in accordance with the Xdemór Terms of Service and any applicable Individual Agreement.

Domain name registration, registrant status, ownership, registrar control, DNS delegation, WHOIS data, domain expiry, domain renewal, domain transfer, registry enforcement, and domain-related disputes are governed by the Domain Names Policy and applicable registrar, registry, ICANN, ccTLD, and legal rules.

This Policy applies only to hosting and infrastructure services connected with domains, including hosting configuration, DNS-related technical assistance, SSL/TLS setup, email routing, redirects, CDN configuration, and service integration where included in the applicable service scope.

Where a hosting or infrastructure service depends on a domain, DNS record, registrar setting, SSL validation, email record, or third-party verification, Xdemór does not guarantee continuity or functionality where the relevant domain-related component is expired, suspended, misconfigured, transferred, locked, deleted, disputed, or controlled outside Xdemór’s managed service layer.

13. Governing Law and Jurisdiction #

This Policy is governed by and construed in accordance with the laws of England and Wales.

The courts of England and Wales shall have exclusive jurisdiction over any dispute arising out of or in connection with this Policy, except where mandatory applicable law, registrar rules, registry rules, ICANN procedures, ccTLD authority rules, or binding third-party dispute procedures require otherwise.

14. Contact #

14.1 Hosting Support #

Hosting support requests relating to Fludnox hosting and infrastructure services should be submitted to:

Hosting Support Email: support@fludnox.com

Brand Division: Fludnox Web Hosting Solutions

14.2 Legal Entity #

The Services are provided by: #

Entity: The Xdemór Group Limited
Company No.: 14456444
Registered Office: 86–90 Paul Street, London, EC2A 4NE, United Kingdom

14.3 Compliance Contacts #

Legal: legal@xdemor.com
Data Protection: dpo@xdemor.com

14.4 Rights, Disputes, and Formal Requests #

Requests relating to legal rights, data protection rights, disputes, complaints, policy matters, or formal notices may also be submitted via the designated Request Form at:

Submit a Request

Submitting a request through the general hosting support channel does not guarantee that it will be treated as a formal legal, compliance, or data protection notice unless the nature of the request is clearly identified.