Refund & Cancellation Policy
• Tier A (Unused Key Grace Window): 100% full refund if requested within 2 hours of purchase with 0 repository downloads initiated or completed.
• Tier B (Verifiable Technical Defect): 100% full refund if requested within 2 hours of purchase, with maximum 2 download attempts, 0 successfully completed repository downloads, and an unresolvable engine defect verified through our server diagnostic logs.
1. Dual-Tier 2-Hour Refund Policy Overview
Because GitHub Backup Manager delivers instant digital license activation and downloads high-value digital source code, git bundles, releases, and documentation directly to your machine, statutory right of withdrawal applies until digital fulfillment begins. Once license fulfillment occurs, eligibility for refund is governed by our objective, verifiable 2-hour criteria below.
2. Eligible Refund Criteria
A full 100% refund will be granted under either of the following two verified scenarios:
- Tier A — Unused Key / Accidental Purchase Grace Period: If you purchased a license by mistake or changed your mind, and have contacted us within 2 hours of purchase with zero (0) repository downloads initiated, attempted, or completed on the usage pass key.
- Tier B — Verifiable Technical Engine Defect: If you attempted to archive repositories on a supported Windows 10/11 x64 environment with the Local Companion, and the engine encountered a fatal execution defect preventing archival, provided that:
- Your refund request is submitted within 2 hours of the purchase timestamp.
- Your license has zero (0) successfully completed repository downloads (no repository was fully archived or extracted).
- Your license has no more than two (2) total download attempts.
- The engine failure is verified in our administrative telemetry log and our technical support is unable to provide a resolution.
3. Automated Telemetry & Administrative Verification
You do not need to assemble complex log dumps or diagnostic code. When you request a refund, our administrative system automatically verifies your key against our cryptographic telemetry database, which records:
- Exact license purchase timestamp and elapsed time.
- Number of repository downloads initiated, in-progress, completed, failed, or cancelled.
- Selected archival presets and download scope settings (Options 1, 2, or 3).
- Local engine diagnostic status, error codes, and failure traces.
This automated verification ensures immediate, transparent dispute resolution without subjective disagreements.
4. Non-Refundable Circumstances
Refunds cannot be issued under the following conditions:
- Completed Archival (Digital Value Delivered): Any usage pass key that has one (1) or more successfully completed repository downloads. Once complete source code, release assets, or wikis are archived to your local computer, the digital product has been consumed and performance is completed.
- Exceeded Attempt Threshold: Any usage pass key with more than two (2) download attempts.
- Exceeded Time Limit: Refund requests submitted more than 2 hours after the purchase timestamp.
- User-Side or External Factors: Archival failures caused by user configuration rather than engine defects, including:
- Supplying an invalid, expired, or rate-limited personal GitHub access token.
- Targeting a non-existent, mistyped, or private repository for which your GitHub account lacks read permissions.
- Terminating the Local Companion, closing the terminal, or disconnecting network access mid-stream.
- Lack of disk space on your local computer.
- Change of Mind After Usage: Change of mind after repository archival has been initiated or completed.
5. How to Submit a Refund Request (3 Simple Steps)
Refund Request - [Your Order ID].
RH-...), purchase email address, and the Dodo Payments Order ID or Receipt Number.
6. Refund Processing & Turnaround Time
- Review: All refund requests are reviewed and acknowledged within 24 business hours.
- Execution: Once approved, your refund is immediately initiated through Dodo Payments, our Merchant of Record.
- Settlement to Your Account: Depending on your payment method and financial institution, the refunded amount will credit back to your original source (Credit/Debit Card, UPI, Apple Pay, Google Pay) within 5 to 7 business days.
- License Invalidation: Upon refund approval, the associated usage pass key is automatically revoked and deactivated.
7. Cancellation Policy (Prepaid Non-Recurring Terms)
GitHub Backup Manager usage passes (24-Hour Pass, 48-Hour Sprint, 28-Day Pro, and Annual Access Pass) are sold strictly as prepaid, non-recurring fixed-term access. There are zero automatic renewals, zero hidden fees, and zero recurring billing cycles. You will never be charged automatically upon term expiration.
8. Chargebacks & Friendly Dispute Resolution
If you have any questions or encounter a technical hurdle, please contact us directly at appsbymmahingu@gmail.com before filing a payment dispute or chargeback with your bank. We process verified requests promptly and reaching out to us directly ensures the quickest resolution without unnecessary payment processor hold times.
9. Contact Support
For any refund requests or billing questions, please contact:
Mehtab Singh Mahingu
Email: appsbymmahingu@gmail.com
Website: https://mmahingu.com
Customer Support SLA: Response within 24 business hours.