Get in touch
One person builds and maintains this extension, and there is no support desk behind it. That is worth knowing before you write, because it sets what you can expect back.
Worth sending: a bug with the steps that produce it, a configuration that will not match a host you think it should, something the documentation does not answer, or a feature you would use.
Worth checking first: the FAQ covers the questions an AEM lead usually asks, and the configuration reference covers what each part of the YAML does.
What happens next
Section titled “What happens next”The message goes to the form handling built into this site’s host, which forwards it to an address held there. That address is not published on this page, which is why there is a form here rather than a link that opens your mail client.
If you leave an email address, it comes through with the message and may get a reply. It may not. There is no timeframe, no ticket, and nothing to chase, so please do not sit waiting on one. A bug report with clear steps is the kind most likely to get an answer, because it is the kind that can be acted on.
Do not put anything confidential in the box. No credentials, no internal instance URLs you would not paste into a public issue, no unpublished page content. Treat it as a message to a stranger on the internet, because that is what it is.
The submission is stored by the host along with what any web host records about a request. That is separate from the extension itself, which collects nothing and makes no request of any kind to its author. It talks to your own AEM instances, and your own configuration URL if you set one up, and to nothing else: no third party, no vendor, no analytics. The privacy policy covers the extension.