BAAM

Subscription and Billing Policy

Draft only. Requires legal review before publication. This software provides compliance tooling, but does not provide legal advice.

Subscription and Billing Policy

Purpose

Explain subscription lifecycle, payment processing, invoices, taxes, renewal, cancellation, and plan changes.

Source model

This slot follows mature SaaS and security-software legal-center patterns: Zapier-style customer terms, DPA, subprocessors, security, and data-transfer material; Avast-style license, acceptable-use, privacy, IP, transparency, and accessibility material.

Jurisdiction focus

Prepare this for EU users and Czech-market operation. Complete operator details, Czech consumer wording, cookie consent behavior, GDPR roles, and cross-border transfer safeguards before publication.

Plans and fees

List plan names, billing intervals, included features, usage limits, currency, taxes, and any launch pricing. Public pricing must match Stripe configuration.

Payment processor

Payments are processed by the configured payment provider, currently expected to be Stripe. State whether payment-card data is handled by the processor, not BAAM AI.

Renewal

Explain automatic renewal, renewal date, failed payment handling, grace periods, and account suspension.

Taxes and invoices

State VAT/tax handling, invoice availability, and what customer billing details are required.

Plan changes

Explain upgrades, downgrades, prorations, feature changes, and effect on active campaigns or stored data.

Cancellation

Explain how to cancel and whether access continues through the current term.

Completion checklist