Effective Date: 11 September 2026

Applicable To: All clients, partners, licensees, resellers and authorised shared-service operators using Fludnox hosting, email, DNS, backup or infrastructure services.

This Hosting Migration, Suspension and Termination Procedure (“Procedure”) governs the operational handling of migrations, service restrictions, suspension, reinstatement, expiry and termination of services supplied by The Xdemor Group Limited under the Fludnox brand.

In this Procedure, “You” and “Your” refer to the business, organisation or professional using the Services. “Fludnox”, “We”, “Us” and “Our” refer to The Xdemor Group Limited acting under the Fludnox brand. “Migration” means the transfer or attempted transfer of Content, configurations or services into, between or away from Fludnox-managed environments.

1. Contractual Status #

1.1 Incorporation #

This Procedure forms part of the contractual framework governing the Services and applies together with the Shared Services Terms of Service, the Shared Services Data Processing Agreement, the Fludnox Hosting and Infrastructure Policy, the Fludnox Backup and Data Recovery Policy, the Hosting Acceptable Use Policy, the Service Level Agreement where applicable and the relevant Order Form or Individual Agreement.

1.2 Relationship with Contractual Rights #

This Procedure explains how migration, suspension and termination rights established under the contractual framework may be implemented. It does not create, remove or extend any substantive right of termination, cancellation, ownership or access, and it does not override the Shared Services Terms of Service or an applicable Individual Agreement.

Nothing in this Procedure prevents the Client from using export, backup, control-panel, WordPress administration or migration functionality that is expressly included in an active Service to perform its own migration, subject to the applicable access level, security controls, software terms and resource limits.

1.3 Order of Precedence #

Mandatory applicable law prevails. The Shared Services Data Processing Agreement prevails for personal-data processing, return and deletion. An expressly negotiated Individual Agreement or Order Form prevails for service-specific migration and termination terms.

2. Migration Requests #

2.1 Authorised Instructions #

A Migration request must be submitted through the authenticated Fludnox support channel by an authorised account contact.

Fludnox may require identity, corporate authority, account ownership, payment status or destination verification before beginning or releasing migration-related information.

2.2 Scope #

Migration includes only the websites, databases, mailboxes, files, configurations, DNS records or other components expressly confirmed in the Migration scope.

Items not expressly included remain outside scope, even where they are connected to the same website, domain, business or account.

2.3 Separate Services #

Domain transfers, Registrar changes, DNS migration, email migration, application migration, website migration and data export are separate technical activities.

Completion of one activity does not mean that all related services have been migrated or terminated.

2.4 No Implied Compatibility #

Fludnox does not guarantee that Content, software, email, databases, licences, configurations or backups will be compatible with the source or destination environment.

Conversion, redevelopment, remediation, licence replacement or configuration work may require a separate agreement and charge.

2.5 Self-Service and Assisted Migration #

Where the applicable Service includes cPanel, WordPress administrator or another export, backup or migration facility, the Client may use the available functionality independently and at its own cost and risk. For a WordPress Service, the Client may use a compatible third-party migration or cloning plugin where technically permitted.

The Client is responsible for third-party plugin licensing, configuration, security, resource use, compatibility, destination readiness and verification of the resulting copy. Fludnox does not warrant that a third-party migration tool will produce a complete, secure or operational migration.

Self-service access does not include managed migration, training, consultancy, agency coordination, plugin installation or troubleshooting, format conversion, destination configuration or other technical work by Fludnox unless the applicable Order Form, Service Description or Individual Agreement expressly includes it. A Client’s lack of technical familiarity does not expand the purchased Service scope.

A request for Fludnox to perform optional migration work, or to provide a third party with restricted access, data or authority, must be submitted through the Fludnox Authorised Service Change and Consent form while the relevant Service and required source access remain active and sufficiently before any scheduled suspension, expiry or termination. The request is subject to scope acceptance, account-holder verification, destination readiness and any applicable quotation or advance payment. Submission does not extend the Service term, postpone a suspension or termination, or guarantee completion by a requested date.

