Refund Renewal Subscrition

I was just recently charged for my "renewal" subscription.

I was unaware that in order to cancel the subscription, the system only allows you this fucitionality 30 days prior to the renewal. This was told to me after the fact by customer service. As well, after researching the "fine print" was found on page 3, section A, subsection ii. Which I think most people will agree as burried in the fine print.

I did not see, received or read the "WARNING" email that I my subscriton was up for the year and it was set to auto-renew. Something Musicbed does automatically... setting subscriptions up for autorenewal.

I did try and cancel my subscription which the system does not allow you to do, unless your within your 30 day countdown.

I also couldn't remove my CC on file. So without knowing, my subscription was renewed and additional $989.89 was charged which I didn't want to do.

I called Musicbed the next day to get a refund. But according the the policy, again found on page 3, section A, subsection ii... isn't something that Musicbed offeres.

I appreciate the excellent customer service provided by Jeremy and Grant in listening to this problem. After a few phone calls and quick responses, Musicbed did refund the money charged a day prior and resolved the issue.

At a minimum, if you:
1 - Automatically rewnew subscriptions.
2 - Only allow the system to cancel auto rewnewals 30 days prior
3 - Do not allow removal of payment methods.

You should allow a "refund period" after renewal payment are made and the system has not been used to download any music. This would allow users to cancel subscriptions that they did not intentional renew. Especially if they are not using the system and not aware of the fine print policy. Or havne't read/received the 30 day countdown email.

I personally found out becuase I was notified my CC was charged for another year. Which kicked off this issue for me.

Again... thank you for your excellent customer service in cancelling my subscription renewal outside your currently policy to not do so.