Thank you for your comment. To be perfectly honest, this is the first request of this kind that I have received.
I will look into writing a formal refunds policy, but for now I will explain my position on the matter here. It makes sense for me to follow the example of other developers who write self-hosted software of this sort, such as Shaun Inman's refund policy for Mint.
--------------------------------
Circumstances under which I can grant a refund
simpleContact Pro is a digital product. Its code is readable PHP and it cannot effectively be "returned". The only situation under which I can grant a refund is if a web server fulfills my stated minimum requirements but simpleContact Pro still does not work (and cannot be made to work through support).
A refund cannot be granted in the event that someone buys it and doesn't like it or chooses not to use it for any reason.
--------------------------------
Regarding feature requests
It is inevitable with any piece of software that it cannot satisfy 100% of all possible user's needs. I would not want anyone to feel their money was wasted and will answer any question prior to purchase. This extends to recommending other products if I believe them to be more suitable.
Feature requests are a crucial part of software development. I receive them gratefully and they help to guide future improvements to the product. However, not all requests are equal. Some may be useful to many users, some to very few. I will not consider the absence of a particular feature to be a "fault" in the product. In many cases that absence may be by deliberate design.
The product is provided "as-is." It is the potential customer's right and responsibility to decide whether it is suitable based on their own requirements and the stated feature-set. The features that you mention are not claimed to be present in simpleContact Pro 2.0.
If I offered a refund in this situation it would set a precedent where any conceivable feature request could arrive with a refund demand and I would soon be making a financial loss on the project. As a developer and businessman I cannot allow this.
--------------------------------
I try to be accommodating where ever I can. I have written several "hacks" to provide functionality that is not present in the current general release. I can make some suggestions for your particular points:
Printable form data
In response to user requests I have been beta testing a CSV export script for the inbox in preparation for version 2.01. I can make this available to you if you wish. I would suggest that this feature could be used in performing a data merge in Word to create a printable document of any layout you wish.
HTML-formatted email
I have written a hack to allow a HTML-formatted autoresponder. It may be that this hack (or some variation of it) will satisfy your needs. I am happy to discuss this with you.