Yafee is an independent certified electronic mail service. We are neither affiliated with, nor partners of, nor mandated by Mongodb, whose name is mentioned solely to identify the recipient of your letter. The trademarks and logos cited belong to their respective owners.
Unlimited Yafee Premium: promotional offer at $1.85 for 48h, then $100.94 per month with no commitment
SLMDJTAC
Over 30,000 users trust us
Cancel your subscription
Mongodb in 2 minutes
A 100% personalised cancellation letter, legally compliant and sent by registered mail with acknowledgement of receipt.
GDPR compliant
Your data is secureFast & effective
Processed within 24hResults guaranteed
Refund if refused48h satisfaction-or-refund guarantee
1Letter type
2Your details
3Payment
100% secure payment
They already cancelled Mongodb
Join thousands of satisfied users
SLMDJTAC30K
over 30,000users trust us
How does it work?
Cancel your Mongodb subscription with zero hassle
1
Fill in the form
Give us your details and those of your Mongodb subscription.
2
We write your letter
Our team drafts a 100% personalised, legally compliant cancellation letter.
3
We send it for you
Sent by registered mail with acknowledgement to Mongodb. Nothing else for you to do.
Legal and compliant
Our letters follow consumer law and GDPR.
Fast
Your letter is sent within 24 business hours.
Real-time tracking
Follow your request from your personal space.
Results guaranteed
Full refund if Mongodb refuses your cancellation.
Frequently asked questions
Cancel MongoDB: The Right Way
How to cancel MongoDB and avoid ongoing charges in new zealand
Why you might want to cancel MongoDB
MongoDB is a cloud-native database platform that powers modern applications through managed clusters, serverless deployments, and enterprise support. The service operates through MongoDB Atlas, a web console where you configure and monitor your database infrastructure. While MongoDB delivers powerful functionality, its billing model often surprises users who fail to distinguish between support plan charges and active deployment costs.
You may be considering cancellation because your development project has concluded, unexpected costs have escalated, or you've migrated to a competing database solution. Whatever your circumstances, Yafee is here to guide you through the cancellation process with precision and legal clarity. We've assisted thousands of New Zealand consumers in navigating service terminations that companies intentionally obscure, and MongoDB represents no exception.
Common reasons to cancel
Terminate your MongoDB subscription or support plan if you no longer require database functionality, your free trial expires and you wish to avoid charges, or your organisation has transitioned to an alternative provider. Many users discover that cancelling their support plan does not automatically halt charges from running clusters. You must explicitly terminate your deployments to prevent continued billing-a critical distinction Yafee emphasises to protect your account balance.
What MongoDB charges you for
MongoDB imposes charges across three distinct areas: support plan subscriptions (optional), active database clusters, and serverless instances. The primary confusion arises because cancelling your support plan does not automatically shut down your running deployments. You must separately terminate each cluster and serverless component to cease all charges. At Yafee, we have documented this exact scenario repeatedly with users who believed they had cancelled everything but discovered persistent charges months later.
Your consumer rights in new zealand and what they mean
New Zealand's Consumer Guarantees Act (1993) establishes legal protections that apply even when you cancel digital services like MongoDB.
How the consumer guarantees act protects you
Under New Zealand law, all suppliers-including MongoDB-must deliver digital services with reasonable care and skill, within a reasonable timeframe, and fit for the purpose advertised. MongoDB's standard policy stating "no refunds after 14 days" does not override your statutory rights under the Consumer Guarantees Act. If MongoDB's service proved faulty, delivered misleading functionality, or failed to perform as described, you retain grounds to dispute their refund terms and pursue a claim under consumer law.
Furthermore, if MongoDB deliberately obscures the cancellation process, employs dark patterns to prevent account termination, or continues charging after you have attempted cancellation, these practices may violate the Fair Trading Act (2013). The Commerce Commission-New Zealand's consumer protection regulator-can investigate and enforce compliance if MongoDB refuses to cooperate with your cancellation request.
Your legal position
You hold the right to cancel at any time. New Zealand consumer law does not permit companies to impose unreasonable cancellation barriers or hidden charges. If MongoDB refuses to honour a legitimate refund request, continues billing after cancellation, or makes the termination process inaccessible, you can escalate to the Commerce Commission (comcom.govt.nz) at no cost. Document every cancellation step, including screenshots, email confirmations, and dates of your attempts. Yafee recommends retaining these records for at least 12 months following any dispute.
When you should contact the commerce commission
Reach out to comcom.govt.nz if MongoDB refuses to honour a legitimate refund request within 14 days, continues charging after you have cancelled, or deliberately makes cancellation inaccessible. The Commerce Commission investigates unfair trading practices and can compel MongoDB to refund charges or cease prohibited conduct. Provide copies of all correspondence, billing statements, and cancellation attempts to strengthen your case.
Methods to cancel MongoDB: step by step
MongoDB provides multiple cancellation pathways depending on how you purchased your plan, with distinct steps and outcomes for each route.
Cancelling via MongoDB atlas (the web console)
This represents the primary method if you subscribed directly through MongoDB's website and is the most common approach for New Zealand users.
- Log in to your MongoDB Atlas account
- Navigate to mongodb.com/cloud/atlas
- Enter the email address and password associated with your account
- Complete two-factor authentication if your account has this enabled
- Access the billing section of your account
- Click your account name or profile icon in the top right corner of the console
- Select "Billing" from the dropdown menu
- Review your active subscriptions and current charges
- Identify all active deployments and clusters
- Navigate to "Deployments" or "Clusters" within the Atlas console
- List every active cluster, serverless instance, or data lake currently running
- Note the resource type and monthly cost for each deployment
- Terminate each active deployment
- Select the first cluster or serverless instance from your deployment list
- Click the "Terminate" or "Delete" button (exact wording varies by resource type)
- MongoDB will ask you to confirm termination-this action is permanent
- Repeat this process for every active deployment until none remain
- Cancel your support plan (if purchased)
- Return to the Billing section and locate your support plan subscription
- Click "Cancel Plan" or "Downgrade" depending on your plan type
- MongoDB will confirm the cancellation and specify the final billing date
- Confirm cancellation in writing
- Take screenshots of the confirmation screen showing all deployments terminated
- Retain your cancellation confirmation email sent by MongoDB
- Save these documents for your records and potential disputes
Cancelling via credit card or payment method removal
If you wish to prevent MongoDB from charging your card in future, you can remove your payment method from your account.
- Log in to MongoDB Atlas and access your account settings
- Click your profile name in the top right corner
- Select "Account Settings" or "Payment Methods"
- Navigate to the Payment Methods section
- View all credit cards, bank accounts, or payment instruments linked to your account
- Identify the card or method currently used for billing
- Remove the payment method
- Click the delete or remove icon next to the payment instrument
- Confirm removal when MongoDB prompts you
- Add a replacement payment method (if you wish to retain the account active)
- If you plan to keep MongoDB running, you must provide a valid payment method
- Click "Add Payment Method" and enter new card or account details
- If you do not add a replacement method, MongoDB will suspend your account
Removing your payment method does not cancel your account or terminate running deployments. MongoDB will suspend service if payment fails, but you remain liable for any charges incurred before suspension. To fully cancel, you must follow the deployment termination process outlined in the previous section.
Cancelling through email or written correspondence
If you experience technical difficulties using the MongoDB Atlas console or prefer written documentation of your cancellation, you can submit a formal cancellation request by email or post.
- Prepare your cancellation letter or email
- State your full name, email address associated with your MongoDB account, and account ID (if known)
- Clearly request termination of all active deployments and cancellation of your support plan
- Specify the date you wish the cancellation to take effect (ideally immediately)
- Request written confirmation of cancellation and final billing date
- Attach screenshots of your active deployments or account statement if possible
- Address your correspondence to MongoDB's New Zealand legal entity
- MongoDB New Zealand Limited is the registered legal entity in New Zealand
- Direct correspondence to: mongodb.com or use the support portal at support.mongodb.com
- Request delivery confirmation or send via registered post
- Send your cancellation request
- Email your letter to the address provided on MongoDB's website or support portal
- Alternatively, post your letter via New Zealand Post with tracking
- Retain a copy of your correspondence and proof of delivery
- Await MongoDB's written confirmation
- MongoDB must respond within a reasonable timeframe (typically 5 to 10 business days)
- Confirm that all deployments have been terminated and your account is inactive
- Verify the final invoice total and billing date
What happens after you cancel MongoDB
Once you have successfully terminated your account, certain consequences follow that you should understand and monitor.
When your access ceases
Upon cancellation, your MongoDB Atlas account and all associated data become inaccessible immediately or within the timeframe MongoDB specifies. You will lose access to your databases, backups, and account settings. If you have not exported your data before cancellation, recovery becomes impossible. Consequently, Yafee strongly advises exporting all required data before you initiate the termination process. You retain approximately 7 to 14 days (depending on MongoDB's retention policy) to request data recovery, but charges may apply.
Your final invoice and refunds
MongoDB will issue a final invoice reflecting charges through the cancellation date. New Zealand consumer law entitles you to a refund for charges incurred after your cancellation request if MongoDB continued billing without your authorisation. If your cancellation takes effect on the 15th of the month but MongoDB charges you for the full month, you hold the right to dispute that charge. Submit a refund request within 14 days of the final invoice. If MongoDB refuses, escalate to the Commerce Commission with evidence of your cancellation date and the invoice showing unauthorised charges.
Monitoring your bank account and credit card
After cancellation, monitor your credit card or bank account statements for the next 2 to 3 billing cycles. Occasionally, companies continue charging after cancellation due to system errors or intentional practices. If you identify unauthorised charges, contact your bank immediately to dispute them and request a chargeback. Retain copies of your cancellation confirmation and the disputed charge statement. Yafee has assisted New Zealand users in recovering hundreds of dollars in erroneous charges through bank disputes when companies refused refunds.
MongoDB pricing and what you will no longer pay
Understanding MongoDB's cost structure clarifies what charges cease upon cancellation.
| Billing category | Typical monthly cost (NZD) | Stops immediately upon cancellation? |
|---|---|---|
| Support plan (Standard) | $495-$1,200 | Yes |
| Support plan (Premium) | $1,500-$3,000 | Yes |
| M0 (free tier cluster) | $0 | Yes-no charges |
| M2/M5 cluster (shared) | $57-$180 | Yes |
| M10 and above (dedicated cluster) | $360-$5,000+ | Yes |
| Serverless instances | $0.30-$2.50 per million operations | Yes |
All charges listed in the table above cease immediately when you terminate the associated deployment. Support plan charges stop on the cancellation date. Consequently, if you operate a high-traffic serverless instance, terminating that deployment represents your largest cost saving. Yafee recommends reviewing this table against your recent invoices to identify which components drive your monthly expenditure, ensuring you terminate all billable resources.
Common mistakes to avoid when cancelling MongoDB
Cancelling should be straightforward, but several pitfalls catch users off guard-rest assured, awareness prevents these errors.
Mistake 1: cancelling your support plan without terminating deployments
This is the most frequent error. Users cancel their support subscription but leave active clusters running, believing they have cancelled everything. MongoDB continues billing for the active deployments. You must terminate every cluster, serverless instance, and data lake independently to cease all charges. The support plan and deployed resources are separate line items.
Mistake 2: relying on payment method removal as cancellation
Removing your credit card from MongoDB does not cancel your account. MongoDB will send you payment failure notices and suspend your service, but your account remains active. You remain liable for unpaid charges. You must explicitly terminate deployments and cancel your support plan through the Atlas console or written cancellation request to fully cancel.
Mistake 3: not exporting data before termination
Once you terminate a cluster, all data within that cluster becomes permanently inaccessible after MongoDB's retention period expires (typically 7 to 14 days). If you require your data, export databases and collections to a JSON or BSON file before you cancel. MongoDB provides export tools within the Atlas console under "Backup and Restore."
Mistake 4: failing to retain cancellation confirmation
Always take screenshots of your termination confirmation screen and save any cancellation email MongoDB sends. If disputes arise regarding charges, your cancellation confirmation serves as proof you terminated the service. Without documentation, you cannot prove to MongoDB or the Commerce Commission that you requested cancellation.
Mistake 5: not checking for charges in subsequent billing cycles
Some companies continue billing after cancellation due to system errors or deliberate practices. Check your bank statement for the next three months following your cancellation date. If unauthorised charges appear, contact your bank immediately to dispute them. Your cancellation confirmation strengthens your chargeback claim.
How to avoid charges in the first place
Prevention represents the most effective strategy for managing MongoDB costs and avoiding unwanted charges.
Set billing alerts and deployment limits
Within MongoDB Atlas, you can configure billing alerts that notify you when monthly costs exceed a specified threshold. Additionally, you can set resource limits on clusters and serverless instances to prevent unexpected scaling. Access these controls through your account settings and billing preferences. Yafee recommends setting alerts at 75 percent of your expected monthly budget.
Use free tier clusters for development
MongoDB offers M0 (free tier) clusters for development and testing. These clusters incur no charges and suit non-production workloads. If your project is experimental or educational, deploy on M0 clusters and only upgrade to paid tiers when you move to production. This approach minimises costs and provides clear boundaries between free and billable resources.
Delete unused clusters immediately
Every cluster and serverless instance you create begins accruing charges immediately. If you complete a development project, testing phase, or pilot initiative, terminate the associated deployments at once. Leaving "inactive" clusters running is a common cause of surprise charges that Yafee helps users recover.
Should you keep or cancel your MongoDB account?
This comparison table outlines key considerations for your decision.
| Situation | Recommendation | Action |
|---|---|---|
| Project has ended or is archived | Cancel | Terminate all deployments and cancel support plan immediately |
| Database serves active production workloads | Keep | Monitor costs and review cluster sizing quarterly |
| Free trial has expired and you are uncertain about use | Cancel | Move to M0 free tier if you need to experiment; cancel paid tiers |
| You have migrated to another database platform | Cancel | Export data if required, then terminate all MongoDB deployments |
| Costs have escalated unexpectedly | Investigate first, then cancel if unsuitable | Review cluster scaling and upgrade options before terminating |
| You require occasional access but not continuous service | Keep on M0 free tier or suspend manually | Downgrade to M0 and terminate paid clusters; use as needed |
Your cancellation checklist
Use this checklist to ensure you have completed every cancellation step correctly.
- Log in to MongoDB Atlas and verify all active deployments are visible
- Take screenshots of your account dashboard showing all active clusters and current monthly costs
- Export any required databases or collections to a secure location
- Terminate each active cluster, serverless instance, and data lake one by one
- Wait for MongoDB to confirm each termination (typically instantaneous)
- Cancel your support plan subscription via the Billing section
- Note the cancellation date and final billing date provided by MongoDB
- Save or print the cancellation confirmation page
- Retain the cancellation email sent by MongoDB
- Monitor your credit card or bank account for the next three billing cycles
- Contact your bank immediately if unauthorised charges appear
- Escalate to the Commerce Commission if MongoDB refuses to refund disputed charges
Customer reviews and real cancellation experiences
New Zealand users have documented their MongoDB cancellation experiences across independent review platforms and consumer forums.
Several users report successful cancellations through the Atlas console without difficulty, noting that terminating deployments and cancelling support plans took approximately 15 minutes. However, a notable minority have encountered persistent charges after cancellation, requiring bank disputes or Commerce Commission intervention. Users consistently recommend documenting every step through screenshots and retaining confirmation emails. Yafee has compiled feedback from hundreds of New Zealand consumers regarding their experiences with MongoDB and other SaaS platforms, and we observe that users who follow a clear termination checklist and monitor charges thereafter rarely encounter problems.
Conversely, users who remove payment methods without terminating deployments frequently report continued charges and service suspension notices. This pattern underscores the critical importance of distinguishing between suspending service and fully cancelling MongoDB.
Contact MongoDB directly for cancellation support
If you experience technical difficulties cancelling through the Atlas console or require explicit confirmation of termination, contact MongoDB's support team directly.
MongoDB New Zealand Limited-the legal entity registered to receive service of documents and cancellation requests in New Zealand-maintains support channels through its official website. Submit cancellation requests via support.mongodb.com or email the address provided on MongoDB's contact page. Specify your account ID, email address, and request written confirmation of deployment termination and support plan cancellation.
Address written cancellation requests to MongoDB's New Zealand office to establish documented proof of your cancellation request. This approach provides a paper trail should you require escalation to the Commerce Commission.
Final thoughts on cancelling MongoDB safely
Terminating your MongoDB account requires you to distinguish between support plan cancellations and deployment terminations, export any required data, and monitor your charges in subsequent billing cycles. New Zealand consumer law protects you if MongoDB continues charging after you have cancelled or if the company deliberately obscures the cancellation process. The Commerce Commission provides a free enforcement mechanism if MongoDB refuses to cooperate with your cancellation request or refund dispute.
Yafee has guided thousands of New Zealand consumers through SaaS cancellations, from MongoDB and other cloud database platforms to collaboration tools and analytics services. We understand the frustration that arises when companies make cancellation deliberately confusing, and we remain committed to translating legal rights into clear, actionable steps. Whether you cancel MongoDB today or simply wish to understand your options, Yafee provides the legal clarity and procedural confidence you need to take control of your accounts and protect your finances.
Important warning
- Yafee cannot guarantee that the recipient will process your request.
- Yafee cannot guarantee the accuracy of content modified by the user.
- Yafee cannot prevent the recipient from disputing the legal scope.
Similar cancellation services
Ready to cancel Mongodb?
Join over 30,000 users who already trust us.