How to cancel Webroot and request a refund

Choose the action you actually want

Turn off auto-renewal when the goal is preventing the next charge while using the remaining paid term. Webroot says SecureAnywhere features continue until expiration after opt-out. This is the safest default when another antivirus isn't ready yet.

Disable the active subscription when access must end before expiration. Webroot's current cancellation article treats that as a support-ticket request containing the account email and attached keycode. It isn't the same button as renewal opt-out.

Request a refund when a charge qualifies under the applicable consumer guarantee or seller policy. A refund can alter access and billing, but submitting a form isn't approval. Keep protection installed until the outcome and replacement plan are clear.

Find the billing party before following any cancellation guide

The seller that collected the payment controls the billing record. Check the emailed receipt, card descriptor, app-store subscription page and Webroot account rather than guessing from the installed logo. A keycode proves a product entitlement; it doesn't prove Webroot directly processed the card.

Don't submit the same refund to several parties simultaneously. That can create duplicate records and contradictory status. Start with the billing owner, then preserve any referral showing that another party must act.

Save the receipt, dates and protection plan before cancelling

Record the product, keycode with most characters masked, account email, expiration date, renewal charge date, seller, invoice number and exact total. Webroot's current SecureAnywhere guidance says notices arrive 30 and 14 days before expiration and the card is charged seven days before expiration. The actual account and emails remain the authoritative dates for this purchase.

Decide what protects the devices after Webroot ends. Turning off renewal normally leaves time to install and test a replacement; immediate disablement or refund can shorten that runway. Export any non-antivirus data or settings that depend on the bundle before access changes.

Create a dated folder for the receipt, opt-out completion screen, confirmation email and later account state. This is ordinary billing hygiene, not an accusation. It prevents a support conversation from depending on memory and lets the cardholder distinguish a delayed confirmation from an unrelated subscription.

Check whether several Webroot-related products renew independently. A household may have SecureAnywhere, a VPN, an app-store trial and a retailer-managed keycode under different emails. Cancelling one entry doesn't establish that the others share its billing status, even when they appear together on the same devices.

Turn off Webroot SecureAnywhere auto-renewal in six steps

Use this workflow for standalone SecureAnywhere controlled by Webroot or the shared Webroot/Carbonite account. Webroot's official opt-out instructions route from Subscriptions and Options to the separate keycode form.

1. Identify the Webroot subscription and billing party

   Record the exact product, keycode, expiration date and seller shown on the receipt or card statement. Use this direct Webroot path only when Webroot or the shared Webroot/Carbonite account controls renewal.

2. Open Subscriptions in the current account

   Sign in through the verified Webroot account route, open Subscriptions and choose Options in the Manage column for the SecureAnywhere subscription.

3. Copy the correct SecureAnywhere keycode

   Copy the 20-character keycode attached to the subscription being cancelled. Mask it in screenshots and don't paste it into a search result, chat advertisement or unofficial support form.

4. Submit the official auto-renewal opt-out form

   Open Webroot's official auto-renewal opt-out page, enter the keycode, select the statement requesting removal of auto-renewal and submit the request.

5. Save the request and confirmation

   Capture the dated completion state and retain the confirmation email with the receipt. Webroot's current form copies say confirmation can take 24 to 48 hours, so don't treat the first click as the only evidence.

6. Verify renewal is off without uninstalling early

   Recheck the subscription or confirmation before the renewal charge date. Keep Webroot installed until the paid expiration date unless immediate deactivation or replacement protection is intentional.

Don't mistake a retention offer for the final opt-out. Read the last state and wait for confirmation. Localized versions of Webroot's current form say confirmation can take 24–48 hours, so submit early enough to verify it before the documented renewal charge date.

Request immediate subscription disablement separately

Webroot tells SecureAnywhere customers who want the subscription disabled—not merely set to expire—to submit an official support ticket and include the account email and keycode attached to the subscription. Use the protected ticket form reached from Webroot support; never post those credentials in a public forum.

State the requested outcome precisely: disable now, stop auto-renewal, close an account, or refund a named invoice. Ask what happens to the paid term and bundled services, then save the response. A ticket saying “cancel” without defining the outcome can be interpreted differently by the cardholder and support agent.

Immediate deactivation can remove the security layer before a replacement is ready. Install and test alternative protection first when the device isn't being retired. If Webroot is being removed because it malfunctioned, our separate uninstall and troubleshooting spokes own the technical cleanup.

Request a qualifying Webroot consumer refund

Webroot currently advertises a 70-day money-back guarantee for consumer products under the applicable license agreement. The Webroot-direct online form asks for the invoice number and exact total from the emailed receipt. Its current instructions describe a 10- or 11-character invoice code beginning with WIN, E, C or R.

Enter the values exactly as issued and submit once. Save the completion state and any case identifier. A guarantee describes the published eligibility window; it doesn't mean every seller, business contract, monthly app-store charge or request filed after the window uses the same Webroot form.

Webroot says requests after 70 days generally have automatic renewal disabled while the user keeps the remainder of the subscription rather than receiving a consumer refund. If an unopened retail package is still returnable, the refund page calls returning it to the store the fastest route. Opened retail products need the documented seller/Webroot process and proof of purchase.

The 70 days run from the purchase associated with the requested refund, not from the day the user noticed the software or decided to cancel. For a renewal charge, use that renewal invoice and date. For an original purchase, use the original invoice; mixing them can make an otherwise clear request look outside the window.

Best Buy and Geek Squad manage their Webroot billing separately

Webroot's refund page explicitly says Best Buy, Geek Squad and certain Total Tech Support Webroot accounts are independently managed; Webroot can't process their account updates, upgrades or refunds. Use the Best Buy signed-in purchase history or digital library and the receipt rather than the standalone Webroot invoice form.

