Core privacy principle

ChopKitty is designed so uploaded files are not sent to a remote processing server. Image compression, format conversion, and PDF image recompression are intended to run locally in the browser.

That local-first design is the main privacy promise of the product and the reason the site emphasizes browser-side processing in its public content.

What file data the tool handles

When a visitor drops a file into the interface, the browser needs to read that file in local memory to generate previews, run codecs, and export the result. Those operations happen inside the browser session.

If a user clears the queue or closes the session, the generated object URLs and in-memory data are intended to be released by the client-side application.

Analytics and operational data

The site includes Google Analytics for basic traffic measurement. That means standard pageview and usage data may be collected by Google according to the site's analytics configuration and Google's own policies.

ChopKitty is being prepared for ad and publisher review, so this privacy page exists to explain the high-level difference between local file handling and the separate analytics or ad ecosystem that may be used to run the site.

What this page does and does not promise

This page is a practical overview, not a substitute for formal legal advice. It summarizes the product's operating model as implemented in the current site.

Files are intended to be processed locally in the browser
Traffic analytics may still occur through third-party tools
Visitors should avoid using any online service for sensitive files unless they understand the surrounding analytics and ad environment