3. Incoming Migrations #

3.1 Client Responsibilities #

Before an incoming Migration, You must:

1. have lawful authority to access and transfer the Content;
2. maintain an independent and verified backup;
3. provide accurate credentials and technical information;
4. disclose material security incidents, malware or corruption;
5. identify relevant data locations and regulated data; and
6. keep the source service active until the Migration has been verified.

3.2 Source Provider Limitations #

An incoming Migration may be delayed or prevented by source-provider restrictions, inaccessible accounts, proprietary systems, unsupported formats, encryption, data corruption, transfer limits or expired services.

Fludnox is not responsible for the acts or omissions of the source provider.

3.3 Migration Copy #

Unless otherwise agreed, an incoming Migration creates a copy in the destination environment. It does not automatically delete the source data or terminate the source service.

You remain responsible for instructing the source provider concerning cancellation, deletion and ongoing charges.

3.4 Verification #

You must test the migrated website, application, database, email and connected services promptly after Fludnox confirms completion.

A Migration will be treated as operationally accepted where You place the destination into production, change DNS to it or fail to report a material migration defect within the verification period stated in the applicable Migration notice.

4. Outgoing Migrations and Exports #

4.1 Client-Led Transfer #

You are responsible for selecting the destination provider, opening the destination account and ensuring that the destination is technically and legally suitable.

Unless an Order Form expressly includes an outgoing managed Migration, You are responsible for transferring or importing the exported data.

4.2 Standard Export Tools #

Where available, Fludnox may provide standard control-panel, database, mailbox, file or backup export functionality included in the Service.

Fludnox does not guarantee compatibility between a standard export and a third-party destination.

4.3 Managed Outgoing Migration #

Custom export, format conversion, mailbox transfer, database conversion, DNS coordination, migration planning, out-of-hours work and destination-provider liaison may be treated as separate chargeable work.

Fludnox may require advance payment and a confirmed scope before performing optional outgoing Migration work.

4.4 Destination Credentials #

Where Fludnox is authorised to access a destination environment, You must provide limited and temporary credentials where reasonably practicable.

You must change or revoke those credentials when the Migration is completed.

5. Migration Scheduling and Change Control #

5.1 Migration Window #

A Migration date or time is binding only where confirmed in writing by Fludnox.

An estimate may change because of data volume, source restrictions, security issues, technical incompatibility, third-party delays or Client dependencies.

5.2 Content Freeze #

Fludnox may require a temporary content, database, mailbox or configuration freeze to reduce the risk of data divergence.

Changes made after the final Migration copy begins may not be included unless a further synchronisation is expressly agreed.

5.3 DNS and Propagation #

DNS changes may be affected by caching, time-to-live values, resolvers, Registries, Registrars and third-party networks.

Fludnox does not guarantee simultaneous propagation or continuous service during a DNS transition.

5.4 Rollback #

A rollback is included only where expressly stated in the Migration plan.

Rollback may be impossible where the source environment has expired, data has materially changed, DNS has propagated, the destination has processed live transactions or third-party systems cannot be reversed.

6. Client Backup and Continuity Duties #

You must maintain an independent backup before any Migration, suspension, termination, software change, restoration or infrastructure modification.

Fludnox backups are governed by the Fludnox Backup and Data Recovery Policy and must not be treated as the sole source of recovery.

You remain responsible for business continuity, customer communications, legal retention, destination readiness and preservation of records required after termination.

7. Grounds for Suspension #

Fludnox may suspend or restrict a Service where permitted by the applicable contractual framework, including where there is:

1. non-payment, failed payment or expiry;
2. a breach of the Hosting Acceptable Use Policy or another incorporated term;
3. malware, phishing, compromise, spam or network abuse;
4. an actual or reasonably suspected security or data-integrity risk;
5. an unlawful activity or binding legal requirement;
6. excessive or destabilising resource use;
7. incomplete identity, authority or registration verification;
8. a disputed account, ownership or administrative authority;
9. failure to cooperate with an investigation or remediation instruction;
10. a material upstream infrastructure restriction or failure; or
11. another legitimate legal, security, compliance or operational ground identified in the contractual framework.

