Section 01

Introduction

This Refund Policy ("Policy") governs all payment, subscription, and credit matters relating to Angularize.dev, operated by Pythrust Technologies OPC Private Limited ("Company", "we", "us", or "our").

By subscribing to any paid plan or consuming any platform credits on angularize.dev or beta.angularize.dev, you acknowledge and agree to the terms of this Policy. This Policy forms part of, and must be read together with, our Terms of Service and Privacy Policy.

⚠ Core Stance All payments made to Angularize.dev are non-refundable by default, in both monetary and credit terms. The limited exceptions and discretionary credit considerations described in this Policy do not create a right to a refund or credit under any circumstance.
Section 02

General No-Refund Rule

Angularize.dev is a software-as-a-service ("SaaS") platform. Access to the platform, its AI-powered code generation features, and associated computational resources constitutes immediate delivery of a digital service upon subscription or credit purchase. Accordingly:

  • All subscription fees are non-refundable, including monthly and annual plans, regardless of actual usage during the billing period;
  • All credit purchases are non-refundable once credits have been added to your account, whether or not those credits have been consumed;
  • Partial billing periods are non-refundable — if you cancel mid-cycle, you retain access until the period ends but receive no refund for unused days;
  • Unused credits expire as set out in your subscription plan terms and are not redeemable for cash under any circumstance;
  • Downgrades from a higher to a lower plan take effect at the next billing cycle; no pro-rata refund is issued for the difference in the current period.
📌 Why No Refunds? Upon access, the Platform immediately provides value through infrastructure, AI model inference, code generation compute, and platform availability — costs that are incurred by us regardless of the volume of prompts you submit. This policy reflects the nature of digital SaaS delivery under Indian consumer law and the IT Act, 2000.
Section 03

Discretionary Credit Consideration

While monetary refunds are not issued, the Company may, entirely at its own discretion, consider issuing platform credits (not cash) in a narrow set of circumstances. A credit consideration is not a right — it is a goodwill gesture that the Company may extend after a thorough internal review.

3.1 Eligible Scenario — Prompt Submitted, No Meaningful Output

We may consider a credit if all of the following conditions are met:

  • You submitted a well-formed, unambiguous prompt to the Platform and credits were deducted from your account;
  • The Platform returned no output whatsoever — i.e. a complete failure to generate any response, not a response you consider low-quality or incorrect;
  • The failure is attributable to a confirmed technical fault on our infrastructure — such as a server error (HTTP 5xx), a timed-out generation request, or a verified platform outage — and not to third-party AI model behaviour, LLM hallucination, or model uncertainty;
  • You report the issue to us within 7 days of the failed generation with supporting evidence (screenshots, request IDs, timestamps, and the exact prompt submitted);
  • Our internal review of server logs and generation records confirms the failure and attributes it to a platform-side fault.

3.2 What "No Meaningful Change" Does Not Mean

The following are explicitly not grounds for any credit or refund, even if you are dissatisfied with the output:

  • The generated code does not match your expectations, aesthetic preferences, or unstated requirements;
  • The output requires further refinement, iteration, or manual editing;
  • The generated code contains bugs, errors, or security issues (see Section 4 — LLM limitations);
  • The prompt was ambiguous, incomplete, or did not fully describe the desired outcome;
  • You submitted multiple prompts iterating on the same feature and did not achieve the result within a particular number of credits;
  • The output is different from a prior generation for a similar prompt (LLMs are non-deterministic by nature).

3.3 Credit Value & Expiry

Credits issued as a goodwill gesture under this Section are platform credits only — they carry no monetary value, cannot be withdrawn as cash, cannot be transferred to another account, and expire at the end of the billing cycle in which they are issued, or within 30 days of issuance, whichever is sooner.

ℹ Review Timeline Credit consideration requests are reviewed within 14 business days of receipt of all required evidence. We reserve the right to decline any request without providing reasons, and our decision is final.
Section 04

LLM Uncertainty, Hallucination & Non-Determinism

⚠ Important — Please Read The core generation engine of Angularize.dev is powered by large language models (LLMs). LLMs are probabilistic systems with inherent limitations. Credits consumed during any LLM inference call are non-refundable and non-creditable regardless of output quality.

4.1 Nature of LLMs

Large language models, by their fundamental design, exhibit the following characteristics that you must understand and accept before using the Platform:

  • Hallucination: LLMs may generate plausible-sounding but factually incorrect, technically wrong, or entirely fabricated code, function names, library references, or configuration values;
  • Non-determinism: The same prompt submitted twice may produce materially different outputs due to temperature and sampling parameters inherent to LLM inference;
  • Context limitations: LLMs operate within a fixed context window. Large codebases or complex multi-file prompts may result in truncated, incomplete, or inconsistent outputs;
  • Outdated knowledge: The underlying model may have a training cutoff that predates the latest version of Angular, Angular Material, or related dependencies, resulting in deprecated API usage;
  • Inconsistency: Generated code quality and completeness may vary across sessions, even for structurally similar prompts.

