Your Privacy Matters

Security & Privacy

Your files never leave your device. All processing happens locally in your browser.

100% Client-Side Processing

  1. You select a file from your device
  2. The file is read into your browser's memory using JavaScript FileReader API
  3. All conversion/processing happens in your browser using WebAssembly and JavaScript libraries
  4. The converted file is generated locally and downloaded directly to your device
  5. At no point does your file travel over the internet to our servers

Technologies We Use

Image Processing

Canvas API, WebGL - Native browser APIs for image manipulation

PDF Processing

PDF.js (Mozilla), pdf-lib - Client-side PDF rendering and editing

OCR (Text Recognition)

Tesseract.js - WebAssembly-based OCR running entirely in browser

Background Removal

@imgly/background-removal - AI model running locally via WebAssembly

Video Processing

FFmpeg.wasm - Full FFmpeg compiled to WebAssembly

Audio Processing

Web Audio API - Native browser audio processing

Security Headers

Strict-Transport-Security

Forces HTTPS connections

Content-Security-Policy

Prevents XSS attacks

X-Frame-Options

Prevents clickjacking

X-Content-Type-Options

Prevents MIME sniffing

Referrer-Policy

Controls referrer info

Permissions-Policy

Restricts browser features

What We Don't Do

✓ We don't upload your files to any server

✓ We don't store your files anywhere

✓ We don't analyze or read your file contents

✓ We don't require account registration

✓ We don't track which files you convert

About Our CSP Configuration

Our Content Security Policy includes some directives that may seem permissive. Here's why:

unsafe-inline

Required for Next.js framework's CSS-in-JS styling system

wasm-unsafe-eval

Required by WebAssembly-based libraries (Tesseract.js, PDF.js) that power our client-side processing. More secure than unsafe-eval as it only allows WebAssembly compilation

Found a Security Issue?

We take security seriously. Please report any vulnerabilities responsibly.