This document outlines the engineering protocols, security frameworks, and mutual responsibilities governing our operating system migration services. We maintain these rigorous standards to guarantee the absolute safety of your private data during your transition to Linux.
Last Updated: July 2026
1. Scope of Engineering Services
Web Reliability provides technical instruction, structural execution, and data-safeguarding pipelines to assist clients in migrating their physical computer hardware from Microsoft Windows 10 to a stable Linux operating system environment.
Because this migration is executed remotely with the client physically interacting with the hardware under our strict technical instruction, this project is structured as a collaborative engineering pipeline divided into separate, risk-isolated phases (Backup, Live USB Compatibility Check, OS Installation, and Restore). Clients who select the Sandbox-Verified Backup add-on receive an additional isolated-environment test-restore phase prior to installation, as described in their service tier.
2. Infrastructure & Data Protection Protocols
To ensure the highest tier of privacy and liability isolation, all data movement conforms to the following structural mandates:
- Client-Side Cryptographic Encryption: Before any user data leaves the client’s local computer, it is compressed and encrypted locally at the terminal using industry-standard open-source backup mechanisms (Borg/Restic) over a secure SSH layer.
- Zero-Knowledge Architecture: The cryptographic keys required to unlock the data payload are managed directly on the client’s local terminal. Web Reliability does not maintain, store, or have plaintext visibility into the contents of the backup payload while it is in transit or at rest on our storage clusters.
- Server Infrastructure Location: Verified encrypted backup payloads are securely stored on our dedicated backup infrastructure located exclusively in the East United States region.
3. Mandatory Data Retention & Deletion Schedule
We do not operate as an indefinite, unmanaged repository for client data. We enforce a strict data-purge window to reduce liability and protect client privacy.
Secure Encrypted Ingestion
Day 0: Project Kickoff
The client-side encrypted backup payload is successfully transferred to our East US infrastructure and verified for integrity inside an isolated scratch virtual machine environment.
System Deployment & Restore
Day 1 – 2: Migration Window
The client-side encrypted backup payload is successfully transferred to our East US infrastructure. For clients on the base tier, the migration proceeds directly to installation once transfer is confirmed. For clients who have added Sandbox-Verified Backup, the payload is additionally restored and verified for integrity inside an isolated scratch virtual machine environment before installation begins.
On-Call Support & Local Stabilization
Day 3 – 14: Safety Blanket Window
We keep your encrypted offsite backup payload intact on our East US storage cluster for exactly 14 days. This serves as an emergency fallback safety net in case you discover a missing local application profile or file path.
Cryptographic Data Deletion
Day 15: Automated Purge
Exactly 14 days after the restoration is verified and closed, the backup payload is permanently deleted from our East US infrastructure using cryptographic wiping protocols. This process is irreversible.
4. Mutual Responsibilities & Safety Precautions
Operating system installations carry inherent operational risks. To mitigate these risks to the furthest extent possible, the project cannot proceed until the following criteria are checked:
⚠️ The Triple-Layer Backup Mandate
The client explicitly agrees to maintain a secondary local copy of their absolute most critical files (e.g., irreplaceable family photographs, primary financial ledgers, core business documents) on a physical external storage drive in their immediate physical possession before the migration phase begins. Web Reliability shall never act as the sole copy of the client’s data.
- BitLocker Recovery Keys: The client is solely responsible for locating and verifying their Microsoft BitLocker drive encryption recovery keys if active. Wiping or modifying an active BitLocker drive without a validated key stops the migration pipeline instantly.
- Software Licensing: The client retains sole ownership and responsibility for preserving physical records of proprietary software licenses, product activation keys, or legacy installation files required to map equivalent tools onto their new Linux environment.
5. Limitation of Liability
Web Reliability utilizes meticulous, industry-validated engineering steps to isolate, test, and protect client data. However, because the physical operating system installation is executed directly by the client at their local keyboard using our remote instructions, Web Reliability cannot control local electrical delivery, hardware component degradation, or failure to execute structural steps as written.
Consequently, Web Reliability’s total aggregate liability for any claims, errors, hardware damage, or data discrepancies arising under this agreement is strictly limited to the total monetary amount paid by the client for the specific migration service tier.
Clean, High-Integrity Systems Engineering
We back our technical expertise with rigid, transparent legal and operational standards. Let’s map out your transition with total peace of mind.