Acceptable Use Policy
A tool that removes a mark deserves a clear statement of what it is for. This is that statement — specific cases, not vague warnings.
Why this page exists
Most sites publish an acceptable use policy because a template told them to. This one matters more than usual: the tools here remove something, and "removing a mark" is a category that contains both entirely ordinary work and genuine misuse. The honest thing to do is name both, rather than hide behind a sentence about "compliance with all applicable laws".
We should also be clear about our position. Files are processed inside your browser and never reach us, so we cannot see what you process and have no technical ability to review or block it. This policy is not enforced by a filter. It is the line we are asking you to hold, and it forms part of the terms of service.
The principle in one sentence
Use these tools on content you created or are authorised to modify. Almost everything else follows from that.
Uses this tool is built for
- Cleaning your own exports. You generated a Video Overview, a slide deck, an infographic, an Audio Overview, or a Gemini image in your own account, and you want the finished artefact to look like your work rather than a tool's output.
- Study material. Turning an AI-generated summary deck into notes, flashcards, or a handout for your own revision, where a badge across the corner is simply in the way.
- Internal decks and documents. Reports, briefings, and slides prepared for colleagues inside your own organisation, where the source material is yours to begin with.
- Personal portfolios and drafts. Work-in-progress you assembled yourself, cleaned up before you show it to anyone.
- Teaching material. Lesson content a teacher generated for their own class.
- Metadata hygiene. Stripping EXIF and GPS data from your own images before publishing them, so a photograph does not quietly disclose where you live.
What these have in common is not the format. It is that the person cleaning the file is the person who made it.
Uses that are prohibited
- Stripping attribution from someone else's work. Removing a watermark, credit, or signature from a file you did not create, in order to pass it off as your own or to publish it without the creator's permission. This is the case this policy exists for.
- Circumventing DRM, paywalls, or access controls. These tools are not designed for that and must not be used as a step in it — including removing marks from material obtained by bypassing a subscription, a licence check, or a technical protection measure.
- Misrepresenting AI-generated content. Removing a badge to disguise the AI origin of content where a platform's rules or the law require that origin to be disclosed. Academic submissions, journalism, political and election material, advertising, and many platform upload policies all have disclosure requirements. Removing a visible badge does not satisfy them and does not excuse them.
- Processing files you have no right to process. Confidential material belonging to someone else, licensed stock content, or media obtained without permission.
- Rebuilding this as a service you control. Automating, scraping, or wrapping these tools to resell watermark removal, or presenting the site as your own product.
- Attacking the site. Attempting to disrupt the site or its CDN, or to interfere with other visitors' use of it. Good-faith security research is welcome and belongs on the security page.
Two things worth being blunt about
Removing a badge does not change ownership
A watermark is a label, not a lock. Taking it off changes how a file looks — it does not transfer copyright, does not grant you a licence, and does not make redistribution permissible. If you were not allowed to use the underlying content before you cleaned the file, you are still not allowed to use it afterwards. Nothing on this site is a rights-clearance mechanism.
SynthID is not removed
Google embeds SynthID, an invisible watermark, in content its models generate. These tools do not remove it and are not designed to. SynthID lives in the underlying pixel and audio data rather than in the visible badge, so it survives every operation described on the about page and remains detectable afterwards.
Anyone hoping to make AI-generated content undetectable will not get that here, and should not represent this tool as offering it.
Enforcement, honestly described
We cannot detect a violation of this policy, because we never see your files. There is no account to suspend and no history to review. Claiming otherwise would be theatre.
What we can do is act on what reaches us. If you believe someone is using this tool against your rights — for instance to redistribute your work with your watermark removed — write to [email protected] with the details and the affected material, and we will respond. Where a report concerns content hosted elsewhere, the effective remedy usually lies with that host or platform, and we will say so plainly rather than imply we have powers we do not have.
We also reserve the right to change or withdraw any tool if it becomes clear that it is predominantly serving one of the prohibited cases above.
Related pages
The terms of service cover the rest of the relationship, the privacy policy explains what data exists at all, and about documents how each engine actually works.