Legal

Policies written to be read

Most legal pages exist to protect the company that wrote them. Ours have an easier job, because the architecture does the heavy lifting: your images and videos are processed in your browser and never uploaded, so there is far less data for a policy to govern in the first place. We’ve tried to keep every document below in plain language, specific enough that you can verify our claims rather than take them on trust.

The Privacy policyis the place to start if you’re wondering what we collect. The short version: your media never reaches us, and the policy spells out exactly what analytics and advertising data does exist, under what consent, and how to opt out. The Cookies page goes further than most, it enumerates the cookies and browser-storage entries the site can set, including the local caches that hold downloaded AI models, so nothing on your device is a mystery.

The Terms cover the ground rules for using a free service: what you can do with your exports (anything: they are yours), what we promise about availability, and the limits of a tool provided at no cost. Accessibility documents our WCAG 2.2 AA commitment and how to report barriers you hit, and Security explains our responsible-disclosure process, if you find a vulnerability, that page tells you exactly how to reach us and what to expect.

The Editorial policy names the accountable team and explains review, corrections, AI assistance, primary-source use, real modified dates, and how product articles are grouped without inventing an expert.

A practical map: “what happens to my files?” is the privacy policy; “what is stored in my browser?” is cookies; “can I use exports commercially?” is terms; “something is hard to use with a screen reader” is accessibility; “I found a flaw” is security; and “how was this guidance checked?” is the editorial policy.