Privacy Policy

What we never receive

Your images and videos are opened, processed and exported entirely by code running in your browser. They are not transmitted to us, and we have no copy of them at any point.

This is a property of how the tool is built, not a promise about how we behave: there is no upload step to disable, because there is no upload.

The AI models are static files served from this site, the same way an image or a stylesheet is. Downloading a model sends us a request for that file — it carries no information about the picture you are working on.

One planned feature will differ: AI seamless repaint for video needs GPU inference on our servers, so files would be uploaded. It is not available yet. Before it ships we will update this page and make the difference obvious at the point of use — it will never apply silently to the local tools you use today.

What we do collect

If you sign in, our authentication provider stores the identity you signed in with: an email address, a phone number, or the basic profile your chosen provider (Google, GitHub or X) returns — typically a name, email address and avatar URL. We do not request access to your files, contacts, repositories or posts on those services.

If you join the beta waitlist, we store the email address you type, whether you selected "reserve a seat" or "I would pay for this", your interface language, and your account ID if you are signed in. We use this to contact you when the feature opens and to gauge how many people want it.

That is the complete list.

Analytics and cookies

This site runs no analytics, no advertising pixels and no third-party tracking scripts of any kind. We do not build profiles of visitors and we do not know how many pages you visited.

We set no tracking cookies. Two pieces of storage exist in your browser and neither is sent to us for tracking: a session token in localStorage that keeps you signed in, and a temporary copy of a file in IndexedDB when you pick an image on the home page — that copy is deleted the moment the editor reads it, and expires on its own after five minutes.

Who else is involved

Authentication and the waitlist table are hosted by Supabase, which stores that data on our behalf and processes it under their own privacy terms.

If you choose to sign in with Google, GitHub or X, that provider learns that you signed in to this site. What they retain is governed by their own policies, not ours.

We do not sell personal data, and we do not share it with anyone beyond the providers named above.

Keeping and deleting your data

Account records are kept while your account exists. Waitlist entries are kept until the feature launches or you ask us to remove them, whichever comes first.

You can ask us to delete your account and any waitlist entry at any time, and we will do so. Write to the address below from the email you signed up with.

Depending on where you live you may also have the right to see a copy of what we hold, correct it, or object to our using it. Ask and we will comply — the amount of data involved is small.

Children

This service is not directed at children under 13, and we do not knowingly hold personal data belonging to them. If you believe a child has signed up, contact us and we will delete the record.

Changes

If we change what we collect, we will change this page and move the date at the top. Material changes will also be announced in the product before they take effect.

Contact

Questions, deletion requests and complaints: hello@watermarkremovers.net