Postclic is an independent certified electronic mail service. We are neither affiliated with, nor partners of, nor mandated by Firebase, whose name is mentioned solely to identify the recipient of your letter. The trademarks and logos cited belong to their respective owners.
Postclic premium unlimited: promotional offer at ₱61.60 for 48h, then ₱3,353.56 per month without commitment
Send an e-Postclic to Firebase
Tracked, timestamped, and certified digital mail
What type of action would you like to take?
Choose the type of mail to generate. The template will be adapted automatically.
The form then adjusts based on your choice
Cancellation service #1 in Philippines
Digital mail
certified, timestamped, tracked, and
recorded on the blockchain
delivered instantly worldwide
Postclic unlimited plan
Promotional offer at ₱61.60 for 48 hours
then no commitment, ₱3,353.56 per month
to keep966649193710
Recipient
Firebase
38th Floor, Seven NEO, E Square, Crescent Park Residences, Building 5th Ave
1016 Taguig City , Philippines
REF/2025GRHS4
Cancellation Firebase: Easy Method
What is Firebase
Firebase as Google's app backend platform
Firebase is a developer platform owned by Google. It started in 2011 and later became part of Google, with operations tied closely to Google Cloud. In practical terms, that means your billing, usage limits, and support experience can feel more like a cloud service than a simple app subscription.
For users in the Philippines, that setup can be frustrating when you just want to stop charges fast. Many people get stuck because the billing area sits inside the Firebase Console, and some paid features also connect to Google Cloud usage. The truth is, Firebase cancellation is more technical than it should be.
What people usually pay for on Firebase
The free Spark plan costs $0.00 (₱0)* per month and is mainly for testing or small projects. The paid Blaze plan also starts at $0.00 (₱0)* as a base because it is pay-as-you-go, which means your actual monthly bill depends on usage such as database reads, writes, storage, hosting, and phone authentication.
A concrete example from Firebase's own billing documentation shows Cloud Firestore can reach about $292.02 (₱292.02)* per month in a high-usage scenario with 1 million app installs and 100,000 daily active users, including $261.90 (₱261.90)* for operations and $30.12 (₱30.12)* for storage and network use (firebase.google.com). Phone number verification also has per-use charges, with examples like $0.1350 (₱0.14)* per verification in Indonesia and $0.0743 (₱0.07)* in Germany (firebase.google.com).
How Firebase works in the Philippines
Firebase is available in the Philippines, but pricing is generally published in US dollars and then billed based on usage. Local PHP display is not the native pricing format, so your bank, card issuer, or wallet may apply conversion or cross-border handling depending on the payment setup, even if the guide below shows PHP equivalents for clarity.
Support is also limited compared with consumer apps. There is no published Firebase support phone number, no open live chat, and no public support email. The support route is the signed-in console and the official contact troubleshooter at Firebase support contact. If you are planning to leave Firebase after cancellation, close alternatives include Supabase, Appwrite, and AWS Amplify.
How to cancel Firebase without getting billed again
Checks to do before you click cancel
Many Firebase users in the Philippines get annoyed for the same reasons: the billing date is not obvious, the console is cluttered, and refunds are usually not prorated. Before canceling, save copies of anything you may need later because Firebase says your historical report data will no longer be available after cancellation (firebase.google.com/terms).
Take three minutes and gather proof before doing anything. This small step matters if you later need to dispute a continued charge with your bank, GCash, Maya, or card issuer within the usual 60-day dispute window used under BSP rules for card complaints.
- Open your Firebase Console and take a screenshot of your current billing plan.
- Note your next billing date and the exact project linked to billing.
- Export any reports, usage data, or billing summaries you may need.
- Save transaction IDs and the last charged amount from your statement.
- Check whether you activated any committed use discount on Cloud Firestore, because that cannot be canceled once purchased.
Exact web cancellation path in the Firebase Console
If you subscribed directly through Firebase or Google Cloud billing, the main route is the web console. The verified path is simple on paper: sign in to your Firebase account, go to Billing, choose the subscription or billing setup you want to stop, click Cancel Subscription, then follow the on-screen instructions (firebase.google.com).
In real use, the tricky part is that Firebase billing can be tied to project-level settings. If you see a billing account instead of a simple plan switch, review the project carefully before confirming. Users often cancel the wrong thing or downgrade a project but leave billable services active elsewhere.
- Go to the Firebase Console and sign in.
- Open the project you want to stop billing for.
- Find the Billing section.
- Select the plan or billing setup attached to that project.
- Choose Cancel Subscription if shown, or remove the paid billing setup according to the visible console options.
- Complete the confirmation screens and save a screenshot of the final confirmation.
If the interface sends you into support flows instead of a cancel button, use the official Firebase contact troubleshooter. That is the best documented support entry point currently available.
Support, email, phone, and postal route
Firebase does not publish a customer service phone number for cancellation. There is also no public support email listed for billing cancellations. Support is handled through the signed-in Firebase Console, and the support hours are not specified in the available official documentation.
If you need a paper trail beyond screenshots, you can send a written notice to the Google Philippines office address listed below, but online cancellation is still the practical route. Some people use a digital registered letter service such as Postclic when they want timestamped proof of sending, receipt, and opening without going to a post office.
Take note that no specific dark pattern was identified in the verified research. Even so, users do report that the interface is complex, especially when Firebase points back to Google Cloud billing pages instead of a clean consumer-style cancellation flow.
What changes after you cancel
Your access and billing status
After cancellation, you usually keep access until the end of the current billing term, unless the service or feature is usage-based and tied to an active billing account that has been downgraded or removed. Firebase's terms say subscriptions may auto-renew after the commitment term ends, monthly or yearly, unless canceled before renewal (firebase.google.com/terms).
That means timing matters. If your next cycle starts on March 31 and you cancel on March 25, the safest assumption is that paid access or paid billing status continues only until March 31, with no refund for unused days. Firebase does not promise prorated credits for a partial month after cancellation.
Your data, reports, and project history
Here is the part many users miss: Firebase states that historical report data will no longer be available after cancellation (firebase.google.com/terms). If you rely on analytics exports, billing reports, or usage history for internal reporting, download them before you cancel.
Canceling a billing setup is not the same as backing up your app data. Export what you need from Firestore, Storage, Authentication logs, or other linked services before making changes. If you forget, support may not be able to restore old report access later.
Refund policy and payment disputes for Philippine users
What the refund rules actually say
Firebase refunds are discretionary. Google's billing terms for Firebase say refunds are typically issued as credits for future services and are evaluated case by case, not guaranteed (firebase.google.com/terms). That is the key point if you are hoping for cash back to your card after canceling.
There is also no prorated refund for unused time after downgrade or cancellation. Charges are generally non-refundable regardless of whether you barely used the service during the billing period. In plain language, if you cancel halfway through a cycle, do not expect half your money back.
Your cancellation rights in the Philippines
In the Philippines, subscription disputes are generally handled under the Consumer Act of the Philippines or RA 7394, with the DTI as the main consumer authority. Firebase's own terms do not give a specific cooling-off period and do not explicitly grant a withdrawal right for Philippine users, so the service terms are stricter than what many shoppers expect.
For online services, there is no universal statutory cooling-off rule like some people assume from other countries. The clearer practical protection is this: if the charge was unauthorized, misleading, or continued after valid cancellation, you can complain to DTI and also dispute the transaction with your bank or e-wallet provider.
How to ask for a refund step by step
Your best chance is to contact Firebase through the signed-in support flow and present a narrow, factual case such as duplicate billing, wrong amount, or charge after cancellation. Billing error cases may be considered, but refunds are still not guaranteed (firebase.google.com/support/troubleshooter/contact).
- Sign in to Firebase Console.
- Open the billing support path through the support troubleshooter.
- State the project name, billing account, charge date, and exact amount.
- Attach screenshots of the cancellation confirmation and your statement entry.
- Request either a refund or billing credit, depending on the error.
Chargeback through bank, GCash, Maya, or card issuer
If a charge appears after cancellation or you did not authorize it, ask your payment provider for a dispute or chargeback. In the Philippines, cardholders typically have up to 60 days from the statement date to dispute a transaction under BSP complaint practice. That is why screenshots and exact dates matter.
If you paid through GCash, Maya, or a credit card, file the dispute directly with the provider and include proof that you canceled before renewal. DTI handles consumer complaints for online subscriptions under RA 7394, while BSP is the regulator for payment-related concerns. Use chargeback as a last resort when support does not fix a clear billing error.
Firebase terms that affect cancellation the most
Auto-renewal, trial conversion, and committed use traps
Firebase's terms say subscriptions may automatically renew after the monthly or yearly commitment term ends (firebase.google.com/terms). If a free trial applies to a Firebase service, it can convert to a paid subscription when the trial ends unless you cancel before the trial deadline.
The biggest catch is committed use discounts for Cloud Firestore. Those commitments can run for one year or three years, and after purchase, you cannot cancel the commitment. If you signed up for one by mistake, standard plan cancellation will not undo that commitment.
Applicable law and post-cancellation consequences
The terms are governed by California law according to Firebase's published terms, but that does not remove your practical consumer complaint options in the Philippines when the issue is a continued charge or payment dispute. For local users, the easier route is usually DTI for consumer complaints and BSP or your issuer for payment disputes.
Another clause that matters is data access after cancellation. Firebase says historical report data will no longer be available after cancellation, so if you need usage evidence for accounting or an internal turnover, export it before you stop the subscription.
Firebase plans and pricing in the Philippines
Main plans and their current structure
Firebase has two primary plans: Spark and Blaze. Spark is free for development and small projects, while Blaze is pay-as-you-go and is the plan where surprise bills can happen if usage climbs.
| Plan | Price (USD / PHP) | Period | Best for |
|---|---|---|---|
| Spark Plan | $0.00 (₱0)* | Monthly | Testing |
| Blaze Plan | $0.00 (₱0)* | Monthly | Production |
Prices are approximate, converted from USD at the rate 1 USD ≈ 1.0 PHP, and you should check the official website for exact local prices.
Which plan costs more in real life
The cheapest plan is Spark at $0.00 (₱0)* per month. The most expensive option in practice is Blaze because charges scale with usage, not because of a fixed monthly sticker price. That means one low-traffic month could stay close to ₱0, while a high-usage month could become expensive fast.
A real billing example from Firebase shows Firestore can reach about $292.02 (₱292.02)* per month in a large usage scenario (firebase.google.com). For phone verification, pricing is also usage-based by country, so costs can rise unexpectedly if your app starts sending many verification requests.
Billing notes that matter before canceling
Firebase does not present a classic monthly versus annual savings structure for its core plans because Blaze is usage-based. The bigger issue is not annual discounts but automatic renewal of applicable commitments and no prorated refunds after cancellation.
If you are on Blaze and trying to cut costs, switching services off before the next cycle can matter more than canceling late. For teams in the Philippines, a simple internal rule helps: review usage weekly and set project ownership clearly so nobody leaves a paid resource running by accident.
Your rights in the Philippines when Firebase billing goes wrong
How local consumer rules apply
For Philippine users, the main law is the Consumer Act of the Philippines or RA 7394, with the Department of Trade and Industry as the consumer authority. Since Firebase does not promise a cooling-off period in its own terms, your strongest local protection is against deceptive billing, unauthorized charges, or failure to honor a valid cancellation.
There is a seven working day cooling-off rule for door-to-door or direct sales in some situations, but that is not a clean match for a developer platform bought online. For normal online subscriptions, there is no universal statutory cooling-off right. That is why proof of cancellation is more useful than arguing for a general withdrawal period.
How to file a complaint with DTI
If Firebase keeps billing you after a documented cancellation, start with support and then escalate to DTI if needed. Your complaint should include your account details, project name, charge dates, amount charged, screenshots of cancellation, and any support case reference.
- Prepare your evidence in one folder.
- Write a short timeline with dates of subscription, cancellation, and charge.
- State the amount in PHP and the original billing currency if shown.
- Submit the complaint to DTI through its consumer channels.
- Keep your bank dispute reference if you also filed a chargeback.
Useful authority contacts
For consumer issues, contact DTI. For payment disputes involving cards or e-wallets, contact your issuer and BSP if the issue is not handled properly. This split matters because DTI looks at the consumer transaction, while BSP-related processes focus on payment disputes and issuer handling.
Firebase's terms are governed by California law, but for a Philippine user facing a local billing problem, the practical path is still local: DTI for the complaint, then your bank, GCash, Maya, or card issuer for the money side.
What users say about cancellation and billing
Overall verdict from available reviews
The pattern is clear: cancellation and billing management are generally viewed as difficult. The available review set here shows 0 positive and 5 negative reviews out of 5, which is a very poor sentiment trend. Local issue reports also point to App Store or Google Play cancellation trouble and a complicated Firebase Console.
To be fair, Firebase remains powerful for developers and offers a free Spark plan, plus strong integration with Google services. But when the discussion shifts to billing clarity and ease of cancellation, the feedback in this dataset is recurring patterns of negative.
| Theme | Frequency | Typical example |
|---|---|---|
| Charge after cancel | 2 | Unexpected continued charges |
| Refund problems | 1 | Refund refused |
| Complex cancellation | 2 | Console too confusing |
| Source | Rating | Number of reviews |
|---|---|---|
| TrustPilot | Mostly 1-2/5 | 5 |
Source summary and individual comments
| Source | Rating | Main topic | Sentiment |
|---|---|---|---|
| TrustPilot | 1/5 | Charge after cancel | Negative |
| TrustPilot | 1/5 | Refund | Negative |
| TrustPilot | 2/5 | Ease of cancellation | Negative |
- "I received over 100 spam emails from this site." (TrustPilot)
- "They sell faulty goods !! and do not offer refunds or even to swap out the fault goods !!! avoid this shop" (TrustPilot)
- "It's incredible how complex Firebase has become, because of the link with Google Cloud... Maybe I will suddenly get a large bill because I made a mistake" (TrustPilot)
Documents and proof to save before and after cancellation
What to save before canceling
Save a screenshot of your current plan, billing page, and the project name connected to billing. Also record your latest charged amount and date, because if a new charge appears later, you will need to compare the timeline clearly.
If you use Firebase for work, export reports before canceling because historical report data may disappear afterward under Firebase's terms. That one step can save you a lot of stress if finance or a client asks for past usage records a week later.
What to keep for refund or dispute cases
For a refund request, keep transaction IDs, invoice numbers, statement screenshots, and the cancellation confirmation page. If support replies inside the console, capture that too. A lot of payment disputes fail simply because the timeline is incomplete.
After cancellation, monitor your bank, GCash, Maya, or card statement for at least one full billing cycle. If you see a continued charge, you will already have the screenshots needed for support, DTI, or a chargeback request.
Common Firebase cancellation mistakes that cost time and money
Using the wrong cancellation channel
A common mistake is trying to cancel in a place that does not control the billing. If your billing is direct through Firebase or Google Cloud, canceling a mobile app setting will not stop the account. If the subscription was handled through App Store or Google Play in your specific case, the store controls the renewal.
Real-world result: users think they canceled, then a new charge arrives. Fix this by identifying the billing source from your statement and matching it to the correct channel before you do anything else.
Canceling without exporting data
Another mistake is canceling first and only later realizing that old reports are gone. Firebase says historical report data will no longer be available after cancellation, so this is not a theoretical risk. It is a documented consequence in the terms.
The solution is simple: export what you need before changing the billing setup. If you run client projects, archive the reports in a shared folder with the cancellation date in the filename.
Expecting a partial refund for unused days
Many users assume they will get money back for the unused part of the month. Firebase's refund rules do not support that assumption. No prorated refund is provided for downgrades or cancellations, and charges are generally non-refundable.
If cost is your concern, your best move is to cancel before the next billing cycle and shut down billable usage early. Waiting until the middle of a cycle usually saves less than people expect.
Ignoring committed use discounts
This is the expensive mistake. If you bought a committed use discount for Cloud Firestore, Firebase says you cannot cancel it after purchase. Some users downgrade the visible plan and assume all costs stop, then later discover the commitment remains.
Take note: if your project uses commitments, review them before cancellation. A normal cancellation flow does not erase a one-year or three-year spending commitment.
Failing to save proof of cancellation
Because Firebase has no public phone line and support runs through the console, screenshots are your best friend. If you cancel and do not save the confirmation page, you may struggle to prove that you acted before renewal.
The fix is easy. Save the confirmation screenshot, the date, and any support case number in one folder. Put a calendar reminder 3 days before the next billing date to verify that no new charge appears.
Quick comparison of cancellation methods
Methods, timing, cost, and effort
| Method | Notice period | Fee | Difficulty |
|---|---|---|---|
| Web/account | Before next billing date | No cancellation fee | Easy |
| App Store (iOS) | 5-10 business days | No cancellation fee | Higher - best proof |
| Postal letter | Before next billing date | No cancellation fee | Medium |
Key takeaway before you choose
The web account route is the main direct method for Firebase. App Store only makes sense if your purchase was actually routed through Apple in your specific case. A postal notice gives extra paper trail but is slower and usually secondary to the console-based method.
There is no cancellation fee specified in the terms, and no early termination fee was found. The real risk is not the fee but missing the next billing date or leaving usage-based services active.
What to do right after cancellation
Immediate checks and statement monitoring
Right after canceling, confirm that you saw a final success screen or support confirmation. Save a screenshot, note the date, and set a reminder for your next expected billing date. That single reminder is often the fastest way to catch a failed cancellation early.
Monitor your bank, GCash, Maya, or credit card statement for at least one full cycle. If an unauthorized charge appears, ask for a chargeback or dispute within 60 days from the statement date if your issuer follows the usual BSP dispute window. Keep your cancellation proof ready.
Alternatives and useful links
If you are leaving because Firebase billing feels too unpredictable, there are practical alternatives. Supabase offers PostgreSQL-based backend services with a free tier and paid plans from $25/month (₱25)*. Appwrite starts from $19/month (₱19)* for paid plans, while Back4App starts from $5/month (₱5)*.
Useful links are below. These are official or verified sources that help with cancellation, billing rules, and consumer action in the Philippines.
- Firebase Terms
- Firebase Support Contact
- Firebase Phone Verification Pricing
- Cloud Firestore Billing Example
- Department of Trade and Industry
Address and in-person contact reality
Physical office address in the Philippines
Firebase does not appear to have a separate cancellation office in the Philippines. If you want to send written correspondence, the available Google Philippines office address is:
- 38th Floor, Seven NEO, E Square, Crescent Park Residences, Building 5th Ave, Taguig City, 1016 Metro Manila, Philippines
This is not presented as a dedicated Firebase cancellation desk, so treat it as a general corporate address only. For actual account changes, the online route through the Firebase Console and support troubleshooter is the channel that matches the published process.
Best practical approach for most users
If your goal is simply to stop future billing, use the console first, save proof immediately, and then watch your statement through the next cycle. If a charge still lands after that, escalate with support, then DTI or your payment provider using the evidence you already saved.
Heads up: Firebase is powerful, but cancellation is easiest when you treat it like a cloud billing task, not a consumer app subscription. Once you approach it that way, the process becomes more manageable and you are less likely to get billed again by surprise.
Similar cancellation services
Verify a sent letter
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.
Written by Beatrice Domingo
Digital-law graduate · 3 years experience
Graduate in digital law and passionate about secure written communication, I have been writing guides on certified mail and electronic registered delivery for 3 years.
FAQ
Before canceling your Firebase subscription, take a screenshot of your current billing plan, note your next billing date, export any necessary reports, and check for any committed use discounts on Cloud Firestore, as these cannot be canceled once purchased. Keep proof of all these details for future reference.
To cancel your Firebase subscription, sign in to your Firebase Console, select the project linked to your billing, go to the Billing section, choose the subscription you want to cancel, and follow the on-screen instructions. If you encounter issues, consider sending a written cancellation notice to the Google Philippines office.
After canceling your Firebase subscription, you will lose access to your historical report data, so it's crucial to export any necessary information before proceeding with the cancellation.
Firebase does not typically offer prorated refunds for canceled subscriptions, so it's important to review your billing details and understand the terms before canceling. If you have disputes regarding charges, keep all documentation for reference.
If you face difficulties canceling your Firebase subscription, use the official Firebase contact troubleshooter available on their website for assistance. Alternatively, you can send a written notice to the Google Philippines office for a paper trail.