Postclic premium unlimited: promotional offer at RM 4.19 for 48h, then RM 228.34 per month without commitment

Cancellation service #1 in Malaysia
Supabase is a backend-as-a-service platform built around PostgreSQL, authentication, storage, edge functions, and realtime features. It launched in 2020 and positions itself as an open-source alternative to Firebase, with pricing and product details shown on the official pricing page.
If you are trying to cancel, you are probably already annoyed because billing pages can feel unclear and nobody wants a surprise charge after cancelling. Fair concern lah. Supabase is mainly used by developers, startups, and product teams that need database hosting and app infrastructure without running everything from scratch.
The paid value is not just storage space. The Pro plan at RM100.00 monthly gives larger database limits, 100 GB storage, 250 GB egress, 100,000 monthly active users, and 5 million realtime messages, while Team is about RM2,400.00 monthly with team-focused access and larger operational use cases "supabase pricing" (supabase.com).
In real life, most cancellations happen when a project moves to another stack, usage drops, or a team realises the Free plan is enough. Some users also leave because free projects may pause after 7 days of inactivity "reported by users" (hackceleration.com), which can be irritating for side projects and internal tools in Malaysia that are only opened once in a while.
Supabase runs on a freemium model. The Free plan is RM0.00 monthly, Pro is RM100.00 monthly, Team is RM2,400.00 monthly, and Enterprise uses custom pricing "price snapshot July 2026" (supabase.com). The research data does not confirm a free trial conversion rule, a commitment period, or local Malaysian billing support such as FPX or DuitNow.
For Malaysian users, that means you should treat the plan as a recurring online service and monitor your own billing date carefully. The published prices in this guide use MYR figures based on the July 2026 exchange snapshot provided in the research, so your live charge can move slightly with currency conversion and extra usage.
Many users feel stressed here because they want to stop billing without losing data too early. The smart move is to spend 10 minutes preparing. Take a screenshot of your current plan, note your latest invoice date, and export any database or storage content you still need before downgrading.
Supabase says cancellation is done by downgrading your organisation to the Free plan. According to its subscription guide, you cancel by going to your organisation billing settings, clicking Change subscription plan, and selecting Free Plan, and the downgrade is immediate "manage your subscription" (supabase.com docs source in research).
The main cancellation method is the web dashboard. The click path from Supabase's own guide is simple: go to your organisation's billing settings, click Change subscription plan, then select Free Plan. This is the key action that ends the paid subscription and moves the account out of the paid tier.
The official help reference for this process is the subscription management documentation. If you want the supporting page open while cancelling, use the billing help context from Supabase's documentation and compare each screen with your account before confirming. Because the downgrade is described as immediate, do not wait until the last minute on billing day if your team still needs paid resources.
Supabase does not list a public support phone number in the verified research. Live chat is also not available. Support is routed through the help centre and community forums, while a direct billing support email was not specified in the available source data.
If the dashboard fails or the account owner has changed, use the help centre path and keep a written record of your request. A registered letter can also work as evidence if you are documenting a dispute. Some Malaysians now use services such as Postclic as a digital registered letter option because it gives timestamped proof of sending, receipt, and opening without going to the post office.
On paper, the cancellation path is senang because it is only a downgrade to Free. In practice, the risk is not a hidden retention trick. The risk is operational. If you downgrade too early without exporting data or checking project limits, your app can hit Free plan constraints immediately.
No dark patterns were identified in the research data. That is good news. Still, users who had billing disputes reported rough experiences with support and project pausing, so proof matters. Screenshot every step and keep the final confirmation.
The research states the downgrade is immediate once you choose the Free plan. So unlike some subscriptions that stay active until the next renewal date, Supabase describes the change as happening right away when you switch plans "manage your subscription" (supabase.com docs source in research).
This matters because your usage limits may drop on the same day. If you were on Pro at RM100.00 monthly and your project depends on higher storage, egress, or active user limits, your team should plan the downgrade outside peak traffic hours. For production apps, do it after backups and after checking current usage.
The verified research does not state the exact auto-renewal clause wording in the terms. Still, paid SaaS billing normally continues until you actively downgrade or close the paid arrangement, and Supabase's own cancellation flow is built around changing the plan before the next billing cycle.
If you leave the plan untouched, expect recurring billing to continue under the active paid plan plus any usage-based charges that may apply. Because the terms data did not specify commitment duration or early termination rules, assume no special grace protection and act before the next invoice generates.
The available terms data does not clarify data retention after cancellation. That means you should not assume your paid-tier environment, backups, or project resources will remain untouched forever after a downgrade. Export what you need before changing plans.
A practical checklist includes database dumps, storage bucket files, environment variables, and screenshots of project settings. If your account only needs a temporary pause, switching to Free may be enough. If your workload is larger than Free limits, plan a migration before you cancel.
This is the part many users worry about most, especially if they clicked cancel and still hope money comes back to the card. Supabase's policy is direct: it does not offer refunds to the payment method on file. When you downgrade, any prepaid subscription fee for unused time in the billing cycle is credited back to your organisation, and those credits do not expire "manage your subscription" (supabase.com docs source in research).
In plain language, that means no cash refund to your bank card in the usual case. You get account credit for future invoices instead. If you are leaving Supabase permanently, this policy is not great for you because unused value stays trapped inside the organisation balance unless you keep using the service later.
In Malaysia, subscription disputes generally sit under the Consumer Protection Act 1999. The law does not create a universal cooling-off period for every online software subscription. The 10 working day cooling-off rule mainly applies to certain direct sales contracts that meet specific written-contract conditions, so it is not something you can automatically assume for a Supabase web subscription.
If a charge is misleading, unauthorised, or not what was agreed, you can still complain to KPDN and consider TTPM for consumer claims. For card disputes, Malaysian banks usually handle chargebacks within about 60 to 120 days from the transaction date or from when the issue was discovered, under Bank Negara Malaysia's complaint-handling framework.
If your issue is not simple buyer's remorse but a billing mistake, ask through the official support route with evidence. Include the organisation name, invoice number, transaction date, amount in MYR, card last four digits if relevant, and screenshots of the billing page before and after downgrade.
Use a chargeback only when there is a genuine billing problem, such as an unauthorised recurring charge, duplicate charge, or a paid service not delivered as promised after you tried resolving it directly. In Malaysia, banks usually call this a chargeback or a dispute for an unauthorised or recurring card transaction.
Prepare a clean evidence pack before calling the bank. Include your cancellation screenshot, invoice, support messages, and bank statement line. If the company ignores you, KPDN and TTPM can be the consumer side escalation path, while your card issuer handles the payment dispute itself.
| Plan | Price (MYR) | Billing period | Main features |
|---|---|---|---|
| Free | RM0.00 | Monthly | 500 MB DB, 50k MAUs |
| Pro | RM100.00 | Monthly | 8 GB DB, 100 GB storage |
| Team | RM2,400.00 | Monthly | Team use, larger quotas |
| Enterprise | Custom | Monthly | Custom quotas and support |
The cheapest recurring option is Free at RM0.00, while the most expensive published recurring tier in the research is Team at RM2,400.00 monthly. Enterprise is custom, so actual spend can go much higher depending on scale and support requirements.
If you are paying RM100.00 monthly for Pro but your app has low traffic and limited storage, downgrading to Free may be enough. On the other hand, if your usage is close to Pro limits, cancelling in a rush can break features fast. Compare your current database size, monthly active users, and storage before switching.
The research snapshot says prices are approximate and based on the exchange rate as of July 2026, so your live card charge may differ slightly. The available sources do not confirm annual billing discounts, historical price increase data, or a trial conversion rule.
There is also no cancellation fee found in the available terms data. That is the good part. The less good part is the refund structure, because unused prepaid value becomes organisation credit rather than cash back to your payment method.
For Malaysian readers, the main law is the Consumer Protection Act 1999. It can help when there is misleading conduct, unfair practices, or a service dispute, even though it does not automatically give a broad cooling-off right for every software subscription purchased online.
For Supabase specifically, this means your strongest practical protections usually arise when there is a billing error or an unauthorised recurring charge, not simply because you changed your mind. The 10 working day cooling-off framework is mainly tied to certain direct sales contracts and written-form requirements, so many ordinary SaaS signups will not fit it neatly.
If Supabase ignores a documented billing complaint, start by organising your evidence. Put your invoice, cancellation screenshot, support messages, bank statement, and a short timeline in one folder. Then lodge a complaint with KPDN and consider a claim at the Tribunal for Consumer Claims Malaysia if money is involved.
Use plain facts. Say when you subscribed, when you downgraded, how much was charged, and what response you received. If your bank is also investigating a chargeback, mention that too so your records stay consistent across all channels.
KPDN is the Ministry of Domestic Trade and Cost of Living. TTPM is the Tribunal for Consumer Claims Malaysia, which handles many lower-value consumer disputes in a simpler forum than court. Before filing, check the latest form requirements and filing channels on the official government sites.
Based on 5 unique reviews, the sentiment is mixed but leans negative on billing and account handling: 2 positive and 3 negative. My honest take is this: the dashboard cancellation path itself looks easy, but the surrounding issues such as billing disputes, inactivity pauses, and support experience can make the overall exit feel difficult.
Recurring themes include responsive support in some cases, no obvious dark patterns, but also frustration over unexplained charges and paused projects. Local relevance is clear because low-traffic apps are common in Malaysia for internal tools, side projects, and early-stage builds, and a 7 day inactivity pause can disrupt that workflow "user-reported issue" (hackceleration.com).
| Theme | Frequency | Typical example |
|---|---|---|
| Support praise | 2 | Fast human help |
| Billing frustration | 1 | Disputed charge conflict |
| Inactivity pause | 2 | Project paused quickly |
| Source | Rating | Number of reviews |
|---|---|---|
| TrustPilot | Mixed | 4 |
| Noizz | Positive | 1 |
If you cancel without records, proving anything later becomes leceh. Save a full-page screenshot of the Billing settings screen, your active plan name, your organisation name, and the last invoice amount. Also export data before the immediate downgrade changes your limits.
For billing complaints, collect transaction IDs, exact dates, exact amounts, and copies of every support message. If the card statement shows a merchant descriptor, save that line too because banks often ask for the precise statement entry.
After cancellation, keep the confirmation screen, any confirmation email if one arrives, and a screenshot of the account showing Free plan status. Check your next statement cycle to confirm no new recurring charge appears.
Supabase billing is tied to the organisation, not just your personal login. A common mistake is downgrading the wrong organisation while the paid one stays active and keeps charging. This is very possible for freelancers or agencies managing multiple client workspaces.
Fix it by checking the organisation name twice before you open Billing settings. Match it against the invoice header and the current project list.
Many users assume unused days will be refunded back to the card. Supabase's published policy says unused prepaid subscription fees are credited back to the organisation for the unused time in the billing cycle, and those credits do not expire. That is not the same as a bank refund.
If you are leaving permanently, ask support clearly whether any billing adjustment is possible in your case, especially if the issue is an error. Do not rely on assumptions can or not.
The downgrade is described as immediate, so waiting until after cancellation to think about backups is risky. If your project uses paid-tier limits, you may suddenly face lower quotas the same day.
A practical scenario is a startup team on Pro at RM100.00 monthly with active storage buckets. They downgrade first, then realise they still needed config details for migration. Save everything before touching the plan button.
Several complaints focused on projects being paused after 7 days of inactivity. That may not be a billing error, but it catches people off guard, especially during planning phases or on internal systems with low usage "reported by users" (hackceleration.com).
If your workflow is slow and research-heavy, decide whether Free is actually suitable before cancelling Pro. Sometimes a planned migration to another service is safer than staying on a paused low-activity setup.
The easiest mistake is also the most expensive later. People cancel, close the tab, and keep no proof. If a charge appears after that, the argument becomes messy.
Always save the confirmation screen and set a calendar reminder for your next billing date plus 3 days. That one habit makes bank disputes and KPDN complaints much easier.
| Method | Notice period | Fee | Difficulty |
|---|---|---|---|
| Web/account | Before next billing | No fee found | Easy |
| App Store (iOS) | Before next billing | No fee found | Medium |
| Google Play (Android) | Before next billing | No fee found | Medium |
| Registered mail | 5-10 business days | No fee found | Higher, best proof |
The web dashboard is the clearest route because it matches Supabase's published cancellation instructions. App Store and Google Play were listed in the research framework, but the available Supabase source did not specify in-app store subscription steps, so do not assume your plan was bought there unless your payment history says so.
Registered mail is slower but useful if you are building a paper trail for a dispute. The best option depends on your situation: fast downgrade through the dashboard, written escalation through support, or formal evidence through registered delivery.
Right after downgrading, confirm the plan now shows Free and save the screen. Then check whether your projects are still behaving as expected under Free limits. If something business-critical breaks, you want to know on the same day, not after your customer tells you.
Set two reminders: one for the next expected billing date, and one 30 days later. Use those dates to inspect invoices and bank statements.
If a recurring charge appears after cancellation, gather proof and contact your bank quickly. In Malaysia, cardholders usually call this a chargeback or a dispute for an unauthorised or recurring card transaction, and the practical filing window is often around 60 to 120 days depending on the bank and card network.
Show the bank your cancellation screenshot, statement entry, invoice, and support messages. If the merchant does not resolve it, the bank process runs within Bank Negara Malaysia's financial consumer protection framework under the Financial Services Act 2013 or Islamic Financial Services Act 2013 complaint-handling environment.
If Supabase no longer fits, three realistic alternatives stand out. Firebase offers a free tier with pay-as-you-go usage and is strong for mobile and web backends. Appwrite offers open-source flexibility with cloud or self-hosted options, with Pro plans starting from $15.00 (RM64.00 approx). Neon focuses on serverless PostgreSQL, with paid plans starting from $19.00 (RM81.00 approx).
For smaller personal tools, PocketBase is free and open-source. If you want a PostgreSQL-based backend with GraphQL, Nhost starts from $49.00 (RM209.00 approx). Compare migration effort, inactivity behaviour, and hosting control before jumping.
No verified physical cancellation address was found in the research data for Supabase. That means the practical route for Malaysian users is online through the account dashboard, backed by screenshots, invoices, and written support contact if there is a dispute.
If you still need hard-copy evidence, send a registered letter to any verified corporate address only after independently confirming it from official company material. Do not send sensitive billing documents to an address you found on a random directory.
For most users, cancelling Supabase is actually a downgrade to Free from the organisation Billing settings. The move is immediate, there is no cancellation fee found in the available terms data, and unused prepaid time is usually returned as organisation credit rather than cash refund.
If your problem is not simple cancellation but an unfair or unauthorised charge, document everything, contact support, then escalate through your bank, KPDN, or TTPM if needed. That sequence gives you the strongest record and the least hassle.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.