Subscription Terms

Scope

These terms govern the subscription plans published on Plans & pricing — Essential, Secure Delivery, Platform, and engagements sized under Custom & RFP — together with any recurring add-on modules attached to them. They supplement the Terms of Service and the Refund & Cancellation Policy. Where your signed agreement or statement of work conflicts with this page, that agreement governs.

Subscriptions are sold to businesses and organizations as recurring professional services.

No automatic renewal

This is the single most important term on this page.

• Farqad Cloud does not operate automatically renewing subscriptions.
• We do not retain a payment card on file for subscription plans.
• No charge is taken automatically at any point in the term.
• The agreement ends on its end date unless both parties agree a renewal in writing before then.

You do not need to cancel to avoid a renewal. Silence ends the agreement; it does not extend it.

Term

The default term is 12 months from the start date stated in your agreement, unless your agreement states a different term. Service begins after the agreement is signed and access has been provisioned.

Billing

• Subscriptions are invoiced monthly in arrears unless your agreement states otherwise.
• Invoices are payable within the period stated on the invoice. Unless your agreement states otherwise, that period is fourteen (14) days from issue.
• No payment card is retained for subscription billing, so refunds and credits are settled by credit note or bank transfer as described in the Refund & Cancellation Policy.
• Fees are exclusive of taxes, which are shown on your quotation or invoice where they apply.
• Your own infrastructure costs — cloud usage, domains, third-party tooling licences — are not included and are billed to you by those providers directly.

Units, and changing them mid-term

Subscription tiers are sized by two counted units: cloud accounts and CI/CD pipelines. Each tier includes a stated allowance, published on Plans & pricing. Production workload counts are a scope descriptor agreed in your agreement; they are not separately metered.

• Adding units. Additional cloud accounts and pipelines may be added at any time at the meter rate stated in your agreement. Additions take effect, and are invoiced, from the start of the next billing month.
• Reducing units. Reductions take effect at the next renewal point, or as your agreement states. We staff engagements against the agreed unit count, so reductions are not applied retroactively or mid-term unless your agreement provides for it.
• Exceeding your allowance. If the units actually in scope exceed those in your agreement, we will tell you and agree the adjustment in writing before invoicing it. We do not meter silently.

Suspension for non-payment

Where an invoice remains unpaid after its due date, we may suspend delivery of the affected services after giving you written notice and a reasonable opportunity to pay. Suspension does not relieve either party of obligations accrued before it, and we will restore service promptly once payment is received.

Termination

• For convenience. Either party may terminate on the notice period stated in the agreement. Unless the agreement states otherwise, service continues through the notice period and is invoiced for it.
• For cause. Either party may terminate for material breach that is not remedied within a reasonable cure period after written notice.
• By us. We may terminate or suspend for non-payment, unlawful instructions, or acceptable-use violations, with notice where practicable.

Refund treatment on termination is set out in the Refund & Cancellation Policy.

On termination

• Access, credentials, and integrations provisioned for the engagement are handed back or revoked as agreed.
• Deliverables produced and paid for remain licensed to you under the Terms of Service.
• Reports, evidence packs, and documentation produced during the term remain yours to keep.
• We retain records as described in the Privacy Policy.

Service levels

Response targets and the availability target published on Plans & pricing describe our operating practice. They become contractual service levels, with any associated remedies, only where your agreement expressly says so in writing. No plan carries a certification, audit outcome, or regulatory guarantee.

24/7 cover is for priority-one incidents and is standard on the Platform tier; Essential and Secure Delivery may add it as a module where agreed in writing. Routine requests on every tier follow the standard support hours. The availability target is measured monthly across the systems we operate under your agreement and carries no service credits unless your agreement provides them. See the service levels section of the Terms of Service.

Changes to these terms

We may update these terms for future agreements. Changes do not alter the terms of an agreement already in force; those change only by written agreement between the parties. Previous versions of this page remain available from the policy index.

Contact

Questions about a subscription, an invoice, or a change of units: support@farqadcloud.com. Support hours are listed on the Company Information page.

Change notification

We may update this policy to reflect legal, operational, or service changes. Material changes will be communicated on this page or through another appropriate notice. Where required by law or contract, we will provide additional notice. Where affirmative consent or a contractual amendment is required, continued use alone will not replace that process.

Each version carries its own number and effective date. Previous versions are available on request.