Skip to content
Asuruas
Legal

Subscription Terms

These terms govern paid Asuruas subscriptions, renewals, plan changes, usage limits, payment failures, and cancellation.

Primary topicSubscription Terms

These terms govern paid Asuruas subscriptions, renewals, plan changes, usage limits, payment failures, and cancellation.

Operating outcomeAccountable improvement

Keep website work visible, accountable, repeatable, and connected to business responsibility.

Review statusMaintained resource

Reviewed for accuracy, clarity, and operational use.

01

Plans and orders

Subscription access is defined by the plan and billing interval shown at checkout, together with any signed order. The pricing page states included websites, audited pages, rendered browser pages, users, history, reports, and support.

02

Renewal and payment

Paid subscriptions renew automatically for the selected monthly or annual interval until cancelled. Stripe processes payment details. Applicable taxes and the amount due are shown before purchase. Failed payments may place the workspace in a limited grace state before paid entitlements are removed.

03

Usage limits

Website count, audited pages, rendered pages, users, history, reports, exports, and integrations vary by plan. Asuruas blocks or limits use when an included allowance is exhausted unless a separately disclosed overage arrangement applies.

04

Plan changes

Upgrades may take effect immediately with Stripe-calculated proration. Downgrades normally take effect at the next renewal and may reduce limits, history, or features. Customers should export affected data before the downgrade becomes effective.

05

Cancellation

Customers may cancel through the Stripe billing portal. Cancellation stops the next renewal and paid access generally continues through the current paid period. Cancellation does not itself delete workspace data; deletion is controlled separately under Account → Data and privacy.

06

Operational implementation

  • Assign an owner for implementing and reviewing the obligations described in Subscription Terms.
  • Map the policy to product settings, contracts, support procedures, data flows, records, and staff responsibilities.
  • Keep the public language aligned with actual production behaviour and contracted commitments.
  • Retain approval, effective-date, change-history, and customer-notice records.
07

Review triggers

  • A material product, pricing, data-processing, security, vendor, or support change.
  • A new jurisdiction, customer class, contract requirement, or regulatory obligation.
  • An incident, complaint, audit finding, or operational exception that shows the published process is incomplete.
  • A change that could create assigning work without scope, acceptance criteria, or a rollback path.
Next useful action

Turn subscription terms into an accountable record.

An implementation checklist showing where Subscription Terms is reflected in product behaviour and business procedure.