Cancellation and refunds

Check before you pay

The free tier downloads 5 single lessons a week with no signup and no card. That is enough to confirm the extension reads your course, resolves your lesson type, and produces a file that plays. If it does not work on your course, you will find out before any money changes hands.

Please do run it before you buy. The refund window below is short precisely because the free tier answers the question first — on your own course, at no cost, in a couple of minutes.

Cancelling a monthly subscription

Use the customer portal linked from your purchase receipt. The portal shows whether cancellation takes effect immediately or at the next billing date before you confirm it. If you cannot find it, email support and we will cancel it for you — you do not need to give a reason. Your downloaded files are unaffected either way, because they are already on your disk.

Refunds

You can ask for a full refund within 24 hours of your purchase, as long as you have not already used it to download at scale. Concretely, that means before you have finished a whole-course export and before you have saved more than five lessons in total. Once either of those is passed, or once 24 hours have gone by, refunds are at our discretion. The list further down is refunded whenever it happens.

The reason for the second condition: the files this tool produces are yours the moment they land on your disk, and a refund does not take them back. Refunding a finished course export is not a refund, it is a free copy. The free tier exists so you can answer the "does it work on my course" question without paying, which is why the paid window is narrow.

Payments are handled by a merchant of record, who is the seller of record for your purchase and appears on your statement. Their own refund terms, and any rights your local consumer law gives you, apply in addition to this page — nothing here reduces them.

If the extension does not do what this site says it does, ask for a refund and you will get one. A claim of that kind has to come with the evidence listed under How to ask below — at minimum a screenshot of what the extension actually showed you. We cannot verify a failure we cannot see, and a request that does not include it will be declined. This specifically covers:

• It cannot read your course at all.
• Exports fail or produce unplayable files, and we cannot fix it for you.
• You were charged twice, or charged after cancelling.

Refunds are not intended to cover the cases we told you about before you paid:

• Your course is mostly YouTube lessons. Which sources are downloadable is stated on thehome page and inside the extension before a run starts, with counts.
• The lessons you wanted are locked, unpaid, or not yet released to your account.
• You already downloaded what you came for. A completed course export, or more than five saved lessons, ends the refund window regardless of how recent the purchase is.
• Repeated buy-then-refund cycles on the same account, email or payment method. We will refund once and decline to sell again rather than keep the loop running.
• The lessons you wanted have no video on them. Plenty of courses are written lessons, and a lesson with no video produces written notes instead. The extension counts what it found — including Videos: 0 — on screen before a download starts.
• The video is DRM protected.

In those cases the extension is doing exactly what it says. Ask anyway if you think the limitation was not clear enough before you bought, because that is a problem with our page.

How to ask

Email shraey.sbdownloader@gmail.com from the address you paid with. You do not need to justify a cancellation — but a refund for something that did not work needs enough detail for us to check it.

A refund claimed on the grounds that something failed requires evidence, and will be declined without it. Attach all three:

• A screenshot of what the extension showed you. The message, the error, or the summary screen — whatever you saw when it went wrong. Nearly every report comes down to a specific line of text, and without it we are guessing.
• The manifest.json from the download folder. Every completed run writes one next to COURSE.md. It records what was found, what was saved, what was skipped and why. It contains no passwords, no login details and no video files — only the outcome of your run.
• The classroom URL you were downloading from.

If the run never got far enough to write a manifest.json, say so and send the screenshot on its own — that file only exists once a run finishes, and we are not going to ask you for something that cannot exist. The screenshot is the part we cannot proceed without.

To be direct about why: a report that describes the problem only in general terms cannot be checked, cannot be fixed, and cannot be told apart from a request for a free copy. Nearly every real fault comes down to one specific line of text on screen. If you no longer have it, reproduce the failure once and photograph it — that is genuinely all we need.

None of this applies to a plain cancellation, or to a request made inside the window at the top of this page. Those need no justification at all.