Security Architecture & Data Privacy
Inspect the technical security architecture of ILOVE2LS. Learn how our client-side WebAssembly sandbox eliminates cloud data transit vulnerabilities.
1. The Privacy Paradigm: Why Serverless Compute Matters
Over 95% of online PDF and image utilities operate on a legacy multi-tenant cloud server model. When a user uploads a document, it travels across public networks, gets stored on a web server, is parsed by an external backend process, and remains cached until an automated script deletes it.
This multi-step pipeline exposes documents to severe attack vectors:
• Man-in-the-Middle (MitM) transit interception
• Shared multi-tenant server directory leaks
• Accidental backup snapshot persistence
• Rogue server administrative access
ILOVE2LS replaces this vulnerable pipeline with a 100% In-Browser WebAssembly Architecture. All binary byte arrays, vector paths, font subsets, and image pixels are parsed, transformed, and re-encoded locally inside your browser's sandboxed virtual machine.
2. In-Memory WebAssembly Sandbox Isolation
Modern browsers (Google Chrome, Firefox, Safari, Edge) provide high-performance WebAssembly (WASM) execution environments that are sandboxed from your operating system and network.
When you process documents on ILOVE2LS:
1. File Selection: Files chosen via input or drag-and-drop are accessed via the W3C File and Blob APIs directly in local device RAM.
2. Binary Processing: The processing engine (compiled WebAssembly and high-performance JavaScript engines like pdf-lib and Canvas 2D) manipulates the byte streams purely within volatile memory.
3. Output Generation: The resultant PDF or image is serialized into an in-memory Blob and delivered via an immediate client-side download link.
4. Immediate Purge: The moment you navigate away or close the tab, the garbage collector releases the memory buffer. Zero data ever touches physical server hard drives.
3. Technical Verification: Audit Our Zero-Upload Guarantee Yourself
We do not ask you to take our privacy claims on faith. You can verify our zero-upload guarantee independently in under 60 seconds using your browser's built-in developer tools:
1. Open any tool on ILOVE2LS (e.g., Merge PDF, Compress PDF, or Word to PDF).
2. Open Developer Tools by pressing F12 or right-clicking anywhere and selecting "Inspect".
3. Navigate to the "Network" tab and ensure recording is active.
4. Check the "Disable cache" box and select the "Fetch/XHR" filter.
5. Drag and drop your files into the workspace and execute the tool.
6. Observe the Network Activity: You will see zero outbound HTTP POST or PUT requests carrying your file data. The file size transferred to any remote server is exactly 0 bytes.
This verifiable proof provides airtight compliance confidence for legal, healthcare, accounting, and enterprise teams handling strict non-disclosure documents.
4. Cryptographic Standards (AES-128 & AES-256)
For our Protect PDF and Unlock PDF utilities:
• We implement standardized Advanced Encryption Standard (AES) with 128-bit and 256-bit key lengths in strict accordance with ISO 32000-1 (PDF Standard).
• Cryptographic key derivation and password hashing execute in your browser runtime.
• When you set a document password, the password is used locally to encrypt the cross-reference tables and content streams. Your password is never transmitted across the network or logged anywhere.
5. Transient Cloud Token Handling (Google Drive & Dropbox)
When importing files from Google Drive or Dropbox:
• We utilize least-privilege OAuth scopes (strictly read-only file access).
• Access tokens are held exclusively in volatile JavaScript variables during the active user session and are never written to cookies, persistent localStorage, or server databases.
• File binary streams travel directly from Google/Dropbox cloud servers over TLS-encrypted connections into your browser's local memory buffer.
6. Transport Layer Security & Content Security Policy
ILOVE2LS enforces strict transport-level and browser-level safeguards:
• Transport Layer Security (TLS 1.3 / 1.2): Enforces 256-bit encryption for all static asset deliveries.
• HSTS (HTTP Strict Transport Security): Prevents downgrade attacks and cookie hijacking.
• Content Security Policy (CSP): Prevents cross-site scripting (XSS) and unauthorized external script execution.
• Subresource Integrity (SRI): Ensures loaded scripts match cryptographic hash standards.
7. Security Inquiries & Vulnerability Disclosure
We maintain an active security research stance. If you believe you have discovered a security concern or vulnerability in any platform component, please report it to our engineering team at security@ilove2ls.com. We respond to all verified security reports within 24 business hours.
