Privacy Policy
Client-Side Architecture
File conversions on FILEMORPH are executed locally within your web browser. Selected files are processed in local memory and are not uploaded to or stored on FILEMORPH servers.
1. Overview
FILEMORPH (https://filemorph.0xff.space) is an independent web utility providing browser-based file conversion tools. This document describes the data handling practices of the website.
2. Local File Processing
When using FILEMORPH tools (including HEIC to JPG, Compress Image, WebP to PNG, Merge PDF, Resize Image, PDF to JPG, JPG to PDF, PNG to JPG, Crop Image, JPG to WebP, and Rotate Image):
- In-Browser Execution: Files are read into your browser's local memory and processed using standard client-side APIs (HTML5 Canvas, WebAssembly, and JavaScript).
- No Server Uploads: File contents are not uploaded to, transmitted across, or stored on external servers or cloud databases.
- Verification: This behavior can be verified using the Network panel in your browser's developer tools.
3. Information We Do Not Collect
Because processing occurs on your local device, FILEMORPH does not collect or log:
- File names, file contents, or image metadata.
- Personal identity information (names, emails, addresses).
- User account data (no account registration exists).
- Payment details (all tools are free to use).
4. Memory Lifecycle
Files processed in the browser generate temporary in-memory Object URLs to display previews and enable downloads. These allocations are released when the job is reset, cleared, or when the browser tab is closed.
5. Cookies & Local Storage
FILEMORPH uses local storage solely to persist your theme preference (Light or Dark mode). No tracking cookies or advertising identifiers are used.
6. Hosting Infrastructure
The static assets for FILEMORPH are served via Cloudflare Pages. Standard HTTP request metadata (such as IP address, user-agent, and requested asset path) may be logged by the hosting provider for operational security and routing purposes.
7. Contact
For inquiries regarding this policy, contact the maintainer at: