nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't cancel glitched free Loom subscription as I'm stuck in a loop

Jane Michael

I signed up for 14 free days of Loom, as I needed to access a video, but it glitched and I was never able to access it (it wouldn't even let me select Loom as my app when entering this question!), and now I keep getting emails asking for my bank details. I've tried to go in and delete my account, but it says I have an outstanding invoice, even though I never agreed to subscribe in the first place. I received advice that I should lodge a billing support ticket, but when I try the link it sends me around in the same loop again and I don't see what I'm told I should see. I need to sort this today as it's my only day off

Accepted answers

Tomislav Tobijas

Hi @Jane Michael ,

You should be able to sort this out by reaching out to support team here: Atlassian Support: Pricing, Billing & Licensing

I believe you can select the following to request the cancellation of the Loom subscription.

Cheers,
Tobi

All comments

Tomislav Tobijas

Hi @Jane Michael ,

You should be able to sort this out by reaching out to support team here: Atlassian Support: Pricing, Billing & Licensing

I believe you can select the following to request the cancellation of the Loom subscription.

Cheers,
Tobi

Korea_c67l7f

In the meantime, just go into your banking app and freeze that card or set the online limit to zero. It takes two seconds and gives you peace of mind so you don't have to keep checking your phone for charge alerts.

You’ve done your bit. Send the email, lock the card, and go enjoy your Sunday

Jane Michael

Thanks for you help Tobi, I was eventually able to lodge a query that was slightly different as the link seemed to send me somewhere different (maybe because the initial subscription glitched?), but I got there in the end and sent a query and Andra from Atlassian replied and has sorted the issue