Manage Npm

How to cancel your npm subscription and protect your digital assets in singapore

Understanding npm and why you might want to cancel

npm (Node Package Manager) is a package registry and toolchain that developers use to share, install, and manage JavaScript libraries and dependencies. If you have a paid subscription with npm, you've likely signed up for private package hosting, team-based permissions, or enhanced organisational controls.

Whether you're consolidating tools, switching to an alternative package manager, or simply cutting back on subscription costs, cancelling your npm account requires clarity and care. You need to know exactly what happens to your packages, when your access ends, and whether you're eligible for a refund under Singapore consumer law.

At Stopee, we've helped thousands of developers navigate subscription cancellations safely. This guide walks you through every step, from understanding your options to protecting your data after you cancel.

Common reasons to cancel npm

You might cancel if you no longer need private package hosting, your team has migrated to a different package registry, your project is no longer active, or you've found a more cost-effective alternative. Budget constraints, changing development priorities, and tool consolidation are all legitimate reasons to reassess your subscription.

What you need to know before you cancel

Once you cancel, your paid features stop immediately or at the end of your current billing cycle, depending on the cancellation method. Private packages may become inaccessible unless you migrate them or re-subscribe. Public packages and your account profile typically remain active, but you lose team permissions and organisational controls tied to your paid plan.

Your consumer rights in singapore and when they protect you

Singapore's Consumer Protection (Fair Trading) Act (CPFTA) gives you rights when you purchase digital services, including software subscriptions. Understanding these rights is critical when you cancel, especially if you're seeking a refund or disputing unexpected charges.

Protection under the consumer protection (Fair trading) act

The CPFTA protects you from unfair contract terms, misleading representations, and unacceptable conduct by suppliers. If npm fails to clearly disclose its cancellation policy, refund terms, or what happens to your private packages after cancellation, you may have grounds to dispute charges or demand remedies.

Key protections include:

• Transparency: npm must clearly state cancellation terms, refund policies, and data retention practices.
• Fair dealing: npm cannot impose unreasonably harsh penalties for cancelling within a reasonable timeframe.
• Remedies: If npm breaches the CPFTA, you can pursue refunds, damages, or cancellation without penalty through the tribunal.

When to escalate to consumer authorities

If npm refuses to cancel your subscription, withholds a refund you believe you're entitled to, or fails to respond to your cancellation request within 14 days, you can escalate to the Consumers Association of Singapore (CASE) or file a claim with the Small Claims Tribunal. Document all communication with npm, including cancellation requests, support responses, and billing evidence.

Cancellation methods for npm: which one applies to you

Your cancellation method depends on where you purchased your npm subscription. You may have signed up directly via npmjs.com, through the Apple App Store, or via Google Play Store. Each platform has different cancellation processes and refund policies.

Cancel via the npm web platform (npmjs.com)

If you subscribed directly through npmjs.com using a credit card or payment method, you cancel via your account dashboard. This is the most straightforward method and gives you the greatest control over your data and packages.

1. Visit npmjs.com and sign into your account using your username and password.
   • If you've forgotten your password, click "Forgot password" and follow the email reset link.
2. Navigate to your profile by clicking your avatar or username in the top right corner.
   • Select "Account" or "Settings" from the dropdown menu.
3. Click on the "Billing" or "Subscriptions" tab within your account settings.
   • This section displays your active plan, billing cycle, and payment method.
4. Locate your active subscription and click "Manage subscription" or "View plan details".
   • You should see options to upgrade, downgrade, or cancel.
5. Click "Cancel subscription" and confirm your decision.
   • Warning: npm may offer a discount to retain you. Decide whether to stay or confirm cancellation.
   • Take a screenshot of the confirmation page for your records.
6. Verify the cancellation by checking your email for a confirmation message from npm.
   • If you don't receive confirmation within 24 hours, contact npm support immediately.

Pro tip: Before cancelling, export a list of your private packages or migrate them to another registry. Once your paid plan expires, you may lose access to private packages without warning.

Cancel via apple app store (iPhone and iPad)

If you subscribed to npm through the Apple App Store, you must cancel through your iPhone, iPad, or Mac settings, not through the npm app itself. Apple handles all subscription management for App Store purchases.