Suspension must not be used for an unlawful purpose or in a manner prohibited by mandatory law.

8. Notice of Suspension #

8.1 Prior Notice #

Where the matter is capable of remediation and delay does not create material risk, Fludnox may provide notice describing the affected Service, the reason category, required action and applicable response period.

8.2 Immediate Suspension #

Fludnox may suspend without prior notice where it reasonably considers immediate action necessary to address:

1. active phishing, malware, attacks or compromise;
2. risk to personal data, credentials or infrastructure;
3. serious unlawful or prohibited Content;
4. a binding legal or provider requirement;
5. threatened or actual service disruption;
6. fraudulent or unauthorised account activity; or
7. another comparable urgent risk.

8.3 Confidentiality #

Fludnox may provide only a limited explanation where further information would disclose security controls, confidential third-party information, another Client’s data, privileged legal material or information that Fludnox is prohibited from disclosing.

9. Scope and Effect of Suspension #

9.1 Proportionate Restriction #

Where reasonably practicable, Fludnox may limit a suspension to the affected website, account, mailbox, process, IP address, domain, service component or administrative function.

A full account suspension may be applied where the affected activity cannot be safely isolated or where the breach is systemic.

9.2 Operational Effects #

During suspension, Fludnox may disable public access, email sending, administrative access, control-panel access, APIs, DNS management, backup creation, privileged access, support activity or other affected functionality.

Existing backups may continue to expire under their ordinary retention cycle.

9.3 SLA #

A period of valid suspension is excluded from availability calculations under the Fludnox Service Level Agreement unless an Individual Agreement expressly provides otherwise.

9.4 Continuing Obligations #

Suspension does not automatically cancel charges already incurred, renewals already processed, applicable subscription fees or other surviving contractual obligations.

Suspension does not constitute a waiver, admission of liability or confirmation that reinstatement will occur.

10. Remediation and Reinstatement #

10.1 Remediation Requirements #

Fludnox may require evidence that the cause of suspension has been corrected. This may include:

1. payment of outstanding charges;
2. identity or authority verification;
3. malware removal and software patching;
4. credential replacement;
5. removal of prohibited Content;
6. account or user restrictions;
7. resource optimisation;
8. security investigation;
9. acceptance of an amended service configuration; or
10. migration to a more suitable Service.

10.2 Reinstatement Review #

Reinstatement is not automatic upon partial remediation, partial payment or submission of a response.

Fludnox may verify the remediation and may impose reasonable protective conditions before restoring access.

10.3 Reinstatement Charges #

Where permitted by the applicable Order Form or pricing schedule, Fludnox may charge for malware remediation, restoration, investigation, emergency intervention, reconfiguration or reinstatement work outside the ordinary Service.

10.4 No Restoration of Prohibited Material #

Fludnox is not required to restore Content or functionality that would recreate the original breach, security risk or unlawful activity.

11. Client Termination and Non-Renewal #

11.1 Termination Notice #

The Client may terminate or request non-renewal in accordance with the notice period and conditions stated in the Shared Services Terms of Service, Order Form or Individual Agreement.

A cancellation request does not terminate the Service retrospectively and does not reverse a renewal or charge already incurred unless the contractual framework expressly provides otherwise.

11.2 Fixed-Scope and Prepaid Work #

Termination of recurring hosting does not cancel completed, commenced, fixed-scope, prepaid or separately chargeable Migration, recovery, development or support work.

11.3 Required Preparations #

Before termination or expiry, You must export required Content, confirm destination arrangements, update DNS, transfer domains where applicable and preserve all information needed for legal, operational or business-continuity purposes.

12. Termination by Fludnox #

