What happens to your files, and what is stored

The file operations themselves — resizing, cropping, converting, merging, splitting, compressing — run in your browser, on your own processor and memory. FIXLYIER sends the code to your device rather than sending your file to a server to be worked on. The tool pages ship a Content-Security-Policy with connect-src 'self', so while you are working, the page cannot open a connection to any server other than this one.

That is a statement about processing, not about storage. Saving your work is a separate step, and it is described below.

How the processing works — and how to verify it yourself — is documented on How it works.

An account stores your email address, the name you give, and your password as a salted hash. Signing in sets a session cookie — that is the only cookie this site uses. Email verification and password reset send one message each through a transactional mail provider, carrying your address and the link; nothing else is ever mailed.

You can delete your account yourself under Account → Data. Deletion removes the account record and its sessions.

Usage limits are counted against an anonymous identity token stored in your browser. It carries no name and no email, and links to nothing outside this site.

A support ticket stores what the form shows: your email, an optional name, the topic, subject and message, and — only when you tick the box — your browser version and screen size. Never your files, their names, or anything about their contents. Resolved tickets may later be anonymized: the conversation is kept for the record, the address is removed.

Saving is not processing, and saving does transmit. When work is kept in your account, the file you opened and the results FIXLYIER produced are sent to FIXLYIER's storage and held there. That transmission is what makes the work durable: you can close the tab, come back, refine what you made, and undo your way back through it.

Every committed change is kept as its own version, alongside what produced it. Storage is per account — files are readable only through your own session, never through a public link. Removing an item from your library, deleting the work itself, and deleting your account are different operations, and each one names what it will do before you confirm it.

When the optional AI assistance is enabled, an instruction you type is sent to a reasoning model together with measurements of the open file — its format, dimensions, size, and the labels of anything you selected. Each request shows its own disclosure listing exactly what is being sent, and requests count against a daily allowance.

Some things cannot be done from measurements alone — looking at a picture to answer a question about it is the plain example. That needs the file itself, so FIXLYIER asks first, naming the provider, and sends only the one file the operation needs. An approval covers that operation and that provider; if the work moves to a different provider, you are asked again. Storing your work in your account and sending a file to an AI provider are separate things, and the second never follows from the first.

Sign-in attempts and account changes are recorded in an audit log with the action, its outcome, a hash of the network address, and the browser identification string. The raw network address is not stored.

No analytics scripts, no advertising, no third-party cookies, no trackers, and no data sales. The site runs on a single server FIXLYIER operates, which terminates connections for it directly — no CDN or edge network sits in front of this site.

Write through the contact form to ask what is stored about you or to have it removed. Quote your ticket reference or account email so the record can be found.