1. Open the Settings app on your iPhone or iPad.
   • On Mac, open System Preferences and select "Apple ID".
2. Tap your name at the top of the Settings menu to access your Apple ID profile.
   • If you see "iCloud" instead, tap that first, then select your Apple ID.
3. Select "Subscriptions" from the list of options.
   • You'll see all active subscriptions linked to your Apple ID.
4. Find the npm subscription in the list and tap on it.
   • If npm doesn't appear, your subscription may have already expired or been cancelled.
5. Tap "Cancel subscription" at the bottom of the screen.
   • Apple will ask for confirmation and may offer a discount to keep you subscribed.
6. Confirm the cancellation and note the effective end date.
   • You'll typically have access until the end of your current billing cycle.
   • Check your email for an Apple confirmation receipt.

Warning: You cannot cancel App Store subscriptions through npm's website or customer support. Apple exclusively controls App Store subscription management. If you experience issues, contact Apple Support directly.

Cancel via google play store (Android)

If you subscribed through Google Play Store on your Android device, Google handles your subscription. You cancel through the Play Store app or via your Google account online.

1. Open the Google Play Store app on your Android device.
   • Alternatively, visit play.google.com on a web browser and sign in with your Google account.
2. Tap your profile icon in the top right corner.
   • Select "Payments and subscriptions" from the menu.
3. Select "Subscriptions" to view all active subscriptions.
   • You'll see each subscription with its billing frequency and next charge date.
4. Tap the npm subscription you wish to cancel.
   • Review the subscription details and features you're about to lose.
5. Tap "Cancel subscription" at the bottom of the subscription details page.
   • Google may display a retention offer or discount.
6. Confirm your cancellation and note the end date of your access.
   • You'll receive a cancellation confirmation email from Google Play.

Pro tip: If you're using multiple Android devices or Google accounts, check all of them to ensure you've cancelled every npm subscription linked to your accounts.

Timeline and what happens to your access after cancellation

Understanding what happens after you hit cancel is crucial so you're not caught off guard by sudden access loss or unexpected charges.

Access and billing after cancellation

For direct web subscriptions (npmjs.com), you typically retain access to all paid features until the end of your current billing cycle. If you cancel on day 5 of a 30-day cycle, you keep access for another 25 days. No refund is issued for the unused portion, although this may be negotiable if you contact npm within 48 hours of cancellation.

For App Store and Google Play subscriptions, access may end immediately or at the cycle end, depending on Apple and Google's policies at the time of cancellation. Check your confirmation email for the exact end date.

Your private packages and team data

Once your paid plan expires, private packages typically become inaccessible. You lose the ability to publish, update, or download private packages unless you migrate them to another account or registry before your plan ends.

Team permissions and organisational features are disabled immediately upon plan expiration. Team members lose access to shared repositories and collaborative tools. If your team depends on npm for private packages, notify all members before your cancellation takes effect so they can prepare alternatives.

Public packages and your account profile

Public packages you've published remain on the npm registry indefinitely. Your author profile stays active, and other developers can continue to install your packages. You simply lose the ability to publish new versions, manage team access, or use advanced security features tied to your paid plan.

Refund eligibility: what npm will and won't pay back

The refund landscape for npm is complex because it depends on where you purchased, how long you've been subscribed, and whether npm explicitly breaks its own terms.

Web subscription refunds (npmjs.com)

npm does not advertise a standard refund policy for direct web purchases. Most mid-cycle cancellations result in access until the billing period ends, with no partial refund for unused time. However, this isn't universal.

If you cancel within 14 days of your first charge and have not materially used the service, you may have grounds to request a refund under the CPFTA's consumer protection provisions. Stopee recommends contacting npm support immediately after cancelling and explicitly requesting a refund with a brief explanation (e.g., "I subscribed in error" or "The service doesn't meet my needs").

Document npm's response. If npm refuses without explaining why, escalate to CASE or the Small Claims Tribunal. You have a strong case if npm's cancellation policy is unclear or if the company failed to disclose refund terms before you purchased.

App store refund policies

