Privacy
Last updated 2026-09-07
The short version
Your customers’ pet photos never leave your computer. Every part of the image pipeline — decoding, background removal, cropping, resizing, mockup compositing and ZIP packaging — runs inside your browser. There is no upload step because there is no server to upload to.
What we do not have
- No copies of your photos, at any point, ever.
- No user accounts, passwords or profiles.
- No database of customers, orders or file history.
- No advertising trackers, no social pixels, no ad retargeting.
- No fonts or stylesheets loaded from anyone else’s domain.
What we do have
Page analytics
We count page views to know which guides are worth writing more of. This runs on Google Analytics, which sets a cookie in your browser and records the usual request metadata — page URL, referrer, approximate location from your IP address, and browser type. It is the only third-party script on the site, and it does not load until you move, tap, scroll or click, so a page you open and close reaches Google not at all.
Nothing you put into the tool is measured. No photo, filename, file size or result is ever sent to Google or to us — the analytics see the page, never the work.
Your browser’s own storage
Two things are stored locally, on your machine, and never transmitted: the background removal model, cached in IndexedDB so returning visits download nothing; and — if you buy Pro — your license key and the timestamp of its last validation, in localStorage. Clearing your browser data removes both.
Payment details, held by Stripe
If you buy a Pro license, Stripe processes the payment and holds your email address and card details under their own privacy policy. We never see your card number. We use your email only to send the license key and, if you ask us something, to reply.
Server contact, once in a while
The single exception to “nothing touches a server” is license validation. A Pro key is checked against Stripe when you enter it and roughly once a day thereafter. That request contains the license key and nothing else — no photo data, no filenames, no image dimensions.
Where the large files come from
The background removal model and the WebAssembly runtime are served from a content delivery network on a subdomain we control. Fetching them tells the CDN your IP address, as any file download would. It tells it nothing about the photo you are working on, because the photo is never part of the request.
Changes
If this policy changes in a way that affects what happens to your data, the date at the top changes and the change is described here rather than quietly folded in.
Privacy questions
- Are my customers’ pet photos uploaded to your servers?
- No. Photos are read, processed and exported entirely inside your browser using WebAssembly. There is no upload endpoint and no storage bucket. Even if we were asked to hand over a customer’s photo, we would have nothing to hand over.
- Does the tool work offline?
- After the first visit, largely yes. The background removal model is cached in your browser’s IndexedDB on first use, so returning visits download nothing. Validating a Pro license key needs a connection, but the cached result is valid for 24 hours.
- What data do you collect?
- Aggregate page analytics through Google Analytics, which loads only after you interact with the page and sets its own cookie, and — if you buy Pro — the email address and payment details you give to Stripe, which Stripe holds rather than us. Your photos are in neither list, and never will be.