Refund and Cancellation Policy

At R Cube Dev, we dedicate significant time, technical resources, and engineering capacity from the moment an agreement is signed. Because custom software engineering, digital consulting, and web infrastructure work require upfront planning and labor allocation, we enforce a transparent and balanced Refund Policy.

By hiring R Cube Dev, paying an invoice, or submitting a security deposit, you acknowledge and accept the terms detailed below.

1. General Policy on Advances and Security Deposits

• Non-Refundable Upfront Payments: Initial deposits, setup fees, and advance payments are strictly non-refundable. These funds secure reserved calendar bandwidth, immediate project setup, architectural planning, and baseline resource deployment.
• Commitment to Scope: Once project work commences, funds paid toward completed milestones, discovery phases, or onboarding are consumed by billable human labor and are non-recoverable.

2. Refund Eligibility: Commitments and Wrongful Delivery

We stand behind our technical execution. While general dissatisfaction with subjective aesthetic choices or changes of mind do not warrant a refund, a refund or credit may be approved under the following strict conditions:

A. Failure to Fulfill Contractual Commitments

If R Cube Dev fails to initiate or complete an agreed project due to internal reasons within our direct control, and we are unable to remedy the failure within an agreed written cure period (typically 14 to 30 calendar days), you may be eligible for a refund of unworked/unfulfilled milestones.

B. Wrongful Delivery of Service or Product

A refund may be issued if the delivered software or technical service demonstrably fails to conform to the approved functional specifications, architecture document, or written Statement of Work (SOW), and:

1. The discrepancy is reported in writing to [email protected] within the defined Acceptance Testing Window (7 to 14 days post-delivery).
2. The failure is verified to stem from our development execution rather than external factors (such as third-party API changes, client server issues, or unapproved third-party code tampering).
3. R Cube Dev is given reasonable opportunity to remediate or correct the non-conforming deliverable but fails to achieve compliance with the agreed specifications.

In such verified cases, R Cube Dev will issue either a partial or full refund for the specific defective milestone, determined fairly by the extent of the unrectified deliverables.

3. Billing Models and Specific Conditions

A. Fixed-Price Milestone Projects

• Each milestone corresponds to a tangible deliverable (e.g., UI/UX approval, core logic build, beta release, final deployment).
• Once you review and approve a milestone or pay the corresponding release invoice, that milestone is considered formally accepted. Payments for approved milestones cannot be retroactively refunded.
• If a project is cancelled midway by the client, no refunds will be issued for completed or in-progress milestones. Any unbilled, uncommenced subsequent milestones will not be charged.

B. Hourly Billing and Monthly Retainers

• Invoices for hourly engagements reflect actual engineering and technical support hours already dedicated to your task or repository.
• Payments for logged and billed hourly work are non-refundable.
• Clients on hourly retainers may pause or cancel future work at any time by providing written notice, stopping further billing for subsequent weeks or billing cycles.

C. GMB and Google Review Services

• Fees paid for Google Business Profile optimization and review management consulting cover professional labor, workflow setup, and marketing consultation.
• Because local search rankings and search engine visibility are dictated solely by third-party search engine algorithms, fluctuations in rankings or platform-side review filtering do not qualify for refunds.

4. Circumstances Not Eligible for Refunds

Refund requests will be denied under any of the following circumstances:

• Change of Mind / Budgetary Shifts: The client decides to cancel, pivot, or postpone the project due to internal business changes, market shifts, or internal financial constraints.
• Client Delays & Lack of Communication: Projects placed on prolonged hold due to non-responsiveness, missing credentials, missing copy/assets, or lack of required approvals from the client's end.
• Third-Party Faults: Delays or outages caused by external hosting providers, domain registrars, payment processors (e.g., Stripe), or external API outages (e.g., Google, OpenAI, AWS).
• Unauthorized Modifications: Codebases or configurations modified, refactored, or deployed by the client or third-party developers without our prior written consent.
• Out-of-Scope Demands: Feature requests or adjustments that exceed the mutually agreed written scope or design parameters.

5. Refund Request Process

If you believe you qualify for a refund under Section 2 (Failure of Commitments or Wrongful Delivery), you must submit a formal written request:

1. Submit Notice: Send an email to [email protected] with the subject line: "Refund Request - [Your Project Name / Invoice Number]".
2. Include Evidence: Provide detailed documentation outlining the unfulfilled commitments, functional defects, or specifications that were allegedly not met, citing the original Statement of Work or agreement.
3. Internal Review: Our management and technical leads will review the request, inspect the repository/deliverables, and issue an official response within five (5) to seven (7) business days.
4. Processing: If approved, refunds will be returned via the original method of payment (or via standard bank transfer/wire) within ten (10) to fourteen (14) business days. Any intermediary payment processing fees, wire fees, or currency conversion losses incurred during transfers are non-refundable.

6. Policy Adjustments

R Cube Dev reserves the right to modify or amend this Refund Policy at any time. Updates will be reflected directly on this page with an updated lastUpdated date.

7. Contact Us

For questions, payment verifications, or dispute resolutions regarding this policy, please reach out to:

R Cube Dev
Kolkata, West Bengal, India
Email: [email protected]