MJ
Dishonest and deceitful company
Other unfortunate patrons of Music Bed have listed off the most glaring and apparently common issues with this surprisingly deceptive and dishonest company (the copyright claims, the pricing, etc) but the issue that I haven't seen written out yet is the cancellation process. Simply put, you can't just go in and cancel renewal. Instead, there is a one month window out of the year where you are allowed to cancel. If you miss that window then you are forced to pay the monthly fee again that you originally agreed to for the next year. So let's say you forget to cancel because it's been close to a year since you subscribed: tough luck. You have to pay it again. If you remember to cancel in the middle of the year you can't go in and simply cancel renewal. You have to wait for the "renewal period". This is what happened to me last year and I've been paying $15 a month for a service that I don't use for a number of reasons (poor music, copyright issues, etc.) but have had no choice to pay for it anyway. Avoid music bed like the plague. There are plenty of other services to choose from.
Response from MusicbedOct 3, 2023
Hey MJ, so sorry about this poor experience. I'm sorry that you were having copyright claims. That's never fun. We do everything we can to help our subscribers steer clear of claims, but we obviously didn't do a great job for you. We are constantly working on our claims system integration with YouTube, so I'd love for you to give us another shot. I'd love to get a discount setup for you to use if you'd be willing to give us another try. If you can get me the email address you use on our site, I can get that discount applied. The main goal of setting a renewal window was to help users avoid situations where they shut it off at the beginning, forget they did that, and one day log on to finish a Project only to find that their Subscription auto-canceled because the auto-renewal had been shut off 11 months prior. We were seeing this pattern and wanted to help users avoid it, but in situations like yours, it's definitely not helping. Our team is re-evaluation this implementation now. Thanks for the feedback!




