Your pixels stay yours.

Ember is a fully client-side application. There is no server component at all: no upload endpoint, no processing API, no analytics, no account system. The page you load is static HTML, CSS and JavaScript — after that, everything happens inside your browser's memory.

How editing works

When you open an image, your browser decodes it directly into an HTML5 Canvas. Filters like brightness or blur are computed by JavaScript reading and rewriting raw pixel values with getImageData / putImageData. Layers are composited with the canvas API's native blend operations. When you export, the browser itself re-encodes the canvas into a PNG, JPG or WebP file and hands it back to you as a download.

What is stored, and where

If you use “Save to browser”, your project (layer pixels and settings) is written to your browser's local storage on your own device. It never travels anywhere. You can also download a project file instead — a plain JSON file containing your layers — and keep it wherever you like. Clearing your browser data removes saved projects.

Verify it yourself

Open your browser's DevTools, switch to the Network tab, and edit an image. Apart from loading the app files and fonts once, you will see no requests — no matter how large the image or how many edits you make. That's the whole privacy policy: there is nothing to police, because nothing leaves the tab.