DESKKIT GUIDES

Browser image tools and file privacy: what stays on your device?

Separate local file processing from web hosting, advertising scripts and the app you choose when sharing.

By AK Software Labs · Published 25 October 2026

Open the tool ↗

“Runs in your browser” describes where a tool performs a task. It does not mean a website makes no network requests. Understanding that distinction helps you choose a workflow that fits the sensitivity of your files.

What DeskKit’s tools process locally

The current web image tools decode your selected image and create the result with the browser’s image and canvas APIs. The text tools transform the text in the page, and calculators work with the values you enter. These tool implementations do not send the selected image, entered text or calculator values to a DeskKit processing server.

What a website still loads

Your browser requests the page, style sheet, JavaScript and logo from the website’s host. Hosting systems can keep ordinary access logs. DeskKit also includes Google AdSense code. Google may process advertising-related information according to its policies and the consent choices and requirements that apply. Read the privacy policy for those separate services.

Sharing changes the destination

When you choose Share and select another app, the exported file is handed to that app through your device’s sharing features. What happens next depends on the app you select and the action you take there. Selecting a file in DeskKit does not itself publish it publicly, but sending it through another service is a separate disclosure.

Local does not mean permanently saved

The active result lives in the current browser workspace until you export it. Reloading or closing the page can discard it. Save a copy if you need it later, and check your browser’s Downloads view. A shared device can retain downloaded files until someone removes them.

A practical privacy checklist

Know the scope of this explanation

This guide describes the current DeskKit website. It does not describe every feature of the Android app or promise that a future cloud feature will work locally. Any cloud-processing feature needs a separate explanation of where files go and what choices are available before you use it.

Further reading

MDN: browser image export · web.dev: understanding image formats

Related guides

Browse all DeskKit tools →