Privacy policy
Your files are cut, re-encoded and saved by your own device. No image, file name, size or page count is ever transmitted. What follows is the short list of things that do leave, and how to stop them.
Last updated 2026-09-28
Your files
Every image you open here is decoded, cut and re-encoded inside your browser, by WebAssembly codecs that were downloaded to your device. The bytes never travel anywhere. There is no upload step, no temporary copy on a server, and nothing left behind to delete.
A consequence worth stating plainly: we cannot recover a file you have lost, and we cannot look at one you have processed. That is not a discretion we are choosing to exercise — we never receive it in the first place.
- Never collected: image contents, file names, file sizes, page counts, pixel dimensions, output files.
- Collected: the target format you converted to, the paper size you laid out on, and which tool you used — values that are already visible in the page controls.
What is stored on your device
Three keys in your browser’s local storage. They are not sent to us, and clearing your browser data removes them.
-
imageto:theme— light or dark, so the next page does not flash the wrong theme. -
imageto:locale— the language you chose. -
imagetoauth:session— a single character,1, meaning "this browser has signed in before". It is a flag, not an account: no email address, no user ID, no name.
Accounts, if you sign in
You do not need an account to use any tool. Signing in exists so the gate can tell a person from a script, and it is one tap: Google, email and password, or a guest session that asks for no email at all.
If you do sign in, Google’s Firebase Authentication holds the credential on our behalf — an email address for email sign-ins, or a random identifier for Google and guest sessions. We can see which method you used and whether a session is anonymous. We do not receive your password, and we build no profile from any of it.
Signing out clears the local flag immediately. To have the account record itself deleted, email huitangyu437@gmail.com and it will be removed.
Analytics
The site uses Google Analytics for Firebase, and it is kept deliberately small. It loads at idle time rather than during page load, and it is skipped entirely when your browser sends a Do Not Track or Global Privacy Control signal — we honour both, rather than asking you to restate a preference you have already set.
These are all the events it can send, with all of their parameters:
- A page view.
-
convert_image— the target format: PNG, JPG or WebP. -
split_image— the paper size the strips were laid out on. -
use_paper_tool— which tool, which paper size, which layout mode. -
login— the method used: google, email or guest.
Advertising and cookies
Advertising here is served by Google AdSense. Ads do not appear on the sign-in, sign-up, password-reset or error pages.
Google and its partners may use cookies or similar identifiers to serve ads based on your prior visits to this and other websites. That exchange happens between your browser and Google: we do not see the resulting profile, and we pass nothing about your files to an advertiser — we have nothing to pass.
You can turn off personalised advertising in Google Ads Settings, or opt out of third-party vendor cookies at aboutads.info. Ads will still appear; they will simply be less relevant to you.
This site sets no cookies of its own. Preferences live in local storage, which is not attached to requests to us.
Your choices
- Do Not Track or Global Privacy Control: honoured for analytics automatically, with nothing to configure.
- Clear browser storage: removes the three preference keys listed above.
- Opt out of personalised ads: Google Ads Settings, or aboutads.info.
- Delete your account record: email huitangyu437@gmail.com .
Retention and changes
Analytics data is kept for the retention period configured on our Google Analytics property; account records are kept until you ask for deletion. There is nothing else to retain — files are never stored, because they are never received.
If this policy changes, the date at the top of this page changes with it, and material changes will be described here rather than applied silently.
Contact
Questions about any of the above, or a request under a data-protection law that applies to you: huitangyu437@gmail.com .