Fludnox may terminate an affected Service in accordance with the Shared Services Terms of Service and any applicable Individual Agreement.

Termination may follow an unresolved suspension, repeated breach, serious abuse, non-payment, unmanageable security risk, permanent provider restriction, legal prohibition, service discontinuation or other contractual ground.

Where advance notice is reasonably practicable and does not increase legal, security or operational risk, Fludnox may provide an effective termination date and available exit instructions.

13. Expiry and Automatic Service Cessation #

A Service may expire automatically where it is not renewed or where the required renewal payment is not successfully processed.

On expiry, websites, applications, DNS, email, control panels, backups and related services may stop operating without a separate termination notice.

Any grace or recovery period exists only where stated in the applicable Service terms and may differ between hosting, email, domains and other components.

14. Permanent Termination and Final Lock #

14.1 Final Lock #

Where the contractual escalation process results in Final Lock, the affected Service is permanently terminated under the existing commercial arrangement.

Access credentials may be revoked, service restoration may cease and any future engagement may require a new risk assessment, new Order Form, revised pricing and advance payment.

14.2 Data Protection Limitation #

Final Lock does not override mandatory obligations concerning the return, deletion, restriction, preservation or disclosure of personal data under the Shared Services Data Processing Agreement and applicable law.

14.3 New Engagement #

Payment after Final Lock does not automatically reactivate the previous Service or restore prior prices, configurations, data or commercial terms.

15. Data Access, Return and Export #

15.1 Pre-Termination Export #

You must use available export tools and obtain any required data before the Service expires or terminates.

Fludnox does not guarantee continued dashboard or account access after the effective termination date.

15.2 Optional Migration Assistance #

Fludnox may condition custom export, destination configuration, format conversion, manual Migration, consultancy and other optional work on full settlement and advance payment.

15.3 Personal Data Processed on Behalf of the Client #

Where Fludnox acts as Processor, return and deletion of Client Personal Data are governed by the Shared Services Data Processing Agreement and Hosting Data Processing Schedule.

To the extent required by Article 28 UK GDPR or other mandatory law, Fludnox will not rely on an unpaid commercial charge to avoid a mandatory obligation to return or delete personal data.

This does not require Fludnox to provide free custom development, data conversion, destination Migration, reconstruction or other work beyond a legally required return or deletion process.

15.4 Non-Personal Data and Deliverables #

The release of non-personal deliverables, licensed materials, proprietary configurations, custom exports and optional handover work remains subject to the applicable payment, intellectual-property and contractual provisions.

Nothing in this Procedure transfers ownership of Fludnox infrastructure, software, internal tools, security configurations, automation or proprietary materials.

16. Deletion and Backup Expiry #

16.1 Active Service Data #

Following termination, active Service data may be deleted, rendered inaccessible or placed into a deletion process according to the applicable Service configuration and contractual terms.

No specific post-termination retention period applies unless expressly stated in an Order Form, Individual Agreement, DPA or Service Description.

16.2 Backups #

Backup copies may remain in protected rotational systems until overwritten or securely destroyed under the applicable backup cycle.

During that period, the data will remain beyond ordinary active use except where restoration is required for legitimate recovery, legal compliance or authorised investigation.

16.3 Legal Preservation #

Fludnox may preserve relevant data where required by law, court order, regulatory direction, legal claim, fraud investigation, security investigation or another legally recognised retention obligation.

Preserved data will be restricted to the relevant purpose and period.

16.4 Erasure Evidence #

Where required under the DPA and reasonably available, Fludnox may provide confirmation that the applicable deletion process has been initiated or completed.

17. Domains, DNS and Certificates #

17.1 Separate Domain Registration #

Termination of hosting does not automatically terminate or transfer a separately registered Domain Name.

Domain expiry, renewal, transfer and cancellation are governed by the Fludnox Domain Registration Agreement.

17.2 DNS Changes #

You are responsible for arranging required nameserver, DNS, mail-routing and certificate changes before the related Service ends.