The card statement can help identify this channel even when the software was installed by someone else. Preserve the Best Buy order, Webroot keycode and cancellation result together. Don't paste the keycode into a search page advertising a “Webroot Best Buy support” number.

For another retailer, read that seller's return and renewal terms. An unopened box, emailed code and automatically renewed service can have different procedures even though all activate Webroot. The billing source, not the desktop icon, decides the first contact.

Cancel Apple, Google Play and older VPN subscriptions in the store

Webroot's WiFi Security cancellation guide states that the subscription or trial must be cancelled through the platform where it was purchased: Apple, Google Play or Webroot.com. Deleting the application doesn't cancel and charging continues until the billing subscription is stopped.

For Apple, use the official subscription-management steps; for Android, use Google Play subscriptions. Confirm the status and end date inside the store account that made the purchase. Webroot can't override a store refund decision merely because its name appears in the app.

Old WiFi Security terms distinguish monthly and annual purchases, but don't project those details onto every current Webroot bundle. Apply the policy attached to the actual store order. Trials must also be stopped in the store before their conversion deadline.

Handle a Webroot add-on inside Carbonite as a bundle

When SecureAnywhere is an add-on to Carbonite Safe, Webroot directs the user to the shared account, Subscriptions, Options and Turn OFF Auto-Renewal. That differs from copying a standalone keycode into the external Webroot opt-out form. Confirm whether the control changes only the Webroot add-on or the broader Carbonite plan.

Save the bundle receipt and current component status. A package can contain backup and antivirus with related billing but different operational consequences. Don't cancel the backup plan accidentally while trying to stop an antivirus renewal, and don't assume removing antivirus also stops cloud-backup charges.

If the account presentation is ambiguous, submit an official ticket naming the subscription and component. The page title, invoice and masked keycode provide enough context without exposing passwords or one-time codes.

Know what remains active after each outcome

After auto-renewal opt-out, Webroot says existing SecureAnywhere features continue until expiration. The endpoint should remain installed and updated during that paid period unless replacement protection is intentionally taking over. Put the expiration date on a calendar and test the successor before the handoff.

Use the pricing and renewal guide to reconcile the regular renewal amount, and the plan comparison to identify bundled services that may need export or replacement. If Webroot will remain on another device, follow the verified installation route rather than reusing an old download mirror.

Immediate disablement or an approved refund can end rights sooner. Antivirus, VPN, backup, password and identity services don't necessarily share the same data-retention or export behavior. Save needed data and recovery information before access changes; don't assume a refund form exports anything.

At expiration or termination, uninstall the old application after the replacement is active, remove unneeded browser extensions and review account devices. The separate account and device guide explains how portal removal differs from local uninstall.

Keep the cancellation record even after uninstalling. Software removal proves only that one endpoint stopped running the client; it doesn't prove a cloud subscription, mobile-store trial or reseller renewal ended. Conversely, an expired subscription can remain installed but no longer provide the same licensed services.

If Webroot already charged the renewal, use a dated decision tree

Match the card charge to the seller, invoice and subscription. A Webroot charge within the published consumer window belongs in the official refund form; a Best Buy charge belongs with Best Buy; Apple or Google charges belong in their store systems. Don't choose a path solely from the word Webroot in the descriptor.

Compare the charge date with the cancellation confirmation. Webroot says its SecureAnywhere renewal charge occurs seven days before expiration, so a request submitted after that charge needs a refund workflow as well as future opt-out. A request submitted before the charge but not confirmed needs the saved submission evidence.

If the billing owner denies or can't find the transaction, request a written explanation and preserve it. Then ask the card issuer about its dispute process for an unauthorized, duplicate or unresolved charge. Describe facts accurately; a merchant disagreement isn't automatically fraud, and a chargeback shouldn't replace the seller's valid refund route when that route is working.

Verify cancellation instead of trusting a closed browser tab

Look for a dated confirmation email and recheck the subscription state. Webroot's form copies say a request confirmation may take 24–48 hours. Check junk mail and the registered address, then use official support if that window passes without proof.

Keep monitoring the payment method around the former renewal date. That's especially important after an email change, account migration or reseller purchase where the installed keycode and billing profile can diverge. A screen saying “request received” and a message saying “auto-renewal disabled” are different evidence.

Retain confirmation until at least one renewal cycle passes and any refund posts. Recent community complaints about business billing support the value of written records, but they don't prove a consumer request will fail. Evidence is useful precisely because most clean cancellations are otherwise forgettable.

If a refund is approved, compare the posted amount with the exact invoice total and note any tax or currency difference before reopening the case. Processing time can depend on the payment rail, so distinguish an approved refund that hasn't yet settled from a request that hasn't been approved.

Avoid fake Webroot cancellation and refund support

Search results for this topic contain fabricated support numbers embedded in Reddit-profile posts, PDFs on unrelated domains and generic “helpline” pages. Don't call them, install remote-control software or reveal the keycode, account password, one-time phone code, card number or invoice to them.

Start from Webroot's official domain, the actual retailer account or the operating-system store. A legitimate cancellation route doesn't require buying another support plan to release auto-renewal. Verify the domain before entering a keycode because the opt-out form legitimately asks for it.

If credentials were shared with an unofficial operator, change the Webroot/account password, enable two-factor authentication, review devices and contact the card issuer using the number on the card. Don't continue negotiating through the search result that caused the exposure.

Official support may ask for the account email, masked product details and invoice evidence through a protected form. It shouldn't require gift cards, cryptocurrency or a second antivirus purchase as the price of cancelling an existing consumer renewal.