4.2 Company Not Liable for LLM Behaviour

Pythrust Technologies OPC Private Limited is not responsible for, and will not issue credits or refunds on account of:

  • Credits consumed during an LLM inference call that returned output the user considers suboptimal, wrong, or incomplete;
  • Credits consumed during repeated prompt iterations required to achieve a desired result;
  • Costs incurred by the user in reviewing, testing, debugging, or correcting AI-generated code;
  • Business losses, project delays, or technical debt attributable to use of generated code;
  • Any outcome arising from the user acting on hallucinated or incorrect LLM output without independent verification.

4.3 Your Obligation to Verify

All generated code must be independently reviewed, tested, and validated by you before deployment to any environment. By consuming credits to generate code, you accept full responsibility for verifying its correctness, security, and suitability. See also Section 8 of our Terms of Service.

📌 Practical Tip To get the best results and avoid unnecessary credit consumption, write specific, detailed prompts that include the framework version, component type, desired behaviour, and any constraints. Vague prompts are more likely to produce outputs requiring multiple iterations.
Section 05

What Credits Cover & How They Are Consumed

Platform credits are consumed based on the computational resources used during a generation request. You should understand how credits are consumed before submitting prompts:

  • Prompt submission: Credits are deducted at the point your prompt is submitted and processing begins — not upon receipt of a completed output. A deduction occurs even if the model returns a partial or low-quality result;
  • Inference compute: Credits reflect the cost of running LLM inference on our GCP infrastructure, which is consumed regardless of output quality;
  • Complex prompts: Prompts requesting multiple components, files, or architectural scaffolding consume more credits proportionally;
  • Re-generation: Each re-generation or follow-up prompt constitutes a new inference call and consumes credits independently.
⚠ Credits Deducted at Submission Credits are deducted when your request enters our processing queue. If you close your browser, lose connectivity, or navigate away before output is displayed, the credits for that inference call are still consumed and are non-refundable.
Section 06

Subscription Cancellation

You may cancel your subscription at any time through your account billing settings. The following terms apply upon cancellation:

  • Your subscription remains active and fully functional until the end of the current billing period;
  • No refund is issued for the remaining days in the billing period;
  • Unused plan-allocated credits expire at the end of the billing period and are forfeited — they are not carried forward and not redeemable for cash;
  • Any separately purchased credit top-ups that have not expired by the end of your billing period are also forfeited upon cancellation — we do not extend their validity;
  • Your account data is retained for 90 days post-cancellation in accordance with our Privacy Policy, after which it is deleted.

If you choose to re-subscribe after cancellation, you do so on the pricing and plan terms in effect at the time of re-subscription. Prior plan rates or promotional pricing are not guaranteed.

Section 07

Genuine Billing Errors

The Company will investigate and rectify genuine, demonstrable billing errors. These are the only circumstances in which a monetary refund may be considered:

  • Duplicate charge: You were charged more than once for the same subscription period or credit purchase within the same billing cycle due to a verified payment processor or platform error;
  • Incorrect amount charged: You were charged an amount materially different from the stated price displayed at the time of purchase, with no prior notice of a price change;
  • Charge after confirmed cancellation: You were charged for a renewal period after a cancellation that was confirmed in writing by us before the renewal date.

To report a billing error, email angularize.dev@gmail.com within 14 days of the erroneous charge with your transaction ID, the charged amount, and the correct amount you expected. We will investigate and respond within 10 business days. Approved monetary refunds for billing errors are processed to the original payment method within 14 business days of approval.

📌 Note Dissatisfaction with the Platform, low usage, or a change of mind are not billing errors and are not grounds for a monetary refund.
Section 08

Situations That Do Not Qualify

For complete clarity, the following situations do not qualify for any monetary refund or platform credit consideration, regardless of how the request is framed:

  • You purchased a subscription but did not use the Platform during the billing period;
  • You were unaware of or did not read this Refund Policy or the Terms of Service before subscribing;
  • You changed your mind after purchasing;
  • You found an alternative tool or decided not to continue with Angular development;
  • Generated code required debugging, editing, or iteration;
  • The LLM produced hallucinated, incorrect, or suboptimal output (see Section 4);
  • A specific Angular pattern, version, or library was not supported by the LLM at the time;
  • You consumed credits on the beta platform at beta.angularize.dev (see Section 12);
  • Your account was suspended or terminated due to a breach of our Terms of Service;
  • You experienced slow generation times or temporary degraded performance that did not constitute a full outage;
  • A promotional or discounted price expired and your subscription renewed at the standard rate;
  • You shared your account with others, resulting in higher-than-expected credit consumption;
  • You did not cancel before the auto-renewal date and the subscription renewed.