Fludnox may cease managing DNS or certificates when the associated managed Service terminates.

17.3 Domain Transfer #

Domain transfer assistance may require identity verification, payment of Domain Name-specific charges and compliance with applicable Registrar and Registry rules.

An unrelated hosting dispute will not transfer beneficial ownership of a Client Domain Name to Fludnox.

17.4 Current Manual Domain Workflow #

Unless and until Fludnox expressly makes authenticated domain-management functionality available in the Client Account, no self-service domain-transfer or Registrar-management facility is promised under this Procedure.

A Registrar-side request, including a transfer or authorisation code, transfer-lock change, change of Registrant or domain contact, or a nameserver or DNS change managed by Fludnox, must be submitted through the Fludnox Authorised Service Change and Consent form. After account-holder and authority verification, the request is processed and recorded through the system-generated authoritative support ticket. A standalone ticket, email or message is not sufficient authorisation for a Restricted Instruction.

Domain requests remain subject to technical availability, applicable charges, security or transfer holds, and the relevant Registrar and Registry rules and processing times. Fludnox does not guarantee completion where a third-party restriction or requirement applies.

18. Email Services #

Termination or suspension of email may stop message sending, delivery, mailbox access, forwarding, filtering and authentication.

You must export required mailbox data before termination and must update mail-routing records where moving to another provider.

Messages received after the Service ends may be rejected, delayed or undeliverable. Fludnox does not guarantee message forwarding or storage after termination.

19. Resellers and Downstream Clients #

A reseller, agency or shared-service operator remains responsible for notifying its downstream clients, arranging migrations and preserving necessary data.

Fludnox may notify a downstream user directly where reasonably required for legal compliance, security, prevention of data loss or service continuity.

Direct communication does not transfer the intermediary’s billing or commercial obligations to Fludnox and does not create a separate commercial agreement.

A reseller must not promise a migration, retention, restoration or reinstatement period broader than the commitment expressly provided by Fludnox.

20. Emergency Infrastructure Migration #

Fludnox may migrate a Service between servers, networks, data centres, security systems or authorised infrastructure providers where reasonably necessary for security, resilience, maintenance, provider failure, capacity, legal compliance or service continuity.

Where the migration materially changes a committed primary data location or international-transfer arrangement, Fludnox will comply with the Shared Services Data Processing Agreement and applicable notification requirements.

Where reasonably practicable, advance notice will be provided. Emergency migration may occur without prior notice where delay would materially increase risk.

21. Charges, Refunds and Credits #

Migration, suspension, termination and reinstatement do not remove charges already incurred.

Refunds, credits and service-credit rights are governed by the Shared Services Terms of Service, applicable Order Form and Service Level Agreement.

A valid SLA credit is not excluded merely because the affected Service is later terminated, but no credit is available for downtime properly excluded under the SLA.

No double recovery is permitted for the same event.

22. Liability and Risk Allocation #

Liability arising from Migration, suspension, reinstatement, expiry or termination is governed by the Shared Services Terms of Service and applicable Individual Agreement.

Fludnox is not responsible for loss caused by the Client’s failure to maintain backups, export data, maintain source services, provide accurate credentials, complete verification, act on notices or prepare the destination environment.

Nothing in this Procedure excludes liability that cannot lawfully be excluded or limits mandatory rights under applicable data-protection law.

23. Communications and Notices #

Operational Migration, suspension and reinstatement requests must be submitted through the authenticated Fludnox support channel or to https://support.shared-services.co/support/tickets/create.

Billing and payment matters may be submitted to accounts@shared-services.co.

Privacy and personal-data matters may be submitted to privacy@xdemor.com, and matters requiring the Data Protection Officer may be submitted to dpo@xdemor.com.

Formal contractual and legal notices must be sent to legal@xdemor.com.

A support request does not constitute a formal legal notice unless Fludnox expressly confirms otherwise.

24. Changes and Governing Law #