Apple App Store purchases are subject to Apple's refund policy, not npm's. Apple typically allows refunds within 14 days of purchase if you request them directly through the App Store. After 14 days, refunds are at Apple's discretion and are rarely granted for subscription access already used.

To request an App Store refund, open Settings > [Your Name] > iTunes & App Store > [Your Apple ID] > View Apple ID > Purchase History. Find the npm charge, tap "Problem?" and select "I'd like a refund" with your reason. Apple usually responds within 48 hours.

Google play refund policies

Google Play allows refunds within 48 hours of initial purchase. If you cancel a subscription and request a refund within this window, Google typically honours it. After 48 hours, refunds are unlikely unless the app was fraudulently charged or you can prove npm failed to deliver the promised service.

To request a Google Play refund, visit play.google.com, go to your order history, find the npm charge, and click "Report a problem". Explain your reason and submit. Google reviews the request within 24-48 hours.

Exceptional cases and escalation

If npm charged you twice, you were charged after your cancellation, or the company failed to process a cancellation you requested, contact npm support with proof of the error. Stopee has seen npm grant goodwill refunds or credits in cases of clear billing mistakes.

If npm doesn't respond or denies your refund claim unfairly, file a dispute with your credit card issuer or bank. Most card companies will reverse charges if you provide evidence of a billing error or failed service. Additionally, you can lodge a formal complaint with CASE, which has statutory power to investigate and mediate disputes with service providers.

Npm pricing and plan comparison

Before you cancel, review what you're paying for and whether a lower-tier plan might be more suitable than cancellation.

Current npm subscription plans and pricing

Prices are in USD and converted to SGD at approximate current exchange rates. Your actual SGD charge may vary based on your card issuer's conversion rate and whether npm applies local taxes.

Pro tip: If you're cancelling because the Pro plan seems expensive, try the Free plan first. You lose private packages, but public packages are unlimited. If your team needs collaboration tools, negotiate a group discount or explore alternatives like GitLab Container Registry or GitHub Packages, which often offer free or cheaper private hosting.

Common mistakes to avoid when cancelling npm

Cancelling a subscription sounds simple, but small errors can leave you without access to your packages, unable to recover your data, or fighting unexpected charges weeks later.

Mistake 1: cancelling without exporting your private packages

Once your paid plan expires, you lose access to private packages. If you haven't migrated them to another registry or backed them up, they may be unrecoverable. Before cancelling, export your package list, document dependencies, and move packages to a free registry like GitHub Packages or Artifactory.

Mistake 2: cancelling the wrong subscription

If you have multiple npm accounts or subscriptions across different platforms (web, App Store, Google Play), you might cancel one and not realise another is still active. Check all your email accounts, payment methods, and device subscriptions before assuming you've fully cancelled.

Mistake 3: not waiting for confirmation

Cancelling on the website doesn't mean it's processed immediately. Wait for an email confirmation from npm (or Apple/Google if using app stores) before assuming the cancellation is complete. If you don't receive confirmation within 24 hours, contact support.

Mistake 4: failing to notify your team

If your npm subscription is shared with team members, they'll lose access to private packages and team features once your plan expires. Notify them at least one week in advance so they can migrate to an alternative registry or prepare for the transition.

Mistake 5: not requesting a refund in writing

If you believe you're entitled to a refund, don't assume npm will offer one voluntarily. Send a formal written request via email to npm support (support@npmjs.com) within 14 days of cancellation, clearly stating your reason and referencing the CPFTA if applicable. Keep the email for evidence in case you escalate to CASE or the tribunal.

Checklist before you cancel your npm subscription

Use this checklist to ensure you've completed all necessary steps before hitting the cancel button.

• I have exported or migrated all private packages to another registry or account.
• I have notified all team members who depend on npm that my subscription is ending.
• I have confirmed my cancellation method (web, App Store, or Google Play).
• I have checked my current billing date and understand when my access will end.
• I have screenshotted my subscription details for records.
• I have confirmed I have no outstanding invoices or unresolved billing issues.
• I have attempted to cancel and received a confirmation email.
• If eligible, I have requested a refund in writing within 14 days.
• I have documented all communication with npm for potential disputes.
• I have checked my credit card statement for any unexpected charges after cancellation.

Alternatives to cancellation: downgrade or pause options

