Product privacy

Your files stay on your device.

Unwrap analyzes the files you choose on your device. It does not upload their contents, filenames, tables, or analysis results to its servers.

File processing

How local processing works.

  1. 1
    Choose your files

    Unwrap can only access the files you select or drop into the workspace.

  2. 2
    Process them locally

    JavaScript and WebAssembly in your browser handle parsing, profiling, ZIP inspection, and previews.

  3. 3
    Explore the results

    Your tables and analysis results remain in browser memory while the workspace is open.

Stays on your device

Workspace data

  • Selected file contents and filenames
  • Detected tables, images, and documents
  • Profiles, relationships, and previews
  • The in-memory DuckDB workspace

Goes online

Website requests

  • Page code, fonts, and application assets are loaded from the site
  • The optional sample ZIP is downloaded from Unwrap
  • Anonymous usage events are sent without cookies or file data
  • The Feedback link opens your email app

Browser storage

What remains after you close the tab?

Workspace filesMemory only

Reloading the page clears the open workspace. It is not restored in a later session.

Display preferencesLocal storage

Labels, related local file or table identifiers, and a few interface preferences may remain in your browser. Unwrap does not receive them.

CookiesNone

Unwrap does not use cookies for the workspace or its cookieless product analytics.

Usage analytics

A small number of anonymous events.

Unwrap records a few anonymous events to understand which features are used. Each event contains the site name, an event name, and a marker showing that the session is anonymous.

It does not include file contents, filenames, cell values, analysis results, cookies, or a user account identifier. Like any web request, it may produce a server log containing technical details such as an IP address.