Wwhaletu.
PRIVACY PROOF

See how local processing
actually works.

“Local” describes where your tool input is processed. It does not pretend that an ordinary website has no network traffic. Here is the precise boundary.

◉ File content stays in the tab✓ Analytics excludes tool content◎ Open-source modules disclosed
THE DATA PATH

Your input takes the shortest route.

A local file tool does not need an upload endpoint. The browser reads the selected bytes, processes them in memory and creates a temporary result.

01You select inputThe browser grants this tab access to the chosen file or text.
→
02Local code processes itBrowser APIs and disclosed modules work in memory.
→
03A temporary result appearsPreview URLs and buffers exist only for the active task.
→
04You save or resetDownloads go to your device; reset releases references.
PROCESSING LEVELS

One badge, a specific meaning

Every tool shows a level based on its actual execution path—not a generic marketing claim.

◉
Local

Input is processed by browser APIs already available on your device.

No content upload
◉
Local with limits

The task stays local, but browser memory, formats or output quality impose explicit limits.

No content upload
◉
Local with WASM

A WebAssembly module is downloaded from WhaleTu, then runs against data in this tab.

Module download only
◉
Local + downloaded code

A specialized JavaScript module is loaded from WhaleTu when the workspace opens.

Module download only
◉
Online data

A request is required and the exact remote data flow must be disclosed before processing.

Explicit disclosure
ANALYTICS & ADS

What ordinary website traffic can contain

  • Requested URL, IP address, timestamp and user agent may appear in hosting access logs.
  • Consented analytics may record a tool slug, category and success/failure event.
  • Analytics events exclude filenames, file bytes, text, passwords, keys, tokens and results.
  • Advertising and analytics scripts do not load when “Essential only” is selected.
MEMORY & CLEANUP

What happens after processing

  • Blob URLs are revoked when results are replaced, reset or unmounted.
  • PDF page objects, canvases, workers and large task references are released where the browser APIs allow.
  • The browser may retain a file you explicitly download.
  • Closing or refreshing the tab clears component state; browser behavior still controls low-level memory reclamation.
VERIFY IT YOURSELF

Use your browser’s Network panel.

You do not have to take the badge on trust. Open developer tools, choose Network, run a local tool and inspect requests. You should see page assets and any consented commercial scripts—not a request containing your file or text.

Choose a local tool →
  1. 1Open Developer Tools
  2. 2Select the Network panel
  3. 3Run a tool with a test file
  4. 4Inspect request names and payloads
OPEN FOUNDATIONS

Specialized code is disclosed

PDF.js, pdf-lib, exifr, AJV, Papa Parse, JSZip, SVGO and Luxon are loaded only where needed. Versions, licenses and adaptation notes remain public.

Review open-source notices →
What “downloaded code” means

The browser downloads a JavaScript or worker module from WhaleTu. The module then processes your input locally; downloading code is not the same as uploading content.