What we respond to, and how quickly
Reports of technical errors, incorrect explanations, security issues, and accessibility barriers are read and acted on. Expect a reply within a few business days for most messages, and sooner for anything affecting user privacy.
Corrections to the technical content are particularly welcome. The explanations on this site describe published specifications, and if one of them is wrong or has gone out of date, we would rather hear it from you than leave it standing.
We cannot verify specific images or text on your behalf, offer an opinion on whether a particular file is AI-generated, or serve as an expert witness. The tools are self-service by design, and a private verdict from us would be exactly the kind of unsupported claim this site exists to avoid.
Reporting a technical problem
Include your browser and version, your operating system, the file format involved, what you expected, what happened, and the exact text of any visible error message. If a specific page is involved, include its address.
Do not attach private files, pasted text, raw manifests, or images containing location metadata unless you have deliberately decided to share them. In most cases a description of the problem and the file format is enough to reproduce it.
If a file is genuinely needed to diagnose the issue, we will ask, and you can decide then.
Security reports
Please report security concerns responsibly and privately, before any public disclosure, so an issue can be fixed before it is exploited.
Anything that could cause user content to leave the browser is the highest severity category here and will be prioritised over everything else. Include reproduction steps and the affected browser.
Please do not run automated scanning against the site, and do not test in ways that would affect other users.
Accessibility
Describe the barrier along with the assistive technology and workflow involved — screen reader and version, keyboard-only navigation, magnification, reduced motion, or contrast requirements.
Reproducible details get fixed fastest. If a control is unreachable by keyboard or a result is not announced, say which control and on which page.
Accessibility issues are treated as functional bugs rather than enhancements. A tool that cannot be operated with a keyboard or a screen reader is broken for the people who need it, and that is prioritised accordingly.
Corrections to the technical content
The explanations across this site describe published specifications — C2PA, Exif, IPTC, XMP, and the Unicode standard — along with providers' own public statements about how their watermarking works. Specifications get revised and provider behaviour changes.
If an explanation is out of date, imprecise, or wrong, quote the passage and point at the source that supersedes it. Corrections that come with a citation are the fastest to act on, and the page's updated date will change when the fix ships.
This matters more here than on a typical site, because the whole premise is that claims are grounded in something checkable rather than asserted. An uncorrected error undermines that directly.
Press, research, and partnerships
Journalists and researchers writing about provenance, watermarking, or detection accuracy are welcome to get in touch. We are happy to explain what the tools do and, more usefully, where their limits are.
We do not accept paid placements, sponsored content, guest posts, or link exchanges. Nothing on this site is published in exchange for payment, and the source lists link to primary specifications rather than to commercial partners.
If you want to link to a specific tool or guide, no permission is needed — just link to it.
Frequently asked questions
Why is there no contact form?
A form would need a server to receive the submission, and this site deliberately has none. The same architecture that keeps your files in your browser also means there is nothing here to accept a form post.
Will you check a specific image or text for me?
No. The tools are self-service, and a private verdict from us would be exactly the kind of unsupported claim this site exists to avoid. If a tool is not working as documented, that is a bug report we want.
How quickly do you reply?
Within a few business days for most messages, and faster for anything affecting user privacy or security. Reports with reproduction details get answered first.
Should I attach the file I am having trouble with?
Not initially. Describe the problem, the file format, and the browser. If a file is genuinely needed to reproduce the issue, we will ask, and you can decide then.
Do you accept guest posts or sponsored links?
No. Nothing on this site is published in exchange for payment, and the source lists point at primary specifications rather than commercial partners.