Fanfold has no crash reporting and never sends anything on its own, so a problem only reaches us if you send it. There is no form here and nothing on this page sends anything.
What you expected, and what you got instead.
If the capture did not go cleanly, Fanfold keeps a record of it with that entry in your history — so this still works days later.
Then paste it into the mail.
Or press Report a problem, next to it: that copies the diagnostics and opens your mail app with the subject and a short template already filled in, so all you do is paste. If nothing opens — that link type only works if a mail app is your system's handler, which webmail users often have not set — press Copy diagnostics instead and paste it into a message to us yourself. It is the same text either way.
No button on the row? Then that capture reported no problem, and there is nothing kept for it. There is also a Copy diagnostics button lower down, under About Fanfold — that one covers your last few captures whatever happened, and only until you close Chrome.
run at +0ms completed +12ms probe ratio=1.02 clipper=yes +840ms step n=17 grew=false +9210ms sealed exit=at-end
No page content, no screenshots, no addresses. It goes to your clipboard, so you read every line before you send it.
Copy it out of your browser's address bar and paste it in. If we can open the page ourselves, we usually see the problem within minutes.
If it is a page only you can reach — behind a login, on a company network, an internal tool — say so, and tell us what kind of page it was instead: a webmail inbox, a company wiki, a spreadsheet, a long list of records. We can often find a public page that behaves the same way and test on that.
Do not paste an address you would not want read by someone else.
The PDF that came out wrong, or a screenshot — attached the way you would to any email. Look at what you are attaching first: a PDF may contain whatever you were capturing, and only you can tell.
A person reads it. If we can reproduce it, it becomes a bug we work on.
There is no ticket system and no status page to check. We reply to your email, or we do not have anything useful to say yet.
So you do not write in about something already being worked on.
Chrome shows this for extensions whose publisher account is new. Ours is: Fanfold was published in August 2026. Google’s stated rule is that a new developer becomes trusted after a few months of following the Chrome Web Store policies, and there is nothing a developer can do to speed it up.
It is not a finding about Fanfold’s code, and nothing was flagged in it. Google says roughly a quarter of extensions in the store carry the same notice.
You will only see it if you have turned Chrome’s Enhanced protection on. Standard protection, which is what Chrome uses unless you changed it, does not show it.
Same address, for anything that is not a capture going wrong.
Answer you, and fix what you reported. Nothing else. The privacy policy says it in full.