Privacy Policy

Images you process

It depends on the tool. Two of them behave differently, so we describe them separately rather than making one blanket claim.

Crop, resize, compress, convert — nothing is sent

These run entirely in your browser. Decoding, resizing, cropping, compression and format conversion all happen on your device. No image data is transmitted, so there is nothing for us to retain, share or delete.

Background removal — a downscaled copy is sent

Automatic background removal runs on our GPU server, currently hosted in the United States. To do that, your browser sends a copy of the image resized to 1024 × 1024 pixels — not your original file. The server computes a cutout mask and returns only that mask; your browser then applies it to the full-resolution original locally. The original image never leaves your device.

The transmitted copy is held in memory only for the duration of the request and is not written to disk or retained after the response is sent. We do not use your images for training.

Click-select background removal is different again: it runs entirely in your browser, and nothing is transmitted.

Session cookie and usage limits

Background removal is limited to a set number of free images per day. To count that, our server sets one HttpOnly cookie (pt_sid) holding a random session identifier, and records how many images that session and your IP address have processed today. The counter resets daily. The identifier is not linked to any account, name or email, and we do not use it for advertising or tracking across sites.

Analytics

We use Cloudflare Web Analytics to count page views and see which pages people arrive from. It sets no cookies, assigns no identifier to you, and does not follow you to other sites — so there is no profile of you to build, sell or hand over. It records the page URL, referrer, and general device and country information derived from the request. We use this only to decide which tools are worth improving.

We also keep our own usage count on this site. When a page opens, your browser posts the page path, the language prefix, your viewport width, and — for the first page of a visit — the site you came from (the hostname only, never the full link or any search terms). Our server adds the two-letter country code it already sees on the request.

We also record when a tool is actually used: that a file was chosen, that a tool was run, that a result was produced, and that a result was downloaded. What we store for those is the tool name, how many files were involved, how long the work took, the output size, and the output format. Your files are never sent for this — no file name, no content, no thumbnail, nothing derived from the image. Only the counts above.

There is no cookie, no identifier and no session anywhere in this: one row is one event, and nothing joins two rows into a person. That means we cannot tell that the same visitor who opened a page later saved a file — we only see totals per step. We accepted that limit on purpose rather than assign you an identifier. We keep these counts because third-party analytics is blocked for many visitors, which left us unable to tell which tools people actually use.

Separately, our host Cloudflare keeps standard server logs (IP address, user agent, requested URL) for security and abuse prevention.

Advertising

Kachakacha does not currently display advertising and sets no advertising cookies.

Your choices

Clearing your cookies removes the session identifier described above; your daily free quota then restarts on the next request. We hold no account data and store no image files, so beyond the records described here there is no personal data set to request or erase.

Who operates this service

Kachakamu (카차카무) · representative: Donghee Youn (윤동희)

Contact

Privacy questions and everything else: qeadzc9503@naver.com

Last updated: 2026-08-20