Back to Home
100% Genuine Transparency

Privacy Policy

LAST UPDATED: JULY 7, 2026

We believe that processing files should be private, secure, and straightforward. Here is our promise: we do not sell your data, we do not require account registration, and your files are processed locally whenever possible.

1. Overview & TL;DR

TL;DR SummaryWe don't collect, store, or sell your files or personal information. Most tools convert files locally inside your browser, while image tools operate in-memory on our server without storing anything.

No Registration

We do not have a registration form, subscription page, or database of users. You are 100% anonymous.

Zero Ads

We have zero advertisements or pop-ups. We do not integrate third-party ad networks or marketing cookies.

Local-First Processing

Audio, Video, PDF, and Text tools process files locally in your browser. No files leave your device.

Stateless Image API

Image tools process files in-memory on our backend server. They are never written to disk.

2. File Processing Architecture

TL;DR SummaryAudio, Video, PDF, and Text tools execute on your device. Image tools securely call our backend server to handle processing in-memory, immediately deleting the buffer once downloaded.

Craft implements a dual-processing model depending on the category of file utility to optimize for processing speed and file size handling:

A. Local Browser Processing (Audio, Video, PDF, Text)

All operations for Audio, Video, PDF, and Text utilities (such as cutting audio, merging PDFs, formatter, diff checker, etc.) are executed directly inside your web browser using client-side libraries.

  • Your file data is loaded into your device's memory local environment only.
  • No file payload is sent over the internet or uploaded to any server.
  • The file conversion occurs instantly on your processor locally.

B. Server-Side In-Memory Processing (Resize, Compress, Convert, Generate ICO for Images)

To ensure high-performance conversion and support formats like AVIF, HEIC, PNG, SVG and JPEG, the Image utilities submit files through a secure HTTPS POST request to our API endpoints.

  • Images are loaded entirely in-memory (RAM) on our backend hosting environment.
  • We process the file in-memory and immediately send the processed file back.
  • Your images are NEVER written to a hard disk, database, or persistent storage.
  • Once the response is returned to your browser, all memory buffers containing the file are instantly discarded.

3. Usage Analytics & Tracking

TL;DR SummaryWe use Firebase Analytics to track anonymous usage patterns (like buttons clicked, tool category, or file size). We never collect file names, file contents, or personal user details.

To help us understand how users interact with our tool categories and guide feature improvements, we log standard usage events. This system uses Firebase Analytics only when deployed to production.

What we track:

  • Tool opening events (e.g. which slug is opened).
  • General category filters clicked (audio, video, image, pdf, text).
  • Search query terms used (to see which tools are most in demand).
  • Anonymous processing metadata: input file sizes in bytes, output file sizes in bytes, input file extension type, and output file extension type.

Strict Restriction: We NEVER log, upload, or collect your files' actual content, individual file names, metadata tags (like GPS coords in image metadata), or personal user details.

4. Cookies & Browser Storage

TL;DR SummaryWe use zero tracking or advertising cookies. We only save interface preferences (like light/dark theme, active tab and scroll position) in your local browser storage.

We value your privacy and refuse to use intrusive tracking cookies, third-party marketing trackers, or cross-site tracking systems.

We do use local browser utilities to store your preference parameters for a seamless UI experience:

  • localStorage (theme preference): Stores your selected layout view style ('light', 'dark', or 'system') so we don't flash the wrong theme on reload.
  • sessionStorage (activeTab & scroll position): Temporarily saves your current view filters and page vertical coordinate so that returning from a tool detail page places you exactly where you left off.

All of these storage details remain completely on your local device. They are never sent to our servers.

5. Third-Party Services

TL;DR SummaryWe host the website code on secure web servers and use Google's Firebase SDK for usage logging. No other third parties receive any telemetry or files.

Craft depends on the following external providers to run the web service:

  • Hosting Infrastructure Provider: Serves our static code files, assets, and processes the image API routes. When you load the site, standard server connection logs containing your IP address and user-agent string are generated (mandatory for server security and DDoS prevention). No files are saved on the server.
  • Firebase Analytics (Google LLC): Aggregates anonymous interaction actions (clicks, tabs opened, file types) to generate usage histograms. Your file contents are never sent to Google.

6. Your Controls & Data Protection

TL;DR SummarySince we do not collect personal identifiers, emails, or store files, there is no data on our servers to request or delete. You can clear all localized settings anytime by clearing your browser cache.

In standard web services, users must request data deletion (GDPR / CCPA). For Craft, our security design renders this unnecessary:

  • Access & Correction: There are no usernames or accounts. We cannot link any interaction telemetry to you specifically.
  • Localized Reset: To purge your theme choices or scroll configurations, simply clear your browser's local cache/storage for our site domain.

7. Contact & Policy Updates

TL;DR SummaryWe will post updates to this policy directly on this page. If you have questions about the file architecture or code details, you can review the private codebase repository (if granted authorized developer access) or reach out to the developer.

We may update this policy periodically to reflect additions of new tools or adjustments to analytics metrics. Any updates will be logged on this page.

If you have questions about the architectural code or need technical clarification, please reach out to the developer, Divyansh Gemini, or review the private codebase repository if you are an authorized collaborator or running a self-hosted deployment.