Postclic premium unlimited: promotional offer at ₱61.60 for 48h, then ₱3,353.56 per month without commitment

Cancellation service #1 in Philippines
Runnable was known as a developer tool for container-based environments and CI/CD workflows. The clearest public fact in the available material is that Runnable was discontinued after its acquisition by MuleSoft, and current pricing and subscription information are very limited.
Here is the part that frustrates many users in the Philippines. You may still see old references to Runnable online, but the current official cancellation instruction is simple and unusual: contact support by email at [email protected] to cancel your account "To cancel your Runnable account, please contact our support team at [email protected]." (runnable.com).
Runnable's paid value was tied to developer workflow automation, hosted environments, and build or deployment support. This was not a typical entertainment or mobile plan, which is why the cancellation flow is more manual than many app-based subscriptions.
The only verified plan data provided here is a monthly plan called Tumexcelpro Plus at $21.99 (₱22)*. That price looks inconsistent with normal exchange rates, so treat it as raw source data rather than a reliable local market offer.
For users in the Philippines, there is no verified evidence of a dedicated iOS or Android Runnable subscription app. The source data says App Store and Google Play cancellation routes do not apply because Runnable does not offer an iOS app or Android app (runnable.com).
That means local users should expect a web and support-based process, not an in-app cancel button. Support hours are listed as Monday to Friday, 9 AM to 6 PM PST, which is a practical issue if you are contacting them from Manila because of the time difference.
A lot of cancellation problems start before the actual request. If you are in the Philippines and you are worried about continued charges or a delayed reply, take screenshots of your account page, your current plan name, your latest billing receipt, and the date of your next charge before you contact support.
The truth is, Runnable's process is more manual than it should be. Since the official instruction is to email [email protected], your own records matter a lot if you later need to question a charge with your bank, GCash, or Maya.
The verified cancellation method is not a self-service button. The official instruction is to contact support at [email protected], and help resources are listed at Runnable Help.
If live chat is available in the Help section, use it to ask for the exact account status after you email. A practical path is this: open Help, open the Help section, start live chat if shown, then send your cancellation email to [email protected] from the same email address linked to your account.
Use a short and specific message. Include your full name, account email, plan name, last payment date, and a direct sentence asking them to cancel before the next billing date. Ask for written confirmation by email. If you want stronger proof, you can also send a postal cancellation notice, and some users now use certified digital letter services such as Postclic for time-stamped proof of sending and receipt instead of traditional registered mail.
Runnable does not list a support phone number in the verified data. The working contact channels are email at [email protected] and live chat through the Help section, with support hours Monday to Friday, 9 AM to 6 PM PST.
If you are sending an email from the Philippines, do it at least several days before your billing date. Because the terms do not specify an auto-renewal clause or a minimum notice period, the safest move is to contact support as early as possible and keep the sent email with its timestamp.
Do not try to cancel through App Store or Google Play just because you searched for "cancel a runnable android." The verified source says those store methods are not applicable because Runnable does not offer iOS or Android app subscriptions (runnable.com).
Do not assume silence means cancellation. If support does not confirm, follow up through chat and keep all screenshots. This matters if a charge appears after you asked to cancel.
Runnable's published material in this dataset does not clearly state whether access continues until the end of the current billing cycle. What is confirmed is that refunds are not available after cancellation, including for unused periods (runnable.com).
Because of that, assume the safest case for your planning: cancel before the next charge and export anything important before you send the request. If support later confirms the exact end date of access, save that email.
The terms available at Runnable Legal do not specify an auto-renewal clause. That does not mean billing cannot continue. It means the public terms in this dataset do not spell it out, so you should rely on your receipts and account history.
If you already saw recurring charges, treat the subscription as ongoing until support confirms cancellation in writing. Put a calendar reminder a few days before the next expected statement date so you can catch any new charge quickly.
Runnable's terms do not specify data retention after cancellation. That is a big gap if you stored build settings, project data, or deployment records there (runnable.com).
Back up what you need before requesting cancellation. Do not wait for support to explain retention later, because there is no verified retention timeline in the available legal page data.
If you are hoping for a partial refund after canceling, heads up: the verified policy is strict. Refunds are not available after cancellation, and there are no refunds for unused periods after cancellation (runnable.com).
That means if you cancel halfway through a month, you should not expect money back for the remaining days unless there is a billing error. This is exactly the kind of point that catches users off guard when a service does not make the flow very visible.
For users in the Philippines, the Consumer Act of the Philippines or RA 7394 is the main consumer protection law for complaints about unfair or problematic subscription billing. There is no universal cooling-off period for ordinary online subscriptions, and Runnable's own terms do not specify a cooling-off period or a withdrawal right.
For direct sales contexts, a 7 working day cooling-off period can apply, but that is not clearly the normal Runnable setup. For a web subscription, your stronger practical protection is evidence: screenshots, receipts, the cancellation email, and any support reply.
The only clear exception in the source data is billing error. If you were charged by mistake, contact [email protected] and include the transaction date, amount, account email, and screenshot of your cancellation request if you already sent one.
If Runnable does not resolve an unauthorized or continued charge, you can dispute it with your card issuer, bank, GCash, or Maya. BSP rules commonly give cardholders up to 60 days from the statement date to dispute a transaction, so do not wait too long.
If the issue looks like a consumer complaint rather than a pure payment dispute, DTI can also be relevant under RA 7394. Your strongest evidence is the cancellation confirmation, or at minimum the email you sent to [email protected] before the charge posted.
The legal page at Runnable Legal leaves several practical questions unanswered in the dataset. It does not specify an auto-renewal clause, a minimum commitment duration, free trial terms, data retention after cancellation, governing law, or dispute resolution procedures.
For a paying user, that lack of detail is not ideal. It means you should not assume there is a grace period, a free trial conversion warning, or a stored-data period unless support confirms it directly in writing.
If you subscribed and forgot to cancel, the public terms in this dataset do not give you a clear contract shortcut for refunds or withdrawal. The practical move is simple: cancel early, save proof, and watch your next statement.
If support gives you a custom answer by email about access end date, billing stop date, or data retention, keep that message. In a dispute, a direct support reply can be more useful than a vague public terms page.
| Plan | Price (USD / PHP) | Period |
|---|---|---|
| Tumexcelpro Plus | $21.99 (₱22)* | Monthly |
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.
The verified plan data above is the only subscription price provided in the dataset, but it conflicts with the broader research note saying Runnable has been discontinued and has no active pricing. So treat this as historical or unconfirmed billing data, not as a dependable current Philippine offer.
Because only one plan is listed, there is no real monthly versus annual comparison to calculate. There is also no verified cancellation fee, no early termination fee, and no documented free trial in the terms data.
In the Philippines, RA 7394 or the Consumer Act is the main law for consumer complaints involving subscriptions and unfair billing issues. If your problem is a continued charge after cancellation, DTI is the practical consumer agency to approach, while payment disputes can also go through your card issuer or e-wallet provider under BSP rules.
The research data also names the Philippine Competition Commission as an authority, but for ordinary billing and cancellation complaints, DTI is usually the more direct path for consumers. If the issue is with card or wallet transactions, your bank, GCash, Maya, or credit card issuer should be contacted quickly.
Runnable's own terms do not specify a cooling-off period or a withdrawal right. In the Philippines, there is no blanket statutory cooling-off rule for all online subscriptions, so do not rely on one unless the seller clearly offered it.
For door-to-door or direct sales, a 7 working day cooling-off period can apply. That does not neatly match a normal web-based Runnable subscription, which is why your cancellation proof is more useful here than arguing over an online cooling-off period that may not exist.
If support does not fix a wrongful charge, prepare a short file with your screenshots, receipt, cancellation email, and support replies. Send the complaint to DTI and explain the timeline in plain language, including the exact date you asked to cancel and the exact amount charged.
If the transaction hit your card or e-wallet, file a dispute with the payment provider on the same day if possible. In many Philippine banking cases, the 60 day window from the statement date matters, so speed helps.
Use the service contacts first, then escalate if needed. For Runnable itself, the working support channels are email and live chat through Help.
Clear verdict: cancellation looks medium difficulty, not because of hidden tricks, but because the process depends on contacting support instead of using a visible self-service cancel button. No dark patterns were identified in the research data, but the lack of a direct account path can still be frustrating.
There are no verified user review quotes specifically about Runnable's cancellation process in the dataset. That means the honest conclusion is based on support flow, terms gaps, and common product issues rather than star ratings or public testimonial volume.
| Theme | Frequency | Typical example |
|---|---|---|
| Manual cancellation | High | Email support needed |
| UI complexity | Medium | Steep learning curve |
| Slow performance | Medium | Peak-hour build delays |
| Source | Rating | Number of reviews |
|---|---|---|
| Verified dataset | No public rating | 0 reviews |
| Common issues data | Mixed signals | 2 issue themes |
The positive side is that no cancellation trick or retention trap was identified. The negative side is that there are no strong public self-service details, which often means more back and forth for users who simply want billing to stop fast.
Build a simple evidence folder before you contact support. Save the account email, latest receipt, current plan screenshot, and your next billing date in one place so you do not scramble later if support asks for details.
If you are claiming a billing error, include exact transaction details. A good file has the charge amount, date, payment channel, and the message you sent to [email protected].
After cancellation, save the confirmation email and check your next bank or wallet statement. That one step often decides whether a dispute is easy or annoying.
One common mistake is using the wrong channel. Because Runnable does not have applicable iOS or Android app subscription cancellation routes in the verified data, trying App Store or Google Play wastes time when your next billing date is close.
Another mistake is expecting a pro-rated refund. Runnable's policy says refunds are not available after cancellation and unused periods are not refunded, so canceling late in the cycle may stop future billing without returning the current month's payment.
If you signed up with one email and wrote support from another, mention both addresses in your message and identify which one is the billing account. If your billing date is near, use both email and live chat on the same day so there is a visible support trail.
If a charge still appears, do not spend weeks arguing informally. Send one concise follow-up to support, then move to your bank, GCash, Maya, or card issuer with the cancellation proof while you are still within the dispute window.
| Method | Notice period | Fee | Difficulty |
|---|---|---|---|
| Web/account | Before next billing | No fee found | Easy |
| Email support | Before next billing | No fee found | Medium, needs proof |
| App Store (iOS) | 5-10 business days | No fee found | Higher, not applicable |
The cleanest path is the one Runnable itself publishes: contact [email protected] and use the Help section if you need follow-up. Store-based methods should not be your main route here because the verified data says they do not apply to Runnable.
Postal mail exists as an extra documentation option, not as the default process. If you need strong timestamped proof, a certified digital letter can be useful, but most users should start with email plus live chat and keep screenshots.
Right after sending the request, save the sent email and take a screenshot of it with the date and time visible. If support confirms cancellation, save that message in a folder and set a reminder for your next expected billing date.
If there is no reply within a reasonable period, open live chat through Runnable Help during support hours, Monday to Friday, 9 AM to 6 PM PST. Ask one direct question: has billing been stopped for your account email.
Watch at least one full statement cycle after cancellation. If you paid by card, GCash, or Maya and a new charge appears, file a dispute quickly and attach your cancellation proof. BSP-related charge disputes commonly need action within 60 days from the statement date.
If the issue is not solved by the payment provider alone, file a consumer complaint with DTI under RA 7394. Continued billing after a documented cancellation request is exactly the kind of fact pattern where your screenshots help.
If you are leaving Runnable because the product is no longer practical or because support-based cancellation feels too manual, several alternatives exist. GitHub Actions works well if your code is already in GitHub, GitLab CI/CD is strong for integrated DevOps pipelines, and Jenkins is still a solid free self-hosted option.
If you want to send a written cancellation notice by post, this is the physical address provided in the brief. Use it only as an additional record, since the official published cancellation method is [email protected].
Mail can be helpful if you are building a dispute file, but for speed, email and live chat are more practical.
Available mailing address:
There is an obvious issue here: this address is identified in the brief as a real estate agency, not clearly as Runnable's own operating office. Because of that, treat postal mail as supplementary proof only and rely mainly on the official support channels published on Runnable's own pages.
If you decide to send a letter, mirror the same content you sent by email. Include your account email, plan, latest charge date, and a clear request to stop billing before the next cycle.
Do not wait for the letter to arrive before contacting support online. For most users in the Philippines, the fastest and most defensible route is email to [email protected], then follow-up through the Help chat, then payment dispute if an unauthorized charge still lands.
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.