Section 09

How to Submit a Request

To submit a credit consideration or billing error report, email us at angularize.dev@gmail.com with the subject line "Refund / Credit Request — [Your Registered Email]". Your request must include:

  • Your registered email address and account username;
  • Date and time of the prompt submission or billing event;
  • The exact prompt you submitted (for credit consideration requests);
  • Screenshots or screen recordings showing the error or absence of output;
  • The request ID or session ID shown in the Platform interface, if available;
  • Transaction ID and amount for billing error reports;
  • A concise description of why you believe a credit or refund is warranted.

Incomplete requests will not be processed. We may request additional evidence before beginning our review. The burden of proof lies with the requestor.

⚠ Time Limit Credit consideration requests must be submitted within 7 days of the relevant generation event. Billing error reports must be submitted within 14 days of the erroneous charge. Requests outside these windows will not be entertained under any circumstances.
Section 10

Review Process & Decision

10.1 Internal Review

Upon receipt of a complete request, our team will:

  • Verify your account identity and subscription status;
  • Cross-reference server logs, generation records, and billing data against your submission;
  • Evaluate the prompt quality and specificity where applicable;
  • Assess whether the failure is attributable to a platform fault or LLM behaviour;
  • Determine, in our sole discretion, whether a credit consideration is warranted.

10.2 Timeline

  • Acknowledgement: Within 2 business days of receiving your complete request;
  • Decision: Within 14 business days of acknowledgement;
  • Credit issuance (if approved): Within 3 business days of decision;
  • Monetary refund (billing errors only, if approved): Within 14 business days of decision.

10.3 Finality of Decision

All decisions made by Pythrust Technologies OPC Private Limited regarding refund and credit requests are final and binding. We are not obliged to provide detailed reasons for our decision. Repeated requests for the same incident will not be re-reviewed.

Section 11

Chargebacks & Payment Disputes

Initiating a chargeback or payment dispute with your bank or card issuer without first contacting us and allowing us to investigate constitutes a breach of these Terms and our Terms of Service.

⚠ Consequences of Chargebacks If you initiate an unjustified chargeback — i.e. a chargeback for a charge that does not constitute a genuine billing error — the following consequences apply:
  • Your account will be immediately suspended pending investigation;
  • We reserve the right to permanently terminate your account;
  • We will submit all relevant evidence (including usage logs, terms acceptance records, and correspondence) to the payment processor and your bank to contest the chargeback;
  • We may pursue the disputed amount through civil proceedings before the competent courts of Gurugram, Haryana, India;
  • You will be liable for any fees, costs, and penalties imposed on us by the payment processor as a result of the chargeback.

If you believe a charge was erroneous, please contact us at angularize.dev@gmail.com first. We are committed to resolving genuine billing errors promptly and fairly.

Section 12

Beta Platform — No Credits or Refunds

⚠ Beta Environment Notice This section applies to beta.angularize.dev.

The beta environment is a pre-release platform provided for testing and evaluation. The following terms apply absolutely and without exception to the beta platform:

  • Any credits consumed on beta.angularize.dev are non-refundable and non-creditable under all circumstances;
  • The beta platform may experience higher rates of generation failure, errors, or unexpected behaviour compared to the production platform — this is expected and does not constitute grounds for any consideration;
  • Features, credit consumption rates, and output quality on the beta platform may differ from production and are subject to change without notice;
  • By using the beta platform, you explicitly accept the increased risk of suboptimal outcomes and waive any claim to credits or refunds arising from beta usage.

If you require production-grade reliability, please use the primary platform at angularize.dev.

Section 13

Governing Law & Disputes

This Policy is governed by and construed in accordance with the laws of the Republic of India. Any dispute arising out of or relating to this Policy or any billing matter shall be subject to the exclusive jurisdiction of the competent courts of Gurugram, Haryana, India.

Before initiating any formal proceedings, both parties agree to attempt resolution in good faith within 30 days of a written Notice of Dispute sent to angularize.dev@gmail.com. For full dispute resolution terms, refer to Section 17 of our Terms of Service.

Section 14

Changes to This Policy

We reserve the right to amend this Refund Policy at any time. For material changes, we will update the effective date above and notify registered users via email or a prominent notice on the Platform. Continued use of the Platform after changes take effect constitutes your acceptance of the revised Policy.

We recommend reviewing this Policy periodically. The current version is always available at angularize.dev/refund-policy.

Section 15

Contact Us

For all refund, credit, and billing queries:

Company Pythrust Technologies OPC Private Limited
Emailangularize.dev@gmail.com
Subject Line Refund / Credit Request — [Your Email]
Address WeWork, 5th Floor, DLF Two Horizon Centre,
Harizan Colony, DLF Phase 5, Sector 43,
Gurugram, Haryana 122002, India