Fludnox may amend this Procedure in accordance with the Shared Services Terms of Service.

Urgent changes concerning security, abuse prevention, infrastructure protection, regulatory compliance or service continuity may take effect within the shorter period permitted by the contractual framework and applicable law.

This Procedure and any non-contractual obligations arising from it are governed by the laws of England and Wales. The courts of England and Wales shall have exclusive jurisdiction, subject to any mandatory rule that cannot lawfully be excluded.

---

Controlled Exit, Verified Instructions and Support Channels #

Integration rule: This section forms part of the policy from 11 September 2026 and controls any inconsistent wording in this document concerning its subject matter.

Document Hierarchy and Operational Instructions #

If governing documents are inconsistent, mandatory applicable law prevails, followed by: (a) an express Individual Agreement or Order Form; (b) the Shared Services Data Processing Agreement solely for personal-data processing; (c) the Shared Services Terms of Service; (d) the applicable brand or service-specific policy; (e) the applicable Service Description or pricing schedule; and (f) an Accepted Client Instruction for the specific operation.

An accepted service-change, access or handover form controls only the requested operational action. It cannot amend a higher-ranking document, remove an applicable payment requirement, require a technically unavailable action, or override mandatory law, the DPA or Registry/Registrar requirements.

Restricted Instructions #

Restricted Instruction means an instruction concerning a domain transfer or change of Registrant; DNS record or nameserver change; hosting migration or cutover; full or partial data export; backup release or restoration; cPanel, FTP, SFTP, SSH or other administrative access; credential reset or disclosure; mailbox or email-routing change; third-party access or appointment; suspension, cancellation, deletion or another destructive action; ownership or account-holder change; or release of personal, confidential or regulated data.

A Restricted Instruction must be submitted through the approved secure form or another instrument expressly accepted for that purpose. The accepted form and generated scope schedule control the requested operational action within the existing contractual framework. A message recorded within the authoritative ticket may clarify but may not add a domain, recipient, dataset, access right or technical action. A material change requires a new instruction or an audited amendment approved through the same verification level.

Material contradictions place the request into Clarification Required. No affected technical action is taken until they are resolved. Blanket authority for unspecified future Restricted Instructions is ineffective.

Granular Third-Party Authority #

Third-party authority is not general permission. Separate scopes apply to submitting technical information; communicating about the case; issuing approved technical instructions; receiving a specified export; performing the Client-side migration; providing DNS or nameserver instructions; receiving time-limited access; and receiving transfer or authorisation codes. Authority to communicate does not imply authority to receive data, access systems, change DNS or transfer domains.

Where relevant, the authority record must identify the third party’s full legal name, legal form or trading status, registration number, full registered or principal business address, named natural-person representative, business email and telephone, exact scope, start date and expiry, approved recipient, receiving provider, destination country and secure destination. Final account-holder approval must be completed through the registered account email or another approved step-up verification method.

Per-Domain and Per-Asset Scope #

Each affected domain must have its own action schedule distinguishing hosting migration, website files, databases, email data, DNS records, nameserver delegation, registrar transfer, change of Registrant, redirects, certificates, backups and administrative access. “Everything”, “full transfer”, “all data” and similar expressions are not executable without the generated schedule. Unselected items remain outside scope. Each declared domain or asset must be verified as belonging to, or being managed within, the relevant account before action.

Hosting migration does not transfer a domain registration. A Full Account Export does not transfer a domain. A nameserver change delegates the DNS zone but does not change the Registrant. A DNS record change is not a nameserver change. Email migration is separate from website migration. The destination DNS zone should be prepared before nameserver cutover where applicable.

Site-Scoped and Full Account Exports #

A Site-Scoped Export is limited to the selected website, files, database or other assets identified in the accepted schedule. A Full Account Export may include every website, database, mailbox, DNS zone, certificate and account configuration supported by the applicable platform and is not limited to a named domain.

