We're committed to building the best software for WordPress and we stand by our work. The following policy outlines what is required to qualify for a refund. Note that all of the Products that we build are delivered as open-source digital items (i.e., irrevocable). For this reason, refunds are granted at our sole discretion.
Qualifying for a Refund Within 30 Days
If you're having trouble, we ask that you work with and follow all advice presented by our support team in an effort to resolve the issue (e.g., attempting to reproduce problems in a clean installation of WordPress). If problems still exist, even when testing in a clean installation of WordPress, we will gladly refund your money within 30 days from the date of purchase.
Refund requests may take up to 14 days to process. Refunds are not guaranteed. All refunds will be granted at the sole discretion of WP Sharks. Absolutely no refunds will be given after 30 days from the original purchase. Please note that by purchasing a Product from WP Sharks, you agree to the terms & conditions of use, including this refund policy. While it is not possible for us to revoke access to open-source software once you have been given download access, when we issue a refund, your account will be downgraded and your license key (which provides access to future releases of the software) will be revoked.
Testing in a Clean Installation (Required): WordPress offers you lots of options! As a site owner you have the ability to mix our Products with other plugins and a theme you like best. This means your environment will be slightly different than ours. Your WordPress installation has different plugins, it has had a different history, and it's probably running with a different theme too. As you can imagine, testing every feature in each of our Products with every possible combination of plugins, and with each and every theme and server configuration that exists for WordPress, is simply not realistic. We need common ground! In fact, our policy is that we require it. Before any refund is granted we ask that you attempt to reproduce the issue in a clean installation of WordPress.