A transparent technical breakdown of how FileBuddy executes file operations without cloud surveillance, persistent disks, or third-party data broker compromises.
Live Browser Sandbox Diagnostic
Verify in real time that your browser environment isolates memory buffers directly on your hardware.
Protected against eavesdropping during Gotenberg calls
1. Tier 1: Pure Client-Side WebAssembly Processing (Local)
For over 85% of utilities on FileBuddy — including PDF merging, splitting, lossless compression, page rotation, image optimization, and data format conversions — your documents are not uploaded to any server. The only exceptions are Word, PowerPoint, Excel, and CSV to PDF, and PDF to PDF/A, which use our conversion server and delete the file right after conversion.
We compile battle-tested open-source libraries (such as PDF-Lib and Mozilla PDF.js) directly into WebAssembly (Wasm) and execute them inside your browser engine's isolated JavaScript sandbox. When you drag and drop a 50MB file, the binary stream resides exclusively in your computer's local RAM.
No Server Ingestion: No bytes of document content leave your local network adapter.
Hardware Acceleration: Processing utilizes your device's multi-core CPU without queueing or server lag.
Complete Offline Resilience: Once the page bundle is cached, operations can run without an active internet connection.
Complex Office document transformations (such as converting Microsoft Word DOCX, Excel spreadsheets, or PowerPoint presentations into vector PDFs) require a full OpenXML typography and layout engine. To achieve commercial-grade visual fidelity without forcing user installations, FileBuddy connects to a secure, open-source Gotenberg container deployed on Render.
Our backend architecture is strictly stateless and ephemeral:
In-Transit Encryption: All requests travel over HTTPS (TLS).
Ephemeral Memory Buffers: Documents are received directly as in-memory streams, converted by headless LibreOffice, and returned immediately.
No disk retention: No converted files are ever written to persistent storage, Amazon S3, or relational databases. The memory container is destroyed immediately after transfer.
3. Architectural Comparison: FileBuddy vs Commercial Cloud Converters
Security Attribute
FileBuddy Architecture
Typical upload-based tools
Primary Execution
In your browser (Office-to-PDF on our server)
Usually on remote servers
Server Data Retention
None for in-browser tools; deleted after conversion for server tools
Varies by provider; check their policy
Account / Email Tracking
None Required · Anonymous
Varies by provider
Engine Source Audit
Built on open-source libraries (pdf-lib, PDF.js, LibreOffice)
Varies by provider
4. Compliance & Privacy by Design (GDPR & CCPA)
FileBuddy adheres strictly to Article 25 of the General Data Protection Regulation (GDPR), which mandates Data Protection by Design and by Default. Because our core processing happens client-side, FileBuddy does not act as a data controller or data processor of your uploaded documents.
We do not sell personal data, maintain document histories, or inject behavioral trackers into file processing streams. Read our full Privacy Policy for detailed disclosure on advertising cookies and analytics.
