Privacy
The picture you drop is decoded into this page's memory, divided there, and written straight to your downloads folder; no server is in that path, so there is no copy anywhere for us to keep or delete.
The short version
- The picture never travels. It is decoded, divided and encoded inside the browser tab you are reading this in.
- Nothing about the picture is stored — not the file, not its name, not its dimensions, not a thumbnail. Closing the tab is the whole deletion process.
- There are no accounts, so there is nothing to sign in to and no profile to attach anything to.
- The archive you download is assembled in the tab and handed straight to your browser’s download machinery.
What happens to a file you open
Choosing, dragging or pasting a picture hands the browser a reference to bytes that are already on your device. The page reads those bytes to work out what format the file really is and to read its orientation flag, then asks the browser to decode it into an in-memory bitmap. From there the tiles are drawn with a 2D canvas, encoded, and written into an archive as a temporary object in the same tab.
There is no request that carries picture data, because there is no server to send it to: this site is a set of static files and a JavaScript bundle. A build-time audit fails the release if any module that touches a picture buffer gains a network call, a storage call or an API route, which is a mechanical check rather than a promise anyone has to remember to keep.
What is kept in your browser
One thing, and only if you use it: the posting ledger for a profile grid or puzzle feed — the list of upload numbers you have ticked as posted — is saved in this browser’s local storage so it survives closing the tab. It is keyed by the grid and its framing, never by the picture, its file name or its pixels, and it never leaves the device. A recipe link carries settings in the part of the address after the #, which browsers do not send to the server, and a saved recipe file holds settings only. The button below empties everything this site keeps in this browser.
What the analytics sees
Pages served from splitpicture.com load Cloudflare Web Analytics, a cookie-free beacon on a property that belongs to this domain alone. For each page view it reports the page address, the referring page, a coarse country, the browser and device category, and how quickly the page loaded. It sets no cookie, stores nothing in your browser, assigns no identifier and does not follow you from one site to another.
The beacon is added by the page only when the address in your browser is splitpicture.com itself. A copy of this site opened anywhere else — a local preview, a test deployment — loads no analytics at all. The beacon has no way of learning that a picture was opened, what it contained, how it was divided or whether any tiles were written: none of that leaves the tab, so none of it is there to report.
No advertising
This site shows no advertising and loads no ad code. There is no ad network, no tracking pixel and no cookie banner, because there is nothing that would need one.
What the contact page sends
One page here does send something, and only when asked to. Pressing send on the contact page posts the name, email address and message you typed, with this site’s domain attached, to a Google Form, which holds the response under Google’s own policies. Nothing leaves while you type or when the page loads, no picture or tile is ever part of it, and nothing else on this site sends anything to Google.
Where the law sits
Because no picture data is collected, there is no picture data to request, correct or erase. The analytics holds aggregate page counts with no identifier attached, so there is nothing in it that could be traced back to you. The only thing this site can hold about you is a note you chose to send from the contact page, which you can ask through that same page to have removed.
If this ever changes
A change that moved any part of the cutting to a server would be a different product, and it would be labelled as one on the page where it happened rather than amended quietly into this policy. Nothing of that kind is planned.