Privacy

Your files stay with you by default

LocalKit keeps supported workflows local, explains what catalog and CDN requests receive, and shows how browser storage can be cleared.

LocalKit is designed around local processing. The catalog service helps the app discover tools and resource plans, while supported tools process your files in the browser whenever the implementation is bundled locally.

What happens locally

  • Supported image, PDF, audio, video, text, QR, EXIF, and AI tools run in the browser using local device resources.
  • Selected files stay in the current browser tab or worker while the tool is running.
  • Preview data and generated downloads are created locally in the tab.

What the server receives

  • The web app requests tool metadata, release metadata, and asset download plans from the catalog service.
  • Local workflows do not require your source files or generated files to be uploaded.
  • Some tools may download models, WASM modules, or media runtimes from the LocalKit CDN; those asset requests do not include your source files.
  • Client-side operational summaries may be sent to help monitor reliability, without including your source files or generated files.
  • If advertising is enabled, third-party ad providers such as Google may receive standard ad delivery signals such as page URL, device information, and cookie or consent state.
  • Normal web server logs may still record requests for pages, metadata, and static resources.

What may be stored in the browser

  • Language and theme preferences may be stored in local browser storage.
  • Recent run summaries, input settings, and tool state may be kept locally to make repeat use faster.
  • Offline resource state may be stored so the app can remember cached assets.
  • Tool resources may be cached in Cache Storage, IndexedDB, OPFS, or the browser HTTP cache for reuse.
  • Full generated files generally stay in memory until you choose to download or save them.

Advertising and choice

  • The app is structured so advertising, if enabled, is separated from tool execution and file processing.
  • Google advertising services may use cookies or similar technologies according to Google's policies and the user's ad settings.
  • Users can manage browser cookies, site storage, and personalized advertising preferences through their browser and Google account settings.

Your controls

  • You can clear LocalKit site data from browser settings to remove local preferences, cached assets, and saved tool state.
  • Prepared tool resources can also be removed from the offline storage controls shown on supported tool pages.
  • Private browsing reduces persistent storage, but it can also prevent offline reuse.