Before you cancel entirely, consider whether downgrading or pausing your npm subscription might be a better fit for your current needs.

Downgrading from pro or teams to free

If you no longer need private packages but want to keep your account active, downgrade to the Free plan instead of cancelling. This preserves your public packages, author profile, and npm history without any ongoing cost. You can always upgrade again if your needs change.

Taking a break from npm

Some developers pause subscriptions during quiet project periods rather than cancel. Contact npm support to ask whether a temporary suspension is possible. While npm doesn't officially advertise a pause feature, support may be willing to accommodate short-term breaks, especially for long-term customers.

What to do if npm refuses to cancel your subscription

In rare cases, npm may fail to process your cancellation request, claim your request was never received, or charge you after you've cancelled. Here's how to escalate.

Step 1: request cancellation in writing

If npm has ignored your cancellation request, send a formal email to npm support with the subject line "Cancellation Request: [Your npm Username]". Include your account details, the date you requested cancellation, and a clear statement that you want your subscription terminated immediately. Request a response within 5 business days.

Step 2: escalate to npm's billing team

If support doesn't respond, reply-all to the support email thread and escalate to npm's billing or account management team. Reference the CPFTA and your right to cancel. Emphasise that failure to cancel may constitute a breach of fair trading laws.

Step 3: dispute the charge with your card issuer

If npm continues to charge after you've requested cancellation, contact your credit card issuer and file a chargeback or dispute. Provide evidence of your cancellation requests and npm's refusal to comply. Most card companies will reverse unauthorised charges within 10 business days.

Step 4: lodge a complaint with CASE

If npm ignores your cancellation request and your card issuer refuses to help, file a formal complaint with the Consumers Association of Singapore (CASE). CASE can investigate npm's practices, mediate disputes, and recommend remedies including refunds and penalty payments. Visit case.org.sg or call 6100 0315 to file a complaint.

Stopee's final guidance: protecting yourself after cancellation

After you've successfully cancelled, your responsibilities don't end. Protecting your digital assets and ensuring no surprise charges occur requires ongoing vigilance.

Monitor your billing statements

For at least three billing cycles after cancellation, check your credit card or bank statements for npm charges. If charges appear, immediately dispute them with your card issuer and contact npm to demand a refund. Most billing errors occur within 30 days of cancellation, so vigilance during this period is critical.

Confirm access loss

Log into your npm account on the date your access should end and verify that private packages are no longer visible and paid features are disabled. If you still have access after the billing cycle ends, contact npm immediately. Continuing to charge for a service you can no longer use is a breach of consumer protection law.

Retrieve final documentation

Before your access expires, download or screenshot any npm documentation, receipts, or account records you may need for tax, compliance, or archival purposes. Some records may become unavailable after cancellation.

Notify dependents

If other developers or teams installed packages from your npm account, consider notifying them that you're cancelling your paid plan. If your private packages are being removed, they need time to migrate or find alternatives.

Getting help: when to contact support and how to escalate

Stopee has helped thousands of consumers cancel services and fight unfair billing practices. If you encounter difficulties with npm, here's the support hierarchy.

Npm customer support (first contact)

Email npm support at support@npmjs.com with your account details, issue description, and what you've already tried. Expect a response within 24-48 hours. Be polite but firm, and avoid threatening language. Keep all correspondence for potential escalation.

Consumers association of singapore (CASE)

If npm fails to respond or denies your request unfairly, file a complaint with CASE. They investigate service provider conduct and have power to order refunds, compensation, and changes to unfair practices. Visit case.org.sg or call 6100 0315.

Small claims tribunal

For disputes under SGD 5,000, you can file a claim with the Small Claims Tribunal. This is faster and cheaper than civil court. You'll need evidence of your cancellation request, npm's refusal, and the financial loss you've suffered. Stopee recommends consulting a community legal clinic before filing.

At Stopee, we've guided thousands of developers and organisations through npm cancellations safely and successfully. Whether you're downgrading, switching registries, or taking a break, our experts understand the process, the pitfalls, and your rights under Singapore law. Visit Stopee to explore guides for cancelling other subscriptions and protecting your digital assets. Your data, your packages, and your financial security matter to us.