Privacy Center

How Toolza handles files, telemetry, and third-party code — generated from a live audit of every tool on this site.

0Browser-only tools
117CDN code, local files
0Server-upload risks
117Unique tools audited

File processing behavior

Every Toolza utility is designed to run in your browser. We do not operate an upload API for tool inputs.

Local by default

Files you select are read with the browser File API and processed in JavaScript (often in a Web Worker). They are never POSTed to a Toolza server.

No account required

There is no login, email capture, or profile tied to your tool usage. Favorites and history stay in your browser's localStorage.

Retention

Tool inputs are not retained by us after the page closes. Session analytics events (no file names or contents) live in sessionStorage for up to 100 events and clear when the tab session ends.

What we never collect

Filenames, file bytes, extracted document text, passwords, form answers you type into tools, and personal document content.

Fully browser-only tools

These pages reference no third-party script CDN for core operation — code and processing both stay on your device (plus first-party Toolza assets).

    Tools with third-party code libraries

    These pages load open-source libraries from a CDN (code only). Your files still never leave the device — the CDN delivers JavaScript, not your data.

    What a CDN dependency means

    A browser downloads a library (for example PDF.js or a QR decoder) from a public host so the tool can run. That host sees a request for the script file — not the document you opened.

    Common hosts in use

    fonts.googleapis.com (117)

    Telemetry & advertising

    Honest boundaries around measurement and ads.

    Product telemetry

    We track a small set of first-party events in your browser session only:

    • page / tool open
    • file selected (count, size, MIME type — not names)
    • processing start, success, error
    • download click, search, favorite toggles

    What is never sent

    • Filenames or file contents
    • Extracted text or passwords
    • Personal document fields
    • Cross-site advertising profiles built from your files

    Advertising

    Toolza may display ads via third-party ad partners to keep the product free. Ad scripts can set their own cookies or storage under their policies — see our Cookie Policy. Ads never receive the files you process.

    Browser compatibility

    Core tools target current Chrome, Edge, Firefox, and Safari. Local processing uses standard Web APIs (File, Canvas, Web Workers, WebAssembly where needed). Features degrade gracefully rather than uploading as a fallback.

    Privacy FAQ

    No. Tool pages do not include upload endpoints. Processing happens in your browser; a privacy audit checks every tool page for server-side form posts or off-site file fetches.
    No. The CDN serves JavaScript code to your browser. Your document stays in browser memory for local processing.
    A privacy-oriented event queue in sessionStorage: which tool opened, whether processing succeeded, and aggregate UI actions. No file names, contents, or passwords.
    Use the clear controls inside each tool, clear site data for toolza.in in your browser settings, or open browser DevTools → Application → Local Storage / Session Storage.
    See the Privacy Policy for the complete legal description. This Privacy Center is the live technical breakdown.

    Questions about a specific tool?

    Each tool page shows a Privacy & Processing section with that tool's exact behavior.

    Read the Privacy Policy