Privacy Policy

Last updated: November 10, 2026

Summary

FileToolkit processes all images locally in your browser. Zero uploads. Zero tracking. Zero data collection.This is not a marketing claim — it is a technical reality enforced by our architecture: static hosting, no backend, no APIs.

How Your Data Is Handled

No Data Collection

FileToolkit does not collect, store, or transmit any of your images or personal data. All image processing occurs entirely within your browser using the HTML5 Canvas API and File API. Your files never leave your device.

No Server-Side Processing

There is no backend server that receives, processes, or stores your images. The application is deployed as static files on Cloudflare Pages. No API endpoints exist for image upload or processing.

No Tracking or Analytics

We do not use Google Analytics, Matomo, or any third-party tracking services. No cookies are set. No fingerprinting occurs. Your usage patterns are not monitored.

No Account Required

You can use all tools without creating an account, providing an email, or any form of identification. There is no user database.

Local Resource Management

Object URLs created for previews are revoked immediately after use. Temporary canvas resources are released. No data persists in localStorage, sessionStorage, or IndexedDB.

Network Requests

The only network requests made are: (1) Initial page load of static assets (HTML, CSS, JS), (2) Font loading from Google Fonts (Geist), (3) Favicon and manifest requests. No image data is ever transmitted.

What We Do & Don't Do

What We Do

  • Process images 100% in your browser
  • Revoke object URLs after use
  • Release canvas memory promptly
  • Validate file types client-side
  • Handle errors gracefully
  • Work offline after initial load
  • Respect your privacy by design

What We Don't Do

  • Upload your images to any server
  • Store your images temporarily or permanently
  • Process images on any backend
  • Use third-party image processing APIs
  • Track your usage with analytics
  • Set cookies or tracking pixels
  • Require account creation
  • Share data with third parties
  • Sell or monetize your data
  • Use your images for AI training

Technical Implementation

Client-Side Only Architecture

FileToolkit is built as a static Next.js application exported to HTML/CSS/JS. It runs entirely in the browser. There is no Node.js server, no Python backend, no database, and no serverless functions. The deployed artifact is a folder of static files served from Cloudflare's edge network.

Image Processing APIs Used

  • HTML5 File API — Reading files from user's device
  • HTML5 Canvas API — Drawing, resizing, compressing images
  • URL.createObjectURL() — Creating temporary preview URLs
  • Blob API — Generating downloadable output files

Memory Management

All object URLs are revoked via URL.revokeObjectURL() immediately after they are no longer needed (after download, after reset, or when replaced). Canvas elements are dereferenced to allow garbage collection.

Limitations & Honest Disclosures

What We Cannot Guarantee

  • Browser vulnerabilities or exploits that could leak memory
  • Malicious browser extensions reading canvas data
  • Operating system or hardware-level surveillance
  • Network-level monitoring of static asset downloads
  • Future changes to browser APIs that might affect privacy

We do not claim "complete privacy" or "absolute security" — such claims are impossible in a browser environment. We implement privacy by design within the constraints of web platform APIs.

Contact

If you have questions about this privacy policy or our data practices, please visit our Contact page.