Privacy

Our promise

ChargeBite Tools is built around zero long-term retention andno sharing of your files. We process documents only to fulfill the tool you requested.

How PDF tools work

Applies to Compress PDF, Merge PDF, and Split PDF:

1. Your file is uploaded over HTTPS to our servers on private infrastructure.
2. It is written to temporary storage scoped to a single job (not a permanent database or object store).
3. We process it and stream the result back to your browser.
4. Temporary files are deleted immediately when the job finishes or fails. A background reaper removes any leftovers.

How Compress Image works

Compress Image runs entirely in your browser. Your photo or graphic is not uploaded to ChargeBite servers for this tool. Processing uses on-device APIs (such as Canvas). Look for the “Processed on your device” label on the tool page.

How ZIP Files works

ZIP Files runs entirely in your browser. Selected files are packed into a standard ZIP archive on your device. They are not uploaded to ChargeBite servers for this tool.

How White Background works

White Background uses ephemeral server processing: your image is uploaded over HTTPS, an ML cutout model removes the background, we composite onto pure white, stream the result back, and delete temporary files. We do not keep a photo archive.

What we do not do

• We do not keep a copy of your documents after processing.
• We do not sell, share, or train models on your file contents.
• We do not require accounts for core tools.
• We do not send uploaded files or file names to advertising networks.

Advertising (Google AdSense)

ChargeBite Tools is free. We load Google AdSense (publisher ca-pub-5986785857761646) so the site can stay free to run. Google may set cookies or use advertising identifiers, and may collect the page URL, IP address, and device information underGoogle’s privacy policy,how Google uses ads, andhow Google uses data on partner sites.

Ads are separate from file jobs. We do not send your uploads, file names, or tool contents to Google for advertising. PDF jobs still upload, process, return, and delete. On-device tools still do not upload.

Operational logs

We may log technical metadata needed to run the service safely — for example job IDs, file sizes, processing duration, HTTP status codes, and rate-limit signals. We do not log file contents.

Privacy-first analytics (Umami)

We run a self-hosted Umami instance to understand which pages and tools are used. The tracker is first-party (same origin), cookieless, and respects Do Not Track. We record page paths, referrers, coarse device/geo, and named events such as “tool opened” or “download clicked”.

Events never include file names, file contents, or the text you paste into a tool. Umami does not use session replay or heatmaps. Page ads (see above) are a separate Google script.

Client-side vs server tools

Tools are labeled clearly: “Stays on your phone” for client-side jobs and “Deleted after the job” for PDF utilities that must run on the server. Prefer on-device tools when you want the file to never leave your machine.

Machine-readable privacy summary

AI agents and researchers can also readllms.txtandllms-full.txtfor a structured product overview.

Contact

ChargeBite Tools is operated by Dilpreet Singh. Privacy questions go to[email protected]or thecontact page. See alsoAboutandTerms.