A Full Account Export requires express account-wide release confirmation, verified account-holder approval, a named recipient, receiving provider, secure destination, personal-data declaration and confirmation that the recipient can use the format. Where the platform supports only a standard whole-account export, Fludnox is not required to create a selective export without a separate scope, quotation and advance payment. No named control-panel, backup product or supplier feature is guaranteed.

Secure Data Delivery #

Personal or confidential exports must use an approved secure method, such as an authenticated portal, SFTP/SCP, encrypted archive or another specifically approved channel. Where appropriate, a password or key must travel separately; Fludnox may record a checksum, time limit, named-recipient confirmation, delivery or download receipt and audit evidence.

Passwords, private keys, complete backups and unrestricted secrets must not be submitted through ordinary form fields or unencrypted email.

Migration Continuation Period and Operational Grace #

Submission, review or approval of a handover request does not renew, extend or pause the underlying Service. The Client must keep the source Service active for the time reasonably required to complete and verify the migration. Where the Service has expired or insufficient paid time remains, Fludnox may require a paid renewal or short Migration Continuation Period before allocating migration resources.

The minimum billing increment is determined by the applicable Service, platform and Order Form. Payment preserves the Service for the stated period only; it does not include custom migration work, guarantee completion or waive separate charges. A revised short-term invoice replacing an annual renewal must be recorded as an agreed variation or replacement invoice. Delay by the Client or receiving provider creates no free hosting, storage, priority work or indefinite retention.

Operational Grace is discretionary, temporary, non-precedential and, where legally and operationally permitted, revocable. It is not a renewal, entitlement, waiver, retention commitment or recovery guarantee and does not freeze ordinary backup cycles unless expressly confirmed. Supplier-specific goodwill remains an internal operational fact unless disclosure is required.

Retention, Access and Recovery #

Retention depends on the category and operational state of the information. Active service data is retained while required to provide the Service. Client-accessible exports remain available only for the expressly stated export period. Protected rotational backups are overwritten or destroyed under the applicable technical cycle and are not ordinary Client-accessible storage. Billing, fraud-prevention, security and audit records are retained under the Privacy Policy. Information subject to a legal hold is retained only for the applicable lawful purpose and period.

Any reference to retention for “up to 90 days” is a maximum operational possibility only. It is not a minimum retention commitment, guaranteed access or recovery period, suspension delay, or representation that a complete or usable backup exists. No universal post-termination access or recovery period and no “no data loss” undertaking applies.

Mandatory Data Return and Chargeable Work #

A payment dispute, suspension or commercial handover restriction does not override a mandatory obligation to return, delete, restrict, preserve or disclose personal data under the DPA or applicable law, or a valid domain Registrant right under applicable Registry/Registrar rules.

Standard export functionality included in the Service is distinct from optional custom extraction, selection, conversion, reconstruction, destination migration, DNS work, configuration, remediation and consultancy. Optional work remains separately chargeable and may require advance payment. A mandatory return or deletion duty does not require free custom development or unlimited administrative assistance.

Special-Category and Regulated Data During Exit #

Before an exit export, the Client must declare whether the selected scope may contain special-category, criminal-offence or other regulated personal data. Fludnox does not represent that it has inspected or verified the substantive contents. Where such data may be included, the delivery method, approved recipient, destination country, applicable international-transfer mechanism and audit evidence must be assessed proportionately to risk.

Official Support and Reporting Channels #

Customer and technical support requests must be submitted through the Support Ticket form at https://support.shared-services.co/support/tickets/create. A request is received only when the system creates a ticket or reference.

Email aliases, WhatsApp, Viber, telephone, live chat and social-media messages are not support-intake channels. They do not create a case, expand scope, restart a review or establish priority. An email reply counts only if the Support Portal successfully records it within an existing ticket and confirms receipt.

Reports of abuse or policy violations must be submitted at https://policies.shared-services.co/submit-request/. Specifically published @xdemor.com privacy, data-protection and formal legal contacts remain valid for their stated purposes.