Privacy First Architecture
Privacy Policy
FileForge is engineered to process documents locally, meaning we never upload, store, or view your sensitive files.
1. Decentralized Client-Side Processing
Unlike standard PDF utilities that upload files to centralized servers, FileForge runs a **decentralized, client-side processing model**. When you select a document or image, modern HTML5 APIs load the bytes into your browser's sandboxed RAM partition locally. All visual drawing, page stitching, compression, and file formatting logic occurs on your own CPU. No server-side transmission takes place, resulting in absolute protection from cloud breaches and hacking.
2. Absolute Zero Data Logging
Because processing is client-side, we have no physical backend databases or queues designed to read your document contents. Close your browser tab, and any active memory allocations containing document buffers are instantly wiped by your browser's native garbage collector. We have no access to your filenames, document text, email addresses, or output documents.
3. Third-Party Advertising & Cookies
FileForge is supported by Google AdSense to remain free for our users. Google, as a third-party advertisement vendor, utilizes cookies (such as DoubleClick) to deliver privacy-compliant ads based on your general demographics and browsing activities. We do not provide Google or any advertisement platform with access to your files or document metadata. You can easily manage personalized ad preferences inside [Google Ads Settings](https://www.google.com/settings/ads).
4. GDPR & CCPA Compliance Immunity
The General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) regulate how personal identifiable information (PII) is transferred, archived, and scrubbed. Because FileForge operates a zero-storage architecture, we do not act as data controllers or processors under these frameworks. Your private files never cross any geopolitical boundaries, giving you complete data sovereignty by default.
5. Anonymized Analytical Metrics
We use anonymized telemetry (such as Google Analytics) to monitor load times, page paths, and tool usage frequencies. This helps us optimize performance benchmarks. These metrics are strictly functional and do not have access to any file content, filenames, or outputs processed locally.
6. Policy Updates & Contact
We reserve the right to revise this Privacy Policy to align with new browser security specifications. Your continued use of our utilities constitutes acceptance of our local-only processing guidelines.
Last Updated: June 1, 2026