Privacy Policy

Last updated 2026. Most of what this site does never leaves your device — this page is mainly about the few things that do.

The short version

Editing happens in your browser. When you resize, crop, caption, convert or build a GIF or image, the file is read by your own browser and the result is written back by your own browser. It is never uploaded, and we never receive it.

Some features send data to a server: AI motion tracking, AI background removal and replacement, sharing a GIF, and reporting a problem. AI processing and sharing run only when you choose them.

We do not ask you to create an account, and we have no way to identify you personally.

Tools that run entirely on your device

These never transmit your files anywhere:

  • All photo format converters — JPG, PNG, WebP, HEIC, SVG and GIF
  • GIF resizer, GIF cropper and GIF maker
  • Video to GIF conversion
  • The image editor
  • Captions, text, timing and export in the GIF editor

Your file is held in your browser's memory while you work and discarded when you close or reload the page. Because the processing is local, large files are limited by your device's memory rather than by an upload cap.

AI motion tracking

This feature sends sampled frames to a server, and runs only when you start a tracking run.

When you do, sampled frames from your GIF are uploaded to our storage, passed to a GPU service that computes where the object you selected moves, and the result is returned to your browser. The uploaded frames are deleted once the run completes, and the working storage they pass through expires automatically within one day regardless.

The frames are used only to produce your tracking result. They are not kept, reviewed, or used to train anything.

If you would rather not upload anything at all, the editor's manual keyframes produce the same kind of moving caption without a tracking run.

AI background removal and replacement

When you choose Find objects, the source image or GIF and your selection points are uploaded to private AWS storage and processed by SAM2 on Modal. Every GIF frame is processed. Masks are returned to your browser, where the cutout, replacement background and final export are composed. Replacement backgrounds are not uploaded.

Source files are deleted after a completed or cancelled job when the browser checks its status. If the tab closes or cleanup fails, the private working files, masks and job responses have a one-day storage expiry rule. Expiry is automatic and deletion may take additional time to complete. These files are used to produce your result, not to train models. Server logs contain job IDs, frame and object counts, dimensions and runtime, but not the media or selection points.

Use Cancel processing to stop a running GPU job. Closing the tab alone does not guarantee server cancellation. Jobs have a one-hour execution timeout. Your browser keeps the masks so changing only a replacement background does not need another server run.

Sharing a GIF

If you use the share feature, the GIF you chose to share is uploaded and published at a public web address so that anyone with the link can view it. Along with it we store the title you enter and the file type.

A shared GIF is public. The link is not guessable, but it is not protected either — treat sharing as publishing. Do not share anything you would not want a stranger to open.

Nothing is shared unless you use that feature. Exporting and downloading a GIF does not share it.

Reporting a problem

The "Report an issue" button sends what you type, along with the page path you were on, your browser's user-agent string, the time, and the IDs of any recent processing jobs so the report can be matched to server logs. Reports are filed in our issue tracker.

The site also reports uncaught JavaScript errors automatically so that broken tools can be found and fixed. Those reports contain the error message, the page path, your browser's user-agent and the time. They do not contain your IP address, your files, or any text you have typed into the editor. Page addresses are reduced to the path, so anything identifying in a link is not included.

Analytics

We use Google Analytics to understand which tools people use and where they fail. It does not run at all unless you press Accept on the banner shown on your first visit. If you press Reject, or ignore the banner, no analytics is loaded.

If you accept, we record which tool you used, how long an operation took, whether it succeeded or failed, and a coarse size band for the file (for example "1–10 MB"). We deliberately do not send:

  • filenames
  • any part of the file itself
  • caption or other text you type
  • exact file sizes
  • the query string of the page address

You can change your mind at any time using the Analytics choices button in the site footer area.

Advertising

Pages on this site may display ads served by Google AdSense. Google and its partners may use cookies to serve ads based on your prior visits to this or other websites, and you can opt out of personalised advertising in Google Ads Settings. More detail is in Google's policy on how it uses data from partner sites.

What is stored on your device

  • Your analytics choice and your light/dark theme preference, so they persist between visits.
  • A temporary copy of the file you are editing, used to hand it between the upload page and the editor, and to recover your work if the page reloads unexpectedly.

All of this stays in your own browser and is never transmitted. Clearing your browser's site data for this site removes it.

Server logs and rate limiting

To stop automated abuse of the features that cost us money to run, we store a short hash of your IP address together with a count of recent requests. These records expire automatically within a few hours.

We should be precise rather than reassuring here: a hash of an IP address is not truly anonymous, because the range of possible addresses is small enough to search. We treat these records as personal data, keep them only for as long as rate limiting needs them, and do not use them for anything else.

Our hosting and content delivery providers (Amazon Web Services) also keep their own operational request logs, as any web host does.

Your rights

Because there are no accounts, we hold no profile that could be looked up, exported or deleted on request. In practice:

  • Analytics — controlled entirely by your Accept/Reject choice, changeable at any time.
  • Device storage — cleared by clearing site data in your browser.
  • A shared GIF — contact us with the link and we will remove it.
  • Rate-limiting records — expire on their own within hours.

If you are in the UK, EU, or a jurisdiction with comparable rules and you want to exercise a right that is not covered above, get in touch.

Children

This site is not directed at children under 13, and we do not knowingly collect information from them.

Changes

If this policy changes in a way that affects what we collect, the updated date at the top of the page will change. Because we keep no contact details, we cannot notify you directly.

Contact

Questions about this policy can go through the contact page.