Cloud Subscription Information

A complete customer subscription record should contain:

• Customer legal name and the FeatBit contracting entity;
• workspace or account identifier;
• plan name, selected MAU allowance, and purchased add-ons;
• subscription start date, current period end, and renewal cadence;
• fees, currency, taxes, payment method or invoice terms;
• support entitlement and any negotiated service levels; and
• links to the Cloud Services Agreement, DPA, and other incorporated documents.

For a self-service purchase, the billing page and Stripe-generated invoice are the primary commercial records. For a negotiated purchase, the signed or accepted Order Form controls the customer-specific scope. Contact contact@featbit.co if procurement needs a countersigned subscription summary.

Customers may select a higher MAU allowance or add eligible features. Current public prices and feature details are on the FeatBit pricing page. An Order may contain custom enterprise scope and pricing.

A Monthly Active User (MAU) is a distinct user key observed through connected FeatBit SDKs during a billing period. The same user key used across multiple projects, environments, or devices in the same workspace is intended to count once for that period. Different user keys count separately, even if they represent the same person.

• Use stable, opaque user keys to avoid duplicate counts and unnecessary personal data.
• Machine, service, or device identities may count when they are submitted as distinct user keys.
• Changing or rotating a key can cause the old and new keys to count separately in the same period.
• Customer can review current plan and reported usage in the Cloud billing interface.

Paid self-service subscriptions are billed in advance for the selected plan and fixed add-ons. Usage above the selected MAU allowance is metered and billed at the overage rate displayed during checkout, on the pricing page, or in the Order. Taxes are added where required.

A temporary overage does not normally interrupt flag evaluation. Continued service during an overage does not make the additional usage free. Stripe processes card details and generates self-service invoices; FeatBit does not receive complete payment-card numbers.

Enterprise customers may instead receive invoices under the payment terms in their Order. Billing questions or disputes should be submitted within 30 days after the invoice date.

• Paid subscriptions renew automatically for the selected monthly or yearly period unless cancelled.
• Upgrades take effect immediately after confirmation and may create a prorated charge or credit.
• Paid-plan downgrades take effect at the end of the current billing period.
• Cancellation to the Free plan takes effect at the end of the paid billing period.
• No further recurring fee is charged after an effective cancellation, except accrued usage and taxes.
• Fees already paid are not refunded for partial periods unless required by law or an Order says otherwise.

Customers should export required information and review feature availability before a downgrade. Features outside the new plan may stop operating when the change takes effect.

Support channels and response targets are plan-dependent and are described on the pricing page or in the Order. Community support is available for the Free plan; paid plans may include priority email or ticket support; Enterprise may include shared Microsoft Teams or Slack channels and a reply target.

A reply target is not a resolution guarantee or uptime commitment. FeatBit Cloud has no public contractual uptime SLA or service-credit schedule unless a signed Order or service-level agreement expressly includes one.

The Cloud Services Agreement governs the service. A customer-specific Order controls plan scope and commercial terms. The DPA controls personal-data processing. If an invoice contains less detail than an accepted Order, the Order remains the subscription-level record and the invoice remains the payment record.